Database Info

Wakelocks

Any ideas on managing the wakelocks on Android and specifically on the Infinity?
I've checked the option of switching off WiFi with screen-off, but in my battery usage stats I still see that over 10% of battery is consumed by Google Services with 672 wake locks & device waked 77 times (WiFi drain itself is 13,5%, so quite OK). This is what GSam Battery Monitor shows. Android stock battery management (in Settings) shows 51% drain by Google Services and 26% by WiFi (but I believe these stats are wrong most of the time or just measure a different thing, as they show tablet inactive with 2% bar and it has been inactive most of the time actually).
I have google auto-sync on and I need it, but I still think this is too high a number. I don't get 672 e-mails daily, so these shouldn't be PUSH notifications etc.
I'm not sure if I'm the only one seeing these high numbers there?

Have you tried CPUspy for finding out how much time in deep sleep you have?
Better Battery Stats is also a needed tool to find more about wakelocks
Sent from my GT-N7000 using xda app-developers app

Yes, I'm looking at it from time to time, but thanks for this. I had some issues when I started this thread, after wipe and re-flashing new firmware it seems OK in the stats: Deep Sleep 44%, 102MHZ 16%, 1500MHz 24% (running on balanced mode, interactive governor).
I'm still curious to get to know how to manage wakelocks under Android from (low) system level however.

Anyone else having lots of wakelocks after flashing new kernels?

Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks

KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.

Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?

KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.

[Q] About Battery Life

Hi,
I have a question regarding battery life of the OPO. I'm still not sure whether I have a defective battery, or some apps drains my battery like crazy (or both?). I hope you can help me with this.
In the first 2 weeks since I got it, I use my OPO for mid to heavy activities (a lot of Whatsapp, Youtube, streaming music, etc). I always start the day with 100% battery and I thought it was normal to see the battery drops to at least 20% at the end of the day. To be honest, I didn't check the battery stats in Settings even once in this time frame, and due to my heavy usage, once again I thought this was normal.
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery. I did some research and found some advice including 1) denying GPservice abilities to "keep awake" and "wake up" via privacy guard (from this thread http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525), 2) turn off location, 3) turn off sync, but none of them seems the solution to my problem. Since then, I always check the battery usage and reset it, to see if GPservice still at the top. Sadly it still there. After I reset the stats, go to sleep directly and check it about 1 hour later, GPservice uses 40% - 60% of the battery usage, draining about 6% battery / hour.
With screen on a few minutes, it easily drops to 5th or 6th place with ~7% usage, with screen and main apps I use on the 1st and 2nd place. When I googled about this using Firefox, that's when I start worrying about something else, the battery itself. With wi-fi and low brightness (less than >20% if I convert it from the slide bar), browsing with Firefox decrease the battery 1% in 2-3 minutes, no or low usage drains 1% in about 5-6 minutes. In contrast, charging increase the battery 1% in 1 minute. Is that normal? IDK, usually bad battery increasing faster when charging and decrease significantly when in use.
Please help, especially about the excessive GPservice battery usage. And if it's possible, I prefer non-root solution for it. Thanks and sorry for my bad English.
OPO - stock rom (unrooted XNPH44S)
Google Play Services 6.7.76 (reverted back to 5.0.89 factory version but things pretty much the same)

cliffflip said:
Hi,
I have a question regarding battery life of the OPO. I'm still not sure whether I have a defective battery, or some apps drains my battery like crazy (or both?). I hope you can help me with this.
In the first 2 weeks since I got it, I use my OPO for mid to heavy activities (a lot of Whatsapp, Youtube, streaming music, etc). I always start the day with 100% battery and I thought it was normal to see the battery drops to at least 20% at the end of the day. To be honest, I didn't check the battery stats in Settings even once in this time frame, and due to my heavy usage, once again I thought this was normal.
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery. I did some research and found some advice including 1) denying GPservice abilities to "keep awake" and "wake up" via privacy guard (from this thread http://forum.xda-developers.com/oneplus-one/general/guide-google-play-services-battery-t2832525), 2) turn off location, 3) turn off sync, but none of them seems the solution to my problem. Since then, I always check the battery usage and reset it, to see if GPservice still at the top. Sadly it still there. After I reset the stats, go to sleep directly and check it about 1 hour later, GPservice uses 40% - 60% of the battery usage, draining about 6% battery / hour.
With screen on a few minutes, it easily drops to 5th or 6th place with ~7% usage, with screen and main apps I use on the 1st and 2nd place. When I googled about this using Firefox, that's when I start worrying about something else, the battery itself. With wi-fi and low brightness (less than >20% if I convert it from the slide bar), browsing with Firefox decrease the battery 1% in 2-3 minutes, no or low usage drains 1% in about 5-6 minutes. In contrast, charging increase the battery 1% in 1 minute. Is that normal? IDK, usually bad battery increasing faster when charging and decrease significantly when in use.
Please help, especially about the excessive GPservice battery usage. And if it's possible, I prefer non-root solution for it. Thanks and sorry for my bad English.
OPO - stock rom (unrooted XNPH44S)
Google Play Services 6.7.76 (reverted back to 5.0.89 factory version but things pretty much the same)
Click to expand...
Click to collapse
Definitely sounds like somethings not right, what apps do you have that access or could potentially access your location? If you're still not having any luck, as a last resort you could try a fresh install of CM11S and install your apps one by one to see if you can determine if any are responsible for sucking battery.
Give the below app a try:
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix&hl=en_GB
Install Gsam to see if you can gain any more insight into whats causing battery drain.
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm

cliffflip said:
Hi,
Until one night I decided to plug the charger earlier than usual, unplug it around 11pm (w/ 100% battery), then I fell asleep. I was shocked the next morning (8am) when I saw the battery has decreased to 65% with no activities whatsoever. I check the battery usage in Settings and then saw Google Play Services (GPservice) at the top of the list with 45% usage, with "keep awake" time almost identical to total time on battery.
Click to expand...
Click to collapse
did you try to use this App: http://forum.xda-developers.com/showthread.php?t=1179809
there you can see which app prevents your phone from going to sleep (partial Wakelocks)

gsmyth said:
Definitely sounds like somethings not right, what apps do you have that access or could potentially access your location? If you're still not having any luck, as a last resort you could try a fresh install of CM11S and install your apps one by one to see if you can determine if any are responsible for sucking battery.
Give the below app a try:
https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix&hl=en_GB
Install Gsam to see if you can gain any more insight into whats causing battery drain.
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm
Click to expand...
Click to collapse
Maps, Google Fit, Google Now, among other things.
CMIIW but I read somewhere that GServicefix does the same like privacy guard, denying some service to keep awake, wake up, etc.
So I installed Gsam and run it about 1 hour. Interestingly in there, Kernel (Android OS) is on the top the % list with 60% usage (mostly phone in idle/sleep). When I switch sorting to Kernel Wakelocks, it shows event0-798 & event2-798 as the top 2 wakelocks with around 7000 wakelocks. I'll update in few hours, thanks.
drcyber said:
did you try to use this App: http://forum.xda-developers.com/showthread.php?t=1179809
there you can see which app prevents your phone from going to sleep (partial Wakelocks)
Click to expand...
Click to collapse
From what I read on the Play Store description, Kitkat and above requires root?

cliffflip said:
Maps, Google Fit, Google Now, among other things.
So I installed Gsam and run it about 1 hour. Interestingly in there, Kernel (Android OS) is on the top the % list with 60% usage (mostly phone in idle/sleep). When I switch sorting to Kernel Wakelocks, it shows event0-798 & event2-798 as the top 2 wakelocks with around 7000 wakelocks. I'll update in few hours, thanks.
Click to expand...
Click to collapse
Please post screenshot of gsam
Try clear cache+dalvic cache in recovery

Hi, sorry for the late reply.
It seems reboot the phone a few times solves the problem. Battery usage now seems normal when idle, even with location & sync turned on.

[Q] No deep sleep but no wakelocks huh?

Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.

I'm experiencing exactly the same issue..

amd-dude said:
Hello all, I recently noticed that my OPO was not going into deep sleep. So I installed wakelock detector and to my surprise, nothing out of the ordinary was going on. I proceeded to wipe the dalvik and cache, still nothing, won't deep sleep. Last night I flashed franco kernel in the hopes that it would solve the problem, guess what, nothing, still won't deep sleep. The phone just drops to 300mhz and stays there for the minimum frequency.
I'm running liquid smooth 3.2 (4.4.4) with the recently flashed franco kernel.
Do you guys have any other suggestions on what to do?, I was just about to flash an entirely new rom and keep it barebones till the end of the week when cm 12s and oxygen os are released.
Click to expand...
Click to collapse
Maybe the PlayServices are the Problem somewhere here is a guid to prevent them to keep your phone awake

Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.

amd-dude said:
Actually play services did not come up in the battery stats to indicate it was indeed active. I ran through anything, there is nothing causing unnecessary wakelocks. So that's why I'm confused.
Click to expand...
Click to collapse
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon

timmaaa said:
Play Services doesn't always show up as Play Services in the battery stats page in your settings menu, it quite often will show up as Android OS.
Transmitted via Bacon
Click to expand...
Click to collapse
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.

amd-dude said:
Not even that, as I said there was nothing android related nor was there any app in wakelock detector that was showing signs of a wakelock. For good measure I did follow the many guides on stopping google services etc. and none of them worked. Phone still won't go into deep sleep. Strangely enough it was wasn't affecting my battery life that much, was still getting about 6hrs on screen time with 14% battery left.
Click to expand...
Click to collapse
Sounds to me like your battery stats might just be screwy.
Transmitted via Bacon

So now I'm wondering, as well. What would an example of good/excellent deep sleep look like? % drop over time?
My battery stats show cell standby at 1%, phone idle at 1%, and over over eight hours go from 100% to about 86%. Would that drain be considered deep sleep, or good deep sleep?

I had a similar issue and able troubleshoot successfully.
Device:
- POCO F1
- MIUI 12.0.3.0, Android 10
- Magisk 21
What tried but didn't help
- There is no wake-locks active
- Tried Battery Saver and Ultra Battery Saver
- Tried Airplane mode
- Tried rebooting
- There is no significant battery drain (only 1.6% per hour)
- Tried disabling Proximity sensor
- Tried wiping dalvik-cache
I have followed the guide by Intel at https://software.intel.com/content/...-no-sleep-issues-in-android-applications.html
As I mentioned earlier, there is no active wakelock, that is why the troubleshooting was much difficult.
I have digged into `/sys/kernel/debug/wakeup_sources` and sorted processes based on the column `prevent_suspend_time`. The process `qtidataservice` was on the top. Not sure what it is, but it's probably from Qualcomm and running under the `radio` user.
The `strace` was showing nothing. I have simply killed that process. It's eventually re-created with a new PID. Interestingly the device began to go Deep-sleep while in idle.

OP7Pro battery drain 10%/h screen off 🤯 HELP

So I've had my OnePlus 7 Pro for over a year now and battery has been getting steadily worse. I've been running the latest stock beta channel (O2_BETA_5 atm) with Magisk and my battery drain has been consistently awful. I'd turn off WiFi in the evening and still my battery would be half gone by the morning. In the beginning the phone would easily last the day and now it barely gets me halfway through. I've attached a SS from AccuBattery showing a 10%/h drain with screen off. I've ordered a new battery but don't see the point of changing it before fixing this glaring software issue. I've done minor tweaks with root (including https://github.com/peterroth/OnePlusBatterySaver) so I don't know - maybe I ****ed something up. I would prefer not to do a factory reset but at this point I don't know what else to try. Please help!

Was also using beta 5, moved too the latest stable. Battery on last beta is bad.
Or maybe install BBS to monitor what's draining your battery

Lot of trash apps.
At least block the Gallery app with Karma Firewall; it doesn't need internet access unless you're using cloud services.
Any cloud services impact battery life...
Google Backup Transport, Framework and Google play Services are known serial offenders.
Google Firebase is another one that runs in the background mining your data like a little b$tch.
Trash apps sometimes wake up Google system apps or Android Services with their bs.