Google Play Services eating battery

[just_luc]

Well I'll be dammed .. Just after writing that last post I remembered something I had changed before the problem started..(after I uninstalled several dozen apps for no reason apparently!)

A developer had asked me for device logs to troubleshoot another issue.. For this I had to enable developer mode .. Did so. Sent the logs.. Didn't see any reason to turn developer mode back off..

Well.. I justly switched it off and my Google services process dropped to the bottom of the list like a hot potato.

Posted via the Android Central App

 

[Air pirate]

Uh oh... I also enabled developer options a couple of days ago. Getting ready to flash 6.01. Didn't flash, but I left dev options on. Hmmmmmm.

 

[Air pirate]

Turned dev options off. Battery usage back to normal.

 

[eric002]

Turned dev options off. Battery usage back to normal.

My question would be why would turning developer options off have anything to do with battery usage at all? I have the developer options on and it doesn't kill my battery per charge.

 

[just_luc]

My question would be why would turning developer options off have anything to do with battery usage at all? I have the developer options on and it doesn't kill my battery per charge.

That is the ten million dollar question .. But it definitely was the cause of my issue, and at least one other person.. I suspect many others.

Posted via the Android Central App

 

[danielson2047]

I'm thinking coincidence. I always have dev options unlocked and have never had an issue.

Posted via the Android Central App

 

[Rgv9fHQ8wSCABtMIOz6z]

I too regularly find my Moto X 2014, 6.0 (new device) having the battery drained by Google Services. Currently 38%. Compared with Mobile standby in an area with a relatively weak signal that eats up 14%, that is extreme. This happens often and it seems to spontaneously occur a few times a week. I don't notice any pattern relating to apps. What I do see in History details is the phone is awake 100% of the time when this occurs. There seems to be no relation to data usage (on WiFi mostly, Mobile data off). GPS is also unused according to the battery history. A reboot fixes things temporarily.

I currently have developer options enabled (to prevent the annoying slow animations between apps and windows only.) but noticed the problem before I ever unlocked the developer options. So that seems unrelated.

Does anyone know a way to diagnose what process or service is causing the permanent awake state? Without root privileges that is.

 

[Kerbin Centurion]

I'm thinking that I should have said "Google Services" and not Google Play Services. I am running v5.1-1743459 of Google Services Framework and v7.5.71 of Google Play Services.

Check out these screenshots. My Nexus 6 NEVER goes through battery so quickly and so consistently - notice how the usage graph is a virtually straight line even though there was only 35 minutes of screen time during the 2-1/2 hours displayed. And, I don't know why Fit is listed at 3% - I have Activity Detection disabled and no connected apps.

View attachment 181803View attachment 181804

This is really getting rediculus.
Check out this massive battery drain.

https://photos.google.com/share/AF1...?key=VkJpRFd0ZXBkUTNnS3RPY0hqWE9BcDNmcEdNQ0F3

 

[vice86]

Turning off Dev Options worked for me too. Was up to 60%. Turned it off and now its down to 48% and my battery is lasting longer. I turned it on a day or so ago...before that I got almost a full 2 days on one charge and using my screen for about 2-3 hours. Today I noticed I was down almost 40% in hours and screen time on was only at 14 minutes.

Also this was a freshly restored Note 3. Didn't even install Facebook back on because that was a battery sucker for me too and the last update just kept crashing.

 

[gamersam2012]

Guys I had the same problem exactly same... I just uninstalled the Google App to the factory version and poof... the problem was gone for good... As some of the people here are saying that it might be due to Google Fit or Wear... I dont think so cause my problem only began when google updated its app for Assistant. Ever since i got assistance, this problem appeared. So now I just uninstalled Google App and the problem's gone. Hope anyone could also benefit from this.
Thanks