Hi
When i'm connected to wear, I get insane wakelocks. I got 25k+ wakelocks in 10 minutes from the Android Wear app.
Suddenly it stopped, but I still had deep sleep problems (gets in deep sleep, but not much) so I checked wakelocks again and now Bluedroid_Timer 340 wakelocks in 1min.
Anyone know a fix for the second issue?
Thanks in advance
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.
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.
This topic has been up a couple of times before, perhaps most interestingly discussed in this thread.
It appears the problem still exists (asusdec_wake kernel wake), and I'm experiencing extreme battery drain during sleep with the dock attached. Currently running Cromi-X 5.4, and I have tried hunds 3.4.4, and _that 8 and 9 kernels.
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up. It only occurs when the tablet is docked, it can occur at both high charge levels and when the dock is empty (mine always drains to 0%). It does not seem to matter whether wifi is on or off. I monitor the battery with better battery stats.
It's a real pity, since I have to turn the tablet off whenever I want to keep the dock attached.
Is anyone else experiencing this drain? Any suggestions for fixes?
Also: obligatory first post thanks-for-making-my-tablet-great to @sbdags, @_that and all the other contributors to Cromi :good:
rkha said:
It appears to behave as following: The tablet enters deep sleep with low battery drain (0.3% per hr with wifi off), and after a while (have seen it happen after a range of 1 - 5 hours) it starts draining quickly as asusdec_wake wakes the tablet up.
Click to expand...
Click to collapse
How do you know that it first enters deep sleep and that it's woken up later?
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
_that said:
How do you know that it first enters deep sleep and that it's woken up later?
Click to expand...
Click to collapse
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
_that said:
asusdec_wake is a wake lock which only keeps the tablet awake, so the question is what causes the wake up and keeps the wake lock?
Click to expand...
Click to collapse
Good point. Any tips on how this can be diagnosed?
rkha said:
It might be a strong assumption, but it's based on the battery drain patterns I've seen. I've tried to monitor this a bit the last few days. Usually the battery drain is as expected during sleep for a while (whenever I check during this period, the asusdec_wake has not been active and the entire period the tablet has been in deep sleep), before it increases and stays high. I attach some screen shots where this can be seen. The change in slope in the battery graph is after about 7 hours. In those screen shots the deep sleep time reported by bbs was 6h24m. I'm not sure the reason for suspend_backoff, but I assume something is forcing the tablet to stay out of deep sleep. If I disconnected the tablet, there are no issues with suspend_backoff (and naturally not with asusdec_wake either).
Good point. Any tips on how this can be diagnosed?
Click to expand...
Click to collapse
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
sbdags said:
Try turning location services off completely for me in settings.
Does that help? Give it a reboot as well.
Click to expand...
Click to collapse
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
rkha said:
Yes it did, thank you! 21 hours, only 3% down and asusdec_wake inactive. I will report back if things change.
Will add always turning this off when tablet screen is off to Tasker. Interesting that it caused this huge battery drain, given that gps and wifi was off anyways. Wakeups from com.google.android.gms decreased from many to nearly none when turning off location access, perhaps it is sufficient to turn of google apps location access in settings.
Thanks again!
Click to expand...
Click to collapse
It's Google now constantly polling for your location as far as I can tell.
I have a Mi2S and I'm running the latest stock ROM 4.4.23.
Ever since the 4.4.11 update I've had poor idle battery life.
Before that when I look at my battery usage, as long as I have good signal and the screen is off, the battery level graph is flat.
Now, almost always when my phone is idle, no matter what there is some heavy drain, it was approximately 25% over 12 hours.
I've tried all the MI2S updates since then and they are all having this issue. I have not installed any new apps or changed anything on my current ones.
Attached are some wakelock detector screenshots.
Sometimes 小米服務 has many wake alerts, but sometimes it does not. Weather app is disabled, and autosync is disabled too. Occasionally 小米服務 does not have many wake alerts but that doesn't seem to reduce idle power draw, and I think it had this many wakes before as well.
Also the 3h wakelock app is the music player; the idle drain happened when the music player was off.
Thanks for reading.
Bump...
So I spent a night in airplane mode, and voila! 3% drain over about 12 hours!
I'm still trying to figure out exactly what it is, but whenever I get the chance to I'm going to spend another night in airplane mode with wifi on.
Bump...
There is a nice little utility app called power tutor, which shows you exactly which app drains your device. Maybe the problem isn't rom related...
You can find it on the play store.
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.