Related
I know there have been multiple threads on sleep issues but I haven't found one like this one.
My phone is able to sleep but only for a certain amount of time. It seems that after I reboot my phone, it can sleep appropriately for the first 8-12 hours and the battery life is amazing during this time and only drops about 20-30%. Up time verses awake time also reflects this. However, after about 8-12 hours, the phone stops going to sleep and the awake timer never stops running. This will drain the remainder of the battery in about 10 hours. After a reboot, the phone is able to sleep again until it develops insomnia once more. Does anyone know what could be causing the phone to stay awake only after being on for several hours? I'm rooted on the stock firmware with the latest OTA. Only extra programs are Google Voice, ePocrates, and Slacker Radio.
*#*#4636#*#* was no help in tracking down the culprit. Spare Parts contributed pretty much nothing either.
Mine did this for the first time yesterday. It's hasn't done it since, but it was very weird. I checked the sleep settings and it was still set to 1 minute, but the phone would not turn itself off.
Probably an app
Same Problem...
I have tried every thing to solve this issue. Change phones; problem return. No apps other than Stock; problem returns. Syncing Exchange, Facebook, and HTC Facebook. Custom Ringtones seem to increase the speed of the error occurrence. Tried leaving them off, but the problem returned. I have changed SD cards. reformated the card, and started it fresh. I have done a factory reset between each test (at least 8 at this point). I have a suspicious that it is the contacts that are getting corrupted, but I have not been able to verify that theory.
Mine has only done it on one evening and not since.
I've been constantly battling sleep issues. I am on PRI/NV 1.77 and latest radio. I tried downgrading to 1.77 just recently to see if it would fix it and it hasn't, but I'm staying put.
Running latest MIUI and Savage 1.6 kernel.
Spare parts had been showing on average 50% running time even though my screen on time would be something like 5%. I had read that ideally these ratios should match, since it means your phone is properly sleeping.
Spare parts shows paltry wake locks of just a few seconds or minutes for Android System as the top app. I've killed all my widgets and even tried airplane mode and don't notice too much of a drop. After getting rid of all updating widgets (minimal text and the MIUI cal widget) and stopping google calendar sync I'm currently at 30% running vs 5% screen on. I've basically got everything that would run in the BG disabled -- set cpu, system monitor, etc. Is this a "good ratio"? Any other ideas on debugging what seems to be an obvious wake lock? I've looked at logcat and don't see a thing that looks interesting, hardly any activity. Am I just being crazy or does it seem like I still have a wake lock?
Thanks for reading
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
freeza said:
If you've constantly been battling sleep issues, I would start looking at rogue apps that may be causing Android System processes to act up.
For instance:
I was battling a sleep issue with before knowing about PRI 1.90 causing it. Went so far as to reinstall my ROM wipe wipe and wipe some more before finally figuring it out.
In another instance I was battling sleep issues because of HTC's Facebook for HTC Sense. It was causing constant sync and I didn't notice because the sync icon would eventually go away, even if it took around half an hour.
One more instance, constantly changing governors with SetCPU was causing Android System process to use up a lot of CPU and my phone would become sluggish, and only after opening SetCPU and closing it again would my phone return to normal.
I would definitely start out by figuring out what apps you may have running at all times that aren't native to Android, then go from there. It sucks but once you figure it out, good times!
Click to expand...
Click to collapse
Thanks for the reply.
So, this is a bad ratio then, i'm not nuts?
I kill EVERYTHING then sleep and i'm still seeing the issues. Is there some more fool proof way I can guarantee nothing is running before sleeping? My guess would be something syncing more than it should have. Should I try toggling everything app's sync off and then sleeping?
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
lil-dice said:
Ok, turned off sync, slept and the top UID was 10018, which on my phone linked back to Google Service Framework. I'm clearing data, turning off sync and watching again to see if it has issues.
Click to expand...
Click to collapse
Interesting, I had that UID 10018 problem before and I never figured it out. It maybe Google Talk, Gmail, or even the Calendar. You may have to try clearing caches of one or all three to really see.
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
lil-dice said:
Cleared data, sleeping didn't improve. I slept with sync off after clearing data...i'm at a loss. I have next to nothing starting up. The only thing I can think is that Spare parts is reporting wrong information. You'd think it would be fairly easy to determine why the phone is not sleeping. If i don't even have sync turned on and it's still not sleeping as much as I feel it should be, I'm at a bit of a loss :/
Click to expand...
Click to collapse
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
freeza said:
Under battery........what are your Up Time and Awake Time looking like?
Identical? minutes apart? seconds?
Click to expand...
Click to collapse
I'm not sure how to get to that in MIUI, in battery settings i jut see my minutes since unplugged. No Awake time.
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Saturn2K said:
What's a good ratio for awake/screen on? I really wouldn't want my awake time to be more than %120 of the screen on time. This can change if you regularly use the phone while the screen is off (music playing, wifi stuff, etc). At least, I'm pretty sure having the wifi on will increase your awake time.
Click to expand...
Click to collapse
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
lil-dice said:
hmm ding ding ding.
Turned off wifi, did a quick 15 minute test and now my awake/screen are right in line....so what gives? Why does wifi prevent my phone from sleeping? Since i'm running MIUI i have to have wifi set to never sleep otherwise you get random reboots...feel like i'm between a rock and a hard place now :/
Click to expand...
Click to collapse
That's just how it is for all AOSP kernel using roms. Their wifi sleep mode is absolutely terrible. On the plus side, it seems as though it doesn't use an absurd amount of battery to keep the wifi on.
Let me preface this by saying I'm not complaning about battery life as 36h is very good. That said, I feel like my phone is awake much longer that it should be. Anyone have any ideas why my Awake time is so much higher than my Screen-on time?
Once again, I'm not complaining but considering my phone was awake almost 5x longer than the screen was on, I feel like I could squeeze some more life out of the phone. I had 1 exchange account @ 15min, 1 gmail on push, no talk/g+, ~2-3 hours off wifi (4g), gps on, bluetooth off, 4.0.4, leanKernel.
When analyzing the wakelocks, I don't see anything that would explain almost 6 hours of extra awake time:
Considering most of this charge I was on wifi, I think I should have been able to achieve more than 1.5h screen-on time. Especially when I see people getting 4-5+ hours on theirs. What could be causing this seemingly excess awake time?
Since those screen shots, I've done another full cycle and here are my results. Same settings as before. It looks as if I did a bit better with the ratio of awake vs screen on, but I still only got ~20 hours. I'll admit, this had much more 4g time and heavier usage.
As you can see it's better, as it was only awake about 3x as much as the screen. You can see where I was at home in the second screenshot (The long bar of wi-fi) and that included me sleeping yet it shows that the phone was consistantly waking up overnight without any usage. Short of "email", I'm not sure what could be causing it. I got MAYBE 3 e-mails overnight.
Signed out of talk/g+/latitude
Location services was NOT disabled in either set of screenshots. Disabled it and charging now. Maybe that will help?
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
armanatz said:
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
Click to expand...
Click to collapse
I have attached all the wakelocks to the previous two posts. I didn't attach CPU spy but I did check it every time. Usually it's between 60-80% but most often it's >70% in deep sleep.
Just did a fresh wipe with a app restore using the market. Location services have been disabled. I have uninstalled all gMaps updates and disabled the app. Is this good enough? Should I convert to user and uninstall using TB?
Just wanted to chime in and say I'm seeing a very similar profile to what you posted. And I'm not entirely sure, but I think this started when I flashed this ROM. What I feel like I'm seeing is that active use of the phone seems to be more of a drain than it used to, but I'm not sure how much of that would be placebo (i.e. remembering when I first got the phone around the holidays and there were a lot of relaxed days at home with constant wifi).
But right now I'm seeing 5.5 hours of awake time and 1 hour of screen on time, with 27% remaining. Total time is 42 hours, which seems to round everything out to a decent battery life, but again, 1 hour of use for 70% of the battery seems lower than what I remember. Not sure if a vote for seeing the same behavior is one for this being normal or us both having the problem, but I can try to post screenshots/more detailed info later if it would help.
This is on the above linked rom with stock kernel, 4.0.4 radios.
That's the same ROM I'm using and I agree, 70% usage for 1h screen time seems too much. I've seen people get over 2.5h screen on time on pure 3/4g
I'm going to see if disabling maps and location services help. Will report back.
I would be interested to see any SS you have, might help.
Sent from my Galaxy Nexus using XDA App
This is after a fresh wipe, fresh kernel install, no maps, no g+, no gTalk, no GPS, no location services, just gmail and 1 exchange @ 15 minutes
Any advice as to what's going on would be very helpful. Thanks in advance.
I also have a problem with wake-locks.
Since phone is relatively new ~2weeks its still stock 4.0.2 GSM. After some time my battery life fell and thanks to XDA i think i found the problem Google backup.
I disabled Google backup to see if i get the same awake time tomorrow.
If the problem doesn't go away, is it possible to resolve this problem without factory reset of the phone?
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
JoeSyr said:
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Click to expand...
Click to collapse
This looks to me like some sort of Maps issue. Try to uninstall/disable maps and see if it goes away. Looks like it's stuck trying to locate you with maps somehow based on those wakelock names.
Catoss said:
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
Click to expand...
Click to collapse
Hopefully the factory reset will fix it, that is an odd problem.
It seems to me like my problem was the version of leankernel I was using. I went from 10.0exp2 to 2.01exp2 and it's much much better
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Timdor said:
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Click to expand...
Click to collapse
mine is opposite of that, i standby fine on data but terribly on wifi. im guessing that is background syncing. i just have to figure out what is doing it
i have my wifi set to never too for better battery life. It seems counter intuitive, but wifi is better on power than 3g/4g. So preventing the phone from leaving wifi back to cellular is better for battery. All my phones have been like this.
yeah thats what i thought it does but mine drains faster on wifi...i leave it on cause i barely get signal in my room an if i sit on 3g it just takes a long time to do anything
What type of drain do you get over 3g vs wifi?
Yesterday I was playing around on 3g all day and I was seeing an average of 6%/hr. My phone is consistantly awake 20-25% of the time according to betterbatterstats. Screen on will always be far less than half of my awake time. Wifi drains around 1%/hr
I did a wipe of my 4.0.4 install and flashed a fresh kernel download. I'm not logging into exchange because, for some reason, I think that's my problem.
Also, changing to Never didn't really fix my issue.
Any idea why my replacement GNex reboots randomly, many times a day? It will be sitting in my pocket, screen off, and I will feel it vibrate. Look at the phone, it's at the Google logo rebooting. Also, if I'm outside on cell data, streaming music with the screen off, it will die in a few minutes.
I did some digging and someone said there is a location bug in 4.2.2, and it is causing certain GNexs to act like this. This morning I shut off all location services and disabled Google Now. My phone lasted the whole day without a single reset, and I was able to stream music.
Is anyone aware of a fix for this? It seems to be an issue on my phone in stock 4.2.2, stock+franco kernel, and CM 10.1.
Thanks!
So weird Issue.
Using Google Maps on MaximusHD 6 with the latest t-mo firmware (2.11) I get constant "GPS SIGNAL LOST" when obviously driving and using it as my nav since I got it. I'm in southern California with a pretty good LTE signal almost everywhere. The highways are pretty open so trees, mountains, buildings etc are ruled out as a probable cost.
Now today I noticed that I normally keep the phone locked/screen off when driving since it's connected over BT so there's no real need to look at it. During a normal 15-20min drive I would get the signal lost alert a lot. Upwards of 10 or so times on that single drive. While with my M8 it never happened especially when literally not 5min after getting out of the parking lot doing maybe 20mph down the street. I first I thought i messed something up since I took the phone apart to apply thermal paste to keep it from overheating.
However today on a drive back I kept the phone with the screen on. Never did it lose signal while the screen was on, but a minute after I locked the phone (screen off) did it lose GPS signal. I turned it back on and after driving 20min or so the signal wasn't lost.
So overall has anyone experience a similar issue? Full cellular coverage with frequent google maps alerts that the GPS signal was lost. Maybe a background gps process being killed or another coming up and hindering it.
Gonna wait for the Thanksgiving break to mess around with stock/custom roms and see if it's just something that can be fixed with a reflash.
I'm having the same issue, have you figured anything out? Have you tried using a different app besides google maps to see if it's the actual app doing it's power save feature, or the background powersaving process being started by the phone being screen off? Really interested because my phone starts burning up to extreme temps...
On the backup I had with the issue I narrowed It down to possibly a background process cutting it off once the screen turns back. Power saving was off and all that would stick while screen was off was maps, Google service, and social apps.
As for the cause I couldn't figure it out. I went with a stock from without issues. Then went back to custom roms and haven't had the issue again. Also I drastically lowered my app count. Barely use any apps not needed for basic functionality.
As for the temp issue you're having. I noticed gets warm just like any other device when using GPS. I have opened up the phone and applied a new thermal coat following off a thread around here.
I have another issue came up where the phone would seek out a GPS signal while battery saving was selected to even location turned off. Killed my battery in a heart beat. Hasn't happened again.
I would suggest you make a full backup and either flash a stock rom or redownload whatever custom rom your using. Do a trial run for a day or two with minimal apps and see if it improves.
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
shivadow said:
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Android 6 should be released around here soon so maybe that'll improve/fix these issues. I wouldn't be surprised if Google services is causing this since it has in the past drained batteries and causes similar issues. If the kernel is involved then the issue has been seen on both stock and custom.
well it may be a setting from the maximums HD, try using other Rom and tell us if problem is solved, try HD Revolution or ViperOne.
Hi all, I got a Moto G3 and having issues with the gps no signal message, it is on and off, but more the time that have no signal. So have heard that Android 6 could be the guilty one.. Do any of you know if there is a fix yet? ?
Enviado desde mi Nexus 7 mediante Tapatalk