This topic has been up a couple of times before, perhaps most interestingly discussed in this thread.
It appears the problem still exists (asusdec_wake kernel wake), and I'm experiencing extreme battery drain during sleep with the dock attached. Currently running Cromi-X 5.4, and I have tried hunds 3.4.4, and _that 8 and 9 kernels.
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up. It only occurs when the tablet is docked, it can occur at both high charge levels and when the dock is empty (mine always drains to 0%). It does not seem to matter whether wifi is on or off. I monitor the battery with better battery stats.
It's a real pity, since I have to turn the tablet off whenever I want to keep the dock attached.
Is anyone else experiencing this drain? Any suggestions for fixes?
Also: obligatory first post thanks-for-making-my-tablet-great to @sbdags, @_that and all the other contributors to Cromi :good:
rkha said:
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up.
Click to expand...
Click to collapse
How do you know that it first enters deep sleep and that it's woken up later?
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
_that said:
How do you know that it first enters deep sleep and that it's woken up later?
Click to expand...
Click to collapse
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
_that said:
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
Click to expand...
Click to collapse
Good point. Any tips on how this can be diagnosed?
rkha said:
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
Good point. Any tips on how this can be diagnosed?
Click to expand...
Click to collapse
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
sbdags said:
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
Click to expand...
Click to collapse
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
rkha said:
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
Click to expand...
Click to collapse
It's Google now constantly polling for your location as far as I can tell.
Related
Hello guys, I had some battery trouble with my Nexus 5, and during my investigations I saw something strange.
I used CurrentWidget app to track my
current drain, during wake and during sleep. Settings: Update Interval = 10 sec, Log Values to file = true, Force Log in sleep mode = true.
When I viewed the log as graph I saw that during sleep the current drain never decreases to something close to 0 mA, it stays around 100 mA,
or goes down to 30-40 mA, but absolutely never less than this, as you can see in the attached screenshots.
I tested and confirmed this behavior with 4.4.4 and 5.0.1, both flashed clean with factory images, without any other apps installed besides Google apps. During the tests I kept the phone with normal usage: WiFi on, 2G network, Bluetooth on, Location Battery saving, Auto-sync on, and just some net browsing. But of course the most important information was collected during sleep with screen off. Surprisingly, by putting the phone in Airplane mode the current drain in sleep remained exactly the same, between 30-100 mA.
I also tested this on a Nexus 4 with 5.0.1 and during sleep it consumes around 2-4 mA, so there is a big difference.
Can any of you also install the CurrentWidget app, configure the logging, wait a few hours than make a screenshot of your current drain graph ?
I want to see if it's something abnormal with my phone of if it's a general thing. It would be very grateful. Thank you.
Is the widget keeping the phone out of deep sleep? A la wakelock... Just a theory.
what are your wakelocks ?
try gsam battery monitor,
i thought currentwidget drains the battery,i only used that program to check charging current and display idle, but never kept it when display was off.
or try betterbatterystats
http://forum.xda-developers.com/showthread.php?t=1179809
republicano said:
what are your wakelocks ?
try gsam battery monitor,
i thought currentwidget drains the battery,i only used that program to check charging current and display idle, but never kept it when display was off.
or try betterbatterystats
http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
I'm not interested in wakelocks, just current drain.
And no, I don't think it's keeping the phone from entering deep sleep, it just wakes up from time to time to log the current.
Anyway, the same app with the same settings on my Nexus 4 records 2 mA in sleep mode, so it's definitely in deep sleep.
So , please can you do this experiment on your phone and share the results ? Thank you so much.
I very rarely got below 27mA. Though I've no idea of it was in deep sleep at that time.
rootSU said:
I very rarely got below 27mA. Though I've no idea of it was in deep sleep at that time.
Click to expand...
Click to collapse
An even better app that can log the current drain of the phone is Battery Monitor Widget. I configured the recording interval to 10 seconds for testing and played with the Graphics window.
The first picture is from a friend's Nexus 5 (stock 5.0.1) and the second one is mine (stock 4.4.4, but same tested on 5.0.1),
As you can see the current drain even in sleep never decreases below 30 mA and the mean is around 100 mA.
This is very bad, because even the Nexus 4 with 5.0.1 has a 3 mA drain in sleep,
so why is the Nexus 5 drain from 10 to 30 times more ?
Can someone shed any light on this ?
At 100mA drain, your phone would hypothetically last 23 hours. 100mA * 23 hours = 2300mAh. I doubt that. It surely must last longer than that, if it is indeed in deep sleep and not kept awake by some application.
My hypothesis is that what you're seeing is a calibration error. The current measurement is more than likely inferred by accounting for other factors. (I doubt the current is measured directly - ie. as an ammeter). Therefore, I would suggest taking it with a grain of salt.
That being said, with all things being equal, if someone were to do the test, they would probably get similar results to you.
JayR_L said:
At 100mA drain, your phone would hypothetically last 23 hours. 100mA * 23 hours = 2300mAh. I doubt that. It surely must last longer than that, if it is indeed in deep sleep and not kept awake by some application.
My hypothesis is that what you're seeing is a calibration error. The current measurement is more than likely inferred by accounting for other factors. (I doubt the current is measured directly - ie. as an ammeter). Therefore, I would suggest taking it with a grain of salt.
That being said, with all things being equal, if someone were to do the test, they would probably get similar results to you.
Click to expand...
Click to collapse
Can you please do the test on yours?
My results are comparable to yours, andreipaval. The current sensor was more than likely designed for limiting charging current and not for measuring sleep current. Plus, more importantly, the phone definitely has to be pulled out of deep sleep to even make a measurement. The sensor being off by less than a hundred milliamps makes little difference when one can charge at much higher rates but it will falsely report the idle drain.
Perhaps it was your Nexus 4 that was off by -100mA and falsely reported 3-4mA. It can safely assumed that the internal leakage of the battery itself is probably more significant than 3-5mA... Thus, as I previously suggested - you might want to consider taking this with a grain of salt. If you want to do a more conclusive test, see how long your phone lasts from 100% to 0% in deep sleep and airplane mode. You can get a pretty good estimate of the drainage that way. (Batt capacity divided by number of hours)
JayR_L said:
My results are comparable to yours, andreipaval. The current sensor was more than likely designed for limiting charging current and not for measuring sleep current. Plus, more importantly, the phone definitely has to be pulled out of deep sleep to even make a measurement. The sensor being off by less than a hundred milliamps makes little difference when one can charge at much higher rates but it will falsely report the idle drain.
Perhaps it was your Nexus 4 that was off by -100mA and falsely reported 3-4mA. It can safely assumed that the internal leakage of the battery itself is probably more significant than 3-5mA... Thus, as I previously suggested - you might want to consider taking this with a grain of salt. If you want to do a more conclusive test, see how long your phone lasts from 100% to 0% in deep sleep and airplane mode. You can get a pretty good estimate of the drainage that way. (Batt capacity divided by number of hours)
Click to expand...
Click to collapse
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
andreipaval said:
Can any of you also install the CurrentWidget app, configure the logging, wait a few hours than make a screenshot of your current drain graph ?
I want to see if it's something abnormal with my phone of if it's a general thing. It would be very grateful. Thank you.
Click to expand...
Click to collapse
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
bblzd said:
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
Click to expand...
Click to collapse
You got almost 6 hours of SOT from a single charge? How did you do that?
It seems impossible to me...
Well, I get anywhere between 5 to 6 hours of SOT if I use the phone heavily (continually). If I'm working and just using the phone regularly, I get between 3-4 hours of SOT. I assume it's the moving around, changing cell towers, turning WiFi on and off and things like that. Also, web browsers are notorious for ramping up CPU frequencies, and hence power drain. I can get 5-6 hours using Tapatalk but not playing games and browsing the web.
---------- Post added at 06:20 PM ---------- Previous post was at 06:17 PM ----------
bblzd said:
I have looked into this myself recently using software readings from Current Widget and agree with your findings. Basically once the phone enters true deep sleep the measurement intervals increase until it's the only process waking the phone and measuring higher rates than would be found without the software waking the device.
I have made a log of power level readings with Current Widget in various forms of usage. The update interval was set to 5 seconds but you can see at the beginning when the phone was mostly idle the update interval becomes delayed and sees above average idle measurements. Compare this to after when I began to listen to music on the phone with the screen mostly off. Here we can see lower numbers while the phone is actively playing music, less so than before when the phone was said to be in deep sleep. There are periods of idle followed by various periods of screen usage following that, more details can be found in the album included below.
There's also the case of background software drains. Things like Google Now and Auto Syncs kicking in, and whatever other apps and services may be installed. These results were with Google Now off, Locations off, Hotword off, Auto syncs on, and Adaptive Brightness on set to 40%.
I took screen shots of my usage having ended the voltage measurements at the 45% mark of this charge.
http://imgur.com/a/5VsRI 45% remaining
http://imgur.com/a/vQpoz 5% remaining
Click to expand...
Click to collapse
Thank you @bblzd for following up with the research and confirming my hypothesis.
andreipaval said:
You got almost 6 hours of SOT from a single charge? How did you do that?
It seems impossible to me...
Click to expand...
Click to collapse
Battery life is determined mostly by usage, settings and signal. So the apps I used, with the settings mentioned, on a strong WiFi signal.
There are ways I could increase battery life further such as lower brightness, disable auto syncs (or have them set on an automated schedule like I was forced to do on Kit Kat) or even disable Dashclock despite its minimal attributed drain. There are also always random factors such as incoming calls, texts, app updates, etc.
Generally the Nexus 5 is great on battery using WiFi, but only average when using data connection or making voice calls. This can be seen in Anandtech's review back from Dec. 2013.
http://anandtech.com/show/7517/google-nexus-5-review/3
I've had this phone for a few days now and I notice some mean battery drain that happens from time to time. I dumped a Bug Report via developer options, and used Google's Battery Historian after leaving my phone unplugged and idle overnight after a full charge and reboot. The tool seems to show that the following kernel wakeup reason seems to be the problem and holding the phone awake for over 1.5 hours:
Code:
Ranking Name Duration/Hr Count/Hr Total Duration Total Count
0 Abort:Wakeup IRQ -1111803216 (null) pending 10m8s737ms 779.87 1h34m13.62s 7243
The only thing that looks remotely relevant is that on the tool WiFi signal strength became weaker when the above wakeup events started.
Has anyone else had similar issues with random battery drains like this and/or happen to know any workarounds?
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
I tried setting wifi to stay on when sleeping when plugged in, after a full idle overnight, I used my phone in the morning and the same issue came up. The ID above was different, but generally the same problem (IRQ with no description pending). Again, it looks to be wifi related based on the battery stats in Historian. I've rebooted, charged up and turned off wifi to see if the problem goes away.
ru_ready said:
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
Click to expand...
Click to collapse
You might want to try enabling developer options and getting a bugreport generated (which has battery stats), and then visualizing it in Google's Battery Historian to see if it is the same problem. Kind of convoluted, I know, but without root, I don't know of any better way to analyze kernel wakelocks (it isn't a partial wakelock issue on my device).
Last night I left my phone idle with wifi off and WLAN Scanning and Bluetooth Scanning off under Location Settings. The battery ran down only 2% over 9 hours and the Wakeup IRQ pending problem did not keep the phone awake!
I am going to try turning wifi back on today but keep the scanning off and see if that keeps this problem at bay. If not, I may use Tasker to force wifi off when the screen is not on and not plugged in.
The wakelocks seem to happen randomly no matter what my wifi settings are. Though I do think it is related to location settings trying to use wifi scanning.
I give up, there is no reason why a phone I just bought should be like this.
Maybe there are some apk wake up the system
@kumodog Maybe there are some apk wake up the system, you can reboot the system and kill all of application programs when you test it in night with wifi on.
After test, you can also use : "adb dumpsys alarm" in command line to find Top Alarms. it will tell you which alarm make system wakeup.
I have a serious problem with stand-by time of my galaxy s7.
I have updated my device to Nougat and i am using ForceDoze to put the phone to sleep (without root, with adb command), although i am not sure if it is really working.
I lose about 3-4% battery every hour when idle.
With idle i mean always on display on, wifi or data on, gps and bluetooth off, power saving off.
When i check better battery stats and accubattery, it shows the phone in deep sleep most of the time.
I think this amount is ridiculous. It shouldn't consume more than 2% with this setup, assuming AOD consumes 1% per hour.
I don't have a problem with screen-on time. Only with stand-by time.
Do you have any suggestions for me? What could be the problem?
Find out what is running on your phone by going to running services. Disable the apps you dont need running, turn off always on display and see your battery times then. Clearly something is running in the background and this is up to you to find out what is running....
Second option root your phone, uninstall the bloat and install greenify.
omeren83 said:
I have a serious problem with stand-by time of my galaxy s7.
I have updated my device to Nougat and i am using ForceDoze to put the phone to sleep (without root, with adb command), although i am not sure if it is really working.
I lose about 3-4% battery every hour when idle.
With idle i mean always on display on, wifi or data on, gps and bluetooth off, power saving off.
When i check better battery stats and accubattery, it shows the phone in deep sleep most of the time.
I think this amount is ridiculous. It shouldn't consume more than 2% with this setup, assuming AOD consumes 1% per hour.
I don't have a problem with screen-on time. Only with stand-by time.
Do you have any suggestions for me? What could be the problem?
Click to expand...
Click to collapse
Hi mate
Most of times is configuration issues or a rouge app , install a an like BBS let it run for a few hours and check the log to see who is keeping the phone awake.
review your settings wifi , location email, FB ........
I think i found what the problem is. It is always-on display. Last night, i turned it off. With only wi-fi on, i lost 1% per hour.
Apparently, AOD consumes way more juice than i thought.
omeren83 said:
I think i found what the problem is. It is always-on display. Last night, i turned it off. With only wi-fi on, i lost 1% per hour.
Apparently, AOD consumes way more juice than i thought.
Click to expand...
Click to collapse
I found AOD prevented Doze from working, which in turn used way more in idle, so it's not specifically AOD draining it, it's because it's not at it's lowest power state during idle
I have had a battery drain for several weeks now. It isn't to severe but the biggest issue bothering me the most is at night it is draining about 5-6% even with battery saver turned on. It used to be that in normal mode, the battery would only drop 2-3% over night. I do not charge at night.
I am fully updated and I even reset the phone to factory 2 days ago and the issue still persists. Nothing seems to stand out in the battery stats with regards to apps sucking battery %. So I think this is an issue where it is not going into Doze or Deep Doze but I dont know how to determine that.
Any suggestions how to find the problem?
(on android 10)
When you wake up in the morning...
Go into "Settings"
Then "Battery"
Then click the top right three dots
Then select "Battery Usage"
It should show you which apps used the most battery during the night.
JohnC said:
(on android 10)
When you wake up in the morning...
Go into "Settings"
Then "Battery"
Then click the top right three dots
Then select "Battery Usage"
It should show you which apps used the most battery during the night.
Click to expand...
Click to collapse
I have done that. No apps appear to be doing anything unusual. There are no battery hogs showing up. Not even excessive google services usage or anything. That is why I think this may be a situation where it isn't going into doze or deep doze like it used to but I dont know how to check or monitor that. that info doesn't show in battery stats.
I never heard of this doze/deep doze mode - where did you see this?
I ask because I typically get 10% loss overnight with what I thought was very good because the pixel often then calculates I have 2 days of remaining battery life with that stat.
JohnC said:
I never heard of this doze/deep doze mode - where did you see this?
I ask because I typically get 10% loss overnight with what I thought was very good because the pixel often then calculates I have 2 days of remaining battery life with that stat.
Click to expand...
Click to collapse
You can google it as there are tons of articles about it but here is some insight into it from the developer side: https://bignerdranch.com/blog/diving-into-doze-mode-for-developers/
OK, so it says in order to go into deep-doze, the phone:
1) Must not be charging
2) The screen is off
3) The phone is not moving
So, during the night, are all three of these conditions met?
Also, the device will come out of deep-doze if an incoming push notification is received - could one of your apps be receiving push notifications during the night?
Also, "Any process using a foreground service is exempt from Doze Mode effects, which is key for long-running applications"...do you possibly have any apps that have a foreground service?
Have you tried to switch off Bluetooth, it has a huge impact on battery even if not in use.
I've used apps before. Can't remember but gsam might be one...
It's possible to identify apps that are holding wake locks. That's the first place to check for battery drain.
lop1 said:
Have you tried to switch off Bluetooth, it has a huge impact on battery even if not in use.
Click to expand...
Click to collapse
I always keep WiFi, bluetooth, NFC and location off.
a1291762 said:
I've used apps before. Can't remember but gsam might be one...
It's possible to identify apps that are holding wake locks. That's the first place to check for battery drain.
Click to expand...
Click to collapse
all the apps I can find to track wake locks seem to need ROOT. I'd rather not do that as then I lose OTA updates.
After some extreme disabling of user app, system apps, services, etc. I finally got back to 3% battery drop overnight. I'm not sure which one was the culprit yet but i'll start enabling things as I need them and keep monitoring.
I'm having heavy battery drain. I already charged to 100 and less to 30 minutes i lost 10%.
It began since last update on my case.
After you see a big drain, DON'T plug in and...
Go into "Settings"
Then "Battery"
Then click the top right three dots
Then select "Battery Usage"
It should show you which apps are to blame for the drain.
badtlc said:
all the apps I can find to track wake locks seem to need ROOT.
Click to expand...
Click to collapse
Gsam needs permissions but these can be set with USB debugging, no root needed.
So one thing I have learned is that it appears every time I reboot, gsam thinks my wifi is on even though I have it off. If i turn it on and then back off. Gsam now says wifi is off.
So i got through the night at 3% battery drain but now I am realizing that my phone will not go into deep sleep during the day. Any suggestions how to fix that?
According to the details in the link posted earlier, it will never go into deep sleep if the phone is moving.
JohnC said:
According to the details in the link posted earlier, it will never go into deep sleep if the phone is moving.
Click to expand...
Click to collapse
I leave my phone sitting on a desk all day. There has to be some Android services that only operate during the day but i can't dtermine what those might be.
badtlc said:
So i got through the night at 3% battery drain but now I am realizing that my phone will not go into deep sleep during the day. Any suggestions how to fix that?
Click to expand...
Click to collapse
Was gsam able to identify which app was holding a wake lock?
Or maybe triggering frequent wakeups?
Both of those would prevent doze...
Battery Guru is good for chasing drains (with ADBs), add BBS + adbs and you can find anything using them together!
a1291762 said:
Was gsam able to identify which app was holding a wake lock?
Or maybe triggering frequent wakeups?
Both of those would prevent doze...
Click to expand...
Click to collapse
Google play services mostly. There was a large amount from "Adaptive connectiviy" but when I disabled that those went away.
Anyone else have this problem? My Always On Display (now renamed to "Always show time and info") will sometimes not turn off when the phone is face down. So the battery will drain a lot more when it won't turn off. It is intermittent though. Sometimes it will turn off, sometimes not. My old Pixel 3axl would always turn the AoD off when face down. I am on the latest release Android 13 update. It's done this now on the release Android 12 and the two Android 13 releases so far.
That's quite surprising as it's a simple proximity sensor function. As far as I've seen, mine has been turning off no problem. It does take 10 seconds to kick in the display shutting off. Not sure if you've taken that into account.
damian5000 said:
That's quite surprising as it's a simple proximity sensor function. As far as I've seen, mine has been turning off no problem. It does take 10 seconds to kick in the display shutting off. Not sure if you've taken that into account.
Click to expand...
Click to collapse
Yep, it sometimes turns off 10 seconds later, sometimes never...glad yours is working for you at least!
nsx2brz said:
Yep, it sometimes turns off 10 seconds later, sometimes never...glad yours is working for you at least!
Click to expand...
Click to collapse
Check to see if it's deep sleeping regardless. That is a main issue. The actual energy used to keep those few dim pixels on is comparably small. I also wonder if some app may be interfering. Anyways check deep sleep first with GSAM. If not deep sleeping, reboot and test again.
damian5000 said:
Check to see if it's deep sleeping regardless. That is a main issue. The actual energy used to keep those few dim pixels on is comparably small. I also wonder if some app may be interfering. Anyways check deep sleep first with GSAM. If not deep sleeping, reboot and test again.
Click to expand...
Click to collapse
It's definitely in deep sleep. According to AccuBattery Pro, it uses ~0.3%/hr when AoD is off and ~0.7%/hr when AoD is on (or not turning off). It does turn into a big difference over 24 hours though. Rebooting doesn't make any difference.
Got massive battery drain on android 13 in standby mode (wifi, mobile data off)
Standby consumes 30-35% over night (idle mode, no always on display active)