I have a Droid 4 running the Unofficial CM11 ROM. I've been using this ROM for a few months now, mainly without issue. Only recently, for some reason, I am getting these uncontrollable wakelocks that cannot be plugged.
http://imgur.com/a/9wSYW
Using BBS, I see that I am having issues with GCM_CONN and GCM_CONN_ALARM. They will not allow my phone to sleep. I am using Amplify and Wakelock Terminator, both set to block these guys, but it's not enough to let the phone go into Deep Sleep.
I also heard about Deep Sleep Battery Saver, and I've downloaded that in an attempt to force the phone into Deep Sleep, but that hasn't worked at all as you can see.
Has anyone had any experience quelling wakelocks of this magnitude before? I cannot seem to figure out what is preventing the phone from going into a normal sleep rhythm.
Related
Anyone else get stupid fast drain while its sleeping? I have wifi sleep policy set to turn off wifi when screen is off, and using the task manager nothing looks to be running that i havent launched myself. But usually i'd have the battery last DAYS and DAYS if i wasn't using it that much, but the last few charge cycles it's been nearly dead at the end of the day. Is there an app I can get to monitor stuff while its sleeping to see if something is keeping it from deep sleep? I can't remember what i've installed recently that could keep it in wake-lock or whatever. Thanks guys.
There's a build in feature in the settings menu to tell you what uses battery
Check that the wifi is actually sleeping when the screen is off. Tap the power button to wake up the tablet then look at the notification bar in the right hand corner to see if the wifi is turning on and connecting. If its not doing that then I dont think the wifi is disconnecting and turning off when the screen is turned off.
For battery issues, two "must have" tools are "better battery stats" and "cpu spy"
gary's right. download better battery stats here:
https://market.android.com/details?id=com.asksven.betterbatterystats
and since the developer of that app loves XDA, there's a free version for us!
OP: http://forum.xda-developers.com/showthread.php?t=1179809
DL: http://forum.xda-developers.com/attachment.php?attachmentid=833619&d=1325149176
Look into the partial wakelock and find the cuplrit!
Battery Drain
Try loading the free util Auto Airplane Mode which has helped fix the SOD issue and the related battery drain during the SOD.
Sorry to push the old post up again.
Recently im suffering from the weird battery drain, i didnt play/use my phone much on sunday , the idle battery drain is huge. like 8 hrs from 100%-40%.
I've installed both betterbatterystats and cpu spy already.
From battstats , it shows that kworker/0:1-3 and kworker/u:12-13 etc using up most of the batt , secondly is the doubletwist music player.
From cpu spy, most of the time is with 200mhz even i didnt use the phone at all, rarely goes to deep sleep mode.
for the process kworker it didnt show whats the process/app is about , anyone else know wt to do now ?
Same problem here :-(
Fully loaded at 7 o'clock and now I'm 34% - this really sucks!
faygo6464 said:
Sorry to push the old post up again.
Recently im suffering from the weird battery drain, i didnt play/use my phone much on sunday , the idle battery drain is huge. like 8 hrs from 100%-40%.
I've installed both betterbatterystats and cpu spy already.
From battstats , it shows that kworker/0:1-3 and kworker/u:12-13 etc using up most of the batt , secondly is the doubletwist music player.
From cpu spy, most of the time is with 200mhz even i didnt use the phone at all, rarely goes to deep sleep mode.
for the process kworker it didnt show whats the process/app is about , anyone else know wt to do now ?
Click to expand...
Click to collapse
All you can do is to check the apps you recently installed or updated. They might lock you from sleep. No easy way to control this
For me it was the "samsung-keyboard" - I froze it and now everything seems normal.
Okay, I've been trying to diagnose a somewhat annoying issue. I've been using a fairly simple set of conditions in the Llama utility to automatically disable Wifi when the screen turns off in CM7 to prevent a wakelock condition and reduce battery drain.
So I activate wifi, I reset the log in CPU Spy, and I lock the phone disabling the screen. When I reactivate the phone and check CPU Spy, wifi was definately off but the phone was never in Deep Sleep, so something was holding the wakelock I guess. I repeat the experiment with no changes and Llama still running, but this time I manually disable wifi before locking the screen. This time the phone immediately goes into Deep Sleep according to CPU Spy-- it works perfectly.
So what is the difference between Llama autodisabling and manually disabling wifi that leaves a wakelock active? I've repeated this experiment like ten times last night, and it isn't making much sense to me.
Thanks,
Gnat
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
mikel81 said:
I would love an answer to this as well. I can add that with juice defender ultimate the same thing happens. It will disable the wifi but the wakelock stays active. I have tried several settings and reboots and tests and the only thing that would get my phone to deep sleep was disabling JD.
Click to expand...
Click to collapse
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
On the general battery issues on Triumph, one of the more helpful discussions I've seen is this one here-- http://androidforums.com/triumph-all-things-root/456795-cm7-triumph-battery-life-improvement.html. In it a quote from Tickerguy blesses the JuiceDefender approach to throttling data use for battery savings, but I don't think he had done any analysis regarding wakelocks. BTW, I reverted to stock today, and I am finding the exact same problems as CM7-- wifi imposes a wakelock, and Llama can't shut down wifi automatically without the wakelock persisting. I have to manually toggle wifi off before screen off before the wakelock is gone.
Regards,
Gnat
gnatd said:
I can't tell whether this is the exact same, because you make it sound like JD has the wakelock. In my case, Llama is running in both tests, the only difference is whether Llama turns off Wifi or I manually toggle it-- manual toggling puts it into deep sleep even with Llama running.
Click to expand...
Click to collapse
Sorry; the wakelock is WLAN. It is almost always active if JD is toggling wifi. I hadn't tried disabling wifi manually but leaving JD active yet. I just tested that and got deep sleep immediately. So it must have something to do with how it disables wifi isn't releasing the wakelock.
You know, after switching back to stock from CM7 I'm really not sure I'm not happier. With CM7 I was getting worse battery performance, which led me to start obsessing about wakelocks and deep sleep. Now that I am back on stock, I do the same analysis and see that I have the same problems with wakelocks and deep sleep-- but the battery performance is better so it's not that big a deal. I'm sure that there are things I could do to make CM7 have better battery performance-- but I wasn't enjoying the process and wasn't finding answers, so why bother?
It's like power management programs. I ran Green Power for a long time, and had some glitchy problems with being unable to get wifi to turn on even though it wasn't supposed to be managed while the screen was on. Then I disabled it, and you know what... my battery life was good enough to get me through the day. Froyo is good enough to get me through the day.
The wakelock was put in there on purpose to prevent the phone from hanging when WiFi was on and the phone went to sleep. I use my power widget to turn off WiFi before I turned off the screen unless I'm actually using it.
You could try and build it to see if removing the wakelock is still necessary. If you need help on that side, just post and I'll help. It's not hard, really.
Hello all,
I'm running Tweaked 2.1 with the 5/24 PBJ kernel. Everything works great, except that I've found my phone won't deep sleep after I've charged it for the night. The only fix I've found is to reboot.
So, to be really clear.
I turn it on - deep sleep happens.
Use it all day, deep sleep happens.
Charge it overnight,
Disconnect and no more deep sleeping happens, it just stays at 100MHz and the battery drains that much faster.
So, my clever cell-phone-friends, any ideas?
Go this thread: http://forum.xda-developers.com/showthread.php?t=1179809
Download Better Battery Stats from the bottom of the second post. Install it, and then wait for the problem to happen again. When you see that it's happened, run BBS and select the options to view partial wakelocks since unplugged. That will show you what is holding wakelocks (preventing the phone from sleeping).
stats
Okay, so, here are the wakelocks after last night's charging.
Partial:
* ImapFolderPusher.....
k-9
12s
* RILJ
Dailer
7s
Kernel:
* "RXNET_MSL_LISTENER_WAKELOCK"
48 m 2 s
* "vbus_present"
2 m 21 s
And it records 51 minutes since unplugged.
I've looked for anything about RXNET... before, and found nothing. Is it maybe something realted to wifi? RXNET sounds like some sort of network receiving thing. I don't suppose anyone else has this problem?
I've also read about turning on the screen while unplugging and other hacky fixes, but nothing has worked for me. Those were for other phones, so I didn't really expect it to work.
In any event -- an further ideas? Thanks for helping.
You definitely don't have an issue with partial wakelocks, but kernel wakelocks seem to be a big problem. 48m of wakelock out of 51m is bad for battery life. I did a quick search and couldn't find anything specifically on that wakelock either. I'll keep looking and see what I can find.
Imnuts is the person to ask about this one.
Sent from my SCH-I510 using xda premium
Fixed!
So, apparently, freezing the Rx Networks PGPS downloader app causes that wakelock. Unfreezing it has let my phone sleep again. Odd that it waited until after charging to be a problem.
ok, im fed up with the shocking battery its terrible i cannot last from morning to bed before charging, things ive done
running cataclys and franco kernel, downclocked to 1.2-1.5ghz, runs same to me i only do daily tasks of texting ect, 2.2 seems to only
take affect on higher needing apps
and also using smart 3g to have on 2g when screens off, what do you guys do?
first things first, make sure your phone is deep sleeping and a app isnt causing the phone not to deep sleep.
use betterbatterystats (search for it) and look under partial wakelock after using the phone for a good hour or two.
if a partial wakelock exists, then google search about that wakelock and debug your phone.
also turn off google location reporting & history.
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.