Related
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.
Hey everyone,
I had issues with NlpWakelock and NlpCollectorWakelock on viperone 7. So, I decided to use app ops to deny Google play services the wakelock permission. My battery life was great (even though I used device only location), I only got around 5-8% wakelock time (as opposed to ~26%) and seemingly nothing was broken, including push notifications. Until I tried using maps. I couldn't get my location, no matter what I did, including reset app ops. So, I went to 4.4.3 stock, thinking location may have been broken on viper. Location worked, but the nlp wakelocks were back. So, I tried using app ops from play store, and even xposed app ops. Even wakelock terminator couldn't stop the Nlps. I came back to viper 7.0.1 with a fresh flash, and now location is back, but the nlp is too! Using my old settings doesn't help.
Is anyone else having issues with nlp wakelocks? How did you manage to fix them on viper one?
Thanks,
sauprankul
sauprankul said:
Hey everyone,
I had issues with NlpWakelock and NlpCollectorWakelock on viperone 7. So, I decided to use app ops to deny Google play services the wakelock permission. My battery life was great (even though I used device only location), I only got around 5-8% wakelock time (as opposed to ~26%) and seemingly nothing was broken, including push notifications. Until I tried using maps. I couldn't get my location, no matter what I did, including reset app ops. So, I went to 4.4.3 stock, thinking location may have been broken on viper. Location worked, but the nlp wakelocks were back. So, I tried using app ops from play store, and even xposed app ops. Even wakelock terminator couldn't stop the Nlps. I came back to viper 7.0.1 with a fresh flash, and now location is back, but the nlp is too! Using my old settings doesn't help.
Is anyone else having issues with nlp wakelocks? How did you manage to fix them on viper one?
Thanks,
sauprankul
Click to expand...
Click to collapse
Did you ever find a solution to this? I am going through something similar right now:
http://forum.xda-developers.com/nexus-6/general/stopping-nlpwakelock-t3039678
seh6183 said:
Did you ever find a solution to this? I am going through something similar right now:
http://forum.xda-developers.com/nexus-6/general/stopping-nlpwakelock-t3039678
Click to expand...
Click to collapse
amplify. It's an xposed module. It stops the NLPs, but idk what the side effects are.
Hi guys, so I've been experiencing a massive battery drain coming from Android OS (kernel?)
Does anyone else have this problem? The process takes up nearly half of all battery usage, but GSam shows no large wakelocks.
I have tried reboots and disabling system processes to no avail, help!
EDIT : I just found the solution.
The battery drain was caused by an outdated google play, I was able to fix it by updating google play to the latest version (5.0.38) and then restarting the phone.
The apk can be found on the website APKMirror
Redliquid512 said:
Hi guys, so I've been experiencing a massive battery drain coming from Android OS (kernel?)
Does anyone else have this problem? The process takes up nearly half of all battery usage, but GSam shows no large wakelocks.
I have tried reboots and disabling system processes to no avail, help!
Click to expand...
Click to collapse
it's the wifi.. turn off the google location settings in wifi advanced settings...it'll resolve itself
ManiacShri said:
it's the wifi.. turn off the google location settings in wifi advanced settings...it'll resolve itself
Click to expand...
Click to collapse
I tried doing as you said this morning, but the problem continues to persist.
There is one person with the same issue under the general OTA lollipop thread.
Do you think the moto features may be causing the battery drain?
I have a similar issue on KitKat, Android OS is draining a lot. I'm trying to figure out how to update Google play or Google play services but can't find any updates in play store. Any ideas? Location is off.
neocryte said:
I have a similar issue on KitKat, Android OS is draining a lot. I'm trying to figure out how to update Google play or Google play services but can't find any updates in play store. Any ideas? Location is off.
Click to expand...
Click to collapse
you have to google "google play apk"
the latest version at the time of this post is 5.0.38
just download the apk onto your phone and install it
Thanks - that same one will work for KitKat though?
neocryte said:
Thanks - that same one will work for KitKat though?
Click to expand...
Click to collapse
In the play store, open settings and click on the build version, it should check and update tot the latest.
Mine seems to be the latest. 6.1
Redliquid512 said:
I tried doing as you said this morning, but the problem continues to persist.
There is one person with the same issue under the general OTA lollipop thread.
Do you think the moto features may be causing the battery drain?
Click to expand...
Click to collapse
that one person on the OTA thread was me But yeah, for me just disabling location under wifi advanced solved it....
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Haven't run into that but I'm having issues with random sleep of death and random reboots. Stock unrooted here as well. I've already done a cache clear and that seemed to work for about 24 hours but I just had another SOD.
Sent from my SAMSUNG-SM-G900A using XDA Free mobile app
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
I been having the same problem
lathamc said:
Does anyone know how to fix an issue where the screen never locks? It just shows the last app when the phone wakes up about half the time.
I have a Galaxy S5 unrooted and stock.
Click to expand...
Click to collapse
mcnaught82 said:
I been having the same problem
Click to expand...
Click to collapse
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
amazingasian said:
In settings, go to lockscreen > Secured Lock Time > Instantly. Thats how I fixed it.
Click to expand...
Click to collapse
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
mcnaught82 said:
That doesn't fix the problem. I adjusted that setting as soon as I did the upgrade. It's a lollipop issue.
Click to expand...
Click to collapse
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
lathamc said:
Was this listed under 'Lock screen'? I checked where the amazingasian stated, and couldn't find the option. That being said, it doesn't seem to be consistent enough to be a setting.
Click to expand...
Click to collapse
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
mcnaught82 said:
Yes it's under lockscreen. To be able to see the setting, 1st u must select a lock screen type, not the regular swype screen. Then go back to the lock screen setting and the option will be available. But lime I said, doing that doesn't fix this issue. Yesterday I turned my screen on and off 3 times just to get it to lock.
Click to expand...
Click to collapse
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
cmerlyn said:
Have you tried a lock screen from Play Store? That might solve the problem. I'm using Hi Locker currently, with no problems at all.
Click to expand...
Click to collapse
I haven't tried it, mostly because I actually like the look of the lock screen and its integration with the rest of the OS. I think it is more of a problem with the OS not recognizing that the screen has been turned off. Therefore, I think it is a problem that would affect all lock screens.
Could it be an issue with Smart Lock? I do have a smart device set up (the Sync system in my car), but the locking isn't being consistent in my car.
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
CAG-man said:
I am having an issue where the Samsung Keyboard crashes when used with some apps. Notably Facebook messenger. Anyone else notice this? Also, on occasion when opening the stock SMS app after unlocking the device, it automatically opens the bottom most conversation. I've cleared both data and caches for the apps. I am fresh install rooted lollipop the day it came out.
Click to expand...
Click to collapse
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
muniz_ri said:
Try my new revised rooted 5.0 process which uses FlashFire. Much more accurate in regard to permissions and contexts.
Click to expand...
Click to collapse
Will do, I have been so busy lately, I did not even notice. Thank you.
my lollipop problems
Stock s5 with lollipop AT&T. Since update and even after cache clearing, I am suffering from extremely slow charging, too fast battery drain. Occasional sluggishness, and occasionally notifications don't work until phone unlocked.
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
This makes me wonder then, because I was a fresh install with the original method Muniz had up. I only TiBu restored a few apps (none affected by my keyboard issue) and let everything else stay fresh. I am going to try the new method for the reasons Muniz pointed out to my prior post that listed the issues I had.
SoCalHTCFuze said:
I used muniz_ri's flash fire method keeping root which installs fresh and lollipop works flawlessly with no bugs, nothing broken. After install, google reinstalls your apps which many rediscover their stored settings on the internal sd. Most lollipop issues seem to be related to the stock update method or manual tibu restore... muniz fresh install lollipop is solid.
Click to expand...
Click to collapse
Totally agree. I also used the FF method and I have no problems what so ever with my phone. @muniz_ri came through again. Thanks.
Sent from my SAMSUNG-SM-G900A
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
simms22 said:
you just in reality not really said nor showed us your problem. ok, battery drain.. i have that. my battery drains when i use my phone.. understand? give us some more info, screenshots, etc.
Click to expand...
Click to collapse
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
StykerB said:
Looks similar to an issue I had, turned out it was an issue that Google play services was having trouble with system update feature. It started when I switch from stock to Pure Nexus rom the rom, and many others, does something to disable the update button in the settings app but in some cases Google Play Services holds a wakelock for it for some reason or another. The way I fixed it was wiping Google play services and uninstalling its updates and letting it start fresh. Also if you have the app "GasBuddy" installed it causes a bluetooth wakelock, it only shows up in kernel wakelocks as "bluesleep," looking for beacons at gas stations to send you ads.
Click to expand...
Click to collapse
Thanks for the tip. No Gasbuddy installed. A few weeks back I had FiveStars installed (a purchasing points app) and it caused a huge Bluetooth wakelock. But that was removed a while ago and didn't affect Google Play Services.
MrBrady said:
Of course - details are always better! Here are some screenshots. I just re-installed the system yesterday (from N release 3 to TuPac's Lite 6.0.1 ROM). Charged overnight and listened to a few minutes of music this morning. The rest of the time the phone has been idle.
Click to expand...
Click to collapse
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
simms22 said:
looks like its google play services updating itself or something. that happens every once in a while. best thing to do is to leave it alone for a day or two and it should "fix" itself after. but in a day or two, check your battery again just to make sure.
Click to expand...
Click to collapse
Yeah, I think you're right.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
Since receiving the 9.0.83 update I have massive battery drain. Anyone else notice this?
Click to expand...
Click to collapse
There is an app in the playstore called 'Disable services.
You can disable the services you don't use/need.
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
MrBrady said:
In case anyone has this same issue, I think I found the problem and solution. The latest version of Google Play Services causes a massive wakelock on ROMs that are blocking system update checks.
Using the DisableService app I enabled the update service and the wakelock has disappeared.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
kornball said:
I've noticed the GPS wakelock using GPS on my N5, my wife's N5X, and a buddy's 6P as well. Did you enable systemupdateservice in only Google Play Services or both GPS and Google Services Framework? Both were disabled for me... Thanks in advance!
Click to expand...
Click to collapse
Just Google Play Services. I didn't think of looking in GS Framework.
Sent from my Nexus 6 using XDA Labs