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
Related
I'm currently using Nik's Codename Jellybean ROM and am getting excellent battery life for the last week or so. I have used the kernel that has come along with it.
However, yesterday when I went out - I turned on GPS (turned on for a short period and then off) for the first time since flashing the ROM and since then, the GPSLocationProvider has been providing partial wakelocks every second whenever the phone is not on airplane mode and preventing deep sleep, killing my battery in the process.
I have attached a screenshot from BetterBatteryStats.
I have looked about in the forum and the only solution from a couple of old threads seem to be rebooting the phone so that the phone can go back into deep sleep mode, which is really not the best solution is it?
If there is any solution or a compatible kernel that prevents this, I'm happy to hear from you.
It may also due to your Google location services which is active. Take the dump again with all location, GPS turned off!!
Edit: Location wake lock dump shows its active for long time. Seems like its due to location service not GPS, which you turned on only for a short duration.
Cool - that may help isolate the problem. I will toggle Maps, Location Services, GPS and see what is causing the issue.
Many thanks
Happens to me also on other ROM and device. But only if i start some app, which is using GPS, but its not enabled yet.
In case I enable GPS, than start the app, use it, close app, disable GPS, then GpsLocationProvider is not running in background.
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
Hi,
I do not have the exact same problem, but my phone drains battery more than often. With wifi, mobile data etc turned off, i have ~10% of drain overnight (7~8 hours). But my phone does enter in deep sleep and battery stats shows me nothing weird (most of battery is being taken from phone iddle /standby cell), it is driving me nuts! My wife have the same phone as mine, same firmware, same system apps, the only diference is mine have the new bootloader, but her phone drains almost half than mine. I'm now reinstalling the firmware with the exact same steps i did in her phone and if someone want i post some screenshots later.
Did you tried installing some custom roms out here who have not all the system apps the original package have?
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
I am using 4.3 Alliance Rom with boeffla kernel. I had the same problem with battery drain during airplane mode. While I was at work with airplane mode on, I lost nearly 20% in one hour. Because of it I switched to 4.4.2 aosp rom "aosb 1.3.0. Probam" (meanwhile there is 1.3.2 published) but there I had music stuttering and camera issues, but perfect battery life. Because of the problems I decided to go back to 4.3 and gave Alliance Rom another chance. And now the battery life is wonderful like on 4.4.2.
Maybe try the same way, first to update on an aosp rom with excellent battery life and then go back to android 4.3. Maybe this will solve your problem, too.
Lilmanio said:
Hello,
I've searched the forums about battery drain problems regarding android phones in airplane mode but each subjects seemed different to mine.
I own a Samsung Galaxy S3 LTE i9305 under Android 4.3.
The phone is rooted, Greenify installed, hoping saving battery life but...
I've tried to do a full data reset + reinstallation of Android 4.3 official, with no success.
I've done the folowing experience 3 times with the following similar behaviour as last time :
- Phone fully charged before to go to bed, Airplane mode activated.
7 hours later :
- Battery is at 80%
- 0 minute in deep sleep, all the time in awake state.
Several behaviours noted by Wakelock detector and Gsam Battery Monitor :
- Device Idle and androidOS consumed 80% of the 20% used
- Misc processes seem to have used a lot of battery among them :
- AlarmManager
- PowerManagerService.WakeLocks
- KeyEvents
I'm including screenshots to illustrate all this.
If anyone has been thru this problem I'd be glad to know how to solve it.
Thank you !
Emmanuel
Click to expand...
Click to collapse
Hi,
By any chance, do you have XPOSED framework enabled and do you use for example Wanam Xposed module ? If an option like "Turn on screen when unplugged" is unchecked (ie if you don't want your phone to wake up after you unplug it from USB), you may encounter battery drain. It seems that sometimes the phone doesn't enter in deep sleep if the USB cable is unplugged from a PC in this case. I have this kind of battery drain and since I've checked "Turn on screen when unplugged" option, no more battery drain after a reboot.
I'm not sure but you must give it a try as it worked for me. No problem so far.... I hope it will help.
Hi and thank you all,
I'm taking good note of your advices.
I did install Xposed and Wanam. I didn't pay attention to this option and since then completly reinstalled 4.3 official ROM. Battery drain vanished.
I now have the phone going to deep sleep normaly.
I've been reinstalling all my apps slowly one after the other, and didn't try yet to reinstall Wanam Xposed, as I know it modifies the system relatively deeply.
But the envy is here and I think I'll install it again. Ok, let's go, I'll do it tonight. I'll pay attention to "Turn on screen when unplugged" option and will ensure it is checked !
It's worth trying, though all these battery draining problems seem mysterious...
I'll post a reply in a few days with the results...
By the way, I installed Agni kernel wich uses Boeffla engine too. After activating "Extreme battery save" mode, the battery life has doubled or so. I'm happy about this.
Thank you again, and let's see how xposed wanam behaves...
GREAT.
Sent from my GT-I9305 using XDA Free mobile app
I have a Moto G 2014 (XT1064) running Android 6.0 that will not go into deep sleep. I could see that the CPU was never going into the deep sleep state even when the phone was not being used and no user apps were actively running in the background. This is causing abysmal battery life as expected. The phone was updated to Android 6.0 via regular OTA updates. I haven't flashed any third party ROMs onto it at all since I bought it.
The first thing I did to investigate was to unlock the bootloader (it was still locked since purchase prior to this) so that I could obtain root access to see what was going on. This also had the additional affect of wiping the phone to stock Andoird 6.0, which I had hoped would maybe solve the problem but it did not.
My first thought was that it was a user app that was holding a wakelock keeping the phone awake. I looked at the user and kernel wakelock counts via BetterBatteryStats and WakeLockDetector, but from what I can tell it is not any user app that is holding a wakelock at all. Instead it must be some kernel level app keeping the CPU awake, but I can't determine what it is. There isn't any single entry in the wakelock list that sticks out as the culprit.
I have done some other investigative tests such as turning WiFi off while the phone sits unused overnight. This did not have any effect as the phone still remained awake the whole time. I also repeated this test with the phone in airplane mode (WiFi + cellular radios off) and again it had no affect. From this I could only conclude that it was not the wireless radios that were keeping the phone awake. The wakelock counts also didn't show any evidence that WiFi, cellular or GPS were holding wakelocks.
Here are two screenshots I took of the BetterBatteryStats and WakeLockDetector apps showing the highest count kernel wakelocks over a roughly 17 hour period:
(I'd link them in properly but I am prevented from posting outside links on this forum until I have 10 cumulative posts...)
i.imgur.com/nPAY3S6.png
i.imgur.com/5VfgFv1.png
You can see that the phone has been awake 96% of the time during this period, and that the highest count kernel wakelocks are from "event8-1877", "event9-1877", "qpnp_soc_wake" and "qpnp-vadc-e4a28400". I could not find any information as to what these entries mean or what they're related to. Whatever they are, they appear to have abnormally large wakelock counts which leads me to believe that they are related to this problem. The other thing that puzzles me is that the total time for the top four entries in that list only sum to about 2 hours, yet the phone has been awake for almost 17 hours within the same period.
If anyone has any idea about this I'd appreciate the help. I may be completely wrong about the root cause here but I'm running out of ways to debug this.
Updating this thread to say that I have also tried re-flashing stock Android 6.0 using the firmware files linked from this thread (in my case I used XT1064_TITAN_RETCA_6.0_MPB24.65-34_cid14_CFC.xml since I am in Canada). I still experienced the same behaviour where the phone would rarely enter deep sleep. It seemed to be marginally better after re-flashing, going into deep sleep about 10% of the time over a 12 hour period or so, where as before it was only going into deep sleep about 4% of the time during the same period. This still doesn't solve the problem though.
Now I am thinking about downgrading to stock Android 5.0.2 and see if that fixes the problem since I don't know how else to diagnose this.
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.
My Xiaomi Mi MIX runs Global Stable ROM 8.2.5.0 (MAHMIDL). Noticing a substantial loss of battery life overnight, I decided to take a closer look using BetterBatteryStats. Turned out that Kernel Wakelock 6aoooo.ssusb was keeping the phone from deep sleep.
The cause was pointed out in this thread https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062: the wakelock initiates when connecting the phone to a PC via USB in MTP mode (probably keeping the phone awake for file transfers) but the service persists after disconnection.
A reboot terminates the wakelock. Luckily I found another workaround by enabling USB debugging in Developer options (although it's hardly a real solution).
Furthermore BBS registers a lot of wakeup alarms from com.google.android.gms and android. Has anyone else noticed this behaviour?
Djezpur said:
My Xiaomi Mi MIX runs Global Stable ROM 8.2.5.0 (MAHMIDL). Noticing a substantial loss of battery life overnight, I decided to take a closer look using BetterBatteryStats. Turned out that Kernel Wakelock 6aoooo.ssusb was keeping the phone from deep sleep.
The cause was pointed out in this thread https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062: the wakelock initiates when connecting the phone to a PC via USB in MTP mode (probably keeping the phone awake for file transfers) but the service persists after disconnection.
A reboot terminates the wakelock. Luckily I found another workaround by enabling USB debugging in Developer options (although it's hardly a real solution).
Furthermore BBS registers a lot of wakeup alarms from com.google.android.gms and android. Has anyone else noticed this behaviour?
Click to expand...
Click to collapse
My mi mix drained 30% over 10 hours (even the battery saver was enabled), I dont know what causing it and I do have USB debugging enabled
Sent from my Xiaomi MIX using XDA Labs