Develop Bugs

Anyone getting random reboots on their stock/unrooted E4GTs?

Everything has been perfect with this phone except now I've had two reboots in the past two days and I'm considering swapping it for a new handset (could be indicative of a larger problem). Yesterday it rebooted when I was browsing the internet, it had 70% battery before the reboot and then the phone was reporting 15% right after. I did a battery pull and it came up to 40% after. Weird. Anyone else have any issues like this?
Sent from my SPH-D710 using XDA App

No issues here. Phone works flawlessly for me under heavy use.
sent from my DAMN phone!

never happened to me either...fully stock, never rooted
If it happens to you again, if you are within the return window, you may want to exchange it

Yep... watch this youtube.com/watch?v=8pMLxyThxEk
what a piece. And sprint is no help. Not in person. Not "Dan Hesse's Office"

That doesn't sound right at all. I haven't had a single one..not even when messing around overclocked to 1.6
Sent from my SPH-D710 using xda premium

Happened to me every time I tried to uninstall/go into parts of the phone. Happened a Month ago, dida format stock...all okay like nothing happened.
-jr
Ps, it was after phone got easy too hot using hdmi out for over 3 hours...I believe the phone was well above the 125°, as o could not touch it.
Sent from my SPH-D710 using Tapatalk

Never had the problem when it was stock...if anything, it did drain the battery a bit. But that's expected.

tubasteve said:
Happened to me every time I tried to uninstall/go into parts of the phone. Happened a Month ago, dida format stock...all okay like nothing happened.
-jr
Ps, it was after phone got easy too hot using hdmi out for over 3 hours...I believe the phone was well above the 125°, as o could not touch it.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I have been told that the phone will shut itself down to prevent heat damage.
Sent from my SPH-D710 using xda premium

I havent had a single one since I posted this thread. I'm thinking it was a fluke. My phone runs like a champ now, especially since I rooted and used autostarts and titanium to get all the bloat under control.

Wait... people on here that don't root? I'm confused...

subcypher said:
Wait... people on here that don't root? I'm confused...
Click to expand...
Click to collapse
At the time I posted this thread I was still waiting for a way to root my current ROM, with no flashing involved. With all the problems that people were having with LOS I didn't want to risk flashing a new kernel and potentially starting to get LOS when I never had it before. I still haven't had a single one and I got this phone on release day

Well, thanks to a FUBAR with the CIQ removal script and no backup, I moved away from stock. I'm now running Calkulin's and haven't had any LOS or random reboots. At least, that's what I'm running while I patiently wait for CM9. That being said, I recommend it.

subcypher said:
Well, thanks to a FUBAR with the CIQ removal script and no backup, I moved away from stock. I'm now running Calkulin's and haven't had any LOS or random reboots. At least, that's what I'm running while I patiently wait for CM9. That being said, I recommend it.
Click to expand...
Click to collapse
Yeah I had the same FUBAR lol. I ended up using odin to go the EG31 route. I really feel no desire to go with a custom ROM. Back in the EVO days the stock ROM was always so bloated even with just Sense that you HAD to go custom to get any performance or decent battery life out of it. The stock ROM on our E4GTs just blazes and is damn near perfect already. The only thing left for me to do is get rid of CiQ and then it will be absolutely perfect. I have the odexed version of the noCiQ mod waiting to be flashed but I'm 1000 miles from home for the next few weeks and can't risk screwing up my phone. I only brought my macbook with me so using odin in case of a fowl up is not an option right now.

_MetalHead_ said:
Yeah I had the same FUBAR lol. I ended up using odin to go the EG31 route. I really feel no desire to go with a custom ROM. Back in the EVO days the stock ROM was always so bloated even with just Sense that you HAD to go custom to get any performance or decent battery life out of it. The stock ROM on our E4GTs just blazes and is damn near perfect already. The only thing left for me to do is get rid of CiQ and then it will be absolutely perfect. I have the odexed version of the noCiQ mod waiting to be flashed but I'm 1000 miles from home for the next few weeks and can't risk screwing up my phone. I only brought my macbook with me so using odin in case of a fowl up is not an option right now.
Click to expand...
Click to collapse
I know what you mean, man. But once you're rooted and have Clockwork on there, you can do Nandroid backups and flash right from your SD card! But, hey, safe journeys.

subcypher said:
I know what you mean, man. But once you're rooted and have Clockwork on there, you can do Nandroid backups and flash right from your SD card! But, hey, safe journeys.
Click to expand...
Click to collapse
Oh I'm aware. I still do nandroids just in case now but honestly, stock ROM+removed bloat + autostarts is awesome.
I used to be flash happy when I had my EVO, I flashed new ROMs all the time (and always ended up back at MIUI). With my E4GT I just want it to work with no problems and I'm happy.

I'm stock too. I did the whole flash everything under the sun with my evolution and evo 3d and other phones. Ill root and flash when cm9 is stable. I had one radom reboot once but I think it was an app issue.
Sent from my SPH-D710 using xda premium

Rooting Leading to LoS

I rooted my phone for the first time yesterday after having it for two weeks. I never had a LoS issue and was getting 3 days of battery life. About an hour after rooting, I got my first LoS. I charged my phone overnight, and verified everything was okay in the morning (had sync). After 6 hours of being at work, I got a low battery warning and noticed it hit LoS again.
I know people with stock phones have reported LoS, but I'm convinced that it's either significantly worse with a rooted phone.

install starburst v1.6 which includes lost kernel.. lost kernel fixed my LOS issues.. maybe it will do the same for you..

Question: I flashed the stock kernel from Bubby to get rid of the LoS problem. Everything succeeded, but I still have root. How is that possible if I put the stock kernel in?

shaklee3 said:
Question: I flashed the stock kernel from Bubby to get rid of the LoS problem. Everything succeeded, but I still have root. How is that possible if I put the stock kernel in?
Click to expand...
Click to collapse
Did you flash a ROM?
Sent from my SPH-D710

I haven't got Los on my new ept4g. S
I don't think its root though
Sent from my SPH-D710 using XDA App

shaklee3 said:
I rooted my phone for the first time yesterday after having it for two weeks. I never had a LoS issue and was getting 3 days of battery life. About an hour after rooting, I got my first LoS. I charged my phone overnight, and verified everything was okay in the morning (had sync). After 6 hours of being at work, I got a low battery warning and noticed it hit LoS again.
I know people with stock phones have reported LoS, but I'm convinced that it's either significantly worse with a rooted phone.
Click to expand...
Click to collapse
It has absolutely nothing to do with root.
That is nothing more than a rumor.
Developers have stated, and so has Sprint, that this is a problem with the Samsung firmware with the phone.
If this is true it was just a mere coincidence.

mattykinsx said:
It has absolutely nothing to do with root.
That is nothing more than a rumor.
Developers have stated, and so has Sprint, that this is a problem with the Samsung firmware with the phone.
If this is true it was just a mere coincidence.
Click to expand...
Click to collapse
I believe you, but I also believe it's worse with rooting or something caused during the rooting process. I had the phone for two weeks and never once saw a LoS. I rooted it using CWM + su, and had 4 LoS over the next two days. It just seems like too big of a coincidence.
ripalsanghani, no I didn't flash a ROM

root does NOT cause LOS. It happens on stock firmware also. It does happen more tho after you root (seems like it)

If it doesn't, then it definitely makes the problem EXTREMELY worse.
I've had two EPIC 4G Touchs (replace one before return policy ended because of stuck pixel) both phones I had running for about a week and half before rooting without issue.
Both immediately had LoS after rooting (and frequently.)
Haven't tried the newest kernel that is supposed to be much better though.
I'll probably feel brave enough soon.
For both phones, they immediately were better after putting stock kernel back in place. So YES definitely the previous kernels at least were either causing or exacerbating the issue. I've been able to recreate it.
I hope the new kernel is better.

100% rooting was the cause of my LoS's.
I had the phone for 2 weeks before rooting, not a single time did I have an LoS, and I was on the thing pretty much constantly. I rooted the phone, tried all 3 of the popular roms out there with the zedo kernel, 30 stock, and stock, and within 2 hours of rooting I had an LoS. After a few days, it got worse and worse, I would get LoS's at least 3 or 4 times a day, and I'd wake up every single morning with it having LoS'd over night.
I have since gone back to stock with the image available on XDA about 4 days ago, and I haven't had a single LoS since with no change in usage and all the same apps and settings as I had before. The only change was no root, and stock image.
It's too bad, I really loved my Evo and how responsive it was to rooting, kernels, and roms. I love this phone, I hope they get this part worked out.
Mario

LOS definitely can happen with stock kernel+stock ROM, but it happens in much fewer cases.
"Root" doesn't cause LOS.
However, many methods of "Root" include a "recompiled" kernel from Samsung stock source code.
It is the "recompiled" kernel which can in some cases exacerbate LOS. In cases where people were already seeing LOS, it could get worse. For people who never saw LOS before, they could start seeing it. There is an attempt to minimize the LOS effects in the "recompiled" kernels. It is called lostkernel.
It is unclear whether LOS getting exacerbated is due to Samsung source code being problematic or the build parameters being slightly off from what Samsung originally used.
Also keep in mind on Samsung Recovery and Android use the same kernel. On other platforms, Recovery and Android are separate so the kernels can be updated independently. What this means is if you install a Custom Recovery, your Android will also start using whatever kernel it came with (because there is only one kernel for both). Up until recently (as in a few days ago) every Custom Recovery came with a "recompiled" kernel so you might have been using a "recompiled" kernel from stock sources even if you didn't realize it, especially if you came from another platform expecting Recovery and Android to have separate kernels.

sfhub said:
LOS definitely can happen with stock kernel+stock ROM, but it happens in much fewer cases.
"Root" doesn't cause LOS.
However, many methods of "Root" include a "recompiled" kernel from Samsung stock source code.
It is the "recompiled" kernel which can in some cases exacerbate LOS. In cases where people were already seeing LOS, it could get worse. For people who never saw LOS before, they could start seeing it. There is an attempt to minimize the LOS effects in the "recompiled" kernels. It is called lostkernel.
It is unclear whether LOS getting exacerbated is due to Samsung source code being problematic or the build parameters being slightly off from what Samsung originally used.
Also keep in mind on Samsung Recovery and Android use the same kernel. On other platforms, Recovery and Android are separate so the kernels can be updated independently. What this means is if you install a Custom Recovery, your Android will also start using whatever kernel it came with (because there is only one kernel for both). Up until recently (as in a few days ago) every Custom Recovery came with a "recompiled" kernel so you might have been using a "recompiled" kernel from stock sources even if you didn't realize it, especially if you came from another platform expecting Recovery and Android to have separate kernels.
Click to expand...
Click to collapse
Good explanation - that being said, at the root of the issue, no pun intended, after having rooted/kernelled/rom'd my device, I started getting LoS's, before, and after, I haven't had a single one.
Just hope they get it worked out, blame isn't something I am throwing around or pointing at, if it gets fixed, that's all I care about It's a great phone, best phone I've ever used by far.

desantim said:
Good explanation - that being said, at the root of the issue, no pun intended, after having rooted/kernelled/rom'd my device, I started getting LoS's, before, and after, I haven't had a single one.
Just hope they get it worked out, blame isn't something I am throwing around or pointing at, if it gets fixed, that's all I care about It's a great phone, best phone I've ever used by far.
Click to expand...
Click to collapse
It's definitely not the rooting itself, but rather the recompiled kernels that seem to cause the increase in LOS.
There are non-kernel roots in the dev forum that don't have this increase in LOS behavior that people complain about in the custom kernel threads.

Maybe I'm just new to this, but I don't believe I flashed a new kernel. All I did was install CWM, then flash the su program. This is when the LoS started for me.

Which CWM did you install? Every CWM except the repacked one from chris41g that came out 2 days ago includes a "recompiled" kernel.

It was the one referenced in the thread at the top of the development forum summarizing the status of everything.
Sent from my SPH-D710 using XDA App

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

Your Los and You...

I have had this phone since day 1 and was in the first group of people to start rooting and screwing around with it. I can tell you that I have had LOS since pretty much day one and struggled with it tremendously. I've noticed that when I've been on trips in areas with bad reception and constantly roaming and unroaming I would get LOS 20+ times a day. I started getting LOS at home on my Airrave while connected to Wifi constantly on the ROM that I had been running for a long time with a kernel that I had also been running for awhile. I read about Strongsteves Odexed ROM and decided to give it a whirl, why not, I've tried every other ROM. I've been running this ROM for a week now with zero Los issues at all. The kicker for me was this weekend I took my family on a trip and again I had bad reception and was roaming in and out all day yesterday. I had zero Los the entire day. I can't explain why it works, but it works. I not even close to a developer but more of a power user/Flash test dummy. I know my way around Android as far as flashing and screwing my phone up and getting it back but other than that, I'm not much help. All I can tell you is it works so long as you don't go dumping other kernels over it. Anyway, just thought I'd get this out there, hopefully more of you will try it and verify that it works.
http://forum.xda-developers.com/showthread.php?t=1323763

The most likely reason it "fixed" your LOS is it changed your kernel back to stock, via chris41g's stock EG30 kernel repacked with CWM and you are in a scenario where you wouldn't have had any LOS if you had stuck with the stock kernel. There are some folks who are in a situation where they would have had LOS even on stock kernel, and this wouldn't have helped them.
So definitely if you see LOS, it is worth a try to go back to stock EG30 kernel, either the completely stock EG30 kernel or the stock EG30 kernel repacked with CWM, to see if the LOS goes away. It won't "fix" the LOS bug as that is in the base kernel/rom from Samsung, but it could make it so in your situation you see it much less or don't see it at all.

sfhub said:
The most likely reason it "fixed" your LOS is it changed your kernel back to stock, via chris41g's stock EG30 kernel repacked with CWM and you are in a scenario where you wouldn't have had any LOS if you had stuck with the stock kernel. There are some folks who are in a situation where they would have had LOS even on stock kernel, and this wouldn't have helped them.
So definitely if you see LOS, it is worth a try to go back to stock EG30 kernel, either the completely stock EG30 kernel or the stock EG30 kernel repacked with CWM, to see if the LOS goes away. It won't "fix" the LOS bug as that is in the base kernel/rom from Samsung, but it could make it so in your situation you see it much less or don't see it at all.
Click to expand...
Click to collapse
And that's pretty much why I posted this. I'm so tired of reading threads of the latest and greatest kernel and then guys saying "omg, omg, los, los!". This has fixed it for me and many others. I'm not going to bash anyone else's work because I sure the hell can't do it, I just think it would clear a lot of the los pandemic up so the devs could focus on what's important, a true AOSP ROM.
Sent from my SPH-D710

I,m on my 4th day with no Los. I went my 1st 2 weeks stock in September with no Los. I started getting Los when I started flashing. I'm sticking with strongsteve. I'll let you know if I do get Los.

fordmanck said:
And that's pretty much why I posted this. I'm so tired of reading threads of the latest and greatest kernel and then guys saying "omg, omg, los, los!".
Click to expand...
Click to collapse
That's cool.
I'm just clarifying your suggestion and saying people can achieve the same behavior with their existing ROM by flashing either the stock pulled EG30 or chris41g's stock pulled EG30 repacked with CWM. I like StrongSteve's work, but the critical factor in the behavior change you saw was the kernel that he included, which can be installed separate from StrongSteve's ROM.
Note, I'm careful to not say people can "fix" their LOS with the stock EG30 kernel, just that they can achieve the same experience (w/r/t LOS) of installing StrongSteve's work, just by installing the stock EG30 kernel with their existing ROM (assuming their existing ROM will work with a stock EG30 kernel)

sfhub said:
That's cool.
I'm just clarifying your suggestion and saying people can achieve the same behavior with their existing ROM by flashing either the stock pulled EG30 or chris41g's stock pulled EG30 repacked with CWM. I like StrongSteve's work, but the critical factor in the behavior change you saw was the kernel that he included, which can be installed separate from StrongSteve's ROM.
Note, I'm careful to not say people can "fix" their LOS with the stock EG30 kernel, just that they can achieve the same experience (w/r/t LOS) of installing StrongSteve's work, just by installing the stock EG30 kernel with their existing ROM (assuming their existing ROM will work with a stock EG30 kernel)
Click to expand...
Click to collapse
I totally understand. I wasn't stock for probably a day so for all I know I never would have had the issue stock. I kind of thought the kernel could be the reason but so many people have said there is no way it's kernel related that I've kind of latched on to that.
Either way if the people that are crying the worst about los would try it, it could help. Anyway, thanks for the input.

i can see this LOS topic is going to be annoyingly redundant.
LOS has nothing to do with you being rooted, stock, whatever. it is random.

cobraboy85 said:
i can see this LOS topic is going to be annoyingly redundant.
LOS has nothing to do with you being rooted, stock, whatever. it is random.
Click to expand...
Click to collapse
Then don't read or reply to them.
If you're not getting Los, good for you, keep on keeping on. Those of us that are, are trying to figure out WTF we can do to not miss important phone calls, or emails, or text, etc, etc...
I'm sorry you clicked on a thread and felt obliged to comment on it.

just stating.. it's a randomly occurring thing
there are like 20 threads on it

cobraboy85 said:
just stating.. it's a randomly occurring thing
there are like 20 threads on it
Click to expand...
Click to collapse
Good thing this is an open phone forum.
I'm trying to help someone out, obviously you don't need it, but there are many cluttered kernel threads about los issues. I'm not smart enough, obviously, to know if it's kernel related or not. I am however smart enough to know when my los is occurring and when it's not, right now it's not and I flashed a different ROM with a different kernel. So if I can help just one person stop posting in Dev threads about their Los so we can get Devs working on the **** that really matters, I'm happy.

well, i guess i shouldn't say it is completely random as SOMETHING is causing it to happen.

cobraboy85 said:
well, i guess i shouldn't say it is completely random as SOMETHING is causing it to happen.
Click to expand...
Click to collapse
Why u still posting? He is trying to help someone out and offer a possible solution. If u don't like it don't post. Go back to your better evo3d.
Sent From My Evo Killer!!!

How many los threads are up now?
Sent from the bridge of the USS Enterprise using LT.Com Worf

You guys still keep feeding Sprint and Samsung by buying this phone and giving them the impression that it's great and rosy. Vote with your pockets and send them the message.
That's what I did. One would think by now that some fix would have come from Samsung concerning their flagship phone, but nothing.
I got tired of missing calls and emails and constantly checking to see if LoS had crept up or not, it got annoying. Went back to my trusty Nexus S.
Sent from my Nexus S 4G

Zero LOS on stock kernel. Got a couple on early custom kernel . Went to pulled stock and zero since. I am running strongsteve's ROM as well and haven't had a single issue with it. I don't understand why if someone takes stock kernel, adds CWM and overclock odd issues seem to arise. If I need to flash something, I use stock w/ CWM5 but go right back to pulled stock after. Maybe I am being overly cautious but I have had 100% success on stock. I am sure we will get an update fix and things will take off from there. Also, my Nexus S 4g doesn't get near the signal strength (especially on 4g) as this phone
Sent from my SPH-D710 using xda premium

Going to try the Rogue pulled stock w/ CWM5 and see if it's as stable ad pulled stock by itself
Sent from my SPH-D710 using xda premium

JohnCorleone said:
Going to try the Rogue pulled stock w/ CWM5 and see if it's as stable ad pulled stock by itself
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I actually did some beta testing for him. I've been running it for 2 days now with zero issues. Again, I know this isn't a fix for everyone, but I'm so tired of reading the custom kernel threads with people crying LOS without at least trying this. I've talked to several people that this has worked for.

LOS some ideas and thoughts

I've read these forums since they were put online and I've followed all the issues with the phone even before I got it. I knew about the LOS issues and even with it I got the phone. While I've had LOS a total of 4 times even before I rooted my phone after rooting it I did notice it a bit more.
kinda going to reference this thread that was just brought up.
http://forum.xda-developers.com/showthread.php?t=1360375
Now normally I would not really post a thread but I do have a few ideas after reading a lot of the things on this forum over the last few months. I remember reading that the source that samsung released for the phone was not correct(correct me if I am wrong here) Was something about it not matching the md5 check with what we have on our phones exactly (ie sounds like samsung left things out or maybe they put up an old source code?)
But this got me to thinking after rooting the phone the other day and noticing LOS far more then I ever have (10 times within 4 days and this was running Calk's rom granted all roms do have the issue not trying to single any one rom out by any means)
What if Samsung actually did something within the kernal itself (and they left it out) that either beefed up the radio for cell signal or something along those lines yet they left out "their" code for doing the same thing for rooted phone on purpose? Don't get me wrong I do love this phone rooted or not (which I currently went back to stock without root tonight)
My reason for bringing this up is this. While I was un rooted (regardless of seeing LOS or not which I did) I noticed a few things between stock and root when it comes to phone signal. Even before rooting I've never really had many issues with my phone in my APT never once had LOS yet after rooting I did. I normally put my phone in one spot while I'm on my computer I don't pay attention to it much cause if I'm online I normally am not going to be on my phone yet after rooting the other day and doing what I normally do with my phone a few hours later I went to leave and picked up my phone and noticed I had a LOS and it had been there for awhile.
Now this is normally a spot where I get full 3G bars and NEVER have any issues at all yet after rooting it showed up. After going back to stock tonight I did what I would normally do and no LOS in sight. It honestly makes me wonder while I know a few people are having the LOS issue even with the stock rom (I've had it) it would seam that after rooting it comes it far more often then not which I find very odd why would "root" cause this issue and on top of that why would the 3G signal actually drop from Full bars to 2-3 bars in the same spot. It's almost like Samsung in general did something with the Android Source and the radio together to kind of deter people from rooting.
I dunno just some thoughts I had mind you it is 5am here and I am a little tired so not all of my thoughts are totally there and kinda scatter brained but this just crossed my mind and figured I would bring it up and see what others might think about this.

Seriously, you wasted all that time posting this this when you should have just went to bed?
Next time you have the choice to post something like this or to just go to bed, choose go to bed...
-> eman is very mean this morning. I need to be nice, it's Thanksgiving and all my posts since I have awoken have just been mean!
Going to try and be nice the rest of the day! Happy Thanksgiving everyone!

Yes thanks for being an ass and not even actually contributing anything. Great work in that department.

Update your modem to eg31, go back to stock kernel. If you have los go into task manager and clear ram to get rid of los. That's all we can do now to limit los until we get another modem update. Los happens if your rooted or not, some more than others
Sent from my SPH-D710 using xda premium

Ontop of the los its bad enuff that samsung makes poor radios in general compared to moto and htc.. i believe even if the los is fixed the ooor radio build that samsung is known for will still contribute to problems ... if they had the radio strength of the photon the epic touch would be far superior ...but until then we need a phone to function and act as a phone and sgs2 wont ...
Sent from my MB855 using XDA Premium App

cidica said:
What if Samsung actually did something within the kernal itself
Click to expand...
Click to collapse
Nice thought, but the reality is that there many, many stock phones with LoS. The only reason that there appears to be more issues with rooted phones is that most rooted users are using custom kernels. Go to a stock kernel and watch your LoS drop back to the same level it would be on a non-rooted stock phone. I have the luxury of having a stock phone in the house along with my rooted one and I have been able to verify this in realtime on an ongoing basis. To the point that I can definitely say that my wife's stock E4GT experiences twice as many LoS incidents as my rooted E4GT running the Rogue Stock 1.1 kernel.
paranoid android85 said:
Update your modem to eg31, go back to stock kernel. If you have los go into task manager and clear ram to get rid of los. That's all we can do now to limit los until we get another modem update. Los happens if your rooted or not, some more than others
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I couldn't disagree more! DO NOT update to the EG31 modem and then go to stock kernel. You may be asking for trouble and since there is no going back from EG31, you could be stuck in a bad way as many have reported.
What you want to do is flash a stock kernel with your current setup and give it a few charging cycles/days to settle in and see if that helps. If not try some of the other posted fixes for data and signal. There are many. Some in my signature.
If none of those work and you feel like you have too many LoS experiences and poor data, then you could try flashing EG31 to see if it helps (knowing in advance that it is a one way ticket and you'll be stuck on that modem until someone figures out a way to provide the EG30 modem or some official source is released.) Might also make it difficult to return the phone for any reason as you will never be able to get back to showing the stock EG30 Baseband in the About phone menu (though most techs won't be savvy/care enough to check.) EG31 works great for me, but it does not for many others.
It's been crazy watching people flashing modems for no good reason and then *****ing about the outcome.
Reading first is better than flashing first 100% of the time.

Haven't had one Los on stock kernel, vipers fix works. End. feels good to be unbanned and able to help
Sent from my SPH-D710 using XDA App

OP, while we do appreciate your efforts in the brainstorming department you could have picked one of the hundreds (literally) of threads discussing this to post in.
A few things:
1.) Rooting does not cause LOS
2.) Stock phones get LOS
3.) Custom Kernels seem to increase LOS occurance
4.) You can be rooted with the stock kernel (and have the same frequency of LOS as pure stock)
5.) Some people are more heavily affected than others
6.) Being in a fringe service area seems to make it worse for some but not others
7.) This has all been discussed ad nauseum
A few other things:
1.) mkasick built a kernel to be as-stock-as-possible. I ran it for almost 2 weeks without a single LOS. I am now running it again. I got less LOS than stock (which was infrequent but did occur), but, I'm going to stick with calling it 'as good as stock' LOS performance.
2.) chris41g has integrated the changes mkasick made into LoSTKernel experimental builds. Others may have as well.
3.) Different phones seem to have varying levels of susceptibility in the same physical area with the same configurations...It appears there may be a hardware component to some units.
4.) Whether Sprint/Samsung's update can address all of these issues (if they are even separate issues at all) remains to be seen.
5.) Don't screw with flashing modems unless you know what you are getting yourself into. (I, personally, am having an awesome time with EG31 modem and mkasick's kernel....others are experiencing nightmare LOS with stock kernel). There is no going back to EG30 modem yet
sage

daneurysm said:
OP, while we do appreciate your efforts in the brainstorming department you could have picked one of the hundreds (literally) of threads discussing this to post in.
A few things:
1.) Rooting does not cause LOS
2.) Stock phones get LOS
3.) Custom Kernels seem to increase LOS occurance
4.) You can be rooted with the stock kernel (and have the same frequency of LOS as pure stock)
5.) Some people are more heavily affected than others
6.) Being in a fringe service area seems to make it worse for some but not others
7.) This has all been discussed ad nauseum
A few other things:
1.) mkasick built a kernel to be as-stock-as-possible. I ran it for almost 2 weeks without a single LOS. I am now running it again. I got less LOS than stock (which was infrequent but did occur), but, I'm going to stick with calling it 'as good as stock' LOS performance.
2.) chris41g has integrated the changes mkasick made into LoSTKernel experimental builds. Others may have as well.
3.) Different phones seem to have varying levels of susceptibility in the same physical area with the same configurations...It appears there may be a hardware component to some units.
4.) Whether Sprint/Samsung's update can address all of these issues (if they are even separate issues at all) remains to be seen.
5.) Don't screw with flashing modems unless you know what you are getting yourself into. (I, personally, am having an awesome time with EG31 modem and mkasick's kernel....others are experiencing nightmare LOS with stock kernel). There is no going back to EG30 modem yet
sage
Click to expand...
Click to collapse
Yeah, I got lucky I guess. I am one of those who has better results on EG31 but I wasn't at first. I was quietly regretting my decision until Chris updated the kernel to EG31 w/CWM5. If you aren't having severe LOS then stay put and experiment with different kernels. I was not happy for a few days as I didn't have LOS to begin with, I thought it was the fix and jumped in immediately. Thankfully things have really stabilized and actually improved for me
Sent from my Nexus S 4G using Tapatalk

JohnCorleone said:
Yeah, I got lucky I guess. I am one of those who has better results on EG31 but I wasn't at first. I was quietly regretting my decision until Chris updated the kernel to EG31 w/CWM5. If you aren't having severe LOS then stay put and experiment with different kernels. I was not happy for a few days as I didn't have LOS to begin with, I thought it was the fix and jumped in immediately. Thankfully things have really stabilized and actually improved for me
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
I took a few days to think about it and gauge the responses from others since I actually have almost no LOS problems stock, none on mkasick's kernel and very very very few on LoSTKernel exp. But the vast majority of issues seemed to be from people who were on a custom kernel. The rest that were on stock kernel seemed to match the percentage that is screwed no matter what so I jumped in. I'm glad I did. I haven't ventured off of mkasick's kernel, LoSTKernel exp will be next up. That kernel just flies...
Either way Wifi and 3G performance is better, but, I would not recommend anyone to flash EG31 modem...make risky decisions on your own.

daneurysm said:
I took a few days to think about it and gauge the responses from others since I actually have almost no LOS problems stock, none on mkasick's kernel and very very very few on LoSTKernel exp. But the vast majority of issues seemed to be from people who were on a custom kernel. The rest that were on stock kernel seemed to match the percentage that is screwed no matter what so I jumped in. I'm glad I did. I haven't ventured off of mkasick's kernel, LoSTKernel exp will be next up. That kernel just flies...
Either way Wifi and 3G performance is better, but, I would not recommend anyone to flash EG31 modem...make risky decisions on your own.
Click to expand...
Click to collapse
Yeah, fortunate for us, it has worked out for the better but if you do it, know that you have to live with your decision until the next update or go to EG12.
Sent from my SPH-D710 using Tapatalk

Running lost kernel on my Refurb e4gt and I've only had Los 3 times. My old phone with zedomax would loss almost every other day
Sent from my SPH-D710 using Tapatalk

nacron said:
Running lost kernel on my Refurb e4gt and I've only had Los 3 times. My old phone with zedomax would loss almost every other day
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
How does the stock kernel fare?

daneurysm said:
OP, while we do appreciate your efforts in the brainstorming department you could have picked one of the hundreds (literally) of threads discussing this to post in.
A few things:
1.) Rooting does not cause LOS
2.) Stock phones get LOS
3.) Custom Kernels seem to increase LOS occurance
4.) You can be rooted with the stock kernel (and have the same frequency of LOS as pure stock)
5.) Some people are more heavily affected than others
6.) Being in a fringe service area seems to make it worse for some but not others
7.) This has all been discussed ad nauseum
A few other things:
1.) mkasick built a kernel to be as-stock-as-possible. I ran it for almost 2 weeks without a single LOS. I am now running it again. I got less LOS than stock (which was infrequent but did occur), but, I'm going to stick with calling it 'as good as stock' LOS performance.
2.) chris41g has integrated the changes mkasick made into LoSTKernel experimental builds. Others may have as well.
3.) Different phones seem to have varying levels of susceptibility in the same physical area with the same configurations...It appears there may be a hardware component to some units.
4.) Whether Sprint/Samsung's update can address all of these issues (if they are even separate issues at all) remains to be seen.
5.) Don't screw with flashing modems unless you know what you are getting yourself into. (I, personally, am having an awesome time with EG31 modem and mkasick's kernel....others are experiencing nightmare LOS with stock kernel). There is no going back to EG30 modem yet
sage
Click to expand...
Click to collapse
+1 Pretty much wrote the same thing one post above yours. I think it is very good to repeat this point over and over. I can't believe that people still flash **** without any pause nearly 4 years into Android's public existence. I've spent the entire week helping people who flashed the EG31 modem without even knowing what a modem is or what it does. And then seeing people recommending EG31 left and right as a fix for everything from slow data to gout. Of course not warning anyone of the fact that this is a flash of no return. It's crazy.
Sent from my SPH-D710 using xda premium

There has been a development today on the LoS issue, someone in the dev thread (sorry, don't remember their name at the moment) found some interesting things in the logcat that occur only when LoS. I plan to work on the script tonight and get another build out. Stay tuned

-viperboy- said:
There has been a development today on the LoS issue, someone in the dev thread (sorry, don't remember their name at the moment) found some interesting things in the logcat that occur only when LoS. I plan to work on the script tonight and get another build out. Stay tuned
Click to expand...
Click to collapse
It was trifthen and yes he did find some interesting info. I am very curious to see what happens when you integrate that into LoS Checker.
I also have to say that you continue to impress with your unending spirit of cooperation in everything you do. I remember that same spirit everytime you were around at MIUI.us and was appreciative of it then as I am now. More about advancement, less about ego. We need more devs like you viper.

daneurysm said:
How does the stock kernel fare?
Click to expand...
Click to collapse
In the few hours I was running stock kennel I didn't get los lol
Sent from my SPH-D710 using Tapatalk

nacron said:
In the few hours I was running stock kennel I didn't get los lol
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That's all I'm sayin', lol.

Spoke too soon, rebooted my phone 4 times in the past 2 days for los
Sent from my SPH-D710 using Tapatalk