I've been getting several wakelocks that follow me on every rom I have tried be it KK or LP
It's the "android.net.connectivityservice.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED"
and "com.android.providers.calendar.intent.clanedarproviders2"
both reaching hundrends of wakeup alarms. Making my device lose a lot of charge when idling.
Any information on either, searching didn't weild many results.
Choopeh said:
I've been getting several wakelocks that follow me on every rom I have tried be it KK or LP
It's the "android.net.connectivityservice.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED"
and "com.android.providers.calendar.intent.clanedarproviders2"
both reaching hundrends of wakeup alarms. Making my device lose a lot of charge when idling.
Any information on either, searching didn't weild many results.
Click to expand...
Click to collapse
Use either app ops or privacy guard and turn off "keep awake" and "wakeup" for calender and calender storage
Related
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
turbofandude said:
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
Click to expand...
Click to collapse
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Aerowinder said:
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Click to expand...
Click to collapse
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
turbofandude said:
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
Click to expand...
Click to collapse
All of the wakelocks that start with Nlp are due to location. Switching the location mode to Device only will stop them. Anything that relies on GPS still works fine. This should be the default setting.
I did a factory restore of the phone, latest Gapps, Carbon rom (07/07 nightly + 07/06 firmware), latest ElementalX Kernel now (so far, better temp/performance + equal or better battery). I know it's only an hour's worth of use, but a problem is pretty apparent.
Location reporting/history is off, Gnow is enabled, keyword detection is off. WiFi is on, and location services are in high accuracy mode. Why is a wakelock created by never released and how do I avoid that?
Is there any reliable setting I can use to avoid a random software issue eating up my battery? This inconsistency is driving me insane.
Before I begin I just want to say that I have been using Android for a while and understand wakelocks etc. I have already made sure none of my apps are causing wake locks by uninstalling them but it has made no difference.
Here are my GSam screenshots: http://imgur.com/a/1Cp9z#0
As you can see, Android System and Android OS are the culprits that are draining my battery, but the phone isn't "awake" when they are draining it, so I am not quite sure what is happening. There is no wake-lock but there is a lot of CPU usage for some reason,
Please ignore the average times shown by GSam at the bottom, I get nowhere near 5hrs screen time, I reset the histories yesterday so its not yet calculated average properly yet.
I have tried - Stock COS11S, the latest COS 12.1 and also CyanogenMod 12.1 nightlies and the recent snapshot and they all exhibit this issue even with no apps installed. Is there a ROM out there that has no issues with this stuff?
Thanks!
Same problem. No idea the solution. No matter what battery app I use to try and tell me what is going on, it's always just listed as "android system" or "system" that is draining battery. I didn't have this on sultan's build so I guess it's back to that.
I dont want to give yo spoilers...
you can try every rom here, every kernel, every mod...
it really up to your personal use... you do this 3 simple things and like me will reach 5, 6 hours SOT.
disable lte and go for EDGE
restrict privacy guards things on apps: keep awake, auto start, wake up... on every app you install
use your social network on browsers... installed apps use background...
I'm currently experiencing a serious Keep Awake bug when on a Lollipop ROM and I have no idea how to stop it.
The phone is constantly awake, even when using App Ops, Amplify, BBS, Greenify etc.
Currently on ASOParadox ROM, but have used COS12.1, Exodus (with AK Kernel) and Sultan's ROM.
Tested both TK and Open GApps.
Testes Sultan's without a GApps package and the problem still occurred.
Anyone know what it could be?
(Not letting me post screenahots as a new user, just battery stats showing a full bar of Keep Awake and minimal SOT etc.).
Edit:
Location, NFC, wifi, Bluetooth all off
App ops: Keep Awake etc. all turned off
Simplysausages said:
I'm currently experiencing a serious Keep Awake bug when on a Lollipop ROM and I have no idea how to stop it.
The phone is constantly awake, even when using App Ops, Amplify, BBS, Greenify etc.
Currently on ASOParadox ROM, but have used COS12.1, Exodus (with AK Kernel) and Sultan's ROM.
Tested both TK and Open GApps.
Testes Sultan's without a GApps package and the problem still occurred.
Anyone know what it could be?
(Not letting me post screenahots as a new user, just battery stats showing a full bar of Keep Awake and minimal SOT etc.).
Edit:
Location, NFC, wifi, Bluetooth all off
App ops: Keep Awake etc. all turned off
Click to expand...
Click to collapse
View the Partial Wakelocks section in BBS and it should tell you which app is keeping the phone awake.
Heisenberg said:
View the Partial Wakelocks section in BBS and it should tell you which app is keeping the phone awake.
Click to expand...
Click to collapse
.
I've had it reinstalled for last 15 minutes and nothing has shown up.
I will let it run longer and report back.
Update:
BBS for 60mins
GsmInboundSmsHandle
4s count 2
bluedroid_timer
2s count 3
*alarm*
2s count 33
(Apologies for poor formatting)
Edit: should mentioned that I've denied those and more through Amplify before and it's never rectified it.
I recently installed wakelock detector to help me save battery life with greenify. Looking at what it says it seems my phone never goes into deep sleep. This screenshot only shows the past hour and a half as before that I greenified things that looked like it might be causing the problem, but it looks the same now as it did before, 0.0 of deep sleep no matter how long I leave it, but none of the listed wakelocks seem to be that long, so I can't figure out why my phone wouldn't be deep sleeping.
Its a rooted Sony Xperia e4 running 4.4.4
Any thoughts?
You should also check Settings -> Battery -> tap on battery graph to open History details. There can be some dependencies between 'Awake' data and other data. Or you can post the screenshot of it here.
Hi, Sorry it took so long for me to respond, I was hoping to get a screenshot from a period where I hadn't touched my phone for longer but I kept forgetting at night time. I notice this time it actually says my screen has been on the whole time (though I never used it in this period at all, and when I picked it up the screen was off) So I have also included a screenshot of the screen wakelock page. Frustratingly, a lot of the things on the cpu wakelock page are already greenified and I manually hibernated them before turning the screen off, so not sure why they are still causing issues.
Either way, none of it adds up to the time awake
I posted a reply on this earlier but it seems to have disappeared. Anyway, I installed betterbatterystats and it showed that *backup* was keeping my phone from sleeping.
Google suggests it isn't altogether unconmon, and following some instructions I found I disabled back up, cleaeed dalvik cache and enabled back up again
So far its worked brilliantly, hopefully it stays that way.
Just an update on case anyone googkes and reads my solution above, it didn't work. Restarting my phone makes it go away for a little while and my phone gets plenty of deep sleep even in only a short space of time, but then *backup* comes back and its all over again. I can't keep restarting my phone every couple of hours. Maybe turning backuo off permanently will help, but then I have no backups, so hardly av good solution.
Hi,
*backup* is a wakelock from Google's Backup service. Wakelocks are so crazy because it regularly backups your data (such as Contacts, your Play Games' progresses, WiFi passwords, app data, etc) to Google's server. Disabling this equals to no longer having up-to-date backups.
You could actually disable the automatic backup, but make sure you backup your data periodically.
It's better for me to use BBS instead for checking for wakelocks.
Sent from my ASUS_Z00A using XDA Labs
krasCGQ said:
Hi,
*backup* is a wakelock from Google's Backup service. Wakelocks are so crazy because it regularly backups your data (such as Contacts, your Play Games' progresses, WiFi passwords, app data, etc) to Google's server. Disabling this equals to no longer having up-to-date backups.
You could actually disable the automatic backup, but make sure you backup your data periodically.
It's better for me to use BBS instead for checking for wakelocks.
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
Yes I've found BBS better to, never would have found the problem otherwise. I turned off back up maybe 13 hours ago and so far so good. Not the ideal solution though eh. Hopefully google will fix it soon
Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"
Hi there, I've been using OOS 9.0.2 and I got some excessive wakelocks by *walarm*:com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION which happens about every 60 seconds. I'm not sure if this is normal or what the culprit could be as the location services are deactivated all the time, yet it occurs. Any idea what it could be? Can it be related to Android Wear?
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Macusercom said:
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Click to expand...
Click to collapse
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
spartan268 said:
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
Click to expand...
Click to collapse
I wish I could say I simply used a wakelock detector or something like that. I loaded my apps to a secondary device and disabled them one by one. I wasn't sure whether Greenify would prevent it but it did. So greenifying different apps and see if it changes was how I figured it out.
My battery consumption during standby went significantly down. Even though alarms are just the triggers and not the wakelocks, triggering the Network Location Provider every 60 seconds prevents the device from deep sleeping and was a main cause of the standby issues. I suggest to check it for yourself with BetterBatteryStats.
My ALARM_WAKEUP_ACTIVITY_DETECTION exceeded 1000 alarms by the end of the day. While I still get a few Android Wear wakelocks if my smartwatch is not connected. They make up at least 150 too. What I'm trying to say is that I don't say you should have no alarms anymore, but even 150 seem normal for Google Play Services. But over 500 or 1000 definitely isn't normal.
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
oksagi said:
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
Click to expand...
Click to collapse
That's my point. Even with light doze active apps still have a maintenance window and Sleep as Android seems to have permanently used sensors via Play Services. Once greenified it stops using it completely and I went from 1.2%/h idle drain to under 0.7%/h or less. I'm just trying to help people who have the same issue as I do. If no app seems to use any sensor, location etc. you don't need Greenify of course. But it can help with some apps.