I have a BlockBeforeSleep Partial Wakelock, and I have searched for 2 days trying to figure out how to disable, it is killing battery life because it starts after reboot the first time i lock the screen and won't stop. I have attached screenshot of betterbatterystats. Does anyone know how to disable it or what causes it? Thanks.
Related
I have got a battery drain issue with my nexus s I9023 working on android 4.1.2 default factory image , no rom no kernet edited
While sleeping in 6 hours battery Drain down from 55% to 5%
The was the last day , I have this issue over two weeks ago , I have used BetterBatteryStats trying to find the process causing that ,
and I found the suspend backoff process cause that , I have changed the wifi with a static IP instead of a dynamic one and the problem still there
any suggestion ?
And thanks in advance for any help.
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Oogway13 said:
Have you installed any recent apps that might be causing this (any system panel app, chrome, etc)?
In Wireless Settings, press the Menu button and go to Advance.
You can try to check/uncheck (so that you can test) the following options:
- Wi-Fi optimization
- Keep Wi-Fi on during sleep --> Try setting to Always or Never
You can also check for any app that might be causing this. I've seen Chrome opening this process and staying there, causing the battery drain. But this might not be your case. You can try to reboot your phone (to clear all processes), and then open one app, close it, lock your phone and let it suspend and check if the suspend_wakelock occurs in betterbatterystats. Tedious....yes....but that way you can know which one is causing the battery drain.
Click to expand...
Click to collapse
Mine does it with wifi off and fresh reboot not opening any apps. I seem to get between 4 hours and 12 hours of lifetime from 100%. I should be upgrading this year but it would be nice if someone could figure this out because I know I am not the only one having an issue.
When I upgrade to a newer version of cm11 I often get a blue screen of death or a sudden reboot before the device has finished rebooting.
How can I find out what is causing this ?
I also have a huge battery drain (like 20-25% overnight), Im using greenify for system apps too, RILJ is causing a lot of drain and powermanager too (betterbatterystats, wakelockdetector), any suggestions ?
Maybe I should disable Fast Dormancy ?
robuser007 said:
When I upgrade to a newer version of cm11 I often get a blue screen of death or a sudden reboot before the device has finished rebooting.
How can I find out what is causing this ?
I also have a huge battery drain (like 20-25% overnight), Im using greenify for system apps too, RILJ is causing a lot of drain and powermanager too (betterbatterystats, wakelockdetector), any suggestions ?
Maybe I should disable Fast Dormancy ?
Click to expand...
Click to collapse
As to the first issue, is this only an issue during bootup? If so, that's a known issue, and after it goes through its reboot cycle a time or two, the phone should be fine. If it's happening other times, we'll need logs of the situation to see the issue.
As for this 'huge battery drain' ... We'll need some logs.
Magamo said:
As to the first issue, is this only an issue during bootup? If so, that's a known issue, and after it goes through its reboot cycle a time or two, the phone should be phone. If it's happening other times, we'll need logs of the situation to see the issue.
As for this 'huge battery drain' ... We'll need some logs.
Click to expand...
Click to collapse
Only during bootup after an upgrade/clean install. Good to know it's a known issue. The drain has stopped (using greenify for system apps).
In wakelock, the process that are the cause of the most wakelocks are : ActivityManager-Launch, LocationManagerService, SyncLoopWakeLock and RILJ, anyone knows how I can fix this?
I've tried to disable and enable location, still getting Android System or Android OS as causing the most battery drain. This started yesterday, before, I didn't have it.
So, using the pc version of wakelock detector, I was able to find that those three services were keeping my phone awake and draining my battery like crazy. What should I do? Anyone with the same problem?
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.