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?
Related
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.
Hello everyone. I've flashed the factory image of lollipop and wiped everything in the process. Last night I went to bed around 2 am, and as you can see my phone has been awake a lot after that. I installed gsam, which atm seems the only compatible battery app, and this is what I discovered: 25 min of kernel wakelocks in the time of wakelocks tab, but when i open the kernel wakelocks tab, it shows basically nothing even remotely that lenghty....
Do you have a similar situation?
Thanks,
TD
After a few battery cycles the situation hasn't changed, lengthy kernel wakelocks, but none in the kernel wakelock tab....
Here's my results, are they ok? It says awake for only 2% of the time but I don't understand why the number are so high in the list.
These are kernel wakelocks and wakelock triggers
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
Recently I have been facing a wierd battery drain issue... A kernel wakelock as "sensor_ind" keeps waking My Device up from Deep Sleep when the Device is locked... The time of device awake and the time that wakelock was on and the time Google Play Services used "Significant Motion Detector" is almost the same (in the screenshot all 3 is on for about 4 hrs)... Is it related to Doze function linked with Play Services or any app using it??? I tried different ROMs with different Kernel but this issue persists in all (for the last 1 week)...
I tried a lot of tweaks to fix it but none helped... I tried adding Play Services to battery optimisation, restricted running in background, restricted keep awake... Tried wiping Play Services data and reinstalling it updates...
I attached screenshots using BetterBatteryStats app before sleeping and after I woke up...
I have the same issue