Spint working with LOS customers - Samsung Epic 4G Touch

I called Sprint today to see what they will do for me since I have LOS. After being on the phone for 1/2 hour. They are shipping me a brand new ET4G. Just wanted to let everyone know so they can try it. I hope my new one will not have LOS.
Also for those how are rooted here is the link to the How to unroot thread if they are sending a new phone.
http://forum.xda-developers.com/showthread.php?t=1281287

Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.

leyvatron said:
Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.
Click to expand...
Click to collapse
I am on my 3rd phone including the 1 sprint is sending. My first one did not have LOS, but was overheating. From what I am seeing not all phones have LOS.
I have gotten days with no LOS then other days with 10+. It is not fun.

The only thing I get is that my battery is garbage. I dont think it overheats, I do have the Android OS bug that drains my battery.
LOS is not common on my end. Glad I don't get LOS 10+ times, I would be mad.

I had my original one returned form Sprint after the 14 day warranty. I spoke to advanced support and talked circles around him on the problems Im having so they send a new one. Now this new on isnt so much loosing Wifi and 3G like the other one, but it is making me reset it a couple times a day. My original one couldnt keep a signal for more than 5 seconds. IDK if Im gonna return this one or not, I just want a phone that works!!!!

leyvatron said:
Do all phones get LOS? or just certain phones?
I get it but once a day or twice. Never had more than 5 a day.
Click to expand...
Click to collapse
I got my myself, wife and son this phone on October 1. By the next Monday I had returned my phone due to LOS and on that Tuesday my son returned his. My wife has yet to experience LOS.
My son and I both rooted our phones. I have read posts that people who NEVER have rooted their phone have had this issue.

I have not rooted the phone and am running completely stock everything. I have major LOS issues. It seems they start mainly when the handoff from wifi to 3g/4g when leaving home or work and no longer being on the wifi network. I dont have too many issues if I keep wifi off all the time and just rely on the cell network for data.

I am working with someone in Dan Hessy's office and she has advised me there is nothing sprint can do without me taking this into a service center first.

LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!

akarol said:
LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!
Click to expand...
Click to collapse
Then fix the stock KERNEL.
Well lets see here. I paid for a phone and I pay for service. So I expect to be able to use my invesment the way it was intended. Losing my signal 5-10 times a day and having to constently reebot. Not a lot of fun in my book. And maybe unlike some people I can not constently watch my phone to check for LOS. In other words I may have LOS for hours before I even notice it.
I am not one to complain unless it is a legit issue.

akarol said:
LOLOL! You guys are all delusional. LOS is completely kernel dependent. It is not a hardware issue. There are way too many variables that could influence reception. It's people like you that raise our TEP costs. Thanks!
Click to expand...
Click to collapse
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
I agree 100%. Thank you.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
Well considering my first phone was an overheated disaster (no root complete stock). The one I am on now had LOS prior to root. So I rooted to hope for a fix. Also read the LOS forums and a lot of un-rooted users getting LOS.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
Not true, it affected mine, and I never rooted.

manekineko said:
Uhh he means it is kernel dependent as in custom XDA kernel dependent.
This problem almost never affects the stock kernel.
Click to expand...
Click to collapse
If that was true, I would be a happy customer. I am not rooted, completely stock, and I get LOS.

dmora01 said:
Sorry but if a pay $500 is bc I need a phone that works, with no this type of problems and I don't care if is hardware or is the kernel, I just need something that works and sprint and samsung are responsible and they need to fix it and we are not supposed to pay for their mistakes.
Click to expand...
Click to collapse
I 100% agree
the LOS is pretty bad on mine, stock or other kernel, its less on stock though
the only saving grace is that I have quick boot on my home page, and this phone reboots the fastest ive ever seen, on any of my smart phones in the past
I just get concerned sometimes, since I have kids that I may miss messages or something
its still a killer phone though,

As much as I hate to say that replacing the phone isn't likely to fix the problem, I do encourage it so Sprint will push Samsung to fix this issue quicker. The more phone replacements, the more sprint spends money on replacing. Also, if it ends up costing more than simply fixing the problem in the first place, they'll be forced to fix it.

Amd4life said:
I 100% agree
the LOS is pretty bad on mine, stock or other kernel, its less on stock though
the only saving grace is that I have quick boot on my home page, and this phone reboots the fastest ive ever seen, on any of my smart phones in the past
I just get concerned sometimes, since I have kids that I may miss messages or something
its still a killer phone though,
Click to expand...
Click to collapse
Stock is not a phone that was rooted then loaded a stock kernel. Stock is an untouched device that has never been rooted in the first place. Based on my personal experience, true LOS with the zero and line do not happen on an out of the box untouched phone.
My untouched phone had no LOS for 4 days until it was rooted. Next 2 days had an LOS each day. Got a replacement phone last Friday. Kept it stock and haven't seen an LOS yet. That would be 6 days without an LOS.
I am convinced it is only happening on rooted or once rooted phones. If I get an LOS I won't be afraid to report it here but I am pretty confident I won't see it. I have used my phone in the exact locations and same instances so far and still no LOS.

I agree. I'm totally stock and I've had the LOS problem mind that it was 3 times now 3rd time being today as I was walking back into the APT and the call just dropped as I looked at my phone there was ZERO signal when I had full bars just seconds before that. So far it's not been as bad as others are having so I've not really looked into getting the phone replaced yet but it's something that I do keep my eyes on to see if/when I'm getting it and how often it might show up.
---------- Post added at 02:17 PM ---------- Previous post was at 02:14 PM ----------
[email protected] said:
Stock is not a phone that was rooted then loaded a stock kernel. Stock is an untouched device that has never been rooted in the first place. Based on my personal experience, true LOS with the zero and line do not happen on an out of the box untouched phone.
My untouched phone had no LOS for 4 days until it was rooted. Next 2 days had an LOS each day. Got a replacement phone last Friday. Kept it stock and haven't seen an LOS yet. That would be 6 days without an LOS.
I am convinced it is only happening on rooted or once rooted phones. If I get an LOS I won't be afraid to report it here but I am pretty confident I won't see it. I have used my phone in the exact locations and same instances so far and still no LOS.
Click to expand...
Click to collapse
I have a totally stock phone it's never been rooted since the day I got it almost 2 weeks ago and I have had LOS on it. I honestly do not think this is a rooted phone issue if that was the case I would never of had it at any point in time and I have. And like I said Stock never once rooted and have not thought about doing it yet.

Related

Rooted Kernels and Loss of Service

We're trying to determine the "root" (pun intended) of the problem so if you wanna come in here and start a fight go find a local bar to do so. We need to try and locate the source of the problem so either post something useful or walk away.
There seems to be some confusion and I dont know if its being ignored or what but theres an issue with these kernels that needs to be looked into further before new ones continue to be released.
Theres an obvious problem for a good amount of people and everytime I look I see comments that there isnt a problem. So heres everything I could quickly find regarding it.
Now Im not trying to be a **** about this but I dont get how the issue is unheard of when its one of the biggest topics in this section. And so we're clear, this is happening in ALL kernels. Unfortunately its been more profound in Zedos because it seems more people went with his method.
All Im asking is before more and more kernels are released that someone at least acknowledge the problem and see if it can be addressed before more and more people root and start complaining because they were told there was no LO.S. bug
zedomax said:
data drop? dunno about that, this shizzle will not drop. It's ZEDOMAX!
Click to expand...
Click to collapse
zedomax said:
jump and we will find out. no they should be worked out. there was no data loss kinks in da first place, where did u get that?
Click to expand...
Click to collapse
________________________________________________________________________________________________________
joetemp75 said:
Man I was fine then I flashed v5 and got the no signal issue
Click to expand...
Click to collapse
SupahDave said:
Everything seemed to be fine last night but today I've had 4 separate times now where my phone has lost signal all together and needed to be rebooted to get phone/data back. When this has happened I tried going into About-->Status to see if I could see anything odd and I kept getting a FC of com.android.phone
Click to expand...
Click to collapse
jimbobtexas said:
I did. No love. I'm without a signal, period.
Click to expand...
Click to collapse
MILH0U5E said:
Got the no signal issue here too. I put it in airplane mode overnight and upon waking this morning the no signal circle was there. I had to do a reboot to get 3g and cell signal back.
Looking forward to seeing this process develop.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
wbyrd said:
Yeah this just happened to me too, everything was fine this morning then I played a game of solitaire and after going back to my home screen I saw the circle. Rebooted phone and everything came back on. It's possible that the circle was there before I played the game of solitaire but I didn't notice until right after I quit playing.
Hopefully it gets straightened out soon. At least rebooting fixes the problem, I can handle rebooting for a little while if needed.
Click to expand...
Click to collapse
plmiller0905 said:
I can't really deal with the issue of having no service. My daughter has a heart issue and can't afford to miss a call. It's not like I walk around all day literally looking at my phone's screen seeing if I have service or not.
I did reboot...so like your's my service is back up.
But I definitely hope this gets fixed soon. I'd rather have root with broken heptic feedback than the inability to receive calls.
But I'm sure the Op the get it fixed...
Click to expand...
Click to collapse
volwrath said:
I've had a dead call issue and also tday my radios were just dead and there was a circle in the middle of the notification barr. A reboot fixed the issues each time, but I think it might be a problem. I thing newer kernels will also fix said issues. Still very satisfied
Click to expand...
Click to collapse
JLine05 said:
I am having the issue of the phone (voice) and sms not working. Strange because everything else is working fine. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
mcflargen said:
Still seems to have the data drop issue. Popped it on the second u dropped it, was great till a min ago. least a "restart" fixes it.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
joetemp75 said:
Man I just lost data again. This sucks
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
kindaskimpy said:
I'm giving this one a try because with the zedomax kernel I kept losing 3G and CDMA calling and not even noticing it unless someone told me they'd been trying to reach me for hours. A quick reboot would solve the issue but then it would happen again.
I'll report back and let you guys know if this one is giving me the same issue.
Click to expand...
Click to collapse
bbedward said:
I did this one because losing service on the other one, haven't lost it yet but its only been a couple hours
Sent from my sprint galaxy s2
Click to expand...
Click to collapse
fordmanck said:
I tried both, i'm back on this one. I lost service with zedos twice and haven't on this at all.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
Telling you right now someone is going to come in here and go "this belongs in General" then a mod will move your thread and deduct 5 points from something, not sure...but just a heads up
I also see a lot of people having issues, but I'm now on day 2 of flashing Zedo V1 and have yet to experience any of these issues. Not sure what I did different, but everything just works... The only thing I did was after rooting was getting my MSL from Sprint and erased the proxy servers in the ##3282 menu.
EDIT: Ok, I just lost service 1 1/2 day after rooting... Bug finally hit me..
I dont mind it being moved and I have no clue what the deduction in "points" does but I'll deal with it.
Now Im getting much better battery but I know people are still losing service on the new OC kernel. My roommate happens to be on e the unlucky ones.
Man...thanks for posting this. Hopefully the mod doesn't close this thread. This definitely is a concern and a serious matter. I don't care if these kernels are, "use at your own risk" these kernels should've been listed as betas, and/or the bugs should've been listed and further testing should have been. If those steps were taken, I bet a lot of people would've held back from flashing them. I know I would have.
Shabby posted this earlier in the other thread (post 160):
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
One thing that got to me was this morning I woke up, hoping to see a stock kernel and/or a way to return to stock. And instead, I see a new overclockable kernel. To me that's just not right. I think that you have to prioritize. That's like putting out a rom that has all data broke. Then instead of fixing it, you put out another rom...while disregarding the issues with the first rom. At least acknowledge the issue and let everyone know it's been worked on....don't just blow it off.
I know some of the devs over in the Evo forums was good about this....if something went haywire with one of their roms or mods...they were all on top of it to get the issue fixed and they also communicated with posting updates on the matter.
Like I said, hopefully the mods don't close this.
I'm definately gonna follow this thread...thanks Wingzfan
i rooted yesterday using zedomax method, did the OC kernel last night.. havent had any issues so far ..
plmiller0905 said:
Shabby posted this earlier in the other thread:
http://forum.xda-developers.com/showthread.php?t=1267762&page=16
post 160
I'm definately gonna follow this thread...thanks Wingzfan
Click to expand...
Click to collapse
Bubby does have the stock kernel pulled. I was testing it till 1:30 in the morning but he's gotta recompile it. It was bootlooping so today thats his first order of business.
As for the kernels, I flashed it by choice. I dont blame the devs for ANYTHING, Im just saying acknowledge theres a bug and lets see how to resolve it.
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
OrygunGal said:
I've been reading through the rooted kernel threads as well prior to jumping on the root wagon and have seen several people mention that they are not rooted and have experienced the loss of service so it seems that the issue may not be exclusive to the rooted kernels...possibly a Samsung bug?
Click to expand...
Click to collapse
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
wingzfan said:
Stocks on its way i promise. Probly tonight actually. Bubby was really close last night. Once we get that Id be curious to see what happens.
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
Sounds good...can't wait
Sent from my SPH-D710 using Tapatalk
This is an issue that started with mine also yesterday. But not only did I lose data but gps also. A reboot fixed it but I would like to know whats going on. I just came from the evo 3d and there was an issue that had to do with the prl so I am going to give that a shot with the 11115 prl that fixed the evo. Will post back with the results later today.
On V5, Ive only had the loss of data once in about 12 hours, versus about 3 times on Zedo V1.
I also did http://forum.xda-developers.com/showpost.php?p=17703908&postcount=11 for the hell of it to see if that helped (even though I got it at a sprint store)
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
wingzfan said:
Very possible which is why im hoping we can get an idea of how man people are rooted vs non rooted having it. Now the only thing is I cant find any complaints online about nonrooted phones doing it except a few here and youd think it'd be widely discussed
Sent from a Galaxy far far away...
Click to expand...
Click to collapse
I would think it would be widely discussed as well so that seems odd. I'm waiting to see what evolves or at least for stock kernel (an undo) before flashing a rooted one. I don't have TEP.
It's still a bit early for the issue to be too widely discussed.
dmarden said:
For the record:
A) People have reported this issue even on the stock kernel. It is not clear where the cause is.
B) For kicks (and because it cannot hurt) I did the whole profile/PRL update thing that someone suggested. Be it luck or real benefit, I have no had the issue since.
Click to expand...
Click to collapse
Nice. I was told by a helpful Sprint cust. serv. rep. a while back that you should update your PRL & Profile when you go into a new area (tavel, move, or even long commute to work) regardless of which phone you have. I would think unboxing your phone would qualify as well. It sure couldn't hurt.
---------- Post added at 06:59 AM ---------- Previous post was at 06:53 AM ----------
dmarden said:
It's still a bit early for the issue to be too widely discussed.
Click to expand...
Click to collapse
Good point. Many people would not likely research on the web/forums, instead they'd likely address the issue directly with Sprint.
plmiller0905 said:
Yeah...I read those too. However, I never lost any service at home with any android phone I've owned..Nexus S 4g, all Evo's, Epics etc. Then today I wake up and I have no service....maybe it is a samsung bug, but I'd rather return to stock myself to see if the issue was still there.
Click to expand...
Click to collapse
Ever owned a Samsung phone before?
This is my 3rd one and I swore after the last one Id never buy a Samsung phone again but I got sucked back in. Samsung is notorious for shipping phones with all kinds of bugs that should be considered showstoppers then pushing out fixes months later.
It would not surprise me at all if that was the case here. I am one of the ones having this issue and I am not rooted. Ive lost data several times after hanging up a call. The data never restores and I have to toggle 3G to get it come back.
I dont think this is a kernel issue. I think its something to do with the rest of the OS, either that or the kernel is a different problem thats just acting the same way.
Ok thats what i was hoping to find is nonrooted and rooted people who are having the issue. Now on my moment this issue was huge so i went to htc and maybe thats the case again. Maybe sammy dropped the ball again. Question is what can be done about it.
Sent from a Galaxy far far away...

[INFO] Information Regarding MR OTA for LOS issue (Updated 10/27/11)

After hours on the phone with Sprint and being transferred to multiple departments, I received a call back today explaining the following:
Samsung has delivered the MR with the LOS update for Sprint. SPRINT WILL NOT BE PUSHING THIS MR OUT UNTIL MID TO LATE DECEMBER POSSIBLY JANUARY.
Please keep in mind this information did not come from a customer service rep or a sprint store rep.
Sent from my LOS 4G Touch
********************UPDATE*********************
*******************10/27/2011*******************
Just wanted to post an update...
Since the original post I have exchanged my E4GT for a new one... I have had the new phone for several days now and although I have not had any LOS issues (specifically circle with line through it) I have lost several calls (Message with "Call Lost)
Spoke to the escalation managers boss and this is what I was told...
-The MR is still in testing at Sprint and the absolute earliest release date will be in December.
- The update will address LOS issue, maintaining wifi connections, and something about refreshing 3g/4g after losing signal (my phone was breaking up and missed some words here and there)
- They are also aware of some minor bugs ie phone dialing wrong people in certain cases and some resource leaks???? (not sure what he was talking about gain) assuming it has to do with battery drain... but there is no guaranteed that the issues will be addressed in the MR and that it may be addressed in the next version of the OS (I'm assuming ICS)
He went on to explain that the service in my area (Southern California) will get worse before it gets better. He said old towers are being replaced with new multi-band towers in the area which means at any given time we will have less towers in service till the upgrades are completed.
Now take everything with a grain of salt... I know that this is not concrete information but the guy is one out of a million at sprint who seems to actually know what he is talking about.
It's time for either EVERYBODY PANIC or SPECULATE WILDLY.
I'll start with the wild speculation:
It's because that's the ICS update and they can't roll that out before the the Galaxy Nexus release due to some sort of exclusivity agreement with Google and Verizon (and maybe Sprint)...
SOMEONE LEAK SOMETHING ALREADY PLEASE FOR THE LOVE OF GOD LEAK SOMETHING.
Okay, NOW EVERYBODY PANIC
daneurysm said:
Okay, NOW EVERYBODY PANIC
Click to expand...
Click to collapse
lol
10 char
Wonder what it'll break on phones like mine that never had any issues to begin with lol.
Sent from my SPH-D710 using xda premium
daneurysm,
Actually in passing the person who contacted me explained that although SGSII will receive ICS it will not be till May or June and that the MR will be separate from ICS
poppygt said:
Wonder what it'll break on phones like mine that never had any issues to begin with lol.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Ive been thinking the same thing the last couple weeks lol
Im going to take pass on it for a couple week after release
neverends said:
daneurysm,
Actually in passing the person who contacted me explained that although SGSII will receive ICS it will not be till May or June and that the MR will be separate from ICS
Click to expand...
Click to collapse
To be honest that seems like a reasonable time frame. For me? No...but from a major carrier, yes. I mean reasonable as in "reasonable to expect." I, personally, find it downright insulting since working (if alpha/beta) builds of it almost certainly exist.
All snarkyness aside, thanks for the heads up.
Sounds like the author is making this stuff up.
Did you forget to mention the important information about ICS release in the OP, OP?
I call BS.
Who cares? We have XDA for stuff like this.
nabbed said:
Sounds like the author is making this stuff up.
Did you forget to mention the important information about ICS release in the OP, OP?
I call BS.
Click to expand...
Click to collapse
My call was not to Sprint to get ICS it was a call to get out of my contract in regards to LOS. The person that responded to me gave me solid information about the LOS MR. He had information about the MR and the rest was speculative. I posted the facts and omitted the speculation in my OP.
Call BS if you like... When you have to wait till the end of the year to get an LOS fix from Sprint just remember you were warned.
_MetalHead_ said:
Who cares? We have XDA for stuff like this.
Click to expand...
Click to collapse
That is what I hope for as well... However we don't have the actual E4GT Kernel yet. Thus far I had 0 LOS prior to root - about 50 instances of LOS after root - and only 5 LOS after restoring to stock thanks to ACS
neverends said:
That is what I hope for as well... However we don't have the actual E4GT Kernel yet. Thus far I had 0 LOS prior to root - about 50 instances of LOS after root - and only 5 LOS after restoring to stock thanks to ACS
Click to expand...
Click to collapse
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
neverends said:
He had information about the MR and the rest was speculative. I posted the facts and omitted the speculation in my OP.
Click to expand...
Click to collapse
I don't see any facts here... its all speculation.
lafester said:
I don't see any facts here... its all speculation.
Click to expand...
Click to collapse
Fair enough. Though the time frame seems reasonable in carrier-logic.
Either way I think it's safe to say that it's enough so that EVERYBODY PANIC.
nabbed said:
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
Click to expand...
Click to collapse
I rooted with the Zedomax pre-rooted kernel and went back to stock by using stock rooted kernel, factory reset, and odined this http://forum.xda-developers.com/showthread.php?t=1273647
then factory reset again and I updated profile after resetting...
lafester said:
I don't see any facts here... its all speculation.
Click to expand...
Click to collapse
that's fine - the information was received from people directly responsible for releasing sprints MR's. Also I contacted Samsung prior to calling sprint and was told that the issue was resolved and the fix was "in the pipeline"
nabbed said:
You should have 0 los after restoring to stock.
If I'm not mistaken, there's not been a single case reported where a person didn't have los, then rooted, restored back to stock-pulled, and had los again.
Did you use stock-pulled kernel or the so called "stock" (which it isn't)?
Did you update profile after restoring?
Click to expand...
Click to collapse
I have not rooted my phone and I get LOS pretty frequently. Factory resets and whatnot do not fix the issue. There is a real issue here, and they're being very quiet and slow about fixing it.
neverends said:
I rooted with the Zedomax pre-rooted kernel and went back to stock by using stock rooted kernel, factory reset, and odined this http://forum.xda-developers.com/showthread.php?t=1273647
then factory reset again and I updated profile after resetting...
Click to expand...
Click to collapse
You obviously messed something up, since you were not getting any los before rooting. You can try a couple of things:
1) Flash cwm kernel of any kind (I prefer cwm4, because it doesn't require external sd card for nand operations.)
2) Wipe system/data/cache, flash a stock rom (as stock as you can find).
3) Power off and flash stock-pulled from bubby, or lostkernel (I think both are los free).
4) Reboot and immediately update profile and prl.
You can also try to ask someone at sprint to reprovision the phone. Or do it yourself with hands-free activation data reset. In case zedo kernel somehow messed up provisioning data.
Another idea (just came up with it, don't know if it makes sense) is to program the phone yourself with qpst app. Compare qpst programming data of your own phone to that of someone else without los. Maybe there's an obvious discrepancy, and you can fix it.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
awesomeindeed said:
I have not rooted my phone and I get LOS pretty frequently. Factory resets and whatnot do not fix the issue. There is a real issue here, and they're being very quiet and slow about fixing it.
Click to expand...
Click to collapse
Where did you get your phone?
nabbed said:
You obviously messed something up, since you were not getting any los before rooting. You can try a couple of things:
1) Flash cwm kernel of any kind (I prefer cwm4, because it doesn't require external sd card for nand operations.)
2) Wipe system/data/cache, flash a stock rom (as stock as you can find).
3) Power off and flash stock-pulled from bubby, or lostkernel (I think both are los free).
4) Reboot and immediately update profile and prl.
You can also try to ask someone at sprint to reprovision the phone. Or do it yourself with hands-free activation data reset. In case zedo kernel somehow messed up provisioning data.
Another idea (just came up with it, don't know if it makes sense) is to program the phone yourself with qpst app. Compare qpst programming data of your own phone to that of someone else without los. Maybe there's an obvious discrepancy, and you can fix it.
---------- Post added at 12:24 PM ---------- Previous post was at 12:24 PM ----------
Where did you get your phone?
Click to expand...
Click to collapse
I got the phone from Best Buy and I re provisioned it myself using ## code and MSL
I rooted early on so it it possible that I never notices LOS prior to rooting
neverends said:
I got the phone from Best Buy and I re provisioned it myself using ## code and MSL
I rooted early on so it it possible that I never notices LOS prior to rooting
Click to expand...
Click to collapse
Are you saying the hardware is defective?
Exchange it.

LOS Strictly a hardware problem?

First of all let me point at that I am currently still a OG EVO user. This will probably be my next phone on DEC. 1 once I am due for a upgrade with Sprint. I really love the design and specs for this phone but I have been turned off by all the LOS talk.
If a phone can't maintain a working signal it isn't much good no matter how nice the screen or specs are.
After doing some research on what I hope will be my next phone, I've come to the conclusion that this is a hardware problem. From what I can gather these phones have some kind of defect with the internal antenna which is causing this problem.
This probably isn't news to anyone on these forums but I just wanted to get some confirmation on this. I'm hoping that if this is in fact that problem the next batch of these phones released around the holiday season will have this problem fixed.
Assuming this hardware problem is not fixed; is there any rom/kernel combination that is known to be most effective in terms of this LOS issue?
Na don't think it's a hardware issue, if so I believe it wouldn't be so random. With the LOStKernel I haven't had any more issues but others have. That being said, if it were a hardware issue i would've had los as well already.
Sent from my SPH-D710 using xda premium
I agree If this is Hardware issues that say the Antenna get low signal and then won't pick it back up. Then That Pickup is what needs to be fixed (and that is software). We've all had low signal or switched to Roaming. This is where the issue is, at least to me. The Low Signal strength maybe a 2nd issue but that may need a Power adjustment.
I also agree with the LOSKernel. I was averaging 1-2 a day and haven't had one in 3 days (I installed 3 days ago).
acrown said:
Na don't think it's a hardware issue, if so I believe it wouldn't be so random. With the LOStKernel I haven't had any more issues but others have. That being said, if it were a hardware issue i would've had los as well already.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Interesting. I was assuming that this was a hardware issue but you guys seem to think otherwise. I could care less as long as there a way to get the damn phone to work. I really want this phone!!!
ditto on the LOStKernal.
i used to have LOS daily about 8 times. now i havent had it in a week and i flashed it in a week.
=D
SantinoInc said:
Interesting. I was assuming that this was a hardware issue but you guys seem to think otherwise. I could care less as long as there a way to get the damn phone to work. I really want this phone!!!
Click to expand...
Click to collapse
Yeah, it's not hardware. The way the bug pops up is extremely circumstantial...so much so that we still don't know the parameters of the circumstance that triggers the bug. Having a low signal seems to have something to do with it but it has also occurred with full signal...but software changes seem to have a gigantic impact on it. I haven't seen one in weeks. I dunno....
I wouldn't be too concerned. I have the phone and I'm not.
...and it is a pretty bad-ass phone. If you are already a Sprint subscriber you'll love it, especially coming from the Evo4G.
I have never had LOS.
Sent from my SPH-D710 using XDA App
I'm thinking this is definitely software related, I personally didn't have a LOS problem until I started flashing kernels.Even on the Loskernel I was experiencing several LOS a day, flashed back to stock rom/kernel and haven't had a problem. From what I have experienced, Los seems to correlate with the phone roaming off of the sprint network and unable to connect back.
Sent from my SPH-D710 using XDA App
Its software. I haven't had LOS since the day the phone came out.
Sent From My Evo Killer!!!
Its a modem issue the kernel can only help so much. Samsung will be releasing a new modem.bin when they give us the maintenance update.
No it's a sprint problem my phone is fully flashed to ntelos and I have been trying to get los since monday even trying different kernels and roms I just cant produce los
Sent from my Galaxy S2 using Tapatalk
I've seen a couple posts saying the LoS issue is related to roaming off/on the Sprint network...this may be true to a certain extent but I sit 5 feet from an Airave and I'll get LoS a few times a day when at home. Happens just as often if not more when I'm out and about.
On a more related note, OP: this phone is great and they will fix the phone somehow or make good on it. If for some reason they haven't solved the problem and you are over the 14-30 days (maybe even waaaayyyy past that...months!) then they will take the phone back. If you can't get them to give you a free Photon or basically whatever you want, then you are a pushover! Just have to start making a papertrail for your issue, that is all really.
Would that necessarily rule out that the air wave itself is not roaming or losing/regaining signal throughout the day affecting your phone?
Sent from my SPH-D710 using XDA App
vdub804 said:
No it's a sprint problem my phone is fully flashed to ntelos and I have been trying to get los since monday even trying different kernels and roms I just cant produce los
Sent from my Galaxy S2 using Tapatalk
Click to expand...
Click to collapse
Its not a Sprint issue.
Its a Samsung issue.
That's been confirmed by developers.
ClutchR1 said:
Would that necessarily rule out that the air wave itself is not roaming or losing/regaining signal throughout the day affecting your phone?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
I have an Airave in my house and do not have any connectivity issues at all to it. I am also using a phone that has not been rooted and have yet to get an LOS either.
My point is that if the air wave is losing connectivity at all, then your phone is as well forcing it to roam
Sent from my SPH-D710 using XDA App
I never got LOS until I started flashing(about 3 days )
I was getting once per day utill the Lost kernel came along, now I've only had 1 LOS in the 10 days or so since the kernel has been out. I definitely believe it's software or modem related.
Bad ass phone nonetheless...dont hesitate!
Love this phone. Got it launch day and have never experienced a single LOS. I've never tried to root it or install a custom kernel.
Stock rom and not rooted, never had LOS.
I only have had LOS when I installed a ROM a long time ago.. Have had no problems on stock rom, stock kernel, rooted

Anyone Still Have Their Phone Unrooted / LOS Bug?

So I would like to know if anyone out there besides me has not rooted their phone yet and if not, have you gotten the LOS bug?
I had purchased an E4GT when it came out and ran it stock for about a week. Did not have on LOS. Then decided to root it and within 12 hours I had an LOS. Within another 12 hours I got another one. Nothing in my use had changed and it happened in my house both times so it was not like I was in another situation that I have not been in.
I exhanged the phone for another one and obviously did not root it this time around. It has been over a month now and I have yet to get an LOS. I have traveled in areas where there is no Sprint service, through farmlands, etc. My phone roams fine. I have been on 3G, 4G, wifi, and an airave and there is nothing that will give my phone an LOS.
I also have a friend who owns the phone and I refuse to root his because he also never got an LOS since release day and I would be willing to bet if I rooted it one would show up not long after.
This is not to bring out the haters but I want to hear from people who have never rooted their phone. Not the ones who rooted then re-installed stock. I am sure we will also get some liars in here but I usually can pick out the trolls.
This is for true LOS, not that your internet connection wasn't working or your calls went straight to VM. I have had things like that happen for years already on all of my past phones.
Never rooted, never had LOS. Damn do I miss wifi tether.
You have been Epicly Touched by Jesse Buck
Yes I'm not rooted and I have gotten LOS. Not as of late (for over the last week) but I've had 4 total the 4th one I really can't blame the phone or Sprint since everyone at the time that was/is on sprint was having the issue (20+ people I go to school with)
Outside of that I've not had an issue as of late but yes I've never been rooted and I've had LOS as have other people in this forum as well.
I do not have LOS with Chris41g's kernel.
My brother who is completely stock/never rooted gets LOS from time to time.
Never rooted, and no LoS for me.
Sent from my SPH-D710 using Tapatalk
mattykinsx said:
I do not have LOS with Chris41g's kernel.
My brother who is completely stock/never rooted gets LOS from time to time.
Click to expand...
Click to collapse
How long have you ran that kernel for?
[email protected] said:
How long have you ran that kernel for?
Click to expand...
Click to collapse
Couple of weeks. I find the newer versions are better than the old.
I haven't rooted yet and I haven't had a single LOS since I got the phone on release day. That's the only reason why I haven't rooted, I'm afraid that if I do then I will start getting LOS. I wish there was a root method that didn't involve flashing anything, then I would pull the trigger on it. But for now, tethering and adfree are not a compelling enough reason for me to root and deal with the risk of LOS. I see no reason to flash a custom ROM or kernel on this phone seeing as though it is fast as hell and butter smooth the way it is. I would like to delete some crap from it though.
_MetalHead_ said:
I haven't rooted yet and I haven't had a single LOS since I got the phone on release day. That's the only reason why I haven't rooted, I'm afraid that if I do then I will start getting LOS. I wish there was a root method that didn't involve flashing anything, then I would pull the trigger on it. But for now, tethering and adfree are not a compelling enough reason for me to root and deal with the risk of LOS. I see no reason to flash a custom ROM or kernel on this phone seeing as though it is fast as hell and butter smooth the way it is. I would like to delete some crap from it though.
Click to expand...
Click to collapse
Totolly Agree and feel exaclty the same way. Although, even with the crap on it their really is no negative effect on the phone at all.
I am willing to say that almost everyone that has rooted their phone has seen an LOS where the ones that never did will most likely never see one.
Everyone is *****ing about Samsung that really is more of a rooting issue and not a manufacturing issue. I hope this gets sorted out and whatever Samsung updates will fix the issue with root. I can hold off for now but once an ICS Rom hits, it is going to be much harder!
Had this phone since launch and haven't rooted yet. No LOS at all. Phone goes on roaming and out just fine. First phone I have had stock but this phone is a beast. Will root once the LOS is solved or there is a rom that I can't wait for.
Sent From My Evo Killer!!!
I got the phone on launch day, LOS (stock) started on day 3. Rooting didnt help. Took it back for a replacement and havent had LOS at all... I rooted/added CWM yesterday, no issues. BUT, I havent flashed a rom yet, and I wont until this "update" is out...
I was stock until 2 weeks ago, and I've had the phone since one week after it came out. On stock, I had LOS 1 time. After I rooted just two weeks ago, I've had it 2 or 3 times.
[email protected] said:
Totolly Agree and feel exaclty the same way. Although, even with the crap on it their really is no negative effect on the phone at all.
I am willing to say that almost everyone that has rooted their phone has seen an LOS where the ones that never did will most likely never see one.
Everyone is *****ing about Samsung that really is more of a rooting issue and not a manufacturing issue. I hope this gets sorted out and whatever Samsung updates will fix the issue with root. I can hold off for now but once an ICS Rom hits, it is going to be much harder!
Click to expand...
Click to collapse
If it were a rooting issue and not a manufacturing issue, then why is the manufacturer admitting that it's a manufacturing issue and releasing an update to fix the manufacturing issue? If it were a rooting issue, they'd have said "don't root and you won't have the problem".
I didn't root at first for fear of LOS, then I got it twice on the 4th day after release so I rooted anyway. Got it 1-2 times a day for a few weeks. Started running chris41g's lostkernel and now I get it once every two days to once a day tops.
Can't wait for Samsung to fix their stock problem at least they're on it this time and not screwing us like the epic 4g...which just got gingerbread i heard.
Not rooted, have had the phone since the week it launched - experienced LOS ONCE while in my house on the couch where I use the phone a lot. Haven't seen it since. I really, really miss being rooted mainly due to wifi tether and hiding annoying ads but I think the biggest thing right now is the effing camera click sounds.
I really wish there was a simple, straightforward root process that just "unlocked" the phone without really changing anything. Is such a thing even in process? Until then, I'm likely not going to do jack because LOS problems would be a ***** compared to the annoying camera clicks.
http://forum.xda-developers.com/showthread.php?t=1269890
17 page thread with all types of users reporting it.
[email protected] said:
Totolly Agree and feel exaclty the same way. Although, even with the crap on it their really is no negative effect on the phone at all.
I am willing to say that almost everyone that has rooted their phone has seen an LOS where the ones that never did will most likely never see one.
Everyone is *****ing about Samsung that really is more of a rooting issue and not a manufacturing issue. I hope this gets sorted out and whatever Samsung updates will fix the issue with root. I can hold off for now but once an ICS Rom hits, it is going to be much harder!
Click to expand...
Click to collapse
Flashing may trigger LOS, but it is not the root cause (no pun intended). My phone is bone stock and had LOS bug pretty bad. Even happened in a Sprint store while I was showing them.
CS had me do a data profile clear/re-update and all has been good since.
If you think rooting is the cause of LOS you're wrong, plain and simple. Some kernels may cause it to happen more often however. I had it 4 or 5 times when stock. I'm rooted now with chris41g's stock pulled w/cwm5 kernel and haven't had LOS since. I won't be surprised if I get LOS again, but it's definitely not because I rooted my phone. It's a problem right out of the box
Once again, root (su binaries and busy box, typically) DOES NOT CAUSE LOS.
The phones can get LOS bone stock. Mine did.
Custom kernels seem to exacerbate the problem...though new kernels seem to have figured it out. (current kernel is over a week in use with no LOS...as good as stock)
You can have root with a stock kernel.
You can debate LOS occurrence frequency differences between stock and custom kernels but please get your terminology straightened out. All of this is causing the conversation to always turn into a debate into an argument, every time and scaring people who want to root...and them the conversation comes back, the cycle persists and just gets louder every time.
Get your terminology straight...
...root has nothing to do with this. Period.
Sent from my SPH-D710 using XDA App
daneurysm said:
You can have root with a stock kernel.
Click to expand...
Click to collapse
Thank you - that is what I was wondering. I understand what you're saying about rooting not being the cause of LOS but, as you said yourself, some of the kernels used to root these phones seem to exacerbate the problem. There are a few different camps of thinking here and one of them is the group that almost never or never experienced LOS out of the box. To them, the link between rooting and seemingly more frequent occurrences of LOS is enough to make them hesitate to root. Another group are those that experienced LOS already and maybe have nothing to lose to rooting and seeing what happens. I can tell you that, having experienced only one LOS since launch on a stock GS2, if I were to root today and experience LOS tomorrow I'd just have to link the two.
I'm not very knowledgeable on the rooting process but I have rooted almost every android phone I've ever had: Hero, EVO, Photon. ... I'll have to read up on which of the latest root methods for this phone seem to be the best as far as not experiencing LOS and maybe I'll just give it a whirl and see. If nothing else, it'll add to the body of knowledge and experience for this phone.
I'm a month into ownership and still no LOS. Been rooted on and off for 3 weeks and have run both types of LoStKernel and the Stock Pulled Kernel. I've flashed back to completely stock unrooted twice to have a clean slate to work with. No issues yet.
Sent from my SPH-D710 using xda premium

VZW signal issues and root.

rhinolow said:
So I went back to 4.0.1 and was getting a steady three bars on my phone
Went to 4.0.2 and am getting a steady 2 bars on 4g
Unlocked, and rooted on 4.0.2, and was getting really sporadic signal behavior, including signal loss
All these readings are from the same location in my home.
Then I went back to 4.0.1 and tested all three conditions and got the same results.
I'm no programmer so I can't say why unlocking/rooting would make a difference, but I believe it's making enough of a difference at this point that I'm going to stay stock and locked at 4.0.2 for now.
You guys that are having a lot of problems, are you unlocked or rooted?
Click to expand...
Click to collapse
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Stock Verizon Nexus here and where I normally get full 4g I get maybe 2-3 3g bars. Most of the time I get zero signal where I at least get 3g.
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Great article. Sure as heck opened my eyes up. Thanks.
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
player911 said:
Root doesn't touch the radio. All it does it give you admin right over the phone.
-Galaxy Nexus
-Asus Transformer
Click to expand...
Click to collapse
Exactly right it must have just been the cell towers by the ops area
I'm currently having issues now before and after root
droid2andyou said:
http://www.anandtech.com/show/5254/investigating-the-galaxy-nexus-lte-signal-issue
Click to expand...
Click to collapse
Just read that earlier today. Lots of great info inside.
The story continues
So, just to follow up. I did return my device for a new GNEX and have not had the same issues. I have been reluctant to root my new phone, but I still don't see any reason why the two would be related. I think I had a bad device. I think there are a substantial number of people that are getting DOA devices, but it doesn't appear to a majority. I'll report back if/when I decide to root and flash anything to my new device.
abendx said:
Now that it's been a few days..... I want others to chime in on this report (no one answered this question in the original thread).
I was having a ton of issues, thought that VZW did something to make it slightly better (which I still believe they did), but stilll... I have issues, although not as bad as the second 12 hours of ownership.
I had made the call to tech support and was then going to return the phone.... when I got home I brought the device back to stock carrier 4.0.1 ROM floating around). Problems were almost completely gone!?! An hour later, the update came and I was worried about the upgrade screwing the radio that was acting better (not that it was perfect by any means!!). So..... after a little thought, I figured I could always go back to 4.0.1 and/or return it. I let the update do it's thing.
There seems to be zero difference between 4.0.1 and 4.0.2, when it comes to the radio.
I was still scared to do much..... I didn't install any apps while I watched the phone for a few hours. Then only Google's apps... the next day the rest of my apps (w/small exceptions, detailed below). Everything ran smoothly.... including the radio. Now it isn't nearly as good as the DX radio in my last phone, BUT..... at least I wasn't constantly with -120dbm and was able to use the phone, as a phone!
So.... I figured after another day that VZW must have fixed something.
Cool, right? Not sure..... I am stock, unlocked, and unrooted. I am afraid to root the phone..... I can't fathom how root could cause a radio issue, but am wondering how many others might have issue with and without root.
Now.... I am still seeing issues, but not nearly as bad. I'll root the phone tonight to see what happens, but would like others input.
Click to expand...
Click to collapse

Categories

Resources