TWS Bug Information - Epic 4G General

EDIT X3 Here is a definite fix for the TWS bug
BIG THANKS to mkasick for his hard work!!!! This fix has been incorporated into the latest bonsai ROM and will be included in the next Syndicate Rom. Thanks Devs!
Link to TWS bug fix/patch
I know the TWS (time without signal) bug is a known issue with this phone. It was present in di18 and is still here is eb13. However, it seems that some people have the bug, and some people do not have the bug after updating to eb13. I have not seen a lot of talk over this issue, which to me, is a HUGE issue. If you are not aware you have it and do not take preliminary steps to correct it, your battery will be drained much faster than normal.
I have tried everything I can think of to solve this issue including re-flashing in Odin several times, factory resets, etc... I am aware of the airplane mode toggle and profile/PRL update work arounds, but I am wondering if there is a FIX for this yet. These work arounds do not stick for me after re-booting, and it is very frustrating.
I am curious to see who has the bug on eb13 and who does not. If you are not experiencing the TWS bug, please post your method of upgrading, current ROM, kernel, etc..
Thank you for your input!
Edit: Thanks rocket, I should have included this to begin with. To check if you have the TWS bug, first make sure you are in an area with good coverage then
1. Charge battery all the way up (not really necessary, but will create a standard for testing)
2. Unplug and then stay in the same location for several hours
3. Go to Menu> Settings> About Phone> Battery Use> Cell Standby
4 Tap on Cell Standby and look for the "Time without signal"
5. If this is a high value such as above 40% you have the bug. I typically see 50 - 51% if I do not airplane toggle. After the toggle, I have 0 - 2% in my house where I have full 3g/4g coverage
EDITX2: Possible fix for TWS bug, need others to try
If you are having the TWS bug, try opening task manager (long press home button) and go to task manager. Then click on RAM management and clear level 1+2 memory. This should reset your radio as well. Get back to the home screen by pressing home button, wait a few seconds and power off the device properly (press and hold power button, power off) DO NOT do a battery pull to turn it off. Once the phone has fully shut down (after you feel it vibrate) wait a few more seconds and power back on. This should correct the problem and I have not had the issue come back after re-boots (no need to airplane toggle anymore).
*Disclaimer* What works for me may not work for you. I have no idea if this is just a device specific fix, but if other people can try this then we can rule that out. Sometimes clearing the memory resets the radio, sometimes it doesn't. I have noticed if it does reset the radio, your TWS bug will be fixed. It should stay after re-boots.

djbacon06 said:
I know the TWS (time without signal) bug is a known issue with this phone. It was present in di18 and is still here is eb13. However, it seems that some people have the bug, and some people do not have the bug after updating to eb13. I have not seen a lot of talk over this issue, which to me, is a HUGE issue.
I have tried everything I can think of to solve this issue including re-flashing in Odin several times, factory resets, etc... I am aware of the airplane mode toggle and profile/PRL update work arounds, but I am wondering if there is a FIX for this yet. These work arounds do not stick for me after re-booting, and it is very frustrating.
I am curious to see who has the bug on eb13 and who does not. If you are not experiencing the TWS bug, please post your method of upgrading, current ROM, kernel, etc..
Thank you for your input!
Click to expand...
Click to collapse
bizzare. Ive never had this bug. On eclair or leak froyos or eb13.

Do not have the bug now, nor did I have it at any point
Current Setup: EB13, Bonsai ROM v3.0.0
Upgrade Method, Flashed back to stock DI18 from DK28 using Odin
Used SWupdate to install EB13
Installed CWM 3.0.0.6
Installed Bonsai ROM v3.0.0

I have the bug. I suspect people who say they don't have the bug don't reboot very often, out of sight out of mind type of thing. I could be wrong.
What I do know is after the PRL "fix" came out tons of people were saying "yay its fixed" then a few days/weeks later they reboot and find its still an issue.
I'm hopeful that because Sprint & Samsung pulled the update (Samsung just pulled it from their site today I think) they would be working on an incremental update which fixes a lot of these complaints. I don't have any inside information, but when other SGS phones have had their updates pulled it seems like new releases were dropping within 2-3 weeks to correct problems. Also, the Samsung rep who reads XDA has been sent a list of bugs compiled on this forum so hopefully they will be addressing them without adding more "fireworks" type bugs
Edit:
I wanted to contribute a bit more to this thread, so first off if you don't know how to tell if you have the TWS bug follow these steps:
Charge battery all the way up
Unplug and then stay in the same location for several hours
Go to Menu> Settings> About Phone> Battery Use> Cell Standby
Tap on Cell Standby and look for the "Time without signal"
If this is a high value such as >40% you either have very poor cell coverage, or you have the TWS bug. I work primarily in a basement so my TWS is about 10% normally, but goes up over 50% when the TWS bug is active.

The TWS bug seems to be endemic to multiple Samsung devices and as far as I can tell they have never admitted or officially recognized that the problem exists. It has effected my phone on DI18, DK28 and EB13. From what I have read it is caused by sloppy modem.bin coding.

I know FOR CERTAIN that I have this bug!!!!!
EVERY DAY I receive voicemail notifications from people when their ORIGINAL call NEVER CAME THROUGH....
I checked the stats one day and my phone had been unplugged for 16 hours.....during that time it logged that I was "without a signal" 50% of that time.
8 HOURS WITHOUT A SIGNAL......ARE YOU FREAKING SERIOUS!!!!
(Looking for another carrier)
[Sprint is the Devil]
BTW
I had this bug in DI18 and I am currently running leaked DK28 with the same problems

I try to remember the airplane toggle mode trick whenever I reboot after swapping batteries and if I remember right away my TWS is 0% but without fail if I forget it's always around 50%. After I remember and toggle airplane mode it slowly lowers the % value as time passes. Running midnight4.1 right now, originally odin'd to eb13.

The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.

muyoso said:
The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.
Click to expand...
Click to collapse
Does not fix it for me. Has the same effect as toggling Airplane mode though. Reboot and it's back...

muyoso said:
The PRL and profile updates fixes this. I had to reflash the ACS rom last night and forgot to update PRL and Profile. This is the result:
I just updates the PRL and profile. Then I rebooted the phone. I will update this post with a new image showing no TWS after an hour or so. I had TWS issues when on DI18 and on DK28. It is completely fixed in EB13.
Click to expand...
Click to collapse
Thanks for the input, but as I stated, for me at least, updating the PRL does NOT stick after re-boots to fix the problem. If this does fix yours, wonderful, but for people like me this is not a solution, only a temporary work around.
The fact that there is such a wide variance among users is very concerning.

bjhill2112 said:
Does not fix it for me. Has the same effect as toggling Airplane mode though. Reboot and it's back...
Click to expand...
Click to collapse
+1 this guy knows what I'm talkin bout!

Add me to the list of "had it, have it, and PRL/Profile updates don't stick past reboot."
My favorite way to fix it is to use a free little app called network I got from the market. It's just a shortcut to a radio settings menu that I used to be able to get through a dialcode, but I like just clicking on the button.
What I see with the menu is that the phone appears to default to "WCDMA Preferred" which is a type of network that our phones cannot access. I switch it to "CDMA Preferred," and the TWS problem will then go away (until next reboot, of course). What would really be great is if changing this setting could get coded into the custom ROMs.

Not sure what's fixed it
OK so when I initially flashed to EB13 I had the bug (also had it in DI18, but not DK28). I got an airplane mode toggle widget and all that shiz to make it easier to deal with.
After a few changes to my phone it is now gone.
I noticed it went away after I put Twilight Zone kernel on my phone, performed a flash to ext4 version EB13 through Odin from here, then reflashed Twilight Zone kernel to be sure it was still intact. I also restored my data from a back up i performed why on rfs/CMW2.
Today I attempted to flash the full Frozen ROM and for the few minutes I had it on my phone I noticed that the bug was back. I reodined using the same method as before, restored data, and wallah its gone.
Furthermore, I saw on here moments ago that there was a firmware update for the camera. After I installed it I noticed it FCing on Sports Scene mode. To fix that I flashed Twilight Zone again and still do not seem to have the bug back.
Anyone else want to try and give it a shot to see if it fixes/changes things for you?
I cannot tell if it's related to the kernel, the switch to ext4, or some combination of those things. Allz I know is its been days and it's still gone.

I definitely have this bug, and what "bugs" me is that I have been scratching my head trying to figure out why a bunch of my calls go straight to voicemail... this is a huge problem imho which hopefully will have a real fix soon. I downloaded the Network app but can't get the CDMA only mode to stick... "process.com.adroid.phone" crashes every time I guess I have to remember to toggle airplane mode after every reboot. This sux

It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.

Gersonian said:
OK so when I initially flashed to EB13 I had the bug (also had it in DI18, but not DK28). I got an airplane mode toggle widget and all that shiz to make it easier to deal with.
After a few changes to my phone it is now gone.
I noticed it went away after I put Twilight Zone kernel on my phone, performed a flash to ext4 version EB13 through Odin from here, then reflashed Twilight Zone kernel to be sure it was still intact. I also restored my data from a back up i performed why on rfs/CMW2.
Today I attempted to flash the full Frozen ROM and for the few minutes I had it on my phone I noticed that the bug was back. I reodined using the same method as before, restored data, and wallah its gone.
Furthermore, I saw on here moments ago that there was a firmware update for the camera. After I installed it I noticed it FCing on Sports Scene mode. To fix that I flashed Twilight Zone again and still do not seem to have the bug back.
Anyone else want to try and give it a shot to see if it fixes/changes things for you?
I cannot tell if it's related to the kernel, the switch to ext4, or some combination of those things. Allz I know is its been days and it's still gone.
Click to expand...
Click to collapse
Does the bug stay away after a reboot or 2? I also noticed that I thought I had this problem solved until one day I noticed my phone died after 6-8 hours into my 12 hour shift, and the reason I belive it is such a battery drain is that the phone doesn't sleep when it thinks it doesn't have a signal in addition 2 constantly scaning for prefered network. For sum reason it is set 2 wcdma by default when that's a gsm network. If anyone knows where that value is saved plz give me a heads up...
Sprint is absolutly no help as their "specialest" told me a task manager would fix this problem -rotflmfao!! after 3 techs and numorious "mistransfers" where I was hung up on I gave up hope that sprint highers compatant ppl..
Sent from my SPH-D700 using XDA App

mkasick said:
It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.
Click to expand...
Click to collapse
I now think I might be a little slow.. because that went way over my head.. lol
and I read it a few times..
and I work as a I.T tech..
but im also drunk right now maybe thats the reason..

Isn't thidls bug just visual? I have it and it had no effect on my phone.
Sent from my SPH-D700 using Tapatalk

mkasick said:
It's happened to me a few times, but not very many. It hasn't happened since upgrading from DI18, but it hasn't happened in a long while before then as well.
The last time I knowingly had TWS, I noticed that:
Battery consumption due to "Cell standby" was not larger than normal.
The "Time on" value was twice that of the phone "up time". They should've been the same since I hadn't charged since powering on, and in no circumstance exceeded it. It may have (and probably should've) been twice the time "since unpluggged", but I don't recall.
Which lead me to think for a while that the TWS bug was merely a reporting bug. That is, if "time with signal" (which isn't reported) is half that of "total time" (as determined by a clock that's running 2x fast), then the phone will report being without a signal for 50% of the time.
But I haven't ran into the problem since to reliably establish the above as fact. It could be that there's multiple issues that result in the same symptom (~50% time without signal). Or I might've be mistaken entirely, since I was only able to check once.
Click to expand...
Click to collapse
musclehead84 said:
Isn't thidls bug just visual? I have it and it had no effect on my phone.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I agree. The "TWS bug" is just a reporting issue. It has no real effect on battery life. The percentage of battery used by the cell radio is the same regardless of what TWS reads.

BigBrotherMotown said:
I know FOR CERTAIN that I have this bug!!!!!
EVERY DAY I receive voicemail notifications from people when their ORIGINAL call NEVER CAME THROUGH....
I checked the stats one day and my phone had been unplugged for 16 hours.....during that time it logged that I was "without a signal" 50% of that time.
8 HOURS WITHOUT A SIGNAL......ARE YOU FREAKING SERIOUS!!!!
(Looking for another carrier)
[Sprint is the Devil]
BTW
I had this bug in DI18 and I am currently running leaked DK28 with the same problems
Click to expand...
Click to collapse
This is what made me think that I probably had this with DI18 and even some of the DK28 roms I ran even though I didn't know how to check for it back then, I would always get voicemails and no record of a missed call in my call log. Very frustrating. So the battery life issue that may or may not be associated with this bug is of little consequence to me compared to not even getting calls due to lack of signal.

Related

[Q] Help! Stuck in airplane mode

My phone is stuck in airplane mode...
It just started earlier today, about the time I had lost signal and would have gone into roaming on the way to my dads house.
In the past Ive run Epic experience with xtreme kernel, and with 2.2 I have tried the original leak, Mammon, and I was on Quantum when it started doing this. I just tried wiping and reflashing to the newest version and its still stuck.
Any ideas?
Note: I did NOT make any attempt at flashing the 2.2 modem.
So this is what I did and it worked flash the stock rom firon or noobnl posted I foget and then flash to 2.2 again it worked for me after a few times.
Sent from my SPH-D700 using XDA App
So flash the stock 2.2 that Firon had posted to get airplane off, then flash back to whatever I want? Or do you mean flash stock as in out of the box 2.1?
Ive never had to odin or whatever all that jazz is, wasnt an option on the hero obviously, and I try to keep my messing with the epic to a minimum. So it makes me a little nervous.
Well you could flash the modem.bin in odn to make it easier idk wher t find that tho search the forums.
Sent from my SPH-D700 using XDA App
Similar Problem with Epic stuck in Airplane Mode
There is a similar thread about this problem under the Sprint Forums. Myself and several others have experienced multiple instances of the Epic randomly going into Airplane Mode on its own. Sometimes it gets stuck there for several hours. It appears that this has something to do with a weak signal. For me, it happens only at my home, where I have little to no signal. I have an Air Rave, but for some reason it appears to go into Airplane Mode more often with the Air Rave on than with it off. This is very frustrating. Sprint does not acknowledge the problem. They say it must be a hardware issue, and we should just get new phones, but I'm on my fourth phone, as is another person on the Sprint forum, so it appears to us that this is really some sort of software bug, but it does not occur often enough to cause Sprint or Samsung to take notice and do something about it.
This happened to me as well the day before yesterday... I had installed ViperRom IMpact, and had car home running navigating me to LAX, and all of a sudden, my phone reboots and then was always stuck in airplane mode after that. I recovered my original rooted rom, stock 2.1 just rooted, and worked fine... Installed SyndicateRom (2.1) and still could get signal. Tried to install another 2.2 ROM, and get the same thing where it's stuck in airplane mode... So I think I'm going to stick it out with SyndicateRom for a bit...
had the same problem a couple weeks ago for several hours. spontaneously fixed. and about 20 mins ago it went into the problem again. no apparent solution.
Possible solution...
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
I have this problem pretty often when I am in a place with bad signal. Reboot the phone into clockwork recovery, in advanced options, fix permissions. This has fixed it every time. Also sometimes just rebooting it will fix it but that only seems to work randomly.
zndotcom said:
I am on EF02 with EF10 modem. This happened to me after the phone was not touched for hours. After many reboots I decided to boot into clockwork (purple) and flush the cache and after the reboot service was restored. Possibly just a coincidence or maybe a solution?
-This is more for googlers than the op.
Click to expand...
Click to collapse
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
I've seen it happen on my phone and a friend's phone. The advice below always works.
tragiquexcomedy said:
I've had the same thing happen on EF02; every time, I pull the battery, boot into recovery, wipe caches & occasionally battery stats (hey why not), & every time the phone reboots with full service again.
Click to expand...
Click to collapse
p3dr0maz said:
I've seen it happen on my phone and a friend's phone. The advice below always works.
Click to expand...
Click to collapse
Just had the same issue pop up on my wife's phone, & wiping caches fixed it a well. Thank God for XDA & Clockwork!

Phone randomly stops sleeping

My phone will randomly stop sleeping, this has happened pretty much since i've gotten it.
I will launch spare parts, running near 100%. Check partial wake lock, nope nothing. And nothing under any of the other menus in spare parts that would indicate it not sleeping. This will occur after a couple of days even after installing no apps, restarting does not fix, neither does pulling battery. It will just start happening and only way to fix is data reset / factory wipe until it happens again, but when it does start happening I might've not even be using it at the time.
Okay, i did actually finally fix it after months without factory reset, it appeared to be when 3g and Data-always enabled was ticked.
ryronz said:
Okay, i did actually finally fix it after months without factory reset, it appeared to be when 3g and Data-always enabled was ticked.
Click to expand...
Click to collapse
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
the red krawler said:
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
Click to expand...
Click to collapse
Wooh, nah for example my running time is 8.7% and screen on is 6.1% so that is pretty good, thats over the course of about an hour
the red krawler said:
If this fixes my no sleep problem, I will name my first child after you.
I've been detailing the steps I've taken to resolve my no sleep issue on another forum, with the last action I took being a flash to factory ROM from huaweidevice.com, changing absolutely nothing on the phone for 24 hours, rebooting, and waiting another 24 hours. Without a reboot between charge/taking off charge, it would be 100% running. If I took it off charge and immediately rebooted, running would be more like 30% (ie: 'normal').
I'll give 'data-always' a go
Click to expand...
Click to collapse
Okay im unsure now, was all fine yesterday, woke up at 7 to alarm, lost 2% overnight. then just put it under my bed but now that i've woken up i've lost 18% because it just stopped sleeping again. I didn't do anything except turn it on check battery, and turn it off. So back to being confused again
Still having this problem, for example. It was sleeping fine when I went to bed then at some point during the night just stopped.
Running 64.6% 10h
Screen on 10ish% 45 minutes
Highest item with partial wake lock in spare parts is like 5 minutes, no other indicators.
This is happening no matter which ROM i try.
Considering a stock ROM with exactly 0 changes still has sleep issues, its clearly a firmware "thing".
For me, it happens after being taken off charge.
For e.g. Last thing before bed I check my running time, and its somewhere around 35-40%. Plug into charger. Take off in the morning, goto work etc, check my run time and its 100% even without the phone being touched.
For the moment I just downloaded one of the "root only" reboot widgets from the Market. Its just part of my morning "get ready for work" routine to hit the reboot widget and reboot my phone.
Its a bit of a PITA but until new firmware is released I cant see a way around it.
the red krawler said:
Considering a stock ROM with exactly 0 changes still has sleep issues, its clearly a firmware "thing".
For me, it happens after being taken off charge.
For e.g. Last thing before bed I check my running time, and its somewhere around 35-40%. Plug into charger. Take off in the morning, goto work etc, check my run time and its 100% even without the phone being touched.
For the moment I just downloaded one of the "root only" reboot widgets from the Market. Its just part of my morning "get ready for work" routine to hit the reboot widget and reboot my phone.
Its a bit of a PITA but until new firmware is released I cant see a way around it.
Click to expand...
Click to collapse
Hey don't know if you've tested it further than that. But its much appreciated, that rebooting after charging does seem to work . But just wondering, if you know... does it only do it when charging via usb (computer) or AC or does it not matter?
I have exactly the same problem.
I also noticed that reboot helps, but only for a while. If i want my phone to go to sleep mode when the screen is off, i would have to reboot it few times a day... Turning WiFi/GPS/Auto-sync on/off does not have any affect on this.
ryronz said:
Hey don't know if you've tested it further than that.
Click to expand...
Click to collapse
As per your suggestion via email, I tried the Malaysian firmware.... It seemed that 'running' time was down alot, but battery life was still pretty average. That was doing nothing more than installing the Malaysian firmware and entering my Google account - no root, no launcher changes, etc.
The lack of Swype was a bit of a downer too
I gave it a whirl from 6:30am to around 5:00pm and 'running' was right down in the 10% range, but battery was still down to ~45% over that time in 'pure' stock form. DAMMIT!
Ah well. It was a good thought and hopefully it worked for you I'm back on roadhound + the OTA update as of about two hours ago.
I'm going to scour the SGS forums and see if anything there can be applied to the U8800 RE: battery life improvements.
the red krawler said:
As per your suggestion via email, I tried the Malaysian firmware.... It seemed that 'running' time was down alot, but battery life was still pretty average. That was doing nothing more than installing the Malaysian firmware and entering my Google account - no root, no launcher changes, etc.
The lack of Swype was a bit of a downer too
I gave it a whirl from 6:30am to around 5:00pm and 'running' was right down in the 10% range, but battery was still down to ~45% over that time in 'pure' stock form. DAMMIT!
Ah well. It was a good thought and hopefully it worked for you I'm back on roadhound + the OTA update as of about two hours ago.
I'm going to scour the SGS forums and see if anything there can be applied to the U8800 RE: battery life improvements.
Click to expand...
Click to collapse
Oh yeah sorry, try using something like juice defender to disable 3g when screen is off or something. 3g radio keeps it running, but it doesn't appear to be, this will stop the battery drains.
EDIT: That does work but its not ideal, turns out the u8800 and the u8800h use the exact same radio so im not sure now, don't know if there is any possible way to figure it out.
ryronz said:
3g radio keeps it running, but it doesn't appear to be, this will stop the battery drains.
Click to expand...
Click to collapse
Sometimes i have 3g data connection running, but phone goes into the sleep mode when screen if turned off. So this is not the cause.
knevski said:
Sometimes i have 3g data connection running, but phone goes into the sleep mode when screen if turned off. So this is not the cause.
Click to expand...
Click to collapse
Oh no, this is just the case for the U8800H malaysian firmware seems normal for all U8800 firmware.
I'm not using u8800H firmware and i have this bug.
Hey guys.
This may not really be the thing you need but I was having similar problems and running 100% on without sleeping etc and came accross another forum where this was an issue (cant remember where)and as trivial as it sounds the solution for me was to go into settings/ applications/ manage applications and running applications and go down to media storage and clear the data. I do this now and then when I have this problem and it seems to help.... Maybe worth a try? It seems to be an issue with a particular media file. I also try to reboot my phone after every charge. Note that my phone is totally stock
astewart said:
Hey guys.
This may not really be the thing you need but I was having similar problems and running 100% on without sleeping etc and came accross another forum where this was an issue (cant remember where)and as trivial as it sounds the solution for me was to go into settings/ applications/ manage applications and running applications and go down to media storage and clear the data. I do this now and then when I have this problem and it seems to help.... Maybe worth a try? It seems to be an issue with a particular media file. I also try to reboot my phone after every charge. Note that my phone is totally stock
Click to expand...
Click to collapse
Thanks for advice, but unfortunately this didn't help either. For some unknown reason, my running time is again 100% although the screen is off most of the time. In Partial wake usage, Android System is in the top of the list.
Oh, Android System partial wake lock seems to be a different issue, but maybe someone can help you out. Whats happening here is running = 100% yet there is no partial wake lock held. Quite unusual
ryronz said:
Oh, Android System partial wake lock seems to be a different issue, but maybe someone can help you out. Whats happening here is running = 100% yet there is no partial wake lock held. Quite unusual
Click to expand...
Click to collapse
Yes, it is confusing also because i have tried different ROM's with same result. I would have thought that all u8800 owners have the same problem.
same problem here...

Phone locks up at 5am each morning.

I've had a SII for a couple of weeks now (new user to android) and I have flashed it to Lightning Rom 1.5. But even before doing this and also afterwards the phone seems to crash/lockup at 5am on about 5-6 occasions.
Is there any program/app I can install to monitor what is kicking in at this time so that I can disable/uninstall it?
Thanks
What do you mean by crash exactly ? Reboot ? Freeze ?
What you could do is plug your phone to your computer before it crashes, and start adb logcat, wait for the crash, and then look at the log to see what caused the crash.
It is completely frozen. I get up at 6:15am and the phone has a blank screen, but I can press a button to activate the screen and the clock is stopped at 5:01am and you cannot do anything else except turn the phone off and back on.
Maybe its the rom? Have you checked its thread? Try flashing bacm to stock. See if problem occurs.
Sent from my GT-I9100 using XDA Premium App
I checked the thread but doesn't appear to be anyone else with same issue. I might try the stock ROM to see if the problem persists. Although I sure it happened once on the firmware that came on the phone (KE2 I think it was).
scheduled backup?
I couldn't find any backups scheduled. So I wiped the phone last night and applied the Lightning 1.5 ROM again and it seems to have been fine this morning..no lockups.
Thanks for the advice.
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
OccasionalDroid said:
I had a similar problem with my Nexus S. It went into a bootloop at around 5am... I'm not sure, but I used to think it might be that network operators refresh their networks at that time, and a buggy radio would crash.. This is not normal, if it does the same thing with stock return your phone for repair, especially if you use your phone as your alarm!
Sent from my Sammy Galactic S2 Beastly Device
Click to expand...
Click to collapse
I'll keep that in mind if it happens again..cheers. Been OK this morning so shall see how it goes.
Its done it a few more times since I did a factory reset, always at 5:01am. After rebooting the phone and checking the battery stats it appears that 'Cell Standby' has used 52% of all battery consumption and the battery drained from 100% to 9% over 8 hours. The problem also occurs even if the phone is on charge over night.
So maybe it is a buggy radio? Gonna take it back to the store tomorrow to be looked at.

[Q] GCM_LIB Partial wakelocks

Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
R0N1N said:
Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
Click to expand...
Click to collapse
+1
Carried by a Raven
mrnovanova said:
+1
Carried by a Raven
Click to expand...
Click to collapse
+1! Something I did/installed/modified in the last week since I got the phone made the battery life plummet. Thought it was the "listen for wake-up command" part of S Voice... better, but nope. GCM_LIB had it awake 7 1/2 hours out of 8 I slept last night. This morning removed Samsung acct to see how that goes. Next the google acct...
I have the exact same problem as the OP, same phone/model too. Any clue what this "GCM_Lib (Android System)" under BetterBatteryStats is? It is preventing the phone from going into Deep Sleep. I notice this GCM_Lib is only active when there is an active connection (either WiFi or Mobile Data) turned on. With Flight Mode, there is no excessive battery drain. I am losing 15% battery over night (6-8 hours sleep). With Flight mode, I am only losing 1%.
I have removed all accounts off my device, and GCM_Lib is still wrecking my battery usage. Phone is unrooted. Any ideas?
I had the same problem on my SGH-M919V, upgrading firmware from MDJ to MG1. Same symptoms about suddenly poor battery life during sleep, and constant GCM_LIB wake locks. In the end, I never did figure out what was causing it, or a good way of fixing it, however I did end up solving the problem indirectly.
I flashed my phone back to the old MDJ firmware (NO data wipe, just firmware only), to check if I was getting the same problem previously, without knowing it. Sure enough, the problem went away, and didn't happen on the old MDJ firmware. So next, I re-applied the new MG1 firmware (again, NO data wipe, just firmware only), figuring that I would systematically disable/uninstall everything, one thing at a time, to try and figure out what app, account or setting was causing this. However, as soon as I re-flashed the new MDJ firmware, the GCM_LIB wake lock problem never re-appeared afterwards.
I don't know if this was something uniquely corrupt or misconfigured with my accounts or phone settings, or something unique to the SGH-M919V phone or firmware, but oddly enough, the firmware rollback & upgrade process described above did somehow fix the problem for me. I'm not sure if this process of firmware rollback without data wipe is supported or recommended without causing other issues along the way. I haven't other any other issues as a result of doing this. But still, make sure to have a full backup of your phone before you start, just in case something goes wrong during the process or some time afterwards.
Having the same issue here, don't know what causes it and how to fix it. I tried killing all the process with the System Panel app, it fixes the wakelock for a moment then it starts again

Phone unresponsive / Android system / huge battery drain from yesterday

Hi everyone,
since yesterday I am having a major issue with my Honor 8 (FRD-L09, unbranded, stock OTA /Android 7.0, security patch level 5.8.2017/). After some time (it can be several minutes or hour) the phone becomes unresponsive. I am able to unlock the display but that is all. It is not possible to swipe left/right/notification bar. Software buttons are working, what helps (for at least some time) is when I hit left square button and clear memory. Even it clears only 20 MB, phone is running ok for some time again. Battery drain is enourmous - yesterday when these problems started for me I had 93% and in 4 hours without using phone at all it dropped to 40% ! When I check battery stats, it is drained by "Android system".
Yesterday I missed some phone calls because of that (I know people called me, but no missed call and no missed call sms from operator). The first sympthoms I noticed yesterday were (apart from slow response) that when I swiped some nofitication away, or I closed some app (that had notification icon), the notification icon(s) did not disappear from the bar, but applications were closed...
What is the most important information is that this behavior started for me yesterday morning OR Wednesday evening /not 100% sure here/. And also what is important is that my colleague has the same phone (bought from different seller, but again unbranded etc.) and he started to have the exact same issues on Tuesday (8.5.2018).
Any help from you would be much appreciated, I am assuming it was caused by some background update of whatever (Google? Huawei?)
Thanks.
skubko
Easier (and faster?) than looking for the needle in the haystack is to backup with HiSuit and then factory reset in the stock recovery.
Then instead of restoring apps, download them from Google Play and setup manually the ones you can. Check progressively for any behaviour (lag and drain). Install something to check SOC utilization per process, like a task manager.
zinko_pt said:
Easier (and faster?) than looking for the needle in the haystack is to backup with HiSuit and then factory reset in the stock recovery.
Then instead of restoring apps, download them from Google Play and setup manually the ones you can. Check progressively for any behaviour (lag and drain). Install something to check SOC utilization per process, like a task manager.
Click to expand...
Click to collapse
Yeap, if this would be case just for myself, it would have been the first thing I would do. But if two different phone owners have the same issue, I do not think factory reset will do the trick. I will just loose everything, will need to setup everything manually, install manually and for nothing as I believe the same situation will appear afterwards... My first guess is Google Play Services. When I check it in Google Play store, from yesterday there are several one-star comments complaining about different misbehaviours, I am just surprised that here in Honor 8 forum I did not find any complaints yet...
I'm having the same issue for the last couple if days
Sent from my FRD-L09 using Tapatalk
My mother has this phone and is having the same exact issues for the last few days. Really bizzare stuff. She just called to let me know she has a full battery before going to bed last night and now it's drained to nothing and the time is somehow two hours behind so her alarm didn't go off. She almost missed getting up for work. A restart seems to return it to normal but not for long.
The same problem appeared by me, fw B404. From yesterday, the wifi goes down, sees no network. Today it appeared unresponsive only SW buttons worked but no apps. I tried the restart now it tooks 10 minutes.
Hello everyone,
I have the same problem for a few weeks on my FRD-L09.
After a few minutes or hours, my phone becomes very slow and the battery is empty very quickly. Wifi becomes hs too. I can just unlock the phone.
I made a factory reset and the problem is still present. Glad to see that I'm no longer the only one to have this problem!
Have anyone installed and pulled some logs from CPU Spy?
I am facing same issue on my L02 model from past 2 days, many apps slows down or not load properly like uber, facebook, walpy, google assistant and some other google apps. May be honor slows down the phone like apple, to increase their latest phone sales or its due to google tickling with their services..
hello all,
- do you have an SD card? if yes, have you tried removing it?
- emui comes with avast pre-installed, which updates and scans behind the scenes. maybe it's a bad virus definition update, try to disable it!
for me, I don't have sd card and avast is not installed.
I'm in stock rom and the problem seems to be present since the B403.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was just toying around with my mother's phone and initallly it was fine but then froze in the same way people describe. Restarted and was fine but then apps started launching on their own until it eventually froze. It's like it's possessed. I've had Play Service issues specific to my Axon 7 in the past but nothing like this. How the hell does the system time change itself and lose two hours? That's bizzare. Someone in China having a little fun?
This just started out of the blue a few days ago. She noticed it Wednesday but it might have started Tuesday. She's 70 and often complains about her phone and it's just her. It's obviously the phone this time.
Hybris03 said:
for me, I don't have sd card and avast is not installed.
I'm in stock rom and the problem seems to be present since the B403.
Click to expand...
Click to collapse
Avast scanner is preinstalled and included in Phone Manager, so you have it for sure, but it is well hidden. Go to Phone Manager -> Virus Scan and you will see their logo. You can disable periodic scanning from there.
Two more questions that may help you:
- Is the problem persisting if you set the phone to Power saving? Or ultra power saving? (although in the latter case most of the functionality is disabled anyway)
- Have you tried to install BetterBatteryStats (with the extra permissions using adb commands) and check what is causing wakeups/alarms and partial wakelocks? Maybe that will help you identify the culprit.
I've got exactly the same problem, which also started a couple of days ago. The phone becomes unresponsive - I can unlock it but not much else, possibly remove notifications but the ones below don't move up when I do. A restart only helps briefly, and I have to do it by holding down the power button for 10 secs, otherwise, it gets stuck on the reboot animation.
edit: My phone is also an Honor 8.
supersakis said:
Avast scanner is preinstalled and included in Phone Manager, so you have it for sure, but it is well hidden. Go to Phone Manager -> Virus Scan and you will see their logo. You can disable periodic scanning from there.
Two more questions that may help you:
- Is the problem persisting if you set the phone to Power saving? Or ultra power saving? (although in the latter case most of the functionality is disabled anyway)
- Have you tried to install BetterBatteryStats (with the extra permissions using adb commands) and check what is causing wakeups/alarms and partial wakelocks? Maybe that will help you identify the culprit.
Click to expand...
Click to collapse
It's ok for avast.
Problem is always present with the different modes of the power manager.
I'm currently at work, I will test BetterBatteryStats tomorrow night.
Thank you for your help
Downgrade to March
Downgrade to March Upgrade B403 seems to solve the problem.
Got an update for L09 B395. my phone becomes unresponsive everytime my phone get sleep while wifi is open. the problem is due to wifi setting "Keep wifi ON during sleep" is set to NEVER. when i changed the wifi setting to "Always" my phone run smoothly again.
aedel said:
Got an update for L09 B395. my phone becomes unresponsive everytime my phone get sleep while wifi is open. the problem is due to wifi setting "Keep wifi ON during sleep" is set to NEVER. when i changed the wifi setting to "Always" my phone run smoothly again.
Click to expand...
Click to collapse
I will try changing the wifi settings and if the problem persists, I will try downgrade to B403.
I'll keep you informed.
Hybris03 said:
I will try changing the wifi settings and if the problem persists, I will try downgrade to B403.
I'll keep you informed.
Click to expand...
Click to collapse
Downgrade was not successful... after some hour the same sh*t.
Indeed, the problem has something to do with WiFi.
kharthax said:
Downgrade was not successful... after some hour the same sh*t.
Indeed, the problem has something to do with WiFi.
Click to expand...
Click to collapse
After mofidifying wifi setting on "never", battery drain seems to be normal.
I confirm that tomorow after a full day of use.

Categories

Resources