Related
I bought a Tab Pro 8.4 and decided to install Cyanogenmod 11 on it (currently on M12).
When I check my Battery usage under Settings after leaving it alone for several hours, "Android OS" is shown to be using over 60%. I tried using the Wakelock Detector app, and that didn't show any rogue apps. The "total wake time" in WD also closely matches the "keep awake" time for Android OS in Settings>Battery. There's even been a few times that my device didn't go into deep sleep at all.
Restarting the device didn't help as the problem would come back after an hour. I've tried several fixes including turning off auto-sync, using Greenify to freeze apps, and wiping my external SD card. None of them worked, but now I think I've found the source of the problem.
If I turn off wi-fi, "Android OS" no longer shows up at the top of my Battery page. Turn wi-fi back on and the problem comes back. Turning sync off doesn't change anything, so it seems like the issue is with the wi-fi itself and not with syncing apps. I even went into advanced Wi-Fi settings and changed it to 'turn off wi-fi during sleep' and still had the battery drain (though not as much - around 30% but still more than anything else). Changing the "Wi-fi Optimization" setting doesn't do anything either. I do notice sometimes when using my tablet that I don't have as many bars (on the wi-fi symbol in the status bar) as I do on my phone.
Does anyone have experience with this wi-fi issue? My GS3 doesn't do this. I assume that the problem is that my tablet device has a bad wi-fi connection and is always scanning or something, but I have no idea where to go from here.
EDIT: I might try downgrading to a previous milestone of CM11. I was reading in another thread how some other people were having wifi issues on M12 as well. My GS3 has been stuck on M10 because later updates broke stuff, so I'll try M10 on my tablet.
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.
I've got a brand new unlocked Moto Z play with the Offgrid battery mod. This morning I was disappointed to see my wifi, despite being disabled, had nearly drained my battery mod. I have the wifi configured to only maintain a connection while asleep and plugged in. The toggle for background location via wifi is absent from the advanced wifi menu.
Why is my wifi constantly on, despite it being toggled off?
I've attached a screen shot of the battery screen.
Edit: found the wifi scanning toggle in locations. I've just switched that off.
fourpointsix said:
I've got a brand new unlocked Moto Z play with the Offgrid battery mod. This morning I was disappointed to see my wifi, despite being disabled, had nearly drained my battery mod. I have the wifi configured to only maintain a connection while asleep and plugged in. The toggle for background location via wifi is absent from the advanced wifi menu.
Why is my wifi constantly on, despite it being toggled off?
I've attached a screen shot of the battery screen.
Edit: found the wifi scanning toggle in locations. I've just switched that off.
Click to expand...
Click to collapse
That's strange. Android Marshmallow comes with Doze functionality, and if the user is not using or moving the phone, it cuts down all background app activity that may eventually drain your phone, thus preserving your battery. You'll still receive notification about emails, and messages in social apps, as they're considered priority, if I'm not mistaken.
I'd say the source of your mod losing battery is your cellular reception. By the print you've posted, the Cellular Network Signal bar is most of the time red, orange or yellow. Poor cellular coverage eats up your battery.
I thank you for saving me the trouble of creating this thread, also did turning off the wifi scanning help?
keep wifi during sleep?
Wi-Fi has been switched off most of the day, wifi location scanning is disabled, and wifi connections while asleep are set to never. Still, it's almost ALWAYS on. Even when my ATT connection is strong it's still sucking down my battery. Wi-Fi remains my largest drain. Larger than cell standby, play services, and the screen.
Edit, looking at my images again, it appears my Z Play is treating the battery mod as a charger. Once the main battery drops to 80% and it switches to the mod battery, the wifi never turns off (despite my settings).
I also have similar problem with my moto z play. I haven't used wifi but still showing top ahead of others. Pls help to resolve this issue.
I had a Moto X Play before for a good while. this problem also showed up there (on Marshmallow as well), but I did find out my battery did not actually get drained, it was a reporting error in Android.
I am not sure if that is the case here with you, is the total battery life definitely lower or is it hard to tell?
Battery is still good but it could be better without the wifi drain. Mine is also more than the total energy the screen consumes and I have battery saver on with wifi location scanning off and wifi on only while plugged in. Not sure what would cause this.
Well, this is interesting. Flew to Boston today around 8:30, and as you can see, toggling airplane mode for the relatively short duration of my flight seems to have fixed my wifi drain. Although the phone did reboot in my pocket around 1530. At the time of this screenshot my internal battery is at 80%, and the battery mod is at 55% with only ~2.5 hours screen on time.
Out of curiosity, when you go into settings>location>3 dot menu>scanning, is wifi scanning turned on or off? Not sure about exact menu location as I don't have a Moto Z play, so working off a custom ROM on my Moto E2. Not sure if it would make a difference, but....
Wi-Fi location scanning is disabled.
Interesting, 24 hours after my flight (both legs visible in the chart) I'm showing no more wifi drain. This is with ~3.75 hours SOT. I am disappointed to see the Offgrid mod lost ~30% over night though. I'll still easily get 2 full days out of one charge, but I was hoping for 3-4. Hopefully Nougat's improved doze helps.
I am thinking my phone is also suffering from the same issue. Take look at my other post:
http://forum.xda-developers.com/showpost.php?p=69486349&postcount=77
Mine is even worse. Even when i activate the airplane mode, wifi does not turn off. It is open literally 24 hours. Seems like it drains the battery but I still have 9-10 Hours of SOT, depending on usage this can go up to 13-14 hours.
I fixed mine by following this:
http://androiding.how/how-to-fix-wifi-battery-drain-on-marshmallow/
emailrob said:
I fixed mine by following this:
http://androiding.how/how-to-fix-wifi-battery-drain-on-marshmallow/
Click to expand...
Click to collapse
Didn't work for me, but I stopped caring. I computed total power usage, wifi does not seem to have that portion
Guys, you must confirm if the WiFi actually drains that amount of power. 8/10 times it is a reporting error in Marshmallow, experienced it myself as well. Gsam battery monitor could tell you more.
This solution is for the MotoZ, a similar issue, maybe it could help us a little
http://forum.xda-developers.com/moto-z/help/extreme-wifi-battery-drain-solution-t3476579
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 ...
My battery drains around 1.5% per hour even after turning off AOD and wake screen for notifications setting. When those settings were on, it was draining 3-4% per hour. Has anyone else noticed the same? Any suggestions to improve the standby drain?
Are these numbers with WiFi and mobile data on? Airplane mode off?
Wifi on. Data off. Airplane mode off.
I'm using a different ROM but I've experienced similar numbers. It's obviously better with WiFi off but that's possibly not the point
Disable battery scenarios , worked for me
heybaybee said:
I'm using a different ROM but I've experienced similar numbers. It's obviously better with WiFi off but that's possibly not the point
Click to expand...
Click to collapse
No, other way around.
Being connected to a Wi-Fi is more efficient than Mobile Data Connectivity.
ApexPrime said:
My battery drains around 1.5% per hour even after turning off AOD and wake screen for notifications setting. When those settings were on, it was draining 3-4% per hour. Has anyone else noticed the same? Any suggestions to improve the standby drain?
Click to expand...
Click to collapse
You could check the Running Services in Developer Options, and see what's running in the background.
cyanGalaxy said:
You could check the Running Services in Developer Options, and see what's running in the background.
Click to expand...
Click to collapse
I can't find the option in developer options. I think it has been removed.
silvercrest said:
Disable battery scenarios , worked for me
Click to expand...
Click to collapse
Will check tonight
under the battery or 3rd party like accubattery should show you what's draining it , Im on the EU weekly and have no such problems
You could try a Custom Kernel like Nexus Kernel
NotZeetaa, the dev behind Nexus Kernel also made a Magisk Module "BatterySaverMod v1.2" that can be found in the Nexus Telegram Group, which limits performance a little bit but reduces Power-consumption for active drain.
You could check with Activity Launcher from Play Store, if the settings-page "Running Services" still exists but may just be unlinked from Settings-GUI.
For me 5g stopped work since 13.0.7
I'm also experience battery drain in 13.0.9 and occasionally network failures. Many times calls ended and receive the message "network not availabe". I've done a factory reset. Will have to do it again
Till this rom have everything work perfectly
I used better battery stats and it showed that wifi had a lot of wakelocks and was preventing the phone from entering deep sleep. I turned off wifi and standby drain went to around 0.5% per hour. I think voice over wifi is the culprit here. I will observe the drain tonight with VoWifi off.
Cabeção-Flu said:
For me 5g stopped work since 13.0.7
Click to expand...
Click to collapse
5g is pretty much useless anyway unless youre downloading very large files. It uses a lot of battery and makes the phone warm as well. I would suggest setting the preferred network type to 4g as it is more than enough for everyday use and saves battery as well.
You guys could use "Naptime" from Play Store. It supports ADB or Root.