yashsingh1/xdaforums huggingface dataset:
[General Topics] v7:
OTA notification can be stopped by disabling SUS.But disabling it actually cause the wakelock.I assume that it is ROM specific.Another Paranoid user had also reported this.I'll recommend to disablle the ActiveReceiver again and do an daivik wipe only.If that doesn't work,then am helpless.
[General Topics] zer0lab.dev:
Hey mate, thanks a lot for your help, but that was my first post here in this thread.. As you can read a few post below I finally succeeded to remove both OTA notification both wakelock issues!

Really don't know how 'cause how [MENTION=4675510]air001[/MENTION] reported in the first posts after wiping davilk cache and rebooting the ActiveService receiver always went back to its original state.. So I tried to also use MyAndroidTools app and after some reboots it finally worked!
[General Topics] v7:
Good to hear from you :)

I'm glad it worked.
[General Topics] Cyclu:
I have checked your log, exactly not trace of these wakelocks.

Good for you:)

Strange that we have these different results with the same version of Play Service, probably because different Rom and setup, justly yesterday I got an PS update to version 7.0.99 we'll see what Mr.Google have prepared for us this time.

I saw in your BBS log that you have analytics service enabled, go to Service>Play Service in My Android Tools and disable it, it will be good for a little for your battery and many for your privacy (see the screenshot) don't forgot disable it after each PS update, because it's automatically re-enabled, it's the only one that is re-enabled after PS updating at least for me;) I am wary of generalizing the things now.
[General Topics] v7:
Thanks for the info :)

I disabled analytics service with Disable Service :thumbup:

Tapped from my furious ZR ;)
[General Topics] kurtextrem:
In the CM Bug tracker "Wakelock Terminator" (play store, xposed module) was mentioned to bring that wakelock under control. Did some try that?

Also.. why is there no one who could "simply" write an xposed module just for the purpose of disabling this wakelock.. would be more convenient.
[General Topics] aayende69@:
Is there any way to use Tasker to automatically disable with a command task, I tried but the response is red, some error is happening with the process.
[General Topics] davboc:
indeed I prefer to enable the service at every boot, until there is a real solution for this...

Yes I'm sure, broadcast receivers are disabled.
[General Topics] IronTechmonkey:
Likewise as to this Play Services update to 7.0.99. Sadly B00-gle still wake-locking. CM11/KK 4.4.4. At least in CM, Privacy Guard can be used keep the service from waking the phone without disabling the service entirely.
[General Topics] ziggyke:
[MENTION=5867207]vaisakh7[/MENTION]

Thanks for these outlined steps so my battery could hold up at least a day instead of couple hours.

I think you made a typo in the OP.

It should say: "Wipe Dalvik Cache" instead of "Wipe Daivik Cache".

In the "Privacy Guard" I've also the possibility to disable "auto start", see added screenshots.

I disabled this and then checked with the app "autostarts" and when I searched for "SystemUpdateService" everything was already disabled.

So I think the steps to perform with autostarts only is needed when not being able to disable "auto start" in the "privacy guard" or for ROM's that don't have the "privacy guard" at all.

And it is working like a charm! :good::victory:
[General Topics] v7:
Hey I messed up with the letters,sorry for that. :D

I know that Autostarts won't be needed if you can disable using Privacy Guard. But not all roms have built in Privacy Guard and on some devices there is no option to disable Auto Start.That's why I made a general solution.
[General Topics] ninjaturtle76:
Thanks, it's nice having my battery back. :)
[General Topics] Kockowan:
Hello,

KitKat 4.4.4 (MackayRom 4.9.13) with Google Play Services 7.0.99:

I did disable in Autostarts the only active SystemUpdateService in 'Secret Code entered' (pls refer to screenshot), did clean Dalvik cache in recovery, reboot.

=> SystemUpdateService in 'Secret Code entered' is still not active after rebooting.

So is there any need for further activities like Privacy Manager/AppOpsXposed?

Thx + regards!
[General Topics] v7:
Read OP.

SecretCodeReceiver must stay disabled.

Tapped from my furious ZR ;)
[General Topics] Kockowan:
Ok, I got it fixed by:

"In app ops, set wake up and keep awake permissions for google play services to deny. "

Pls refer for screenshot to: http://xdaforums.com/showthread.php?t=2529461&page=287#post59775322

Thx + regards.
[General Topics] poodleDoo:
[MENTION=5867207]vaisakh7[/MENTION]

Kudos to you sir!

I tried Amplify, Disable Service and whatnot to stop this crazy wakelock.

Your solution got my Nexus 5 into deep sleep as it had not been in weeks!
[General Topics] Takamoto:
Hi,I'm on jb 4.1.1 root and I can't to have app ops(4.3+). I tryed xprivacy xposed and lbe security master but those two haven't option for disable "wake up" and "keep awake"..any solution?
[General Topics] v7:
I can't find a permission manager for 4.1 JB.

Try this.Use DisableService to enable "systemupdateservice".Open the app and in system entries you'll find Google Play Services.There you can find the service.This must block the wakelock.But you'll have to re enable the service after every reboot.

Tapped from my furious ZR ;)
[General Topics] Hinterecke:
Found a solution posted by a Brad Hudson which works fine in Pac-rom on galaxy s3 mini and probably wil work in any rom with init.d support. I am new here and not allowed to post outside links so please google "systemupdateservice+wakelock+tasker+solution+Dimitris+Psallidas" if you want to see the thread where i found this solution.

Created userinit.sh in /data/local, gave it all the rwx permissions and pasted this in it;

#!/system/bin/sh
pm enable com.google.android.gms/.update.SystemUpdateService
pm disable com.google.android.gms/.update.SystemUpdateService﻿

Tested it first with the disable line commented out and after reboot checked in myandroidtools if systemupdateservice was running, and it was. No need to completely stop all google services from working.
[General Topics] v7:
Why mess up with complex tasker when you have a simple solution? :D

Tapped from my furious ZR ;)
[General Topics] Hinterecke:
If you mean Brad' s solution then because it probably doesn't work for everyone, see the picture.

But for me it worked, just created his userinit.sh script in /data/local et voila.. :)

View attachment 3238314
[General Topics] v7:
Its good for you :)
[General Topics] Hinterecke:
It is :D

So I can let the rest of google's services stay awake to let them happily go on killing my battery.. :)
[General Topics] v7:
I hate these Play Services running on background without much purpose.The only thing the do is to drain the battery as fast as possible.:banghead:

Why the engineers at Google update these Play Services?To increase bugs?maybe :mad:

Tapped from my furious ZR ;)
[General Topics] Hinterecke:
Don't know and i hate the drain as well so i amplify a lot of them, but i don't know what effect keeping them al sleeping would have on things such as my GPS navigation.
[General Topics] v7:
I've amplified a few only.I had almost every bad service amplified a while ago.And I broke something like GPS and push.So I reverted the changes.I saw a battery guide here at the forum,followed it and now I'm a happy man.

Tapped from my furious ZR ;)
[General Topics] Hinterecke:
Tried a lot of things from this forum and Greenify and Amplify became my battery's best friends but amplify indeed can have some strange effects, on stock rom (Samsung s3 mini) amplifying GCoreFlp made google play services crash all the time and now on pac rom it's okay. Funny stuff.

But keeping google services from waking up doesn't have negative influences on your GPS if you're using apps like runtastic road bike?
[General Topics] pasionporelrojo:
After a lot of non-successful other ways to fix it (I've been in lot of forums/posts trying to get rid of battery drain), I've been able to stop "systemupdateservice" drain because of this post.

A million of thanks for your help :D
[General Topics] josephiskandar:
Thanks a lot for these advices! My phone was basically never going idle, now it is going idle again which has amazingly improved my battery life :D

Google Play Services enabled:

•	CheckinService

•	EventLogService

•	SystemUpdateService

Google Play broascast receivers disabled:

•	CheckinService$ActiveReceiver

•	SystemUpdateService$ActiveReceiver

•	SystemUpdateService$Receiver

•	SystemUpdateService$SecretCodeReceiver

What about these broadcast receivers? I left them activated for now (see screenshot):

•	CheckinService$ImposeReceiver

•	CheckinService$Receiver

•	CheckinService$SecretCodeReceiver

•	CheckinService$TriggerReceiver

Also, I don’t really know what a broadcast receiver is. What phone functionalities are affected by disabling all these SystemUpdateService and CheckinService broadcast receivers ? Is it fine to completely disabling them, or would it be better to use Amplify to limit them?

Note: SystemUpdateService was disabled at every reboot, so I used the Tasker profile you linked. It has two actions on boot, one to enable and one to disable SystemUpdateService, which is probably for a slightly different problem than mine. I personally only left the command to enable it on Boot, which is working.
[General Topics] Cyclu:
Glad it worked for you:)

The broadcast receivers are very well explained here:

http://www.vogella.com/tutorials/AndroidBroadcastReceiver/article.html

The SystemUpdateService broadcast receivers and corresponding service are responsible for OTA updating, I personally don't use it anymore, because I have a custom ROM, so I have disabled these broadcast receivers completely. So is better disabling them if you don't want use the OTA.

About CheckinService broadcast receivers:

Google Checkin is the service responsible for sending to google the data in /data/system/dropbox. Crash dumps, lastkmesg, dmesg, full logcat dumps are in here. On Google Checkin (Open up Play Store, Sync gmail, Login to a Google service) this data is synced.

Disable them completely, it also will be much better for your privacy.

I also have amplified this alarm (Check if it appers for you in Better Battery Stats) "com.google.android.gms.checkin.EventLogService$Receiver", which has appeared after renabling the "CheckinService" service, even if the corresponding receiver was disabled, which is very bizarre:eek:.

I have set for it in Amplify "Allow every" 86400 (24h).
[General Topics] TimberW:
Hi everyone,

This wake lock is killing my phone, at the moment, the method describes works. My phone will go into deepsleep. But if I charge my phone, then the wakelock will continue and it won't go into deepsleep

If I restart the phone, it is able to go into deepsleep again. Is anyone experiencing this as well?
[General Topics] kurtextrem:
Simplest solution:

- Xposed

- Wakelock Terminator

Search for the play services, filter: "SystemUpdateService". Done.
[General Topics] HeathenMan:
this works perfect. lost 1%/Hour on sleep
[General Topics] aayende69@:
This is new and does not let phone go to deep sleep, reverted all and still have it working constantly, any suggestions?
[General Topics] v7:
Try amplifying it.

Tapped from my furious ZR ;)
[General Topics] Cyclu:
I have also had this wakelock, you have to enable this service: com.google.android.gms.checkin.EventLogService (first screenshot) and disable the corresponding broadcast receivers (second screenshot).

Additionally I have used Amplify to amplify this alarm (third screenshot) which appeared after activating the above service.

See my post @51 for more info.
[General Topics] lost_:
OP should include this as an alternative. This works.

I've tried privacy guard, disabling the receivers and rebooted, cleaning dalvik and cache, etc a few times, all to no effect. Using Wakelock Terminator occurred to me early on, but I haven't used it in over 9 months because it wasn't reliably blocking some alarms. I guess WT works best for partial wakelock likes the ones caused by SystemUpdateService.
[General Topics] alan-31:
I have AOKP which is basically dead because there's no one working on it now and SystemUpdateService stays active no matter what. I've tried everything, Auto starts, Xposed, wake lock terminator and the service still keeps the phone awake 100% of the time and draining the battery.

Sick and tired of Google doing this bull**** and not giving control to the user.
[General Topics] HeathenMan:
What about modify of gplay services with lucky patcher? just use the excludes from 'insane battery life' thread
[General Topics] eranyanay:
Hi everyone,

Im running CM11 on my phone and started suffering from the SystemUpdateService.

during my attempts to solve it, I ended up with no SUS wakelocks, but with RILJ wakelocks, constantly!

Is there anything I can do about it?

they disappear only when phone is charging
[General Topics] v7:
Use amplify to limit RILJ

Tapped from my furious ZR ;)
[General Topics] eranyanay:
Doesnt it require Xposed?

I dont have it...Im also running in ART mode.
[General Topics] ocd_amp:
This method does not work. Tried it all. Autostarts, Disable Service, AppOps method (Carbon ROM AppOps is different than the one in Cyanogenmod 11) Nothing worked. Then I got Script Manager, and created a script. There are threads all over XDA about this.
[General Topics] v7:
It may not work for you but for others including me :thumbup:

Tapped from my furious ZR ;)
[General Topics] ocd_amp:
If your ROM does not have init.d support, the best thing you guys can do is make a Script that autoruns on boot.

The problem is, CM 11 devs decided it was a good idea to stop Google Play Services auto update. So Google decided to Nuke CM and Any other ROM that attempts to stop Google's systemupdateservice

Google wants to kill off Custom ROM development and are heading towards an Apple like Walled garden type approach.

If Google were buying us free batteries and free electricity I wouldn't have so much of a problem with this but this particular incident has made me extremely furious. I am sure others feel my sentiment, so I apologize if it seemed like I was renouncing your method. I am not. Anything anyone does to help each other here is very much appreciated.

Let's try to find out Exactly HOW Cm based roms disable the systemupdateservice in the first place so that we can stop it from happening at boot rather than "RE-Enabling" this service using Script Manager or any other extra stuff. Thanks Vaisakh!

Forgot to include the thread I got it from, so credit goes to him and many others like him - So far it is working, but please do try the EASIEST methods first and if everything works, leave it alone. Note, this does not just apply to Carbon ROM, but any Cyanogenmod 11 based ROM. AFAIK CM has fixed this in CM12.

http://xdaforums.com/optimus-l9/general/carbonrom-wakelock-systemupdateservice-t3059218
[General Topics] NetBender:
The method worked for a week until today. Have you found another way?
[General Topics] v7:
I can't figure out how this wakelock is returning after applying my fix.The fact is that after applying the fix I've never seen a trace of the wakelock not even after turning off filter stats in BBS.As long as my phone gets to sleep,I won't find another solution.My fix works for me(maybe I'm lucky) :rolleyes:

Here's the dump I pulled out today.
[General Topics] ocd_amp:
So here's the real question...

WHERE is this Code within the CM and CM based ROMS that disables SystemUpdateService at boot?
[General Topics] v7:
The commit says that they fixed it for CM12.But still there are people suffering from the wakelock.BTW I don't know about CM11.

Tapped from my furious ZR ;)
[General Topics] IronTechmonkey:
CM11 has not been patched for this wakelock but the following fix has remained effective.

[EDIT - correcting a few items below]

Privacy

Privacy Guard

Google Play services

Wake up - denied

Keep awake - denied

Auto start - denied

CM11 2/16/15 nightly Moto Atrix HD (MB886) with no other utilities managing services.
[General Topics] eranyanay:
Does it require xposed? Can I run it on mokee (cm11 based) with ART?

isnt there any alternative way?
[General Topics] v7:
Does your rom have an inbuilt privacy manager? If so,then that'll do.

Edit :Sorry wrong quote.

You can't install Xposed on KK ART :(

Tapped from my furious ZR ;)
[General Topics] eranyanay:
Yes, I have Privacy Guard, Can I just go to "Phone" and cancel "Wake up" & "Keep Awake" without causing any dangerous behavior with phone calls (while asleep maybe and dialer needs to wakeup phone and show the call activity?) ?
[General Topics] v7:
Read post above your's.

Tapped from my furious ZR ;)
[General Topics] eranyanay:
I see it, I couldnt understand if privacy guard with "Allow wakeup" & "Keep awake" disabled in "Phone" app is enough to reduce RILJ, and if its not causing any weird behavior with incoming calls?

Because the only alternative ive got is to switch to dalvik & install xposed & amplify
[General Topics] v7:
I think you should go with the latter option.

Turning off Keep Awake and Wakeup in "Phone" may cause issues.Switch to Dalvik and try my fix.

Tapped from my furious ZR ;)
[General Topics] ocd_amp:
I think the best method would be to find out if we can get that CM patch and patch it into our ROMS. As far as I know, Custom ROMS Disable systemupdateservice, but, with Script Manager and the script to enable it, seems to put the phone into sleep. I do not know about RIL interface wake locks but from what I have noticed, it stays at 1-2%. So as long as Google Services is allowed to do its thing, it seems to be alright, and the phone goes into Deep Sleep. So the Script Manager method has worked. However, the fact that we have to install a third party program just to run a 1 line script, seems like an awful waste of resource and just another program having to start with the ROM.

I re-iterate that we need to find exactly WHERE in the ROM does SystemUpdateService gets disabled, and enable that. I believe it is in one of the JAR but I could be wrong, since Google Update still works even when SystemUpdateService is disabled. Proof being I flashed an older backup but GMS Core got updated even with the service disabled.
[General Topics] NetBender:
I'm on Liquidsmooth 3.2 (last updated in November) so this may also be a ROM issue (in my case).

I resolved with the first method described here: OnePlus Forum.
[General Topics] ocd_amp:
NetBender: I used Script Manager and a 1 line script. So this program starts with the ROM and runs the a few seconds later. Its not the most efficient way but so far it works. CM is not interested in patching this and None of the ROMS based on CM11 have released any patch for us. The problem is Google wants control, and these ROMS tried to bypass it without allowing the user to have any input in whether they want this or not.

So we are all still searching for THE best solution, and so far everything else is just a band aid. Install this, install that...Really not efficient. My CM11 seems to works with the AppOps method. But CarbonROM does not.
[General Topics] NetBender:
I'm using the first method at the moment.

When i'll find a few spare minutes, i'll try the second one so i can disable once for all the ongoing Tasker service (it's only 10MB but my Galaxy Nexus needs all the RAM that i can give to it).
[General Topics] ocd_amp:
Update: Problem solved

Everyone please go here and thank him. He has eliminated Wake Locks from Google Play Services.

http://xdaforums.com/oneplus-one/themes-apps/mod-google-play-services-update-wake-t3078082

This solves the problem. Make sure to Force Stop, Delete Data, then Flash this, Wipe Dalvik/Data

Scripts, Extra Programs, Xpose, etc, Not needed anymore.
[General Topics] DeadlyByNite:
Yes! Finally a fix worth my while! Thanks a million!
[General Topics] ocd_amp:
Anytime. That's why we are all here. Pass it forward.
[General Topics] MrPofkis:
I dont know how to use privacy guard. I cant such options. I use AICP release 7 on i9100 (kit kat). Any guidance?
[General Topics] v7:
Try AppOpsXposed
[General Topics] twiztid_:
Disabling the receivers works, until I reboot. The receiver stays disabled, but the drain comes back. I have to ENable then re-disable the Secret Code -> Google Play Services receiver to stop it from draining again. I have tried clearing Dalvik cache, and it doesn't help.

I'm on CarbonROM (Android 4.4.4) for the Infuse4G, using the last Paranoid Android GApps.

I tried the modded Play Services from here, but it didn't seem to work and I think actually upped my drain if I didn't enable/disable the service manually. The modded Framework caused a bootloop, but I may have done something wrong there.
[General Topics] IronTechmonkey:
Assuming Carbon has the same Privacy Guard as CM, have you tried this. this:

Settings - Privacy - Privacy Guard - Google Play Service (long press) - disable "Wake", "Keep awake" and "Auto start"
[General Topics] twiztid_:
Yeah, I've tried that for Google Play Services, Play Store, and Services Framework, but there is no "Wake" and "Auto start" options on any of them. I tried AppOpsXposed as well, but all it did was give me a headache trying to remove it (Actually, apparently I STILL haven't removed it completely, the long press page still lists it as App Ops). All the available options were the same under App Ops as they were in Privacy Guard.

Thanks for the reply.
[General Topics] IronTechmonkey:
That the Google Play Services does not have those items in privacy guard is anomalous.
[General Topics] v7:
I'm running GPS 7.3.29.No wakelock issues.It seems that they fixed the issue.

Tapped from my furious Dogo ;)
[General Topics] twiztid_:
I was thinking about switching from CarbonROM to either stock CM11 or Beanstalk. Will probably do that tomorrow, thanks for the info.
[General Topics] ocd_amp:
I can confirm that CarbonROM App Ops / Privacy Guard does NOT have the same functionality as CM11. Infact it seems it is more limited. Is there a way to get the same App Ops into CarbonROM? There is only "Keep Awake" option. Nothing else.
[General Topics] twiztid_:
Switched to Beanstalk on my phone, wakelocks are gone without even going into Privacy Guard. Thanks again for the help!
[General Topics] ocd_amp:
That's because the problem is in Cyanogenmod's implementation of their Framework which disables Google's update service altogether but it does not stop Google Play Services form updating - You can download Calkulin's 030 and wait for a while, you will see that it will auto update to 034+ after a while, returning the WakeLock issue. I have since fixed the problem at the root thanks to Calkulin. No more Wakelock, and SystemUpdateService is fully active! :)
[General Topics] twiztid_:
Problem does not exist on the two other builds I've used on my phone, Unofficial CM11 and Beanstalk (built off CM11), both are older than Carbon, Android 4.4.2 vs 4.4.4. Howver, I did not notice the wakelock on my Nook when I ran official CM11 stables and nightlies.
[General Topics] v7:
I only had the issue on one of the Unofficial CM 12 build.I've used CM 12.1,RR and now the on PAC builds.No issues so far.No fixes needed.

Tapped from my furious Dogo ;)
[General Topics] ocd_amp:
I have modded the Framework-Res for CM11 KitKat and I am testing it now, if it goes well, I will Mod Carbon's Framework and pass it on to their Dev Team and fix this issue once and for all for EVERYONE!
[General Topics] IronTechmonkey:
Cant really blame CM just because CM11 dev stopped before this wakelock became prevalent. It was addressed in the CM12/CM12.1 version which are still being developed and in CM11 it is easily managed with Privacy Guard.
[General Topics] belloni:
Hello, on autostops app, Under "Secret Code Entered" when I try to disable google play services secret code receiver but nothing happens? I grant it permission but it just spins then doesn't disable? I have a samsung so i can't install xposed either...
[General Topics] v7:
I think you meant Autostarts.

Had you disabled any of the receivers with any other app before trying this?

Tapped from my furious ZR ;)