35 replies to this topic

[Sinvany]

Hello everyone,
This morning when I woke up I've noticed there has been a massive battery drain on my phone. A quick look through BetterBatteryStats showed it was the infamous wakelock SystemUpdateService, part of the Google Play services.

I tried rebooting numerous times, the wakelock kept coming up straight after boot.
I tried using Disable Services app, to my surprise this wakelock was already ticked off and disabled, yet still working on my phone's background!
I tried doing the same with Autorun Manager app, same thing - SystemUpdateService is disabled, yet still running.

I have no idea what else to try. I haven't installed anything new lately, haven't tweaked anything on the phone, nothing I can think of that would cause it.

Any thoughts or tips would be mostly appreciated, my phone didn't go into deep sleep even for 1second in the last 18 hours.

Something that came up to my mind right now though - could it be an issue maybe with Google releasing android's update 4.4.4 OTA? And for some reason my CM phone tries to connect to the Google update services constantly?

[Silkeyway]

Also posted on xda forums: http://forum.xda-dev...d.php?t=2799210
As stated there too, I'm experiencing the exact same problem you described on my Nexus 4 device, just like OP.
If anyone needs any more information, I'll try to deliver asap.

[ImpassionedRule]

Experiencing this bug on S3 as well.

I've tried using built-in Apps Ops to remove "keep device awake" and "location access" from Google Search.
I've also tried Greenifying Google Play Services, turning off Location Reporting/History in Google Now, and rebooting several times.

On Wakelock Detector, it has triggered the phone to awake ~80% of the time.

[Silkeyway]

copy&paste from xda:

So just trying stuff without any deeper thoughts, I just did two things, locked the phone afterwards and now the wakelock seems to be gone:

1. I enabled SystemUpdateService using Disable Service App, which had already been disabled when we first looked.
2. I looked into the CM update function, where - having selected all stable releases - nothing was showing and refreshing didn't work. Got the idea to look into Disable Service App again, and found that UpdateCheckService of CyanogenMod-Updater was disabled. Enabled it, refreshed CM updater, got a list of stable releases.

My beginner's guess would be #1 did it - but why was #2 even an issue in the first place?

[Sinvany]

Thanks for sharing,
I used Disable Service app and enabled SystemUpdateService both under Google Play Services and Google Services Framwork (like I said before, both were ticked off and disabled).
I also checked the Cyanogenmod-Updater but everything there was enabled for me, and the updater seemed to work fine. Didn't touch that one, it doesn't seem to be related to the issue.

Anyway - straight after I enabled SystemUpdateService I noticed my phone could finally get into deep sleep mode. I've made a reboot and strange thing is that right after that, I see SystemUpdateService back on and kicking. The service popped up again on my wakelock list. I went through Disable Service again and to my surprise the service was disabled again (ticked off), and I enabled it just a moment before. Apparently a reboot kicks the phone back and re-disables the SystemUpdateService.

To conclude things I've no idea what's up with this whole SystemUpdateService issue all the sudden, but apparently enabling the services through Disable Service fixes the problem temporarily (until the next reboot) and allows the phone to go into deep sleep finally.

[Silkeyway]

Now, to me the question is:
Is enabling SystemUpdateService a workaround for some other issue, or is SystemUpdateService getting disabled the issue?

[Sinvany]

Well I'm thinking SystemUpdateService is being disabled by default on CM roms to avoid incidents where the OS is constantly looking for OTA updates and attempting to download them.

Although what's funny here is that since about the 30th of June/ July 1st, this service kept coming up even though it is disabled. So I'm guessing something strange is happening here with this service and maybe the new updates Google has been releasing lately.

I'm sure enabling the service that is supposed to actually be disabled is merely a random temporary fix for this (especially when you need to apply that on every reboot you make). It's contradictory since this very specific service needs to be disabled to AVOID that same problem in the first place.

[slybunda]

anyone solved this problem then? i had M6 on my phone for 1 month with no issues, but im not sure if this problem is caused by M7 or a recent update to a google app. i may just down grade back to M6 and see how things go.

[razorloves]

slybunda, on 02 July 2014 - 01:24 PM, said:

anyone solved this problem then? i had M6 on my phone for 1 month with no issues, but im not sure if this problem is caused by M7 or a recent update to a google app. i may just down grade back to M6 and see how things go.

http://forum.xda-dev...&postcount=5031

[Sinvany]

I don't believe it's an M7 specific problem, I strongly suspect it's a compatibility issue concerning the new updates Google released.
In any way though if you downgrade let us know what are your conclusions, I'm still only speculating as it seems not too many people are experiencing these issues.

[razorloves]

Sinvany, on 02 July 2014 - 02:00 PM, said:

I don't believe it's an M7 specific problem, I strongly suspect it's a compatibility issue concerning the new updates Google released.
In any way though if you downgrade let us know what are your conclusions, I'm still only speculating as it seems not too many people are experiencing these issues.

right. it's a new ota update service that was added in a recent Google Play Services update. Here's is the fix where cm blocks this new service. It's already in the nightlies http://review.cyanog....org/#/c/66894/

but if you are on m7 and dont want to use nightlies, you'll have to wait till m8 comes out to get the fix. But in the mean time, you can disable the services by following the instructions in the xda link i posted earlier, a couple posts up

Edited by razorloves, 02 July 2014 - 02:09 PM.

[slybunda]

so if i just slap on the latest nightly this issue will be resolved?

[razorloves]

slybunda, on 02 July 2014 - 02:18 PM, said:

so if i just slap on the latest nightly this issue will be resolved?

yes. if you look at the link i posted, it shows the fix was merged on the 29th. So, any official nightly after that will have it. And i've seen numerous people confirming that it's fixed with the new nightlies.

[Sinvany]

Thank you razorloves for clarifying this out for us.

[slybunda]

brilliant thanks for this info razorloves, i will update to new nightly since its less faffing around, and new milestone M8 might even be out for next week.

brilliant thanks for this info razorloves, i will update to new nightly since its less faffing around, and new milestone M8 might even be out for next week.

[razorloves]

You're welcome

[xristofer]

I can't tell if I have this same problem on an LG e970 with 11-20140608-SNAPSHOT-M7-e970, but it started in the last 48 hours after an OTA update that included some Google apps like Google Play Music and some other things. And it happens even booted in Safe mode.

WLD says the phone is awake 98% of the time. And lists Google Search as the top Wakeup offender: even if the phone is in airplane mode, even if Location services are off, even if Google Now is disabled. The worst kernel offenders are msm_hsic_host (6 minutes), radio-interface (3 minutes), and main (1 minute), in a total time since battery stats reset of 1 hour. Yet Settings > Battery shows the worst offender as Google Play Services 82%, and when I click on it it says "Keep awake 1h 10m" which is the current uptime of the phone. So, basically it's not sleeping but I can't tell what's keeping it up.

So if I have the same problem reported here, great, I'll check out the xda link and see about manually fixing this to tied me over for M8; unless someone tells me I can definitely apply a Nightly and not have to do the /data and cache erase, I'd rather not mess around with rebuilding my phone since M8 is probably due in 3-6 days anyway.

[keksbox]

Same problem here since yesterday. Suddenly the system started being awake almost 100% of the time. As mentioned above I used 'Disable Service'.  Under Google Play-Services item 'SystemUpdateService' was ticked off. Ticked it on (which is somewhat the opposite way of what the xda thread describes) but now everything is back to normal. So it's not a big deal with M8 beeing around the corner anyway.
Cheers

[Sinvany]

Keksbox yeah you've done it right, just make sure if you reboot your phone you'll need to use Disable Service app again (reboot overrides the changes we've made apparently), otherwise the SystemUpdateService will kick back in and your phone will not go into deep sleep mode. Of course waiting for M8 here too for a final and proper solution to this.

Xristofer, if you have the same issue as we do with the SystemUpdateService no need to go look through the XDA forums everything is written here - Just use the Disable Servie app. Under Google Play services and Google Services Framework you'll see SystemUpdateService ticked off. Tick it back on and that's it, shouldn't bother you anymore.

[Aninimouse]

Glad I found this explains my wakelock problem