Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
keeekeeess said:
Hi all,
I just installed cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip and I have a big problem with SystemUpdateService which is always on and draining my battery. The phone will not go in deep sleep, it will just stay awake.
I tried all of the following:
1. Installed Disable Service and went on to disable SystemUpdateService, but it was already disabled.
2. Installed Autorun Manager and went on to disable com.google.android.gsf.update.SystemUpdateService$Receiver. but it was already disabled
3. I copied FOTAkill.apk in the System folder with RS Root Explorer and restarted, but the problem kept persisting
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Does anybody know what else I could do?
Click to expand...
Click to collapse
I installed (cm-11-20140609-SNAPSHOT-M7-galaxysmtd.zip) on my device
and i am not found this problem?
try wakelock detector to see what's keeping it awake http://forum.xda-developers.com/showthread.php?t=2179651
Starting today, I got this issue as well on a Nexus 4 device running the M7 snapshot with hellscore kernel. The first 2 steps you took didn't work for me too. Didn't know about #3 this far.
keeekeeess said:
The only way to stop is is to disable GoogleServiceFramework, which will cause my phone to display the "unfortunatelly google play has stopped" error now and then, which is annoying and just a crude fix to the problem.
Click to expand...
Click to collapse
Doesn't sound pretty, but how did you do this? Still better than running out of battery halfway through the day, I'd guess.
pryerlee: WLD says exactly that - Google Play Services -> SystemUpdateService, for me currently 4h23m, being 100% of the time - plus it says "x2" (what's that precisely?)
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
it is not work this servicein with lock screen!!
(i speek arabic good but english not good)
Sent from my GT-I9000 using XDA Free mobile app
pryerlee: Couldn't make anything out of those.
Just linking the other way round as well, maybe it'll help - the issue popped up on CM forums too: http ://forum.cyanogenmod. com/topic/96459-systemupdateservice-wakelock-on-cm11-m7-massive-battery-drain/
(sry for destroying the link, I'm blocked from posting it.)
pryerlee said:
not sure if this will help but read tho the post http://forum.xda-developers.com/showthread.php?t=2388243 http://forum.xda-developers.com/showthread.php?t=2378962
Click to expand...
Click to collapse
I did all of the options, the service is closed yet it was still running.
I compromised and installed Paranoid Android 4.4.2 and the problem is no more.
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?
Running CM 11 M7 Snapshot 6/9/14 msm8960 on Motorola Atrix HD MB886. Have seen something similar.
Details:
- Have not seen this issue for weeks of running this ROM until now.
- This seems to have started a few (2?) days ago after an update. Google Play Music, Maps, Search, Drive, Sheets, and Docs all received updates in the past week.
- Typically, based on the configuration and usage of my phone, when the screen on is off the phone is in Deep Sleep (percentage in high 90s).
- At some point after some app or service is run, the phone stops going into deep sleep.
- Better Battery Stats shows SystemUpdateService as having partial wakelock for about the same percentage of time that the phone should be in deep sleep (high 90s).
- SystemUpdateServices does not seem to be hogging battery even considering that it might be folded into another category, but the wakelock causes the phone to use battery more than twice as fast as in deep sleep.
- A restart clears it up until the SystemUpdateService is invoked again by... whatever... seems to be something I do manually - still chasing it.
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Silkeyway said:
IronTechmonkey,
confirming your descriptions, up to the point where you describe that a reboot clears the issue up until a certain unknown event some time after boot. This is clearly not the case for me.
Instead, I was just able to reproduce the behaviour I described above. The wakelock remained gone since my last post, then I had to reboot for another reason, and it was there again basically from the first second (100% awake time since boot). Looking into Disable Service, SystemUpdateService was unchecked / disabled - again I checked / enabled it, and the wakelock stopped immediately.
Click to expand...
Click to collapse
I've been able to consistently replicate the problem 100% by running the Google Play app when the phone has a data connection.
If I run the Google Play app when the phone has no data connection the problem does not occur until the next time the phone has a data connection, whether or not Google Play is running.
I do have all auto-updating disabled in google and elsewhere which makes this easier to chase.
See if it happens when your phone has no data connection, with apps and google things set not to autoupdate.
As for the temporary fix: Like you said: Disable Service app, System Apps list, Google Play Services, SystemUpdateService enable/disable.
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
I also had the wakelock on my P990.
systemupdateservice was disabled in gooogle service framework, but it was still active as receiver and actice receiver in google play services - disabling it there solved the wakelock for me.
Silkeyway said:
I'll try with those conditions asap. No time just now.
However, doesn't this all raise the question why SystemUpdateService is disabled? Shouldn't this default to enabled?
Or to put it differently: Is enabling SystemUpdateService a workaround, or is it being disabled the issue?
Click to expand...
Click to collapse
Now that I've tested during a work day I'm seeing the problem occur more pervasively as some of you are
- It starts any time I go on line.
- Reboot sometimes but not always fixes
- Toggling using Disable Service app no longer works reliably
- Must stop Google Services Framework to fix issue until next time I go on line
= Royal PITA!
As for your question; It is not uncommon in the world of computers (and phones) to have to toggle a setting on/off or off/on to get the setting to stick, especially when something deeper in the system is turning it on and off without a flag letting the user know.
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Silkeyway said:
... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Indeed hoping the same, and it looks like M8 and the nightly to which you refer will not yet be using the KK bootloader (great for my old Moto AtrixHD MB886 w/JB bootloader). Found that same XDA post referring to Autorun Manager which looks like a good temporary fix - working good so far. Does not hold setting through restart but still more effective than others..
I've the same issue here since 2/3 days on my 9001 running CyanogenMod 11.0 by ADC-Team - Release 8, maybe it was some app update occurred recently... I didn't have any issue with the same rom before.
---------- Post added at 10:29 AM ---------- Previous post was at 10:00 AM ----------
I can confirm that downgrading Google Play Services to version 4.3.25 is a working workaround.
http://forum.xda-developers.com/showpost.php?p=53851739&postcount=3026
Silkeyway said:
Just summarizing what was found on the CM forums where I tried to link previously:
Seemingly permanent workaround: http://forum.xda-developers.com/showpost.php?p=53739230&postcount=5031
Related fix, merged into nightly since Jun 29: http://review.cyanogenmod.org/#/c/66894/
Haven't tried that workaround, had no time to go for the nightly... hopefully the fix will already be included in the M8 stable release(?).
Click to expand...
Click to collapse
Hey everyone,
i can confirm the issue for CM11 M7 and it all started with the recent update to Google Play Services 5 v84.
The workaround mentioned before works very well until a reboot ... lets hope the best for CM11 M8!
Best workaround I've found:
"Finally I was able to block the SystemUpdateService wakelock, using this app:
https://play.google.com/store/apps/d...com.rs.autorun
go to settings, enable the option to show system entries
find google play services and disable:
SystemUpdateService$Receiver
SystemUpdateService$ActiveReceiver
SystemUpdateService$SecretCodeReceiver
done... no more wakelock and it didn't break anything, syncs all work ok
I know this app doesn't look the best, but I tried others like "Android Tuner Free", "Disable Services", "Gemini App Manager", etc, but they allowed me to only disable the main service and didn't show the other receivers that had to be disabled."
As the other user said, this is all caused by the Google Play Services update that has being rolling out this last week. The solution above is reboot proof (At least for me). Thanks to the user who posted it.
Hi, I've been trying to track down the issue with BetterBatteryStats+ and Wakelock Dectector FULL and found that the issue is with the bluetooth_pm wakelock. I've been googling about and people only mention it but nothing gets resolved. There's only one mention of it on XDA but no reply:
http://forum.xda-developers.com/showpost.php?p=63955981&postcount=29777
What makes it's annoying is that when it goes away randomly and I get to enjoy the damn Doze feature but only to have it come back randomly. And this is when bluetooth is on. I haven't not factory reset the phone and restarting the phone may or may not have temporarily fixed.
What's is the damn "bluetooth_pm" wakelock? There's not a lot of info on this wakelock and I can't use Amplify or DisableServices to reduce or get rid of outright. I hope someone has a solution this issue.
EDIT: It's a Kernel wakelock.
Sorry for bumping this again. I have still not found the reason of why it happens aside from disconnecting from my devices (I have my phone connected to my lg tone headphones, motorola headset, my car, and my android wear watch).
Is there a way to get into the kernel and just kill it manually or set a timeout setting to kill it. The only way for me to fix it is to restart my phone; I shouldn't have to restart to get rid of this annoying wakelock.
I really hope to hear a response soon. Thanks in advance.
Bumping one more time, now with logs if ANYONE is just willing to look into this and find out what's wrong: http://forum.xda-developers.com/showpost.php?p=66119017&postcount=30423
In this post attachment, it happened again just 15 minutes ago. Please, someone has to be technical to read the logs better than what I can come up to determine what's wrong with it or provide an app to find and kill this wakelock without having to restart the bloody phone.
I know this is super old but I found out that GasBuddy of all things was causing the damn bluetooth wakelock. Not a damn clue aside some saying it uses bluetooth for location but REALLY?
Luckily, using Greenify fixed the problem
I had the exact same symptoms and phone, did the same steps and found the same thing is as you. GasBuddy for some reason causing bluetooth wakelock. Greenify, as you experience, 'cured' the problem. Interestingly, after dealing with this issue for months, after only a few hours of verifying a fix, GasBuddy updated (with new logo) and while somewhat improved the wakelock issue, it's still an issue. Unfortunately, Greenify seems to have a more difficult time hibernating the new version...
This is kind of a big bump, but I'm having the bluetooth_pm wake lock on my G6 and Google doesn't show me much except for this thread. I don't have GasBuddy on my phone. Has anyone experienced the bluetooth_pm wakelock and figured out a way to get rid of it?
xPhantom said:
This is kind of a big bump, but I'm having the bluetooth_pm wake lock on my G6 and Google doesn't show me much except for this thread. I don't have GasBuddy on my phone. Has anyone experienced the bluetooth_pm wakelock and figured out a way to get rid of it?
Click to expand...
Click to collapse
I am having same issue on my Verizon g6. I lose about 10% battery per hour when screen is off. Phone wake locks through the roof.
This has been happening randomly for a few months. I can go days when notifications are fine and they come through on my phone immediately. Then, for no reason, there are days when no notification show at all until I wake my phone.
They're clearly being blocked and my phone only attempts to pull them in when I wake it. Like a doze setting
It all started around the time Marshmallow 6.01 landed on the phone.
All battery saving optimisation settings are off.
All notifications are set to on.
I have tried EVERY app that I can find to set the Google heartbeat interval to a lower time. None solve the issue.
Factory reset doesn't fix it.
I have (always on) fiber internet so idle timeout settings on the router cannot be to blame for killing the Google heartbeat check.
I have tried it on mobile data only and it is the same
Other people online have had the same issues on other Samsung devices but I can't find anyone suffering from this on the Note 5.
Could it be an issue (somehow) with my Google account, since all notifications have to be pushed through this?
Worried that if I get a new phone I'll still have the same issue.
Any help would be appreciated.
are u using greenify??? what android u have 6.0.1 ??? did u try on smart manager / battery / to not optimize app u want get notification????
N920c/64g/cc n7 port v3/ arise sound/ doulby /xposed greenify+powernap+amplify
Not got Greenify.
Not enabled any power saving at all.
All apps are set to notify
Either the phone is blocking notifications randomly, or my Google account is.
I 7se Google Maps daily on the S10. But if the screen goes off it stops giving directions and I have to hit Start again and resume. Only way it stays on is if I start the trip and physically hold the phone and not let the screen lock. Anyone else? Never had this issue with any other phone, Galaxy or otherwise.
I have the same issue. I use Automate to automatically turn AOD on and off based on received notification. I originally thought it causes this problem. Unfortunately, I can´t proove it because I needed to drive and hadn´t time to play with the phone. Just an idea to consider.
Edit: maybe it is Google maps bug. Have you tried uninstalling app updates?
Might have to do just that. But it does seems like a Maps bug, yet it was fine on my Note 8, and the iPhone X before that. So idk if it's Maps or a software bug with the S10. Normally I just tap "start" and then immediately click the lock/wake button and set the phone down and it sends the directions through the car or headset.
Verizon variant here by the way 100% stock.
Try to prevent the phone to set the Maps app to sleep. I had a similar thing with the old version of Maps (V6 which I still use).
Just search for 'Sleeping Apps' in your settings