Post Reply

Stock Android 4.3 'Android OS' permanent wakelock

OP andrewf403

4th August 2013, 04:15 PM   |  #1  
OP Senior Member
Flag Odessa
Thanks Meter: 152
 
161 posts
Join Date:Joined: Jul 2007
More
Looking at some XDA and Reddit posts, small set of users (my Nexus 4 including, unfortunately) experiencing some sort of bug with stock not rooted Android 4.3 after OTA on all range of Nexus devices.

The bug is Android OS holding device awake all the time and not letting it into deep sleep. It looks like it has not huge impact on battery life, but still it is abnormal. Rebooting devices, for me, curing this, but only for a day or two, after a few days wakelock makes its come back.

Unfortunately WakeLock Detector does not show who is guilty, looks like it is in the kernel. I just have bought BetterBatteryStats, and will look at its data tomorrow. What WLD does show is that my Nexus 4 had 0:00 of deep sleep today:





Here is what Android's battary stats looks like:





And here is what is should look like and does look like on my 2012 Nexus 7, that is unaffected by this. And stats looks the same for a few days after I reboot my Nexus 4, before wakelock occurs again:



I have to assume that it has nothing to do with connectivity, because same thing happens even if I disable wifi and mobile data entirely.

Here is a list of topics about the same issue I could found, but they only have questions, not answers.

Android Police's review of 2013 Nexus 7: http://cdn.androidpolice.com/wp-cont...2-16-14-17.png
XDA thread about another Nexus 4: http://forum.xda-developers.com/show....php?t=2388072
Reddit thread about Nexus 4: http://www.reddit.com/r/nexus4/comme...attery_issues/
Reddit thread about 2012 Nexus 7: http://www.reddit.com/r/Nexus7/comme...roblems_since/
UPD: one more thread about 2013 Nexus 7 http://forum.xda-developers.com/show....php?t=2394813
UPD: one more Nexus 4 thread http://www.reddit.com/r/nexus4/comme...ot_of_battery/

Unfortunately, I also do not have any answers (yet). The purpose of this post is gather all the info I've found in one place, and maybe rise the awareness about this.

Update:

Ok. I had BetterBatteryStats on my phone for 30 minutes, and this whole 30 minutes PowerManagerService held wakelock itself. So, it safe to assume that it is an offender.
Attached Thumbnails
Click image for larger version

Name:	2013-08-04 14.48.47.png
Views:	1169
Size:	93.8 KB
ID:	2164359   Click image for larger version

Name:	2013-08-04 14.53.38.jpg
Views:	1183
Size:	36.1 KB
ID:	2164361   Click image for larger version

Name:	Screenshot_2013-08-04-17-54-27.jpg
Views:	1135
Size:	25.7 KB
ID:	2164366   Click image for larger version

Name:	2013-08-04 15.22.11.png
Views:	1054
Size:	105.2 KB
ID:	2164398  
Last edited by andrewf403; 15th August 2013 at 04:25 PM.
The Following 3 Users Say Thank You to andrewf403 For This Useful Post: [ View ]
6th August 2013, 08:30 PM   |  #2  
Member
Thanks Meter: 7
 
82 posts
Join Date:Joined: Sep 2010
Hi, I saw your reply on this thread.

I read some speculation somewhere that the wakelocks might be caused by the device continually trying to poll for location, and apparently this behaviour could be corrected by the latest version of Google Play Services v3.2.25. I don't see the wakelocks now after upgrading to it earlier today, however this could also be because I rebooted my phone... Nevertheless I'm still not getting great screen-on time, just about 3.5 hours compared to other people's 5+ hours.

What's your version of the app? If you don't have 3.2.25 you can either download it directly (Android Police has put up a copy of the apk, but it might not be a Nexus 4-specific one) or download a more recent version of Play Store and wait for it to update Google Play Services automatically.

I'll report back here if I notice any more changes in my phone.
6th August 2013, 11:10 PM   |  #3  
OP Senior Member
Flag Odessa
Thanks Meter: 152
 
161 posts
Join Date:Joined: Jul 2007
More
Quote:
Originally Posted by mlj11

Hi, I saw your reply on this thread.

I read some speculation somewhere that the wakelocks might be caused by the device continually trying to poll for location, and apparently this behaviour could be corrected by the latest version of Google Play Services v3.2.25. I don't see the wakelocks now after upgrading to it earlier today, however this could also be because I rebooted my phone... Nevertheless I'm still not getting great screen-on time, just about 3.5 hours compared to other people's 5+ hours.

What's your version of the app? If you don't have 3.2.25 you can either download it directly (Android Police has put up a copy of the apk, but it might not be a Nexus 4-specific one) or download a more recent version of Play Store and wait for it to update Google Play Services automatically.

I'll report back here if I notice any more changes in my phone.

Location related wakelock are reflected in Android System and Google Services in the Android's battery stats, and as NLP (and some others) in the BetterBatteryStats. They account for about 1 hour of awake in a day. And they actually DO something.

This wakelock unfortunately does not show in Partial Wakelocks statistics in BetterBatteryStats, so I think it occurs somewhere deep in kernel.

If you use Google Now, or some other location based apps like Aviate, 3.5 hours of screen time is great. I do not turn off Wi-Fi, even when it is not available, use Google Now (without location history). 3 hours of screen on is what I expecting as a best case scenario.

Unfortunately, at days then 'Android OS' wakelock happens it nowhere near 3 hours.
6th August 2013, 11:38 PM   |  #4  
Member
Thanks Meter: 7
 
82 posts
Join Date:Joined: Sep 2010
So you're saying that location polling only affects "Android System" and "Google Services" wakelocks. Ok, I didn't know that.

But I did note that my "Android OS" wakelocks have now stopped. Although I cannot say whether the update to Google Play Services / Google Play Store had anything to do with it, or whether it was simply because I rebooted my phone. Do you know for sure that Play Services has no effect in this respect?

And yes, I do use Google Now and also Field Trip.

In any case, I'm also noticing that my battery drains at a much faster rate (as compared to 4.2.2) when I have my phone turned on.
7th August 2013, 01:23 AM   |  #5  
Galaxo60's Avatar
Senior Member
Flag Mexico City
Thanks Meter: 359
 
931 posts
Join Date:Joined: May 2012
Quote:
Originally Posted by andrewf403

Location related wakelock are reflected in Android System and Google Services in the Android's battery stats, and as NLP (and some others) in the BetterBatteryStats. They account for about 1 hour of awake in a day. And they actually DO something.

This wakelock unfortunately does not show in Partial Wakelocks statistics in BetterBatteryStats, so I think it occurs somewhere deep in kernel.

If you use Google Now, or some other location based apps like Aviate, 3.5 hours of screen time is great. I do not turn off Wi-Fi, even when it is not available, use Google Now (without location history). 3 hours of screen on is what I expecting as a best case scenario.

Unfortunately, at days then 'Android OS' wakelock happens it nowhere near 3 hours.

Quote:
Originally Posted by mlj11

So you're saying that location polling only affects "Android System" and "Google Services" wakelocks. Ok, I didn't know that.

But I did note that my "Android OS" wakelocks have now stopped. Although I cannot say whether the update to Google Play Services / Google Play Store had anything to do with it, or whether it was simply because I rebooted my phone. Do you know for sure that Play Services has no effect in this respect?

And yes, I do use Google Now and also Field Trip.

In any case, I'm also noticing that my battery drains at a much faster rate (as compared to 4.2.2) when I have my phone turned on.

Possible answer here:

http://forum.xda-developers.com/show...php?p=44361765

Hope it helps.

The Following 2 Users Say Thank You to Galaxo60 For This Useful Post: [ View ]
8th August 2013, 09:16 AM   |  #6  
OP Senior Member
Flag Odessa
Thanks Meter: 152
 
161 posts
Join Date:Joined: Jul 2007
More
Quote:
Originally Posted by Galaxo60

Possible answer here:

http://forum.xda-developers.com/show...php?p=44361765

Hope it helps.

It'll help with Google Services drain, I think. Anyway Google Play Services just updated for me (with Android Device Manager), hope it'll fix Android OS drain too. Hope is not high, though )
8th August 2013, 04:57 PM   |  #7  
Senior Member
Thanks Meter: 33
 
326 posts
Join Date:Joined: Aug 2010
I've recently have this issue as well with "Android OS". Luckily I can still make it through the day easily but annoyed this kind of stuff still happens. I got the latest Google Play Services yesterday and still have this issue today after a full charge. Will reboot and see what happens I guess.
8th August 2013, 08:51 PM   |  #8  
Senior Member
Thanks Meter: 2,389
 
584 posts
Join Date:Joined: Nov 2011
Quote:
Originally Posted by flintdragon

I've recently have this issue as well with "Android OS". Luckily I can still make it through the day easily but annoyed this kind of stuff still happens. I got the latest Google Play Services yesterday and still have this issue today after a full charge. Will reboot and see what happens I guess.

I've been seeing this on my Galaxy Nexus with AOSP 4.3 as well. It looks like this patch might be relevant: https://github.com/CyanogenMod/andro...d0eacfcd2003b9
8th August 2013, 09:51 PM   |  #9  
OP Senior Member
Flag Odessa
Thanks Meter: 152
 
161 posts
Join Date:Joined: Jul 2007
More
Quote:
Originally Posted by steven676

I've been seeing this on my Galaxy Nexus with AOSP 4.3 as well. It looks like this patch might be relevant: https://github.com/CyanogenMod/andro...d0eacfcd2003b9

It looks relevant indeed. Although, I would not call the drain "rapid". I'm now looking close to my device statistics and try to pinpoint exact moment this lock occurs to find the cause.

If it is indeed caused by concurrent condition in PowerManagerService there is not much to do, but flash another, patched, ROM. But I eager to stay on stock.
9th August 2013, 01:42 AM   |  #10  
Junior Member
Tucson, AZ
Thanks Meter: 1
 
7 posts
Join Date:Joined: Mar 2011
Also seeing this with my Nexus 4. Reboot doesn't do much at all for me.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes