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.
Related
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
Has it been COMPLETELY confirmed by those that only get LOS on custom roms...when you return to stock does everything go back to normal completely? I STILL havnt rooted my phone and installed a custom rom but I think im ready for some custom rom and black and blue themed goodness. Is it becoming more worth it now?
It has been mostly proven that neither kernels nor roms cause los. It is simply the phone itself and the network area you are in. Not all phones are created equal....
+1 cause its time for a custom rom
Sent from my SPH-D710 using XDA App
I got LOS before I rooted my phone. Stock rom stock kernel no root and had LOS
jase33 said:
It has been mostly proven that neither kernels nor roms cause los. It is simply the phone itself and the network area you are in. Not all phones are created equal....
Click to expand...
Click to collapse
Right, this of course is one of those things thats still SLIGHTLY shrouded in I guess whats classifiable as a mystery. Im really just trying to verify that those who DID have problems only when on a custom rom, that those symptoms were remedied by going back to stock. Im really more a less trying to convince myself that even if i wade out into the waters of custom roms and i by chance DO encounter a problem, a stock flash would be the cure all.
rrmzr1 said:
+1 cause its time for a custom rom
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
lol
10 char
I got it before...then after rooting and adding a custom rom + kernel. After flashing Chris's LOStKernel 1.0.0.2 and the modem over Starburst 1.7 I went a week without an LOS. Then I flashed to Viperboys ROM, and started getting them again. Went back to my Nandroid backup, and now I am 2 days without LOS again...... So not sure it is strictly the Phone itself.
Starburst ROM with lost kernel = very little LoS
Sent from my SPH-D710 using XDA App
dkpaladin said:
I got it before...then after rooting and adding a custom rom + kernel. After flashing Chris's LOStKernel 1.0.0.2 and the modem over Starburst 1.7 I went a week without an LOS. Then I flashed to Viperboys ROM, and started getting them again. Went back to my Nandroid backup, and now I am 2 days without LOS again...... So not sure it is strictly the Phone itself.
Click to expand...
Click to collapse
BAH, this is what I keep throwing back and fourth in my mind. Lol I havnt had a LOS yet...and im just afraid that after i root and do stuff to the phone....itll be a bug fest :\
I had LOS a few times before rooting (I was only stock for about a week, if I remember correctly). After Rooting and using custom kernels, it got worse. depending on which custom kernel, it could be between 5-20 times in a day. I was very frustrated. I never did go back to completely stock. I tried every kernel that was in these threads. I found 2 that work for me flawlessly. I haven't had a LOS issue since I switched to either of the 2 "Stock Pulled Kernels". I am currently on and have been since flashing the one with CWM. I am still rooted and running the Midnight ROM. I am also rocking the v6 supercharger script with setting 6 and the ACS AIO Mod. I have had the Android OS bug since day one and today I formatted my internal and external sd cards to see if that improves. More than one user claims that it has for them so, my fingers are crossed. I still get decent battery life for how I use it, anyway. If you flash a ROM or kernel, you can always go back to completely stock or partially stock. You really have nothing to worry about. Get a usb jig for a few bucks and it will put you even more at ease. Good luck and happy flashing.
No offense but this is asked daily, a little reading.
Developers have stated that it is a problem with the phones firmware.
It has nothing to do with rooting.
Or Sprint's network.
Or the color of your shoes.
LOSt Kernel is recommended until Samsung gets off their ass.
Doing well here. No LOS ever since purchase on launch day. Rooted a week ago with stock rom and root and no change to kernel. Still no LOS. I work by traveling all over the US and no issues there either.
Sent from the EPIC Touch
I know this has been said before, but I just wanted to get my opinion in! I have flashed almost everything out there on my phone, and read everything on the LOS issue and I'm pretty sure it has very little to do with the rom/kernel. Maybe the rom/kernel could make it worse...but I haven't seen any actual cases of that with the current selection of custom software. It's gotta be the modem software, no? Which I'm pretty sure is totally separate from the rom/kernel.
jedwardmiller said:
Doing well here. No LOS ever since purchase on launch day. Rooted a week ago with stock rom and root and no change to kernel. Still no LOS. I work by traveling all over the US and no issues there either.
Sent from the EPIC Touch
Click to expand...
Click to collapse
Same here. Got 2 LOSs while testing a kernel. Went back to stock kernel with root and zero issues since launch day
Sent from my Nexus S 4G using xda premium
Everyone has there own opinion on the situation. My opinion is once you root this phone, going back to stock right now is not the same as a stock phone that has not been rooted.
On my first SGS2 I did not see an LOS until the day I rooted. Exchanged for a new phone because of it and I have had my replacement for 2 weeks now and have not seen an LOS on it.
I will not be rooting this one unless I see an LOS pop up to prove to me it happens on un-rooted phones. I know people have made the claim but I have not seen it.
Who knows, maybe on stock, LOS does happen but maybe signal comes back on it's own so that is why I haven't seen it. Anyway, this phone is still amazing running stock. I get great battery life and it is zippy as anything. Now if an ICS working Rom pops up soon, that will be one tough decision on what to do.....
Also, I though after about 2 weeks a a device is out a true stock Odin from either Sprint or Samsung leak out. I do not believe we have seen this yet and correct me if I am wrong, but isn't that truly the only way to return this phone like it was out of the box?
[email protected] said:
Also, I though after about 2 weeks a a device is out a true stock Odin from either Sprint or Samsung leak out. I do not believe we have seen this yet and correct me if I am wrong, but isn't that truly the only way to return this phone like it was out of the box?
Click to expand...
Click to collapse
If you Odin this and do a factory reset, you will be back to complete stock.
ran mine stock the first couple days with no LOS. tried a couple of Zedomax's roms, and started getting daily LOS. Went to the pulled stock kernel, over 3 weeks now, not a single LOS.
My wife's E4gT is stock.. mine is on Starburst 1.7 which includes the LoSt Kernel. She gets LoS about once a day... I have had 2 since switching to the Lost Kernel over a week ago.
I got LOS within 4 hrs of receiving the phone (stock obviously). Searching the forum reveals that this issue affects all phones, rooted or not. With all the purported solutions, YMMV.
Sent from my SPH-D710 using XDA App
I've had my Epic Touch 4g for about 3 weeks now and I have noticed something outside the normal LoS threads I've seen lately. I only seem to get LoS when I flash kernels, mainly ones with CWM 4 or 5 or ones that are rooted.
The issue clears up as soon as I flash the stock EG30 rom. It's the same deal with either EG12 or EG30 modem.bin.
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App
I better hurry and comment before this one gets locked.
I've owned the phone for a little more then 2 weeks. I have had a total of 4 LOS events. 3 with a Zedomax kernel(all in the same day) and once with the latest lost kernel experimental. For the last week the lost kernel stable has had none. Can't comment on unrooted los because my phone was only stock for 15mins after unboxing.
haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol
playya said:
haha yea my phone lasted 15 minutes as well from my boys house to mine..lol @OP I am not sure how much reading you do on here but I hear a whole lot of stories of people who get LOS and there phone has been untouched. I have a friend who has had the phone for a month or so and has only had 3 LOS but all from the same tower(phone rooted).
Don't try and figure it out, sit back and wait for an answer, return your phone if you like or sell it but unless you are a developer or know about phone software and you have a solution. I personally think we should refrain from making statements we are not 100% sure about. IMHO
NoT trying to be disrespectful but its a pretty touch subject in here and honestly you are like the millionth person to say the same thing in a new thread....lol
Click to expand...
Click to collapse
+1
10 char
alex6969 said:
Not really looking for answers, I can wait a few weeks for you guys to work your magic. I just wanted to set a precedent with my own experiences.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
As far as "here's my proof with evidence in anecdotal form" is concerned, that precedent has already been set.
The facts are this:
1.) Untouched stock units have had LOS (mine included).
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
3.) Kernels built from said source seem to exacerbate the problem
4.) You can have root AND the stock (pulled) kernel.
5.) Root binaries and/or busybox do not cause LOS.
6.) rooted+stock kernel installs seem to have the same occurance of LOS as bone stock, uninformed alarmist anecdotes notwithstanding.
7.) This has been covered in over 9000 threads already. Please search in the future.
8.) Samsung and Sprint are aware of the issue (in stock phones) and are issuing inconvenience credits if pressed and are supposedly working on a firmware to fix the issue.
Please pass this information on to the next student of science who presents his "proof" of this "discovery", as there will likely be more.
Now how do you like them apples ......my boys wicked smart .....
Good will hunting
But seriously please search and find the previous 50 threads that say the same uninformed thing ... If it was only a root thing would Samsung be fixing it ..... Hell no
Sent from my SPH-D710 using xda premium
I have had my phone since launch day and have only had LOS one time when it tried to go into roaming and never got back a signal. That was shortly after I rooted with a stock kernal. I have not had LOS since but I have never flashed a custom kernal or ROM. The phone has been mostly trouble free.
Where did you find the EG30 modem bin?
Ditto. WTF SamSprint?
daneurysm said:
2.) Samsung seems to have released incomplete source. What is missing (whether it is in the source or in tool-chain/build parameters) is unknown.
Click to expand...
Click to collapse
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
daneurysm said:
3.) Kernels built from said source seem to exacerbate the problem
Click to expand...
Click to collapse
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
Thanks for the informative post.
I've been on Starburst+LoSTkernel for almost a week now with no problems. Before that I was strictly a pulled-stock kinda guy given my experiences. But I'll give that a shot and let you know. I get very infrequent LoS with stock kernel, though they do happen once every 2-3 weeks...usually a few times that one day. So, in a few days of very routine use (location/tower/times always the same, to a tee) I'll have a pretty good idea, assuming randomness doesn't factor into it as much as it could.
mkasick said:
I looked into this more late last week. The kernel source is complete. I'm not certain that it's unmodified, but I'm no longer certain it's modified either. The majority of the difference between EG30 and source-built kernels is a bunch of debugging options that Samsung left enabled in the kernel defconfig--options that alter the core behavior of the kernel enough to plausibly exacerbate a code bug.
I posted a source-built kernel that's as close to stock EG30 as possible, but I've not gotten any feedback on it. Does someone dare to try?
Click to expand...
Click to collapse
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
I do get reboots after I get some texts, but, every other kernel (even stock) was doing this...I think it's the ROM...so, don't even worry about that. Later I'll nandroid back to my original stock install and flash this kernel on top and report back.
daneurysm said:
I've been using it since I posted my last reply last night. No more LOS than stock so far...and typically with the Samsung-source compiled kernels I've used I would have seen at least one by now.
Click to expand...
Click to collapse
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.
mkasick said:
That's good news.
My goal with that kernel is to just be stock, so if it's indistinguishable from stock behaivor wise, that's a good thing.
LoStKernel may have made much of the source-based problems irrelevant. But perhaps the defconfig changes may still prove useful.
Click to expand...
Click to collapse
Just to keep moral up I want to specify that "no more LOS than stock" means "stock rarely gets LOS and so far I have gotten absolutely none."
Good work man, thanks for the effort.
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
I updated to EK02 radio yesterday and got 2 Los the same night. Full circle with line. Went from EG31 to EG30 then updated to EK02...
Anyone else? I'm wondering if mix matching with this particular build causes issues.
Calk's 1.5a + rogue 1.1.3 + EK02.
Sent from my SPH-D710 using Tapatalk
Duce HD2 said:
I updated to EK02 radio yesterday and got 2 Los the same night. Full circle with line. Went from EG31 to EG30 then updated to EK02...
Anyone else? I'm wondering if mix matching with this particular build causes issues.
Calk's 1.5a + rogue 1.1.3 + EK02.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
That's a good question. I think that different ROM\Kernel\Modem combos definitely work better that others. You can always try a different modem and\or kernel and just play around with that until you find one that works best. Flash trifthen's LoSD script. I get LoS roughly twice a day and each time the LoSD script is able to repair the radio without having to reboot my device which is great. So once it detects LoS it's maybe 30 seconds I'm without service and even then I usually still get my texts\VM's.
http://forum.xda-developers.com/showthread.php?t=1374560
Thanks. I usually don't get Los using EG31 radio with my current set up. It was just weird that after updating to the "fix" I got Los twice... Lol. I really didn't see people reporting it after updating,
Now I'm back on EG31 cause I can't risk Los. I'll give it another shot once I move to all EK02.
Sent from my SPH-D710 using Tapatalk
I don't think the radio plays a big part on LOS. I think it is mostly the kernel. Best combo would be the ek02 modem and ek02 kernel.
Sent From My Evo Killer!!!
Weird I would always get los at, two places on my bus ride yo and from school since I flashed ek02 modem it hasn't happened. I
Duce HD2 said:
Thanks. I usually don't get Los using EG31 radio with my current set up. It was just weird that after updating to the "fix" I got Los twice... Lol. I really didn't see people reporting it after updating,
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I've only been testing the EK02 modem a few days since I wanted to wait until there was a way to flash back to the EG30. So far I haven't really noticed much of a difference at all. My 4G speeds have always been good but connection has been sketchy (maybe because of all the buildings in downtown Portland?). 3G speeds are still awful but the phone signal is good as I never have dropped calls. LoS has been pretty consistent but I notice that if I don't switch between 3G\4G\Wifi I usually don't get it at all.
Yes I'm willing to put up with all this **** just for unlimited data
Duce HD2 said:
I updated to EK02 radio yesterday and got 2 Los the same night. Full circle with line. Went from EG31 to EG30 then updated to EK02...
Anyone else? I'm wondering if mix matching with this particular build causes issues.
Calk's 1.5a + rogue 1.1.3 + EK02.
Click to expand...
Click to collapse
Please see:
http://forum.xda-developers.com/showthread.php?t=1382189
crzchn said:
Please see:
http://forum.xda-developers.com/showthread.php?t=1382189
Click to expand...
Click to collapse
I got LoS on the completely stock ROM too. So while I'm not saying the ROM's aren't playing a part I think dude should have just made a request for a stock EK02 ROM\Kernel to test that theory. To make a thread like that is just ****ty.
Duce HD2 said:
I updated to EK02 radio yesterday and got 2 Los the same night. Full circle with line. Went from EG31 to EG30 then updated to EK02...
Anyone else? I'm wondering if mix matching with this particular build causes issues.
Calk's 1.5a + rogue 1.1.3 + EK02.
Click to expand...
Click to collapse
Try upgrading to Calkulin's 2.x ROM which is based off the EK02 OTA release.
Just flashing the modem is by itself not going to change anything regarding LOS. It's probably your kernel. People reported a lot of LOS on Rogue 1.1.3. SH just posted a kernel update that includes the EK02 source changes, v1.3.0. I'd flash that and see how it goes. While you're at it, you may want to consider updating to Calk's EK02 based ROM as well.
That's kinda what I was thinking about the kernel playing a bigger part on los, probably helps having the matching radio with it?...maybe?
I think I'll give Calk's latest release today... Time to upgrade.
Sent from my SPH-D710 using Tapatalk
What do you guys suggest as far as kernel goes? Chris41g's EK02 stock rep? Or Rogues stock EK02?
Sent from my SPH-D710 using Tapatalk
Duce HD2 said:
What do you guys suggest as far as kernel goes? Chris41g's EK02 stock rep? Or Rogues stock EK02?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Depends on if you want a stock or custom compiled EK02 kernel. So either of these two should work well (I would start with Rogue's latest custom kernel ... if you get LOS move to stock) ...
Custom: http://forum.xda-developers.com/showthread.php?t=1341564
Stock: http://forum.xda-developers.com/showthread.php?t=1368207
Duce HD2 said:
What do you guys suggest as far as kernel goes? Chris41g's EK02 stock rep? Or Rogues stock EK02?
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
I would try them both. I am on a 2.3.4 ROM and I am having the best results with EG31 modem and Chris's EK02 kernel.
Sent from my SPH-D710 using xda premium
Thanks guys, just had another Los on EG31 wtf Lol. It has to be related to kernel, cause I've flashed a couple different ones to try out yesterday, and ever since Los is my friend now. So maybe the EK02 radio had nothing to do with it.
I like custom kernels, so I'm giving rogue 1.3.0 a shot. If not, Odin bts and start fresh again.
Sent from my SPH-D710 using Tapatalk
LOS... Might as well be POS...
I went back to bone stock, no root EG30 so I could take the OTA. Took the OTA and left the phone completely stock. That very day I got 3 LOS back to back in about an hour. Next day 2 LOS back to back within about an hour.
EK02 didn't fix LOS. WTF, Samsung?
This is my first Samsung device (that I kept) as I returned my first POS called a Nexus S. This will be my last.
I love the phone otherwise, though.
First post. Seemingly unique problem.
Hi everyone,
I have been reading several posts on the XDA, and would like to thank everyone for the wealth of knowledge and willingness to share it.
I don't mean to hijack the thread, but this is the closest thread subject to my problem, that I could find, without starting my own thread.
I had no issues with LOS or poor battery, etc. with the stock phone at all. The only thing that I noticed was that the wifi would quit working after a few mins, and I would have to toggle it a few times (2-5 times) and it would start working again. Then when the EK02 update got pushed to the phone I noticed a few things were different. I seemed to get GPS lock a lot faster than before, and the other thing was that the wifi connection would get disconnected very frequently (once every 120-180 seconds). And since the phone was constantly disconnecting/hunting/reconnecting the wifi, my battery life took a big hit (was reduced to 1/3 - 1/2 of what it was before)
I tried several modem/kernel combos (Calkulin's) but nothing would fix the problem (other than reverting back to bone stock EG30 modem and rom).
Has anyone else experienced something similar? Especially after the EK02 update? Or does anyone have any ideas about why this might be happening?
Any help/clues are greatly appreciated.
--K.