Related
Last night, around 2am, I unplugged my phone from the charger before i went to sleep (it had WiFi on) and now when I woke up and checked it at 1:30pm the next day, I had 35% battery left! WHAT!? checked battery stats and Android OS ate up 51%! with phone idle at 12%
anyone have any idea what's going on? I have everything except WiFi turned off, GPS, Location Services, Auto-Sync, Auto-Backup, everything. I also underclocked everything via cpu master and trickster mod. I greenified facebook, viber, skype and any other app that could potentially wake my phone from deep sleep.
I checked trickster mod, deep sleep was at around 5hrs with 162mhz at around 7hrs. don't have any screenies of those since I rebooted my device right after I plugged in the charger (helps with displaying correct percentage)
I've attached a screenshot. I've never seen that kind of downar plunge in my battery stats. ever. this is the first time it's ever happened.
I'll install wakelock detector and give it a few hours. I know my phone drains around 1%/hr while idle, maybe even less.
EDIT: I already started when I took the second screenshot. I forgot to take a screenshot of the rest of my battery stats. so don't mind the time and the difference in battery percentage.
that's kernel problem. I meet that problem before, while I'm using AK-kernel with Vanir ROM. Kernel make screen always on to increase respond for S2W and Double Tap to Wake, but also cause this problem. In Android 4.4.2 also have this issues ( Nexus 4 and Nexus 5 is an example, you can search Google for this ).
You can install Better Battery Stats to check wakelock issues, but you can't do nothing, unless you have to changed to another kernel
BIBUBO BCJ said:
that's kernel problem. I meet that problem before, while I'm using AK-kernel with Vanir ROM. Kernel make screen always on to increase respond for S2W and Double Tap to Wake, but also cause this problem. In Android 4.4.2 also have this issues ( Nexus 4 and Nexus 5 is an example, you can search Google for this ).
You can install Better Battery Stats to check wakelock issues, but you can't do nothing, unless you have to changed to another kernel
Click to expand...
Click to collapse
don't have S2W and knock on enabled on my kernel. I also tried those and their battery drain is nothing compared to this!
I've charged my device and now it's showing Google Search as the culprit. now looking for a solution.
vangeodee said:
don't have S2W and knock on enabled on my kernel. I also tried those and their battery drain is nothing compared to this!
I've charged my device and now it's showing Google Search as the culprit. now looking for a solution.
Click to expand...
Click to collapse
what's your kernel ?
BIBUBO BCJ said:
what's your kernel ?
Click to expand...
Click to collapse
Solid Kernel + Stock 4.1.2 with a few xposed modules. I've solved the problem. Had to completely turn off Google Now and blocked wakelocks from Google Play Services.
I'll give this 3 hours and see if it goes back to the 1%-1hr idle drain. Battery stats seems to have improved, I'll post my post-fix battery stats in around 5 hours just to check if the problem comes back.
aaaaaaaaaaand it's back. This time it's not Android OS but Google Play Services that's eating the battery up. I now get 2%/hr with this new problem.
I checked trickster mod and my phone is not entering deep sleep. checked wakelock detector and it showed GCMSEND as keeping the phone awake. (1h 52m out of 2h)
Anyone know a fix for this? I've currently filtered it in Wakelock Terminator and I'll see how it goes from there.
UPDATE:
22 mins in and phone is in Deep Sleep 84% of the time. filtered GCMSEND and added 2 lines to build.prop that supposedly improves deep sleep.
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
Source: http://forum.xda-developers.com/showpost.php?p=46301722&postcount=2
Will leave it overnight to see if it stays this way.
yeah, noway to fix it because it was an issues of kernel.
If GCMSEND always running, you can downlod app called Disable Services, and Open it to disable some service in Google Play Store and another system app. Try it and will see if it's working.
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Eidoss said:
My battery will completely drain after <10 hours while the screen is off!
However I was able to find out thatquickgooglesearchbar is always the top app.
Those screenshots are a bit old but it's still the same thing, I did manage to root it today, and I was testing Greenify which did nothing even with the Xposed modules, service disabler apps just did not show that specific service for some reason. I was able to remove the widget with Xposed GEL settings but it was still running even though the widget wasn't there.
So can someone please help me out here, maybe the search bar isn't the problem but I just want some battery life.
h ttp://imgur.com/a/gdXKW
(I still can't post links sorry If this is against your forum rules but this is urgent)
Click to expand...
Click to collapse
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Darke5tShad0w said:
search and install betterbatterystats (read the whole first post) and it will tell you if its wakelocks etc.
Service disabler apps will need a setting to show system apps (or something similar) ticked or switched to etc.
greenify system apps in greenify also needs to be selected. You may also need to cut wake up paths to get it to stay greenified.
You could alternatively delete the apk of hibernate it (byfar the easiest option of all this).
Click to expand...
Click to collapse
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Eidoss said:
I don't need betterbatterystats, I have battery Battery Historian, check the screenshots, It's clearly the search bar, on my other phone It isn't shown as a top app.
Also I went in the system folder /apps and there was no googlesearchbar, or in any other system apk remover tool, perhaps it was removed by another app, but it's still for some reason running.
Click to expand...
Click to collapse
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
sfhub said:
Your 3rd image shows googlequicksearchbox had 370ms (milliseconds) of wakelocks over a 9hr period. I really doubt that is your issue.
If it is your top app, then it is probably because of Google Now launcher listening for OK Google spoken keyword.
I seriously doubt that is your battery drain problem as almost 90% of people probably have OK Google turned on and are using Google Now launcher and only a very few have serious battery drain.
BTW wakelocks aren't the issue usually. In the past it has been "partial wakelocks" which means an app locked the device from sleeping, but never released the lock, so the device never goes to full sleep. If you see some app with partial wakelocks or if you see some app with hours of regular wakelocks then that might be an issue. Minutes or microseconds of wakelocks are inconsequential.
I suggest you flash factory image and install your battery tester only. Turn off wifi, bluetooth, nfc, cell radio. Test the drain overnight. That is a baseline for the minimum drain your device can have. Then enable what wireless stuff you normally have turned on. See what that drain is. Then start installing apps and see what that drain is.
If you have reasonable/expected battery drain with stock and everything turned off, then it is just a process of elimination to see what is causing your battery drain.
If you can't get reasonable/expected battery drain with stock and everything turned off, then you probably have a bad battery.
For the record, my overnight battery drain with everything turned off is 0-1% With wifi turned on about 1-2%. With wifi+cell about 2-3%.
IMO the biggest drains for standby are wifi and/or cell signal related. Either bad signals or apps sending data in background or apps that are polling all the time.
Click to expand...
Click to collapse
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Eidoss said:
Factory reset didn't do anything a few days ago, the results were exactly the same that was when my phone wasn't rooted, so I guess I should return the phone, and get a new one?
Click to expand...
Click to collapse
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
sfhub said:
What is your battery drain per hour with nothing installed and all wireless turned off and everything stock?
I'd only return it if that is significantly more than 0-.2% or 1% every 5 hours.
Otherwise it is something you have installed or something to do with the signal and how it interacts with your phone.
Once you start installing stuff or turning on wireless (wifi/bt/cell) then it is no longer purely about the battery and there are more factors that need to be isolated independently.
You really need to establish a baseline to see what the minimum battery drain is. Then you can determine if the battery is the problem or something else.
If you just install everything and turn everything on, there are too many moving parts.
Click to expand...
Click to collapse
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Eidoss said:
Okay, I now have android N, and my battery life seems to be better, I will leave mobile data off. I will see tomorrow if my battery life has changed.
Do you think I should use Adaptive brightness for more battery life?
Click to expand...
Click to collapse
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
sfhub said:
Which battery life was the one you think you have a problem with, standby or in use? IMO for in use battery time this phone is about average. Your title of "wakelock" made it seem like you were concerned about standby battery time as it doesn't matter if there is a wakelock if the device is already turned on and in active use.
When turned on, the screen is probably the number one thing eating power, so adaptive brightness could help, but if you are in a bright area, it might be worse than if you fixed the brightness below max.
Even if you have adaptive brightness turned on, the slider scale still is useful as you give the adaptive brigthness mechanism some idea what level of brightness you feel comfortable when the mechanism detects dark, med, bright situations.
One of the worse things for eating power is for the cell radio to be turned on but have no signal, like inside office building or just a bad signal area in general. The reason is the cell radio is power efficient once it establishes signal, but when it is searching for (or loses) signal it uses a lot of power.
If you are doing a lot of disk activity like taking video or hdr pictures, it would probably help to have your userdata unencrypted as this device does software (kernel) encryption and doesn't use the fast/more power efficient co-processor.
Click to expand...
Click to collapse
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Eidoss said:
Standby is the problem, on screen times are good enough.
Anyway, I don't even know what to do at this point. Android N didn't help enough (cell data is off), I guess I can flash Android 6.0 again and then try to fix it using apps...
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
What is the power drain over a couple of hours with *no apps installed* completely stock, and wifi/cell turned off? What is the change when wifi is turned on?
Eidoss said:
What do you suggest I should do, I'm out of ideas at this point.
Click to expand...
Click to collapse
Have you set "WiFi on during sleep" to "Never"? in the Advanced WiFi settings?
In the original release, there was a bug where WiFi would stay on even if you had set it to "Never" draining battery in standby.
Somewhere between MDA89E and MHC19Q they fixed it and WiFi will go to deep sleep after being in standby for a while, but they introduced another (or exposed existing) bug where WiFi will not resume after coming out of sleep, unless you cycle WiFi off/on. So you're standby battery should be better with this setting, but it'll be a little more annoying when turning on your device.
Hi,
(I'm on Ressurrection Remix 5.8.5 / Nougat 7.1.2 final, rooted; installed O+3 OB24 firmware)
Recently (around mid-Feb) I started having problems with battery life on my device. I haven't changed anything (significant, not that I remember) but it was annoying me so on the road to figuring out which app/part of the system could cause the battery drain I ended up with pure Resurrection Remix rom without any Gapps (or any other apps for that matter) and... battery was still draining like crazy (which only annoyed me more). And with helpers like WakeLockDetector it say that my device was in deep sleep less then 50% of the time (and it was mostly laying on the table!)
The other day I noticed that if I disable WiFi all of the sudden device got decent sleep time (about 10-25% of awake time, which was consistent with my use case). I check the settings of wifi and had "keep wifi on during sleep" set to 'always' (however from performance and battery drain perspective having wifi on and even having idle TCP connection open shouldn't drain battery that much). I switched it to 'keep on only while charging' (no effect) and then to 'never' (also no effect).
Then I turned to old friend - 'llama' aplication and configured it to disable wifi the moment I turn off the screen and then when I turn on the screen activate wifi. With that setup I went from having 20-25% by the end of the day (unplug the phone around 6-7am, check around 6-7pm, i.e. after 12h) to still having 70% left with the same usage/timeframe. Generally this could be it, but! This is still kinda semi-automatic and I would loose notification if I don't explicitly wake device.
I was under the impression that this should be handled by doze - i.e. if the phone is lying on the table it would force device into deep sleep and then periodically wake it up to allow apps to refresh it states. In my case it looks like something is preventing doze from working correctly and placing phone into deeps sleep. I wan't as low-level as my (current) knowledge let me and I'm kinda stuck and don't know what to check next or how to fix it.
After using llama to disable wifi while screen is of the wakelock by 'PowerManagerService.WakeLocks' went down significantly as well as awake time.
Battery details: https://www.dropbox.com/s/bvf47nzx7ob5wc8/battery-details.png?dl=0 (wifi always on)
Wifi config: https://www.dropbox.com/s/2v65dugidp57rrd/wifi-config.png?dl=0 (nunca/never)
I would be very thankful for all suggestions.
.wojtek said:
Hi,
(I'm on Ressurrection Remix 5.8.5 / Nougat 7.1.2 final, rooted; installed O+3 OB24 firmware)
Recently (around mid-Feb) I started having problems with battery life on my device. I haven't changed anything (significant, not that I remember) but it was annoying me so on the road to figuring out which app/part of the system could cause the battery drain I ended up with pure Resurrection Remix rom without any Gapps (or any other apps for that matter) and... battery was still draining like crazy (which only annoyed me more). And with helpers like WakeLockDetector it say that my device was in deep sleep less then 50% of the time (and it was mostly laying on the table!)
The other day I noticed that if I disable WiFi all of the sudden device got decent sleep time (about 10-25% of awake time, which was consistent with my use case). I check the settings of wifi and had "keep wifi on during sleep" set to 'always' (however from performance and battery drain perspective having wifi on and even having idle TCP connection open shouldn't drain battery that much). I switched it to 'keep on only while charging' (no effect) and then to 'never' (also no effect).
Then I turned to old friend - 'llama' aplication and configured it to disable wifi the moment I turn off the screen and then when I turn on the screen activate wifi. With that setup I went from having 20-25% by the end of the day (unplug the phone around 6-7am, check around 6-7pm, i.e. after 12h) to still having 70% left with the same usage/timeframe. Generally this could be it, but! This is still kinda semi-automatic and I would loose notification if I don't explicitly wake device.
I was under the impression that this should be handled by doze - i.e. if the phone is lying on the table it would force device into deep sleep and then periodically wake it up to allow apps to refresh it states. In my case it looks like something is preventing doze from working correctly and placing phone into deeps sleep. I wan't as low-level as my (current) knowledge let me and I'm kinda stuck and don't know what to check next or how to fix it.
After using llama to disable wifi while screen is of the wakelock by 'PowerManagerService.WakeLocks' went down significantly as well as awake time.
Battery details: https://www.dropbox.com/s/bvf47nzx7ob5wc8/battery-details.png?dl=0 (wifi always on)
Wifi config: https://www.dropbox.com/s/2v65dugidp57rrd/wifi-config.png?dl=0 (nunca/never)
I would be very thankful for all suggestions.
Click to expand...
Click to collapse
Is wifi/BT scanning on in Location? If so switch it off.
Also check whether the firmware you use is correct or requires updation.
tnsmani said:
Is wifi/BT scanning on in Location? If so switch it off.
Also check whether the firmware you use is correct or requires updation.
Click to expand...
Click to collapse
I have BT off (haven't used it in my life…)
As for wifi scanning - you mean notification about available networks? yes, its' off.
What do you mean about firmware? Could that affect radios? in that case - which firmware should I install with RR 5.8.5? I'm not sure if "the latest" is alwasy the best idea (problems with compatibility)
.wojtek said:
I have BT off (haven't used it in my life…)
As for wifi scanning - you mean notification about available networks? yes, its' off.
What do you mean about firmware? Could that affect radios? in that case - which firmware should I install with RR 5.8.5? I'm not sure if "the latest" is alwasy the best idea (problems with compatibility)
Click to expand...
Click to collapse
Go to Settings>Location then click the three dot menu at top right, then click Scanning and disable wifi and BT scanning.
If that doesn't work, check on the ROM thread which firmware is recommended for your version of the ROM and flash it.
That one is also off.
As for firmware - I have (it seems) latest recommended one.
Hi, I recently got my S9 but however lately I've been getting idle drain. With mobile data off, I lose about 2% every 2 hours and with mobile data on, I lose 4% every 2 hours. I have GSam installed and used ADB to give it permission for battery stats. Below are screenshots
http://imgur.com/gallery/5c4Q4j4
It seems to be from IMS service. I read that it can be from either WiFi calling or volte. I do not want to turn off either. Had anyone else experienced this? I still have good battery but this idle drain isn't normal. I haven't left my phone overnight so I guess I might try that tonight and see how much it drains
Hi there,
I am re-opening this old thread since I am facing the exact same behaviour with my new S10+. Due to IMS wakelocks, my battery drains 30-40% overnight (while I'm sleeping for 7 hours). If I put my phone in flight mode, it loses 1% overnight. Did you manage to find a solution afterall? I really hate having to put my phone in flight mode every night. Thanks in advance :highfive:
panmitz said:
Hi there,
I am re-opening this old thread since I am facing the exact same behaviour with my new S10+. Due to IMS wakelocks, my battery drains 30-40% overnight (while I'm sleeping for 7 hours). If I put my phone in flight mode, it loses 1% overnight. Did you manage to find a solution afterall? I really hate having to put my phone in flight mode every night. Thanks in advance :highfive:
Click to expand...
Click to collapse
Did you ever find a solution to this? Experiencing same problem now ...
Hi ... did any of the posters above find a solution to this issue ?
I am stuck at exactly the same problem: The phone (S9, stock-rom) drains approx 20% over night, doing nothing. Reason (according to GSam Battery Monitor) is the high power consumption of Apps > Android-System > 48 mins (264 count) wakelocks caused by ImsService.
If you look at the picture of batter usage in Gsam you clearly see, the phone stays active all night and barely sleeps/dozes :-(
What I already tried, without any effects:
- clearing cache of all "IMS*" Services in App Manager
- wiping cache partition
- disabling AOD (Always On Display) and VoLTE Telephony
- removing and re-adding google account
I am a little clueless and would like to avoid a factory reset as especially all those nasty "push-tan applications" will most likely need a re-authorization :-(
I'd heavily appreciate any hint.
After a long journey it seems that I found a solution: At least on Android 10 there seems to be a bug in google location services. If you disabled location history, the API requests are still made but get stuck each time (every 60 sec.) and keep the phone awake instead of returning to sleep.
The "bitter" solution was to turn on Google Location history again ... and suddenly the drain ends, as the detection and transmission of the location is ways faster, than letting the die in a timeout ...
Hey guys,
I always wondered, why my phone wouldnt Deep Doze (according to Gsam). Be aware: I am not talking of the Deep Sleep (the CPU state, that is happening).
I always lost between 1,5 and 2% per hour overnight with the phone just sitting on the table, connected to the home wifi.
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Yes, I am aware that there is this Mobile Network Standby Drain Bug. But since I disabled "Always use mobile date" in developer settings and was using WIFI during mentioned times, I dont know how that appiles to me.
Anyone has ideas?
Thanks!
Put it into airplane mode overnight and see if you get the drain. At least you'll know if it's a app or radio issue.
xflowy said:
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Click to expand...
Click to collapse
Blade22222 said:
Put it into airplane mode overnight and see if you get the drain. At least you'll know if it's a app or radio issue.
Click to expand...
Click to collapse
no offense dude, but did u read my post? see above.
What the heck is deep doze?
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
xflowy said:
Hey guys,
I always wondered, why my phone wouldnt Deep Doze (according to Gsam). Be aware: I am not talking of the Deep Sleep (the CPU state, that is happening).
I always lost between 1,5 and 2% per hour overnight with the phone just sitting on the table, connected to the home wifi.
I disabled the Sim-Card (physical one, no e-sim) before going to bed tonight and my phone deep dozed now.
Yes, I am aware that there is this Mobile Network Standby Drain Bug. But since I disabled "Always use mobile date" in developer settings and was using WIFI during mentioned times, I dont know how that appiles to me.
Anyone has ideas?
Thanks!
Click to expand...
Click to collapse
May be related to a ProxyController bug that people have reported. One workaround I've heard of (cannot confirm it works) is to turn off Airplane mode, reboot, then turn on Airplane mode,
ProxyController wakelock draining battery - Google Pixel Community
Thanks everyone!
Napa7m said:
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
Click to expand...
Click to collapse
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
Lughnasadh said:
May be related to a ProxyController bug that people have reported. One workaround I've heard of (cannot confirm it works) is to turn off Airplane mode, reboot, then turn on Airplane mode,
ProxyController wakelock draining battery - Google Pixel Community
Click to expand...
Click to collapse
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
xflowy said:
Thanks everyone!
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
Click to expand...
Click to collapse
Just by doing what I said...
I was about to send the phone back until I discoveredt this fix. Battery life is great now.
I don't use any of those apps.
xflowy said:
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
Click to expand...
Click to collapse
Sounds like a bunch of hooey to me. Light doze, deep doze, medium awake doze.. come on look at your cpu stats and deep sleep when screen is off. If it's not deep sleeping overnight at least 90% then something is keeping the phone awake and you need to find it. Get BBS and look at your alarms and partial wakelocks. You have a runaway program that is constantly waking up your device. Mine was Mi Fit and I tweaked it so it's not awake all night long. Went from 1.8% / hour to 0.4% - 0.7% consistently.
@Napa7m Insta and WhatsApp shouldn't be doing it. Not sure about Telegram but I do recall some issues a year ago and I deleted it from the phone.
bobby janow said:
Sounds like a bunch of hooey to me. Light doze, deep doze, medium awake doze.. come on look at your cpu stats and deep sleep when screen is off. If it's not deep sleeping overnight at least 90% then something is keeping the phone awake and you need to find it. Get BBS and look at your alarms and partial wakelocks. You have a runaway program that is constantly waking up your device. Mine was Mi Fit and I tweaked it so it's not awake all night long. Went from 1.8% / hour to 0.4% - 0.7% consistently.
@Napa7m Insta and WhatsApp shouldn't be doing it. Not sure about Telegram but I do recall some issues a year ago and I deleted it from the phone.
Click to expand...
Click to collapse
you should do some reading
xflowy said:
Thanks everyone!
I did all that. No deep doze tho. And even when I had deep doze when disabling the sim-card entirely, i had more than 1% drain per hour in standby. How tf do u get .2-.5%!? Do u have telegram/whatsapp/insta?
I see no proxy handler wakelock in gsam so i dont assume its that. Already did that airplane mode reboot and it didnt work.
Click to expand...
Click to collapse
Either something is using up power when device should be deep sleeping, or it's just defective.
So he's right, monitor app usage and go from there. The built-in battery stats work well enough. It's how I discovered that 'mobile network standby' was consuming 20-30% over night with nothing going on.
DOn't forget to expand the 'system usage' at the very bottom of 'battery usage'.
xflowy said:
you should do some reading
Click to expand...
Click to collapse
I did and it still sounds like you're looking in the wrong place for your awake status. It's a background process that can't really be tweaked or modified on it's own. But alarms and wakelocks can that's why I said look there first. If your phone is not deep sleeping err.. deep dozing then something is keeping it awake. Find it and you're home free. What kind of deep sleep are you getting overnight?
xflowy said:
As stated above, it is a doze state that is being entered after the light doze. Check Gsam battery for your stats regarding deep doze.
Click to expand...
Click to collapse
Deep sleep = deep doze? My wifi is on and have 4G enabled. This as taken about a month ago but nothing has changed.
Napa7m said:
I had the same problem, dropping 2-3% per hour over night. I turned 5G off, turned off 'mobile data always active' in developer settings and turned off adaptive connectivity.
Now im only losing .2-.5% per hour overnight.
Click to expand...
Click to collapse
I have about the same as you, mobile network standby around 20-25% overnight. I don't turn off 5G but I am connected to wireless with a very good signal. I have mobile data always active enabled as well as adaptive connectivity enabled. What I did to was turn off every adaptive setting in battery settings. Perhaps it's the wifi I'm connected to but I'm getting average 0.5-0.6% drain overnight. Deep sleep around 92 %. As I said, I did see some partial wakelocks and alarms when I was almost 2% / hour and either deleted the apps or figured out how to stop/slow them when not in use.
@bobby janow ok my man. first of all. a read for you, what deep/light doze is: https://www.andreasschrade.com/android-battery-optimisations
and no, its not the same as deep sleep. deep sleep is the cpu frequency.
my phone is now (out of a sudden) going into deep doze overnight, so that seems fine. also wakelocks couldnt have prevented my phone from going into deep doze, cause then, it would have also not gone into deep doze when I had my cd-card disabled (since there should be still wakelocks, when my phone is connected to wifi and all, right
since mobile standby is concerningly huge in the battery stats i assume its the usual culprit, but disabling adaptive connectivity, 5g and enabling that dev option does not help.
tho i am willing to find some wakelocks (since they seem to affect the device also a bit in terms of my standby drain). according to gsam everything is fine in that department, cant really find unusual wakelocks. does bbs show more there? im not very keen in running an adb to make it work...what does that command line do exactly?
thanks!!
@xflowy BBS needs 4 adb commands and it takes about 30 seconds to complete with a copy and paste from his thread. It has two wakelocks stats, kernel and partial. The kernel ones are meaningless to me but the partial tell a lot, you'll see. Also just as important is the alarms stat. It gives you that amount of time an app is firing i.e. wakeups. Check it out see if it helps you. Thanks for the read, but it's beer day today and that looks like it will take all my concentration. Lol.
@xflowy On first read it looks like battery optimization regulates doze mode, right? I mean that's really the only way?
It also happened to me after many tests I have managed to solve it, deactivating the sim card and esim, and restart, then activate the sims and drain solved, it already goes into deep sleep.
I have the exact same issue. I thought I'm the only one. But I'm unable to resolve with this by disabling sim n reboot method. Can anyone suggest if it's hardware fault ?