I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.
Related
After updating to latest version of Google Play Services I have started to notice some sort of partial wakelocks. After 6hrs use I've got 44mins wakelock by google play services. Has anyone else noticed such behaviour? I have tried Purity Rom, Cm and Carbon just incase if there's difference, but I've encountered the same wakelock always. Here's what wakelock detector shows
http://forum.xda-developers.com/showthread.php?t=2785128
Lethargy said:
http://forum.xda-developers.com/showthread.php?t=2785128
Click to expand...
Click to collapse
Edit:thanks!
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
simms22 said:
wakelocks are how your phone works, they are supposed to be. an occasional incident might happen, and a process will get "stuck", which could keep a wakelock active. tell me, your wakelock, is it draining battery faster than usual? a reboot will usually fix these kinds of incidences. but you say you flashed roms since, and still the same.. so my next question is which apps are you using that is using this wakelock?
Click to expand...
Click to collapse
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
rockknee said:
Afaik I don't use any apps that trigger these wakelocks I've experienced. The only solution I've found so far is to disable services called "Configfetchservice" and "userpresenceservice". I've got these wakelocks no matter what ROM or even if I had disabled all Google stuff (sync, location, device manager and so on). Always after a day I have about an hour of Google play services wakelocks by userpresenceservice and configfetchservice. Never had this before. I'm sure it has something to do with latest google play services versions. I know wakelocks are very important part in smartphones but these kind of wakelocks are everything else but wanted.
Click to expand...
Click to collapse
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
simms22 said:
so you are saying that these wakelocks exist for you.. one very important question to an answer you havent mentioned at all, are these wakelocks causing battery drain?
Click to expand...
Click to collapse
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
rockknee said:
Not really shocking drain but noticable it is, which is nothing exceptional. It does these wakes during deepsleep every now and then. And of course when device is not used much and there is google play services on top 3 consuming elements at settings-> battery that's not the way it should be. Now I'm going to enable those services again and look for the logcat if I could find out to which app it is related to.
Click to expand...
Click to collapse
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
simms22 said:
if its draining some battery, but nothing in large amounts, i wouldnt really worry about it. as sometimes these wakelocks appear, then disappear a week or two later.
Click to expand...
Click to collapse
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
rockknee said:
I guess you're right. I'll just keep those services enabled for a week or so and see wheter it goes away or gets nasty and drains my battery in couple hours.
Click to expand...
Click to collapse
a while back, these kinds of things drove me crazy. then one day i just decided not to think about them anymore, and have been better off since. sure, every once in a while(rare, usually location oriented) a wakelock will appear that will drain lots of battery, but ill just use the disable services app to kill that wakelock for a week or two, then ill switch it back and all will be normal.
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.
I recently installed wakelock detector to help me save battery life with greenify. Looking at what it says it seems my phone never goes into deep sleep. This screenshot only shows the past hour and a half as before that I greenified things that looked like it might be causing the problem, but it looks the same now as it did before, 0.0 of deep sleep no matter how long I leave it, but none of the listed wakelocks seem to be that long, so I can't figure out why my phone wouldn't be deep sleeping.
Its a rooted Sony Xperia e4 running 4.4.4
Any thoughts?
You should also check Settings -> Battery -> tap on battery graph to open History details. There can be some dependencies between 'Awake' data and other data. Or you can post the screenshot of it here.
Hi, Sorry it took so long for me to respond, I was hoping to get a screenshot from a period where I hadn't touched my phone for longer but I kept forgetting at night time. I notice this time it actually says my screen has been on the whole time (though I never used it in this period at all, and when I picked it up the screen was off) So I have also included a screenshot of the screen wakelock page. Frustratingly, a lot of the things on the cpu wakelock page are already greenified and I manually hibernated them before turning the screen off, so not sure why they are still causing issues.
Either way, none of it adds up to the time awake
I posted a reply on this earlier but it seems to have disappeared. Anyway, I installed betterbatterystats and it showed that *backup* was keeping my phone from sleeping.
Google suggests it isn't altogether unconmon, and following some instructions I found I disabled back up, cleaeed dalvik cache and enabled back up again
So far its worked brilliantly, hopefully it stays that way.
Just an update on case anyone googkes and reads my solution above, it didn't work. Restarting my phone makes it go away for a little while and my phone gets plenty of deep sleep even in only a short space of time, but then *backup* comes back and its all over again. I can't keep restarting my phone every couple of hours. Maybe turning backuo off permanently will help, but then I have no backups, so hardly av good solution.
Hi,
*backup* is a wakelock from Google's Backup service. Wakelocks are so crazy because it regularly backups your data (such as Contacts, your Play Games' progresses, WiFi passwords, app data, etc) to Google's server. Disabling this equals to no longer having up-to-date backups.
You could actually disable the automatic backup, but make sure you backup your data periodically.
It's better for me to use BBS instead for checking for wakelocks.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Hi,
*backup* is a wakelock from Google's Backup service. Wakelocks are so crazy because it regularly backups your data (such as Contacts, your Play Games' progresses, WiFi passwords, app data, etc) to Google's server. Disabling this equals to no longer having up-to-date backups.
You could actually disable the automatic backup, but make sure you backup your data periodically.
It's better for me to use BBS instead for checking for wakelocks.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Yes I've found BBS better to, never would have found the problem otherwise. I turned off back up maybe 13 hours ago and so far so good. Not the ideal solution though eh. Hopefully google will fix it soon
I'm having the most aggressive wake lock I've ever witnesses on Android to date. This job.delay is driving me crazy because there seems to be very little data or answers to how to solve this issue. I can't even recall ever seeing it in BBS before Oreo or if it was there the amount of wakeup intents were negligible. I have a list of running background apps that I'm attaching and have went down the list and frozen each app , besides BBS of course, to see if the wakeups would stop to no avail. Just see the image I've attached and no that the wake up rate will not slow down and will reach astronomical numbers before my battery dies. Any help is appreciated.
Sorry, I'm no help but I have the same issue on my Note 8.
Whatever is causing the *job.delay* alarm is murdering my phone.
mookiexl said:
I'm having the most aggressive wake lock I've ever witnesses on Android to date. This job.delay is driving me crazy because there seems to be very little data or answers to how to solve this issue. I can't even recall ever seeing it in BBS before Oreo or if it was there the amount of wakeup intents were negligible. I have a list of running background apps that I'm attaching and have went down the list and frozen each app , besides BBS of course, to see if the wakeups would stop to no avail. Just see the image I've attached and no that the wake up rate will not slow down and will reach astronomical numbers before my battery dies. Any help is appreciated.
Click to expand...
Click to collapse
Use a wakelock detecting app, then identify the wakelock(s) that are bothering you, then use an app that can manage your wakelocks by enabling/disabling as needed to get the effect that you want.
Sent from my SM-S767VL using Tapatalk
Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"
Hi there, I've been using OOS 9.0.2 and I got some excessive wakelocks by *walarm*:com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION which happens about every 60 seconds. I'm not sure if this is normal or what the culprit could be as the location services are deactivated all the time, yet it occurs. Any idea what it could be? Can it be related to Android Wear?
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Macusercom said:
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Click to expand...
Click to collapse
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
spartan268 said:
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
Click to expand...
Click to collapse
I wish I could say I simply used a wakelock detector or something like that. I loaded my apps to a secondary device and disabled them one by one. I wasn't sure whether Greenify would prevent it but it did. So greenifying different apps and see if it changes was how I figured it out.
My battery consumption during standby went significantly down. Even though alarms are just the triggers and not the wakelocks, triggering the Network Location Provider every 60 seconds prevents the device from deep sleeping and was a main cause of the standby issues. I suggest to check it for yourself with BetterBatteryStats.
My ALARM_WAKEUP_ACTIVITY_DETECTION exceeded 1000 alarms by the end of the day. While I still get a few Android Wear wakelocks if my smartwatch is not connected. They make up at least 150 too. What I'm trying to say is that I don't say you should have no alarms anymore, but even 150 seem normal for Google Play Services. But over 500 or 1000 definitely isn't normal.
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
oksagi said:
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
Click to expand...
Click to collapse
That's my point. Even with light doze active apps still have a maintenance window and Sleep as Android seems to have permanently used sensors via Play Services. Once greenified it stops using it completely and I went from 1.2%/h idle drain to under 0.7%/h or less. I'm just trying to help people who have the same issue as I do. If no app seems to use any sensor, location etc. you don't need Greenify of course. But it can help with some apps.