This started around the time I wanted to check and see if my GPS was still working after the update. I went through the hoops to get google maps to be able to use the GPS and it was working fine. But shortly after, I noticed excessive battery drain, and BBS showed me that my phone was not sleeping at all.
I am now seeing 3 partial wakelocks from google services framework: Checkin Handoff, Event Log Handoff, and SystemUpdateService.
Tried several of the usual things to track it down and in the process I'm seeing some oddities:
1. Using autostart manager, I unchecked the checkin and SystemUpdate-related autostarts for Google Services Framework, but they won't stay disabled. Generally speaking, the autostart manager is working - other receivers stay disabled.
2. Settings -> Accounts & sync -> Google -> Maps & Latitude brings up a location settings screen in maps. This has an option for Automatic check-ins which is checked. I un-check it, it says in a toast message that it saved, but if I exit out and come back in, it's still checked.
I'm thinking those two issues are caused by the same thing that's keeping these wakelocks going. Any ideas?
Oh, also, the only checkin-type message I find in logcat is this (repeated often). Indeed, there is no /data/data/com.google.android.gsf/.checkin.CheckinService - should there be?
04-11 09:46:28.412 W/ActivityManager( 553): Unable to start service Intent { cmp=com.google.android.gsf/.checkin.CheckinService }: not found
[Q] do you have /data/data/com.google.android.gsf/.checkin.CheckinService?
Answering myself trying to change the thread title.
Someone who has stock JB, please check and see if you have the abovementioned file. If so can I have it please? (or if it's data I'd like to know what goes in there).
Made a little progress.
I was actually able to disable the autostarts using "Autorun Manager" instead of "Autostart Manager". I'm not sure exactly why unless it is because these autostarts have $ characters in them.
This makes the wakelocks go away.
I'm still curious why I can't turn the setting off in maps and whether the 'not found' error is anything important.
Exactly the same issue (although mine is an S3 running Omega Rom 4.1.2).
Constant Wakelock for 3hrs 36m all of a sudden (seen with Wakelock Detector). Used "DisableService" app to disable all sub-services under Google Services Framework. Play store seems to still work OK.
Related
Ever since the launch of ICS for the I9100, the AudioOut_1 wakelock has been bugging me beyond limits. I was happy to reach the end of the day with a fully charged battery. Because I finally found a solution, I wanted to share it with everyone, because google is full of questions of people experiencing the same issue as me, without a solution in any of the found threads. I saw numerous solutions, from freezing certain system apps to setting your device to silent, with none of these solutions working for me.
First of all: AudioOut_1 is NOT, i repeat, NOT the wakelock that is caused by the keytones, touch sounds or screen lock sound. Before you continue and saying you are experiencing any Audioout wakelocks, please confirm that you have turned of these first!
For everyone not knowing what a wakelock is, I recommend you look for chamonix' thread on the app BetteryBatteryStats. Without his awesome tool, I would never had discovered the source of my drain. Because I'm still a forum-rookie, I can't link to his thread, so please use google or the XDA search option
After blaiming countless apps for starting the AO1 wakelock, and not closing it, thus keeping my phone awake, I started searching more precisely. The way I discovered the responsible app is as follows:
1) Search and Download BetterBatteryStats from the Play Store.
2) Search and Download Watchdog Task Manager Lite from the Play Store.
(Once again, because i'm a novice, I can't link, I'm sorry )
3) Use the Samsung Task Manager (or any task manager, but Sammy worked for me) to kill all processes in RAM.
4) Go to BBS, press menu button, Actions, Set Custom Ref.
5) In the bars in the top of BBS, select 'Partial Wakelocks' in the upper and 'Since Custom Ref.' in the lower one.
6) Wait for AudioOut_1 to appear. This can take some time because it is probably triggerd by a service.
Once it appears, it never stops. Refresh every couple of seconds and verify that it is actually adding seconds to it's wakelock time.
7) Start Watchdog Lite and look for the process that is possibly using the AudiOut_1 wakelock. Kill that process (tap on it and select kill) and go back into BBS. If the AO1 stopped counting, this is possibly the app. If it didn't stop counting up, go back into WL and stop the next service you suspect being the culprit.
When you've found the app, try freezing it with Titanium Backup or deinstall it, wait for a couple of hours and check if it really was the one, and report back here to help other users
Hope this helps killing this nasty bug! For me btw, the app responsibly for my drain was AirPlayIt. And I wasn't even using it
Here is the link to the BBS thread => http://forum.xda-developers.com/showthread.php?t=1179809
If this app helps you, consider a donation to the developer or buy this app from Google Play store.
For a few days now I've noticed a massive battery drain of Google maps, up to 60 per cent of the battery use, without evening opening the app (must have been running in the background). I have temporarily disabled the app on my phone, but am I the only person with this problem?
stevennekens said:
For a few days now I've noticed a massive battery drain of Google maps, up to 60 per cent of the battery use, without evening opening the app (must have been running in the background). I have temporarily disabled the app on my phone, but am I the only person with this problem?
Click to expand...
Click to collapse
Make sure the "Location reporting" (in Google Maps settings) is disabled if you don't want the battery drain. Moreover, Google Now activates the Location reporting so you might have to disable Google Now as well...
P.s: this post should be in Q&A section, doesn't it ?
vakbrain said:
Make sure the "Location reporting" (in Google Maps settings) is disabled if you don't want the battery drain. Moreover, Google Now activates the Location reporting so you might have to disable Google Now as well...
P.s: this post should be in Q&A section, doesn't it ?
Click to expand...
Click to collapse
I have google now disabled all the time, and the location reporting was unchecked too.. Besides that, even if that had been activated, it shouldn't have taken 60% of my total battery (I had about 70% of my total battery left when I noticed it today), should it?
(...and yes, this one should be in the Q&A section, hadn't thought about that when I posted it though...)
I had the same issue. I turned all location reporting off and turned off Google now, also made sure GPS was off. All that helped a fair amount but Maps still kept running in the background even though I'd never used the app. In the end I used an app called Greenify to hibernate maps and a bunch of other background apps and it made a world of difference. Use wakelock detector to see which apps are causing wakelocks and disable any you don't need running.
Wyman Gibuil
use an extension car battery so it can add battery life even for month, just make sure you will get the same voltage
Its coz of google location services bug that HTC phones are having after the update.
If you are interested about it: http://www.androidpolice.com/2013/0...ssues-for-htc-owners-google-working-on-a-fix/
In short:
Only location service thats working if you have this bug, is gps. Rest of locations services (wifi, mobile newtwork etc.) wont work.
Who couses it? - latest updates for google services.
How to fix it? - atm google is working on fix. There is some type of user fixes you can try. (see post).
Hope it explains your drain. I have this bu and i get this unusual drain from maps too.
Something that is catching my attention as i mess with roms, is whenever I first sign into google services the google talk app is immediatly alerting me i have invite requests etc. meaning that app seems to be sitting in the background running and probing for network access. Clearly a battery drain, but I cant find a way to disable this behaviour short of freezing the app in titanium backup.
Have google really been this silly and put an social chat app on the OS that is forcefully always running unless removed?
On GB roms there is an option to not auto sign in, on ICS/JB roms (and also on GB if you update it to hangout app) there is no way to avoid auto signing in.
So am I right the app cannot be turned off, and is there any known ill affects to freezing the app?
Freeze it. It's always the first thing I freeze when I do a clean install.
Hi,
For some reason SystemUpdateService is absolutely destroying my battery (phone awake 98% of the time) because it's not running and Android is constantly trying to run checks against it.
The service is under both of the following apps:
Google Play Services
Google Play Services Framework
If I use the DisableService app I can kick them back into action again... but whenever I restart my phone, they're disabled again. Also, sometimes they randomly switch off again at random.
Any idea how to keep these services running please?
Many thanks
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
tange1 said:
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
Click to expand...
Click to collapse
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
tnsmani said:
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
Click to expand...
Click to collapse
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
tange1 said:
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
Click to expand...
Click to collapse
Do you have Xposed? If so, install AppOpsXposed and untick the "Keep Awake" function of Play Services. Another thing you can try is uninstalling the update to the Play Services, reboot and then manually update it and again reboot.
If it is still not arrested, Google is your friend.
Unfortunately I've the same problem on my OnePlus 2 with stock ROM. I've installed Greenify two days ago, and enabled aggressive doze with amazing results! Last night I enabled Doze on the Go (using ADB) and since unplugging my phone this morning there is this constant wakelock of Google Play Services. Disabling Doze on the Go as well as reinstalling Greenify didn't help. Looking forward to a solution!
This is a known problem. Sometimes it's worse and sometimes less, but Google Play Services is a known offender in this manner. And Google processes in general. Part of the reason for this is that Google often wakes up your device, periodically, to track your location (horrible, yes, and it continued to happen for me even when all Google location options I could find, as well as GPS, were turned off).
Solutions that have reportedly worked for some people in the past (try one at a time or all of them) - they don't require root:
-Make sure you do not Greenify/freeze/hibernate Google Play Services, or similar processes, as this may make the issue worse.
-Clear cache and data of Google Play Services.
-Manually update Google Play Services to latest APK version available from your device, downloaded from the web. Make sure you select the right version for you. http://www.apkmirror.com/apk/google-inc/google-play-services
-Try turning off as many Google background features as you can, such as location tracking/history, etc.
I guess some of these steps may only work after the next reboot, so reboot the device when you're done.
But as I said, this process is a known big offender. The above may not work, or may work temporarily. The stronger and more permanent solutions require root (you don't really need to try the above options if you do these). The more of them you do, the less 'keep awake' you should experience:
-Install Xposed Installer app and install Xposed Framework, so you can use the modules mentioned below...
-Use AppOpsXposed module (or CM Privacy Guard if you have it) to deny keep awake permission to Google Play Services, and other Google background apps.
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Cultar said:
..............
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Click to expand...
Click to collapse
The unpaid version of Amplify will block a maximum of a couple of wakelocks related to location. Only the pro version is capable of blocking other wakelocks and alarms including those of Play Services. But as you said, it is not automatic and you will have to set it up.
Any updates on this?
Google play services is awful
MSK1 said:
Any updates on this?
Google play services is awful
Click to expand...
Click to collapse
Not a Greenify issue. Some devices/ROMs/configs seem more susceptible to GPS runaway. Clearing GPS cache+data on occasion followed by an immediate reboot has proven helpful for some. Good luck.