I dont think im the only one with LOS after EK02, correct? Lately it almost seems worse. When i leave the 4g on all day long, I can't tell if I am experiencing a LOS until I turn it off.
For example, I was able to browse the web this morning, but when i turned off my 4g, the 3g icon never returned - so i rebooted my phone. Of course after i rebooted my phone, i'm receiving text messages that I missed during the LOS. This phone is starting to really piss me off. I was happy with it for the first few months, but now it has become a real pain. People think you are ignoring messages. My phone is completely stock, and if there is a rom that works to solve this, i'll be rooting today.
I can't say I blame you for your frustration. A new modem has been leaked called EL13 that you can get here.http://forum.xda-developers.com/showthread.php?t=1389874
People are having success flashing it on top of the stock ROM with EK02 update that you now have. I plan on trying it today.
Just my personal experiences. The only time I got a LoS on the EK02 was when i was running SetCPU and had messed with the Voltages. Once I reset Voltages back to stock rom voltages or removed SetCPU, regardless of rom my LoS issues always went away. Again this is only my experiences and in no way reflects what may be the root cause of the issue on the EK02 rom. I was clearly setting something to low for the phone to maintain service is all I was trying to point out.
Related
Yes, I know, another LOS thread. I wanted to have a spot where we could place symptoms and possible solutions. Quite of few ideas are floating around but are attached to other threads.
First, my own experiences.
I had the problem before rooting and after rooting (using Zedo's kernel).
I can duplicate the issue 100% of the time by taking my phone to work (a big metal warehouse) where I usually have little or no signal. During the work day I experience LOS. When I leave the building, the phone will not recover without a reboot. I had the poor signal issue before I got this phone, so I know the building causes that part.
During the day I will see Error 67 messages periodically.
Checking phone status usually indciates I am in service, not roaming, not connect to the network. The signal strength is -101 dBm 0asu.
Sometimes after LOS and before the reboot, the phone looks to have a good signal but attempting to make a phone call results in a screen with a green bar at the top (see image below)
If I am in the middle of a call and leave the service range of my Airave I use at home, I sometimes experience LOS and the green screen. Reboot is required.
From reading various threads and from personal experience, i believe there are different types OF LOS bugs floating around. For me, I only experienced the LOS bug when i was on a custom kernel. When it occurred, the top bar had a circle with a line through it. No signal bars and the only workaround was a reboot. I think also in status service and signal would say unavailable but would need to verify
Sent from my Epic Galaxy S2
*LOS twice in 6 days.
*Both times it seemed to happen upon wake. Once the screen was off but music was playing so I doubt the phone was in some sort of deep sleep.
*Switching airplane mode on and off fixed it for me.
*I'm not rooted
*My signal was fair, not great but not zero either prior to LOS.
Sent from my SGS2
krazyflipj said:
From reading various threads and from personal experience, i believe there are different types OF LOS bugs floating around. For me, I only experienced the LOS bug when i was on a custom kernel. When it occurred, the top bar had a circle with a line through it. No signal bars and the only workaround was a reboot. I think also in status service and signal would say unavailable but would need to verify
Sent from my Epic Galaxy S2
Click to expand...
Click to collapse
This is exactly what happened to me. Maybe it's just coincidence but it never happened before I rooted or when I used a rooted stock kernel.
I started seeing LOS upon installing CWM (no kernel). Ever since I ODIN the stock kernel (which took out CWM and removed nasty yellow icon from the boot screen) several days ago, I have not seen LOS
There are already multiple discussions about LOS and everyone's own analysis of it. Let's boil this down to two things:
1. Sprint is aware of the issue and have it documented by myself and a few others.
(http://community.sprint.com/baw/message/341145#341145)
@Everyone who volunteered to help out in providing additional information and logs: thank you so much, received great examples and response from everyone and it helped expedite getting this issue identified and properly documented, it will be resolved in the next maintenence release.
Click to expand...
Click to collapse
2. This is not caused by rooting. Any experience on your part to suggest so is purely happenstance. Many were in such a rush to root that they didn't bother to use their phone long enough in a purely stock state to see this issue. Now I won't say that any actions on your part (flashing a kernel, etc.) couldn't have exacerbated the issue - but it is not caused by rooting. It is a pre-existing condition with the radio firmware that will be resolved soon.
Mmk.?
Closing this thread - contribute in the other threads already doing the same thing.
I am running the Blu Kuban, and have been having problems with talk failing and random reboots. I follow the Rom posts from devs pretty regurly. I have seen that Ruj, and others reccomend removing the themed version of talk, and installing the stock version that is availble in the Rom updater. I tried this about a week ago, but even after fixing permissions in the recovery my phone would keep restarting till I reinstalled the rom. I was working just fine after a fresh, and wiped out install up untill a few days ago. I am getting the messages again that my talk app is failing, or sometimes not responding. It was not untill I started messing around with goveners that I started having this issue. I had the default hyper after install, but switched it to wheatly. It was not untill I switched to hotplug two nights ago that I have been having issues with talk. I was having the same problem with the newset Kuban kernal with random reboots of the phone, and thought it was with govener, as that is all I have changed in Ex tweaks. The mods I have installed are; Blank pull down, No rotate/no landscape/no crt, In call sms notification, and finally no battery bar. My restarts of the phone have been random, they can be from anything from loading facebook, turning on wifi, adjusting phone volume, to even putting phone to sleep. I guess after my long rant of problems is there anything that I can do differently to make phone run better? I am not overclocking or underclocking. Have not played with voltages. I turned my screen off profiles off too. I am thinking that unless it gets worse, I will wait for Ruj, to release any new kinds update. Is it the kernel that is giving the problem? I saw someone posted to try older kernel version, is that very dependable?
Also I know this post is getting pretty long, but can someone please tell me if there is any sort of geographical list of modems that work best in certain area's? http://forum.xda-developers.com/wiki/Samsung_Epic_4G_Touch/Modems this showed me that there is a bunch to try, but I want to know which ones work best in area before I go messing around. Does Sprint use different ones in different locations is what I am asking about modems.
There is a talk fix in the 4th post of the faq.
As far as the modems, they are kind of a subjective choice. My phone is best on fg20 and my wife uses fe22. You just goes try them all until you get one you like. I currently use the latest Kuban kernel and do not have any reboot issues. If you keep having issues I would recommend a fresh install or setting extweaks back to the defaults, then making adjustments one at a time until you are happy with the setup.
I ran a couple of searches on Google( and in this forum) to try and find the original thread about this issue, however I didn't find it so I'm posting here in case anyone else can be saved by this fix.
First, some background:
I have been running CM10 Nightlies for almost a month now, also using the leaked Jelly Bean radio version T999UVLI2 with absolutely no problems. Everything was working great, data, ROM, etc. (Prior to that I was on Stock ICS, rooted. Had not run any custom ROMs whatsoever).
I noticed after flashing the latest CM10 Nightly (Oct. 14) that my phone had started acting a little weird - nothing drastic mind you, just a few glitches here and there. The weird thing was, all of the previous nightlies I had flashed pretty much worked flawlessly for me, minus a volume issue when in-call which was a known bug. I had done a clean flash as I always do, so I attributed the glitches to a possible bug or two in the latest Nightly and figured it would probably be resolved in the next release. No big deal.
Yesterday afternoon, after reading a thread that is tracking all available T-Mobile radios by region (to see what works best in your area) I saw someone who posted that the T999UVLI3 radio gave them the best speeds, and they happened to live in the same exact city as I do here in Southern California. So I decided to flash the new radio using Team Sonic's Modem flasher, which I used in the past to flash the LI2 radio that I was currently on. I flashed the T999UVLI3 radio and found that it did indeed provide better data speeds than the LI2 radio, so I was pretty happy about that. Used my phone all day/all night with no problems, everything was great.
I always leave my phone plugged in at night so that I have a fresh charge in the morning - this morning I turned off my phone while it was still plugged in as I leave it off during the drive to work to save a little battery before I start my day. Typically I unplug it first and then turn it off, but not always. So nothing really out of the ordinary there.
I get to work and turn on my phone, and all of the sudden I notice that I have no bars - at all. It doesn't say "T-Mobile" at the bottom of my lock screen. I figured it was just taking it's time booting up, which would be very weird as it never does that, but I waited. And waited. Nothing. Now I'm starting to get a little worried.
Went into settings and checked "About Phone" and it said my Baseband version was "unknown". Oh crap. IMEI, unknown. Serial number, unknown. GREAAAAT
For the life of my I couldn't imagine how this could happen when I didn't even do anything from last night to this morning. I started going over everything I had done recently to my phone.. the power off while plugged in, the nightly update to the Oct 14 build, then it hit me.. the new radio version. Maybe that was it
In a desperate attempt I booted into recovery and ran Team Sonic's Modem Flasher and flashed back to T999UVLI2. Rebooted the phone and... BAM! Back to normal. W...T...F..?
If anyone loses their IMEI, before going through the entire injection fix process, try reflashing a radio. Worked for me!
Any theories on why this happened? Many people have been using the T999UVLI3 radio, I believe without any issues.. but I could be wrong. Anyone flashed that radio and lost their IMEI?
I am currently having some data connectivity issues with my E4GT. I have been running the Blu Kuban rom for some time now and have been a huge fan of it, but now my phone is acting really weird (no fault to the rom at all). First my GPS wouldn't lock as I thought this was kernel related I re installed the Blu Kuban rom with both of the other kernels and still couldn't get a GPS lock. Since I use GPS daily for work I went back to my classic Epic Venum rom and the GPS worked albeit poorly, it got me through the day. When on this rom whenever I used data my phone would drop down to zero percent battery and power off, this seems to occur only over 4g/3g and not over wifi. I tried flashing multiple modems from EG30 to FI27 on a multitude of roms (both GB and ICS) and using desktop Odin, but I cannot figure out what is causing my phone to crash (which now occurs consistently). I tried installing new roms (currently on AOKP build 37) which works great until the data is used and then it crashes again. I don't think this is cause from any specific rom, and I am now fearing it is a hardware issue. To summarize GPS now works, using data causes my phone to crash regardless of the rom used. Just thought I would ask the community, any help would be greatly appreciated. Thanks!
Update: I ended up restoring to stock to see if that would fix the problem and it didn't. So I took it to the Sprint store where they discovered I had a defective battery, and it just so happened that I bought the phone a year ago today so the new battery will be covered under warranty . I will update my status upon receiving the new battery, but I am feeling optimistic at this point.
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.