Doze hasn't worked since 6.0.1 OTA - anyone else? - Nexus 5X Q&A, Help & Troubleshooting

Since getting the OTA, Doze hasn't worked at all. I haven't installed any new apps, and am stock/unrooted. Here's the battery graph from last night with the phone sitting on the nightstand.
Any ideas?

Same here. So you had a flat line before the update?

Yep, flat line before the update. Here's the detailed battery view (4% after my first screenshot, but serves the same purpose). Looks like something is keeping the phone awake but nothing else changed outside of updating the OS.
I restarted and that didn't help. Maybe it has to re-optimize.

Doze appears to be working on mine but I've only had it for a day and am using it a lot. When not in use for an extended period of time the battery graph completely levels out and doesn't decrease at all. Then again I think I've only gone about 20 minutes without touching it since I took it off of the charger this morning.

Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.

See attachment for Doze. It works better on my 5x than 6p. I'm not sure why. Total flatline.

Looks solid to me

Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank

mtca said:
Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank
Click to expand...
Click to collapse
Wait, Current Widget actually works properly with you with the 5x? It rarely updates for me. All software current monitoring tools seem to do so.
I figured it must be something with how the power regulation works on this device.
With my Nexus 5 it would update exactly as intended and could be plotted on the graph, until the phone entered deep sleep then the updates became infrequent. This was on Lollipop before Doze existed, so that tells me that it is because of Deep Sleep not Doze.

bblzd said:
Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.
Click to expand...
Click to collapse
You may have solved my problem. Using Wakelock Detector, I saw that Google Maps was slamming my phone too keeping from dozing. I deleted my offline maps and disabled the option. Hopefully that fixes it for me

Related

[Q] Why won't my phone goto sleep?

I think my phone is suffering from the Android OS keep awake bug. I just charged my phone to 100%, rebooted, opened and closed the camera app and left it alone for about an hour and a half. I am down to 92% batter life remaining. This seems excessive. The Android OS app shows a keep awake time of exactly 93 minutes which is also exactly the same as the up time.
I don't quite understand BetterBatteryStats just yet, but BetterBatteryStats shows "gps-lock" as 1h27m4s under Kernel Wakelocks since charged. Nothing else comes close. The highest Partial Wakelock is ActivityManager-Launch with 12s. Under Other Awake is 93 minutes and Screen on is 2 minutes. BetterBatteryStats is the first item under Process the surfaceflinger and com.android.phone.
Before rebooting I had set my GPS settings to (and they remained this way after reboot)
-Google's Location Service : Unchecked
-GPS satellites : Checked
-Location & Google search : Unchecked
Other stats:
-Verizon LTE
-bigxie IML74K Build 2
-franco.Kernel #12 (hotplug enabled, 350k low, 120k high)
-No widgets
-No other apps were opened
-Gmail is set to sync. I haven't run or configured Google+ (don't use it). Gmail/Calendar/Contacts should be the only things syncing, no facebook sync.
I had similar issues before flashing the kernel and rom.
How can I get this thing to go to sleep? I don't think this should be consuming so much battery life while idle.
you have a "bad app" that is preventing the phone from deep sleeping.
get cpu spy from the market to verify how long your phone is staying in each state
do you have any notifications in the notification bar?
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
lethologica said:
No notifications were received in the last 90 minutes (forever alone yes). I just installed CPUSpy. This says 00:01:25 was spent in 1200Mhz, 01:39:52 in 350mhz and 0:00:0 in Deep Sleep.
How can I find what app is preventing deep sleep? The only apps listed in the battery app are Android OS, Screen, Phone Idle, Cell standby and Android System.
Wouldn't this bad app show up in BetterBatteryStats under Process?
Click to expand...
Click to collapse
I don't use BetterBatteryStats so I wouldn't know.
I personally set my CPU speeds from 700-1200MHz (as indicated by Franco and others... setting it to ~300 is bad because it makes the phone use more power to catch up)
How many apps do you have? can you use AppBrain or something to provide me a list of what apps you use?
I just took a list at my CPU Spy...
0:09:51 1200Mhz
920 MHz... 0:01:35
700MHz: 0:09:49
Deep Sleep: 3:21:43
82%... 3h 50m 35s on battery
Android OS 28%
Screen 24%
Google Voice 14%
Phone idle 14%
Android system 7%
Cell standby 3%
Nova Launcher 3%
Wi-Fi 2%
Beautiful Widgets 2%
Market 2%
700-1200MHz. Conservative Governor. Hotplug off
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
lethologica said:
I did try 700 with earlier versions (I think 8 & 9) and was also getting poor battery performance during idle. I wish there was an easier way to determine what app is preventing deep sleep, however it would almost certainly have to be a system app as I did not run any app when I started this test.
Click to expand...
Click to collapse
It doesn't have to be a system app. A app can be started as the moment as Android OS is started.
Not all apps are listed in that battery monitor. I can tell you that for sure. Definitely something is wrong with your phone setup.
The best way to debug it (in my opinion) would be to backup all of your apps and reflash the ROM from scratch. Flash bigxie's ROM (or try another ROM if you choose to) and Franco's Kernel.... install CPU Spy and leave the phone off for like 5-10 minutes. See if it deep sleeps.
Edit: Try this https://market.android.com/details?...251bGwsMSwxLDEsIm5leHRhcHAuc3lzdGVtcGFuZWwiXQ this should help you figure out what app it is.
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
lethologica said:
Thanks for the tip. I am going to recharge and test again with all GPS settings disabled to rule the GPS out. Seeing the gps-lock as the top process in Kernel Waitlocks makes me wonder. I will give SystemPanelLite a try after this test.
Click to expand...
Click to collapse
You did update to the latest Google Maps right? it contained fixes for the battery. Maps is a huge drain if it runs in the background. I always leave my GPS deactivated even though it's activated ondemand. I just don't trust it.
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
lethologica said:
Ahh hah! It has only been 20 minutes, but the GPS is the culprit. I did the same charge, reboot, camera cycle. Then I walked away. Checked CPUSpy and sure enough there was 18 minutes of deep sleep time out of a 20 minutes up time. Google Maps is up to date by the way.
Now the funny thing is, the GPS isn't all that great even when it was keeping my phone awake. Last night I checked the GPS after I got out of the subway (public transit, not sandwiches), for a second it still thought I was in the location prior to taking the subway. It took close to ten seconds to get within 500 meters of my location, and after that it was unable to pinpoint my exact location. The phone has been able to pinpoint my exact location in the past though.
So now, how can I determine if this is a software bug or a hardware bug? If it is software then no big deal, I can hold out. If it is hardware then I need to revert to factory, unroot, etc.
Click to expand...
Click to collapse
It's probably software. Something is keeping the GPS on. Either by a app or ROM. Most likely app.
If you're not using gps with google location services, it will take a while to lock.
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
joshnichols189 said:
Also, you have an app that is requesting GPS constantly while the phone is sleeping.. That is all.
Click to expand...
Click to collapse
Any idea on how to figure out what that app is?
I'm not sure how to find an app that is constantly requesting GPS, but I know the app Watchdog will help find an app that is running in the background consuming processor cycles.. you might want to try that but I have no idea if it will work.
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
did you tuck your phone in?
I had that problem with a Rom and turning on and off the Bluetooth would fix the problem.
Sent from my GalaxyNexus using Tapatalk
imail724 said:
holy ****! thank you! I've been trying to figure out what was causing my phone to not deep sleep for a week! I uninstalled google maps and it worked! now I'd like to figure out how to have both deep sleep and google maps installed...
Click to expand...
Click to collapse
Try disabling GPS when you're not using it. Worked for me.
i tried to freeze the google maps, but still getting the GPS wakelock.
from the other thread, some one mentioned about facebook.
i freeze facebook in titanium backup. looks like the GPS time is not increasing.
are you guys having this issue installed facebook app?
the other thread:
http://forum.xda-developers.com/showthread.php?t=1419087&page=3

[Q] High "Awake" vs "Screen On" time

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.

Strange Battery/CPU Usage

So my battery life has been average, nothing great but nothing terrible. Today I noticed the battery was draining quicker than usual and the phone was slightly laggier and warmer than usual. I looked at battery usage and "Android OS" was at 70%, when seemed abnormally high. I clicked on that and 'total CPU' was at 13 hours. Anyone have any suggestions? I uninstalled some recent apps and my brightness has been relatively low throughout the day..and I've restarted the phone a couple times. I also heard Android OS often can mean some Google services too.
MaxG338 said:
So my battery life has been average, nothing great but nothing terrible. Today I noticed the battery was draining quicker than usual and the phone was slightly laggier and warmer than usual. I looked at battery usage and "Android OS" was at 70%, when seemed abnormally high. I clicked on that and 'total CPU' was at 13 hours. Anyone have any suggestions? I uninstalled some recent apps and my brightness has been relatively low throughout the day..and I've restarted the phone a couple times. I also heard Android OS often can mean some Google services too.
Click to expand...
Click to collapse
That is insanaly high but i feel your utter pain bro..
My best advice is to try and restart the phone. Try and also remove the battery charge it fully and then just leave it for couple hours with the phone locked and display off.. Are you using NFC on location high, wifi and bluetooh all those battery eating goodies if so turn them off?
Try those suggestions and let me know how you get on. If you still having issues i tell you the next stage to the diagnosis (hopefully) which is what I i done lol..
blazer_2704 said:
That is insanaly high but i feel your utter pain bro..
My best advice is to try and restart the phone. Try and also remove the battery charge it fully and then just leave it for couple hours with the phone locked and display off.. Are you using NFC on location high, wifi and bluetooh all those battery eating goodies if so turn them off?
Try those suggestions and let me know how you get on. If you still having issues i tell you the next stage to the diagnosis (hopefully) which is what I i done lol..
Click to expand...
Click to collapse
Well, right now my phone is charging. Android OS is down to 55% which is still way too high. I've already restarted the phone a couple times and just uninstalled Chrome Beta since that was my last app I installed and I figured it might have been doing something. I use WiFi a decent amount but I almost always have NFC and Bluetooth off (and Auto-Sync when I'm not charging). I have location on "battery saving mode".
MaxG338 said:
Well, right now my phone is charging. Android OS is down to 55% which is still way too high. I've already restarted the phone a couple times and just uninstalled Chrome Beta since that was my last app I installed and I figured it might have been doing something. I use WiFi a decent amount but I almost always have NFC and Bluetooth off (and Auto-Sync when I'm not charging). I have location on "battery saving mode".
Click to expand...
Click to collapse
Hmm, Right that seems to abnormal the next stage is to hop on to the Play Store. Download and install an app called 'Greenify' this all go through your system to see what is running that takes a lot of apps and directs you to stooping/disabling them...
On a side note is your brightness level set too high or is it on auto brightness try set it on 40% if you can...
I can't really say much more at this stage? Try those up and report back
blazer_2704 said:
Hmm, Right that seems to abnormal the next stage is to hop on to the Play Store. Download and install an app called 'Greenify' this all go through your system to see what is running that takes a lot of apps and directs you to stooping/disabling them...
On a side note is your brightness level set too high or is it on auto brightness try set it on 40% if you can...
I can't really say much more at this stage? Try those up and report back
Click to expand...
Click to collapse
Well, it seems to have sort of fixed itself. I woke up this morning and "Android OS" usage was down to about 15% and the CPU Total and Keep Awake time reset also. On a side note, I got great battery life today by turning off Google Now, background data, auto-sync, location, and keeping brightness at about 35-50% (which I usually do anyway).
That's really good glad it's sorted it self out keep an eye out on it and keep me posted coz I had more to suggest but hey ho
..
Its all good
Sent from my LG-D855

High battery drain with doze overnight

I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
bosox284 said:
I'm no stranger to Android and troubleshooting problems, but right now I'm honestly at a loss as to what is causing my battery drain. I'm losing a little over 1% per hour while the device is in doze overnight, adding up to around 10-12% over 8 hours. Previously the max I would lose was close to 5%. I can't pinpoint exactly when something went rogue, but I want to say it was after the January update. I don't think I've added any new apps. I've obviously tried to clear data/cache in Google Play Services among some other apps too.
I've tried to use the battery historian, GSam, BBS, you name it. GSam is showing my device as constantly waking up overnight while in deep doze, but I can't attribute that to any wakelocks. BBS is basically clean as far as partial wakelocks go, and battery historian shows that 7% of the battery drain is unaccounted for. The one thing I have seen a few nights now is the Significant Motion that's in Google Play Services. I've also seen that under Phone and under Android System. I'm wondering if it's some kind of sensor, but I can't figure out what is causing it to stay on. I keep my phone on my nightstand overnight.
My next steps are going to be turning off always on display (AOD), turning on airplane mode overnight, and then doing a factory reset. I'll report back for anyone that comes across here, but I wanted to see if anyone has had similar issues.
I'm attaching a few screenshots, maybe someone can pick up something I'm missing.
https://imgur.com/a/rGxXQ
Click to expand...
Click to collapse
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it ?
Badger50 said:
Are you rooted by chance? I've seen this mentioned in a couple other threads. Seems the culprit has something to do with GPS's, tethering in developer options, wifi and bluetooth scanning or a rouge app. Most all the cases I've seen have been since the 8.1 update.
Solutions I've seen...turn off everything in the pic.
Clear cache/data on play services(kinda risky)
Clean flash the January update with fastboot.
Turn off bluetooth and wifi scanning.
Check your router setup(some wifi setups like to keep waking the device. I get this in hotels at times)
Try turning wifi off at night.
How many apps are using location services?(I had a weather app that was keeping my device awake)
This can definitely be a bugger to identify. Sure hope you find it
Click to expand...
Click to collapse
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
I wouldn't worry about turning off AOD saving you a bunch, I turned mine off and didn't notice any diff at all in overnight batt drain, so set it to DIM, and still haven't noticed any additional batt drain from when it was off.
If you really want to be a miser without totally losing AOD,
"always on" OFF,
"Lift to check phone" ON,
(Settings>Display>Ambient display>)
set it to DIM (Settings>Display>Screen Saver>Current Screen Saver gear>Night mode checked)
which is how mine is set up
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
Where is that fix touch module?
Sent from my Google Pixel 2 XL using XDA Labs
Prattham said:
Where is that fix touch module?
Click to expand...
Click to collapse
Look in downloads in magisk manager.
Badger50 said:
Wtf weather was the one giving me trouble at one time. I just turned a few things off on that one. Are you using the "enable doze for GSM" magisk module like in the pic. That really seems to keep google play services in check :good:
Click to expand...
Click to collapse
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
bosox284 said:
I've been trying to avoid using that module just because I don't want to delay anything from GCM, but I'm going to look into it if I can't identify another culprit.
Click to expand...
Click to collapse
Delay what? ?
Badger50 said:
Delay what? <span class="emoji-outer emoji-sizer"><span class="emoji-inner" style="background: url(chrome-extension://immhpnclomdloikkpcefncmfgjbkojmh/emoji-data/sheet_apple_32.png);background-position:73.97179788484137% 79.9647473560517%;background-size:5418.75% 5418.75%" data-codepoints="1f914"></span></span>
Click to expand...
Click to collapse
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
bosox284 said:
GCM = Google Cloud Messaging, it's integrated into apps for push notifications. My (perhaps incorrect) assumption is that by dozing Play Services, you could delay push notifications for other apps.
Click to expand...
Click to collapse
Haven't noticed any delay what so ever with any push notifications from any apps. Google or otherwise :good:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
I noticed this as well and it seems to have started after the January update. Although mine isn't quite as bad. Pre-January update I was losing about 2-3% in like 8 hours. I'm now losing that much in like 4-5 hours. There were 2 days in a row where I actually lost like 15-18% over like 7 hours.
rickysidhu_ said:
I lost 11% overnight (8 hours), I have Amplify, Enable Doze for Google Play Services Magisk module and ForceDoze, and still getting that drain.
Could it be these apps conflicting with one another?
Click to expand...
Click to collapse
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
The Jan update has been ****. I would get almost 7 hrs SOT with 20% left. Now all I get is ****ty 4 hrs and phone at 10%. Usage wise it's the same since day 1 nothing new as such. No rogue app on BBS. This is messed up.
Badger50 said:
Get rid of amplify and forcedoze. Then see what happens. You've got too many things trying to do the same thing!
Click to expand...
Click to collapse
Yeah I had a feeling that could be it. I'll give it a shot by removing them, thanks for the suggestion! :highfive:
Badger50 said:
Look in downloads in magisk manager.
Click to expand...
Click to collapse
It isn't there that's why i asked
Sent from my Google Pixel 2 XL using XDA Labs
bosox284 said:
I am rooted. I've got WiFi/bluetooth scanning off, but I did just notice that Tethering hardware acceleration was on. I'm turning that off. I'll see how that goes tonight, if it's still draining then I'll try turning WiFi off and see what happens.
I've got GasBuddy, Google, Play Services, Maps, and WTForecast using location. None of those usually show up in any battery stats aside from Play Services.
Click to expand...
Click to collapse
Try to run "su" and then "top" from terminal,
See what is your top process,
In one occassion, my magisk hide stucked up and using 30%++ of CPU all the time, even when idle, and that drain the battery in no time,
Am on 8.1 Jan, Kiriskura Kernel,
Tweak applied is Brevent, Amplify and my own EnableDoze for GMS.
Never lost more than 5% in 9 hours of sleep. Average is 2-3% with wifi on. Less than 2% when network is totally off
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
You can try the one attached.
I cant find it in download section as well
Prattham said:
It isn't there that's why i asked
Click to expand...
Click to collapse
My bad. I forgot that it was a special build by another user. Install it from magisk manager. If it doesn't install, then flash it in twrp.
https://github.com/AndroPlus-org/ma...b/master/magisk-module-fix-touch-pixel2xl.zip

Question Abnormal battery consumption when idle?

My Asus ROG Phone 6 loses 5% battery life in 24h while just idling.
WiFi and Bluetooth are turned off. I don't have a SIM card installed yet, but even with a "Aeroplane mode" activated, I get the same consumption.
Is that consumption normal?
What irritates me is that in the beginning I saw horizontal lines in the "Battery usage" chart, indicating close to zero battery consumption when the phone was turned off. I don't get these horizontal segments anymore.
I installed GSam Battery Monitor and it shows 100% time spent in Deep sleep (but shows a "5% / 5%" for "Discharge Screen Off"). In the "OTHERS" chart, "Doze" is a continuous line but "Active" shows a lot of interrupted small blocks ("Screen" is obviously completely absent). "Wifi" is shown as always on, but I believe that is a bug because I turned off the location-based features that turn on Wifi automatically, turned on Aeroplane mode, etc. After a restart, the "Wifi" bar was correctly absent for a while but briefly turning Wifi on, got it back to "always on". I'm 99.9% sure this is a GSam bug.
I have double confirmed with "DevCheck" that the CPU goes to "Deep sleep" and spends pretty much all the time in that state.
I get about "5m" combined App Wakelocks in 48h.
The biggest battery consumer is "Kernel (Android OS) 7.5%", followed by "System (*wakelock*) 2.3%", "Google Play services 1.6%". These figures are from a 14 day period in which I used the phone for 3h to play a game (6.7% consumption) and otherwise only turned it on to check the battery. I currently don't have access to the percentage figures during pure sleeping since I plugged in the phone for charging.
Using GSam Battery Monitor, I don't see any app wasting battery life in the background. It's the kernel that consumes the vast majority of the battery life, if the phone is idle. The Android/Asus Battery usage stats show "Phone idle" with 54.7% for that 14 day period. The next one is the game with 3.8% (played for 3h) and then there is "Screen" with 1.9%.
I'd understand this kind of idle figure if the phone had a SIM card installed and bad reception but as I said before there is no card in the phone yet and the consumption is the same if I put it in Aeroplane mode.
I'm running Android 12, build 32.2810.2212.241.
The battery "system mode" is "Dynamic". The refresh rate is set to "60Hz" (not that it should matter with the screen turned off all the time). "Battery Saver" in the "Developer options" is turned "on".
I'd be grateful if someone could comment on the 5% battery life loss within 24h. I realize that many will not be able to compare this with their figures, as they'll have a cell phone service running, but perhaps those who turns on Aeroplane mode, should have comparable figures, for an 8h period, or so.
My Huawei Mate 20 (running Android 10) shows pretty much no consumption at all over night via the battery stats, when I turn on Aeroplane mode. Perhaps it loses 1% or at most 2%, I'll check again. Should the ROG Phone 6 behave the same, or is this difference to be expected?
Again, I'm irritated that I definitely saw multiple horizontal (no usage) periods in the battery usage chart in the beginning. I'm pretty sure these appeared before I had given the phone a full charge yet, so perhaps they weren't really indicative of close to zero consumption due to a lack of battery capacity calibration.
TomKay said:
My Asus ROG Phone 6 loses 5% battery life in 24h while just idling.
(...)
Click to expand...
Click to collapse
Congratulations. 0.2%/h is a very good result.
TomKay said:
My Asus ROG Phone 6 loses 5% battery life in 24h while just idling.
WiFi and Bluetooth are turned off. I don't have a SIM card installed yet, but even with a "Aeroplane mode" activated, I get the same consumption.
Is that consumption normal?
What irritates me is that in the beginning I saw horizontal lines in the "Battery usage" chart, indicating close to zero battery consumption when the phone was turned off. I don't get these horizontal segments anymore.
I installed GSam Battery Monitor and it shows 100% time spent in Deep sleep (but shows a "5% / 5%" for "Discharge Screen Off"). In the "OTHERS" chart, "Doze" is a continuous line but "Active" shows a lot of interrupted small blocks ("Screen" is obviously completely absent). "Wifi" is shown as always on, but I believe that is a bug because I turned off the location-based features that turn on Wifi automatically, turned on Aeroplane mode, etc. After a restart, the "Wifi" bar was correctly absent for a while but briefly turning Wifi on, got it back to "always on". I'm 99.9% sure this is a GSam bug.
I have double confirmed with "DevCheck" that the CPU goes to "Deep sleep" and spends pretty much all the time in that state.
I get about "5m" combined App Wakelocks in 48h.
The biggest battery consumer is "Kernel (Android OS) 7.5%", followed by "System (*wakelock*) 2.3%", "Google Play services 1.6%". These figures are from a 14 day period in which I used the phone for 3h to play a game (6.7% consumption) and otherwise only turned it on to check the battery. I currently don't have access to the percentage figures during pure sleeping since I plugged in the phone for charging.
Using GSam Battery Monitor, I don't see any app wasting battery life in the background. It's the kernel that consumes the vast majority of the battery life, if the phone is idle. The Android/Asus Battery usage stats show "Phone idle" with 54.7% for that 14 day period. The next one is the game with 3.8% (played for 3h) and then there is "Screen" with 1.9%.
I'd understand this kind of idle figure if the phone had a SIM card installed and bad reception but as I said before there is no card in the phone yet and the consumption is the same if I put it in Aeroplane mode.
I'm running Android 12, build 32.2810.2212.241.
The battery "system mode" is "Dynamic". The refresh rate is set to "60Hz" (not that it should matter with the screen turned off all the time). "Battery Saver" in the "Developer options" is turned "on".
I'd be grateful if someone could comment on the 5% battery life loss within 24h. I realize that many will not be able to compare this with their figures, as they'll have a cell phone service running, but perhaps those who turns on Aeroplane mode, should have comparable figures, for an 8h period, or so.
My Huawei Mate 20 (running Android 10) shows pretty much no consumption at all over night via the battery stats, when I turn on Aeroplane mode. Perhaps it loses 1% or at most 2%, I'll check again. Should the ROG Phone 6 behave the same, or is this difference to be expected?
Again, I'm irritated that I definitely saw multiple horizontal (no usage) periods in the battery usage chart in the beginning. I'm pretty sure these appeared before I had given the phone a full charge yet, so perhaps they weren't really indicative of close to zero consumption due to a lack of battery capacity calibration.
Click to expand...
Click to collapse
I lose 0% on 10 hours standby in flight mode
Thanos88 said:
I lose 0% on 10 hours standby in flight mode
Click to expand...
Click to collapse
That's great!
What build number of Android OS are you running?
I'd be grateful, if you could check it and post it here.
Have you done anything to get this performance or is it "out of the box"?
ze7zez said:
0.2%/h is a very good result.
Click to expand...
Click to collapse
I'm not so sure.
First, remember that this figure is without any cell phone service drawing current.
Second, I initially saw segments of the battery consumption graph that were horizontal, but no longer do.
Third, look at what Thanos88 reported.
I've seen other posts about unusually high idle consumption of the ROG Phone 6. I believe most users will not even notice because they don't shut down their phones fully and the idle consumption disappears as noise under the all the higher normal consumption. Perhaps other users don't complain, because they don't suffer from the issue I seem to be having. I don't know.
TomKay said:
That's great!
What build number of Android OS are you running?
I'd be grateful, if you could check it and post it here.
Have you done anything to get this performance or is it "out of the box"?
Click to expand...
Click to collapse
android 12
.197 firmware
Done plenty of app debloating
Thanos88 said:
android 12
.197 firmware
Done plenty of app debloating
Click to expand...
Click to collapse
Thanks!
I note that you are not on the latest version (.241). That could explain the difference. Perhaps I saw the near to zero consumption before I accepted the update to .241? That is quite possible.
I've done a lot of app debloating as well, removing Facebook, etc., but as I mentioned before, there are no apps that cause any noteworthy battery consumption. Did you do anything out of the ordinary? I first just uninstalled and/or disabled some apps/services that I did not need and later even uninstalled some via ADB. The latter made no difference regarding battery consumption.
My 5%/24h figure comes from
41.3% Android System
15.2% Kernel (Android OS)
4.4% Phone Services
3.5% com.android.systemui:screenshot
3.1% Google Play services
2.0% com.google.uid.shared:.....
1.9% GSam Battery Monitor
0.9% ASUS Launcher
There are some more (e.g., 0.4% Gmail) but they don't use much at all.
Time Held Awake (over a 37h period):
Kernel (Android OS) 10m 53s
Android System 4m 1s
Google Play services 16s
com.google.uid.shared:..... 2s
com.android.systemui:screenshot 1s
That's all, no other apps/services are reported to keep the phone awake (while it was idling).
Number of times Waking Device
Google Play services 48
Android System 34
Calendar Storage 8
android.uid.calendar:..... 7
com.android.systemui:screenshot 6
com.google.android.partnersetup 5
There are a few more, but the next one has a figure of 3 and the rest are all lower.
No network data used (no SIM card, Wifi turned off) and no location used either.
I note that further battery consumers were sensors used by
Dirac Control Service 13m 5s
Android System 1m 17s
I do not know whether this is normal.
Is it possible to revert to the .197 firmware (or whatever firmware version my phone originally had) by performing a factory reset?
Or does the latter just clear all user data but leaves the current firmware in place?
In the latter case I would have to flash the .197 firmware manually, correct?
Would the latter be safe regarding warranty, etc.?
I don't want to root the phone or anything like that, I just would like to avoid unnecessary battery consumption.
TomKay said:
Thanks!
I note that you are not on the latest version (.241). That could explain the difference. Perhaps I saw the near to zero consumption before I accepted the update to .241? That is quite possible.
I've done a lot of app debloating as well, removing Facebook, etc., but as I mentioned before, there are no apps that cause any noteworthy battery consumption. Did you do anything out of the ordinary? I first just uninstalled and/or disabled some apps/services that I did not need and later even uninstalled some via ADB. The latter made no difference regarding battery consumption.
My 5%/24h figure comes from
41.3% Android System
15.2% Kernel (Android OS)
4.4% Phone Services
3.5% com.android.systemui:screenshot
3.1% Google Play services
2.0% com.google.uid.shared:.....
1.9% GSam Battery Monitor
0.9% ASUS Launcher
There are some more (e.g., 0.4% Gmail) but they don't use much at all.
Time Held Awake (over a 37h period):
Kernel (Android OS) 10m 53s
Android System 4m 1s
Google Play services 16s
com.google.uid.shared:..... 2s
com.android.systemui:screenshot 1s
That's all, no other apps/services are reported to keep the phone awake (while it was idling).
Number of times Waking Device
Google Play services 48
Android System 34
Calendar Storage 8
android.uid.calendar:..... 7
com.android.systemui:screenshot 6
com.google.android.partnersetup 5
There are a few more, but the next one has a figure of 3 and the rest are all lower.
No network data used (no SIM card, Wifi turned off) and no location used either.
I note that further battery consumers were sensors used by
Dirac Control Service 13m 5s
Android System 1m 17s
I do not know whether this is normal.
Is it possible to revert to the .197 firmware (or whatever firmware version my phone originally had) by performing a factory reset?
Or does the latter just clear all user data but leaves the current firmware in place?
In the latter case I would have to flash the .197 firmware manually, correct?
Would the latter be safe regarding warranty, etc.?
I don't want to root the phone or anything like that, I just would like to avoid unnecessary battery consumption.
Click to expand...
Click to collapse
Try to force stop and clear data & clear cache of Google play services , then reboot your device , charge to full and then see what happens
Thanos88 said:
Try to force stop and clear data & clear cache of Google play services , then reboot your device , charge to full and then see what happens
Click to expand...
Click to collapse
Thanks for the tip! I've done that before, without the "charge to full". I can try the exact sequence you have described.
Given the usage figures, Google play services are not using much:
Just
3.1% Google Play services
compared to
41.3% Android System
15.2% Kernel (Android OS)
4.4% Phone Services
Are you saying that either Google Play services are using battery in a way that GSam does not catch, or that Google Play services somehow responsible for the high system consumption?
I would say Google play services is causing the issue. Also I forgot to mention, make sure you force stop, then click "uninstall updates" on Google play services, then clear cache , then Clear data then reboot your phone.
If that doesn't help, I highly recommend you dow load BBS (Better battery stats) , give it adb permissions, and monitor your battery life/wakelocks with that app
TomKay said:
Thanks for the tip! I've done that before, without the "charge to full". I can try the exact sequence you have described.
Given the usage figures, Google play services are not using much:
Just
3.1% Google Play services
compared to
41.3% Android System
15.2% Kernel (Android OS)
4.4% Phone Services
Are you saying that either Google Play services are using battery in a way that GSam does not catch, or that Google Play services somehow responsible for the high system consumption?
Click to expand...
Click to collapse
Thanos88 said:
I would say Google play services is causing the issue. Also I forgot to mention, make sure you force stop, then click "uninstall updates" on Google play services, then clear cache , then Clear data then reboot your phone.
If that doesn't help, I highly recommend you dow load BBS (Better battery stats) , give it adb permissions, and monitor your battery life/wakelocks with that app
Click to expand...
Click to collapse
I followed the steps you described (including the "uninstall updates") and will report results, once the phone has fully charged and has idled for 24h. If there is no change, I'll uninstall GSam and install BBS.
Thanks a lot for your help.
Sadly, clearing the data&cache of Google Play services and downgrading it, did not help, at least it does not look like it helped right now.
This time, the battery lost 6% in 30h (went from 100% to 94%).
The last few hours showed very little battery consumption, though. Perhaps there was some book keeping to do after reboot which caused some consumption up until very recently.
I'll let the phone idle for another 24h and see whether the flat period continues. It would be awesome if it did.
I let the phone idle for another 24h and even though I restricted battery usage for more apps/services, the idle consumption did not change.
I'll try Better Battery Stats now.
T
TomKay said:
I let the phone idle for another 24h and even though I restricted battery usage for more apps/services, the idle consumption did not change.
I'll try Better Battery Stats now.
Click to expand...
Click to collapse
That's odd. What's your software number?
Thanos88 said:
T
That's odd. What's your software number?
Click to expand...
Click to collapse
Android 12, build 32.2810.2212.241
Three updates more current than your .197 version.
I would have thought that if Google Play services were at fault, GSam Battery Monitor would have showed that. But perhaps not. I'll see whether BBS will provide any better clues. I could also try to disable Google Play services (just for diagnosing purposes), but I'm not sure that would result in any useful data, as many apps complain, if one disables Google Play services completely.
I suspect the difference between your idle consumption and mine is the firmware version. I've disabled/restricted so many apps/services, I doubt the phone would run normally now. So far, no culprit has been identified.
TomKay said:
Android 12, build 32.2810.2212.241
Three updates more current than your .197 version.
I would have thought that if Google Play services were at fault, GSam Battery Monitor would have showed that. But perhaps not. I'll see whether BBS will provide any better clues. I could also try to disable Google Play services (just for diagnosing purposes), but I'm not sure that would result in any useful data, as many apps complain, if one disables Google Play services completely.
I suspect the difference between your idle consumption and mine is the firmware version. I've disabled/restricted so many apps/services, I doubt the phone would run normally now. So far, no culprit has been identified.
Click to expand...
Click to collapse
It's going to be the firmware then, or maybe even an app you've installed. I'm currently on 44% battery, with 9 hours 41 mins SOT, 1 days 2 hours off charge
Thanos88 said:
It's going to be the firmware then, or maybe even an app you've installed. I'm currently on 44% battery, with 9 hours 41 mins SOT, 1 days 2 hours off charge
Click to expand...
Click to collapse
I think I can exclude any user apps, since,
1. The issue is the same if I start the phone in "Safe mode" (disables all user apps).
2. GSam Battery Monitor would have reported high usage by an app.
The battery consumers are the OS and motion sensors.
I turned off "Lift phone to check" (or similar) and the phone indeed does not activate the lock screen when I move it while the screen is dark. The phone stills faintly shows the fingerprint area if I move it, so some motion detection must be going on. I don't think this behaviour can be disabled, or can it?
TomKay said:
I think I can exclude any user apps, since,
1. The issue is the same if I start the phone in "Safe mode" (disables all user apps).
2. GSam Battery Monitor would have reported high usage by an app.
The battery consumers are the OS and motion sensors.
I turned off "Lift phone to check" (or similar) and the phone indeed does not activate the lock screen when I move it while the screen is dark. The phone stills faintly shows the fingerprint area if I move it, so some motion detection must be going on. I don't think this behaviour can be disabled, or can it?
Click to expand...
Click to collapse
The fingerprint motion can be switched off in the settings however, it's probably the firmware that's causing the main issue imo
Thanos88 said:
The fingerprint motion can be switched off in the settings however, it's probably the firmware that's causing the main issue imo
Click to expand...
Click to collapse
where in the settings can be turned off fingerprint motion ?
luki2411 said:
where in the settings can be turned off fingerprint motion ?
Click to expand...
Click to collapse
Not sure if it's just me or they've removed that option looks like it can't be removed but I surely that motion can't be the battery culprit. It has to be the firmware

Categories

Resources