Any ideas on managing the wakelocks on Android and specifically on the Infinity?
I've checked the option of switching off WiFi with screen-off, but in my battery usage stats I still see that over 10% of battery is consumed by Google Services with 672 wake locks & device waked 77 times (WiFi drain itself is 13,5%, so quite OK). This is what GSam Battery Monitor shows. Android stock battery management (in Settings) shows 51% drain by Google Services and 26% by WiFi (but I believe these stats are wrong most of the time or just measure a different thing, as they show tablet inactive with 2% bar and it has been inactive most of the time actually).
I have google auto-sync on and I need it, but I still think this is too high a number. I don't get 672 e-mails daily, so these shouldn't be PUSH notifications etc.
I'm not sure if I'm the only one seeing these high numbers there?
Have you tried CPUspy for finding out how much time in deep sleep you have?
Better Battery Stats is also a needed tool to find more about wakelocks
Sent from my GT-N7000 using xda app-developers app
Yes, I'm looking at it from time to time, but thanks for this. I had some issues when I started this thread, after wipe and re-flashing new firmware it seems OK in the stats: Deep Sleep 44%, 102MHZ 16%, 1500MHz 24% (running on balanced mode, interactive governor).
I'm still curious to get to know how to manage wakelocks under Android from (low) system level however.
My phone not going into deep sleep
GSAM reports held awake for 7 hours and CPU spy reporting not deep sleeping at all, but when looking at individual apps in GSAM, the apps it shows as holding the phone awake only reported as several minutes.
The app WLD (wakelock detector) shows wakelocks for only several minutes under CPU wakelock. Under kernel wakelock nothing is listed. Same with CPU Spy. CPU spy shows nothing at all for kernel wakelocks and only several minutes for partial wakelocks.
It's as if the phone doesn't log kernel wakelocks, or the kernel wakelocks are logged in a way that the app can't read.
What is the next step to determining the cause if these apps don't show the kernel wakelocks? Install some log app? If so, then how to interpret the log to see what the kernel wakelocks are caused by?
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
I've had this phone for a few days now and I notice some mean battery drain that happens from time to time. I dumped a Bug Report via developer options, and used Google's Battery Historian after leaving my phone unplugged and idle overnight after a full charge and reboot. The tool seems to show that the following kernel wakeup reason seems to be the problem and holding the phone awake for over 1.5 hours:
Code:
Ranking Name Duration/Hr Count/Hr Total Duration Total Count
0 Abort:Wakeup IRQ -1111803216 (null) pending 10m8s737ms 779.87 1h34m13.62s 7243
The only thing that looks remotely relevant is that on the tool WiFi signal strength became weaker when the above wakeup events started.
Has anyone else had similar issues with random battery drains like this and/or happen to know any workarounds?
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
I tried setting wifi to stay on when sleeping when plugged in, after a full idle overnight, I used my phone in the morning and the same issue came up. The ID above was different, but generally the same problem (IRQ with no description pending). Again, it looks to be wifi related based on the battery stats in Historian. I've rebooted, charged up and turned off wifi to see if the problem goes away.
ru_ready said:
Mine seems like it is always awake. Android OS has been keeping it awake for 8-9 while I'm at work.
Click to expand...
Click to collapse
You might want to try enabling developer options and getting a bugreport generated (which has battery stats), and then visualizing it in Google's Battery Historian to see if it is the same problem. Kind of convoluted, I know, but without root, I don't know of any better way to analyze kernel wakelocks (it isn't a partial wakelock issue on my device).
Last night I left my phone idle with wifi off and WLAN Scanning and Bluetooth Scanning off under Location Settings. The battery ran down only 2% over 9 hours and the Wakeup IRQ pending problem did not keep the phone awake!
I am going to try turning wifi back on today but keep the scanning off and see if that keeps this problem at bay. If not, I may use Tasker to force wifi off when the screen is not on and not plugged in.
The wakelocks seem to happen randomly no matter what my wifi settings are. Though I do think it is related to location settings trying to use wifi scanning.
I give up, there is no reason why a phone I just bought should be like this.
Maybe there are some apk wake up the system
@kumodog Maybe there are some apk wake up the system, you can reboot the system and kill all of application programs when you test it in night with wifi on.
After test, you can also use : "adb dumpsys alarm" in command line to find Top Alarms. it will tell you which alarm make system wakeup.
Hi,
my phone's battery is draining really fast as it is not going into deep sleep. it is being kept awake by GPIO_KP kernel wakelock. does any one know what it is and how to disable this?
Thanks