What are people using to detect wakelocks on Kit Kat for the Moto X? Better Battery Stats doesn't seem to work, and I hear Wakelock Detector is having the same problem. I just received the phone a couple days ago, and it's not enjoying the great battery life that it's has been lauded for. According to the stock battery chart, the device seems to remain continuously awake for long stretches of time even with the screen off, wifi off, and no music playing. I would love to find out what's causing this.
Betterbatterystats has been updated now for kitkat, but almost everything needs root..
Sent from my XT1060 using Tapatalk
Kit Kat removed support for the wakelock tracking commands that BBS used before. With root it can do what it needs to do and there is an exposed modules that re adds the wakelock command so all battery tracking apps will work.
PC version of Wakelock Detector
Tested on Windows 7
download link : http://bit.ly/1h2Hzmw
Instructions
# install usb drivers of your phone (nexus phones need to install http://developer.android.com/sdk/win-usb.html)
# turn on "debugging" option on your phone (developer section)
# connect the phone via usb , run the app , enjoy wakelock stats
After Android 5.1.1 update on my Xperia ZR, The Facebook App and other Apps are keeping Mobile Radio Active for very very long time. This is causing severe battery drain.. Is there any fix for this issue?
How can you know which apps are keeping Mobile Radio active?
I used Wakelock detector and found that RILJ is waking mine up by having between four- and six-thousand instances in a period of a few hours.
Still trying to get to the bottom of it though...
According to BBS, https://m.imgur.com/gbpwAIy,ARaAKEw,YhEGL7w,8rCXPAf,ekGOuPM
Android has a very high alarm count, and it's also partially preventing my phone from entering deep sleep. I somehow forgot to provide a screenshot of bbs's main screen, but IIRC it was awake 27% of the time and deep sleeping the rest. I'd absolutly love to achieve the 0.0%/hr. drain. Plus, I don't use gapps. I also have few xposed modules for battery saving, but I'd really love to fix these. I tried doing a ddg (and google) search on the alarms from Android, especially PKT_CNT_SAMPLE_INTERVAL_ELAPSED, but no luck. Other than that, I have absolutly 0 partial wakelocks and I, obviously, have a few kernel wakelocks. Without any kernel wakelocks, the device wouldn't even work, but even then, the kernel wakelocks barley even exist. I'm currently running minimal os 5.1.1 with the v13 monster kernel. Thank you in advance.
I have a similar problem in stock rom (http://forum.xda-developers.com/moto-g-2014/help/android-os-wakelock-hell-t3390342)
A question:
Do you use "Ambient display" (screen wakes up when you get a notification)?
rafaelrgi said:
I have a similar problem in stock rom (http://forum.xda-developers.com/moto-g-2014/help/android-os-wakelock-hell-t3390342)
A question:
Do you use "Ambient display" (screen wakes up when you get a notification)?
Click to expand...
Click to collapse
No I don't. I've had it in several different roms.
sonic64 said:
According to BBS, https://m.imgur.com/gbpwAIy,ARaAKEw,YhEGL7w,8rCXPAf,ekGOuPM
Android has a very high alarm count, and it's also partially preventing my phone from entering deep sleep. I somehow forgot to provide a screenshot of bbs's main screen, but IIRC it was awake 27% of the time and deep sleeping the rest. I'd absolutly love to achieve the 0.0%/hr. drain. Plus, I don't use gapps. I also have few xposed modules for battery saving, but I'd really love to fix these. I tried doing a ddg (and google) search on the alarms from Android, especially PKT_CNT_SAMPLE_INTERVAL_ELAPSED, but no luck. Other than that, I have absolutly 0 partial wakelocks and I, obviously, have a few kernel wakelocks. Without any kernel wakelocks, the device wouldn't even work, but even then, the kernel wakelocks barley even exist. I'm currently running minimal os 5.1.1 with the v13 monster kernel. Thank you in advance.
Click to expand...
Click to collapse
Revert back to stock rom and update to marshmallow, from this you will be able to get deep sleep mode easily and the rom will be much stable. then for any customization use xposed framework. also use greenify app in boost mode you will get maximum out of your android. cheers.
Phone : P9 Lite
OS : EMUI 4.1
Android : Marshmallow 6.0
Rooted.
Installed better battery stats.
Problem: Numerous wake lines shown in Battery Graph. (Not completely solid, but is numerous) . Preventing DOZE to ever take effect. Unknown if wlan_sdio_lock is the culprit.
Dear friend, trust me, wakelocks don't inhibit normal working of doze, in fact doze inhibits them from working. As much as I know doze will start working if you keep your device stationary and with screen turned off for 30mins or more. The wakelock you named is probably an essential system component related to WiFi, which may b you r always using at home. I'll recommend not to touch any wakelocks, don't use amplify etc. Use force doze app available at play store. You'll understand what to do with it after installing.
Hey everybody!
I was really really happy to use it, but after flashing the last weekly version (31 January) I'm experiencing heavy battery drain because of SystemUI wakelocks.
WLD shows the DozeService multiple wakelocks, so the "Android" process is the first in list...
Is it just only mine problem? If not, how can I fix it?