Some days ago I had some problems with vibration, which stopped working for notifications. I installed an application called "Sound Manager" and was able to solve that issue. Now, I find my phone to be extremely slow on some things. For example, grabbing and dragging the notifications panel takes something like 5 or 7 seconds, and the "settings" button (the virtual button left of the Home button) also takes a lot to respond. OS Monitor tells me that "/system/bin/immvibed" is taking a whole 98% of CPU load. I don't know if this two things are related, but from the process's name, i suspect it has something to do with vibration settings (I cannot find any useful information online about such service). Annoyingly, I can't kill it, because it comes back to life immediately.
Is there something I can do? What does this process do?
Any help is appreciated
Solved
Apparently, all I needed do was a system restart!! Funny I failed to think about that before... Now the process is using no CPU resources. I still wonder what triggered it into that strange "all your CPU are belong to us" mode, though.
Anyway, problem solved.
Some crazy continuous loop most likely.
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 looked for other threads in which someone else faced the same problem, but I have not found any answer nor good solution.
The problem is that the screen of my S3 MINI turns on automatically.
I changed the ROM twice (2 different ones, CM 10 and 11), so I don't think the reason is a single "defective" app: I believe in another explanation, according to which the reason would be a broken pin inside the microUSB port of the smartphone.
That pin let turn the screen on like if it was put /unput in charge.
The Question: is there a ROM / KERNEL / APP that prevent the screen from making this error?
How much is hard to edit a rom/kernel in order to avoid that the screen lightness wolud depend from that pins?
And if the reason is a defective app, has someone ever discovered which one is?
I'm afraid it's a way to screw the consumer: this automatic and uncontrollable activity of the display destroys the battery life. It's like if the smartphone is broken: you should change it.
I cannot accept that a 440€ smartphone acts in this way. I'll never buy a Samsung product.
I won't talk about the home button broken (could someone give me an advice on which app that simulates the virtual buttons is better?).
Thank to you all!
Pietro C.
UPDATE 28/12/2014 h14:34 ITA
I did a screenshot and I also photographed with a camera the display while it was showing the CPU activity. I noticed something (an app? a opened file? a function?) that appears only when the display turns on automatically. Some green words. I'm going to upload photos.
UPDATE 16:30
Cannot upload photos. Here are the scripts that appears on my phone:
com.android.system
surfaceflinger
system_server
com.teslacoilsw.launcher
kworker/u4
com.android.phone
com.facebook.katana
com.facebook.orca
kworker/2
kworker/6
kworker/1
irq/72...
irq/474
mmcqd
ueventd
rild
mediaserver
admsrv
org.cyanogenmod.voiceplus
dhd_dpc
com.google.processo.location
org.whispersystems.whisperpush
com.textra
com.google.android.googlequicksearchbox.search
AND the last 5 listed down here are the green scripts that appears only when the phone turns on automatically.
migration/I
kworker/I:0
ksoftirqd/I
watchdog/I
kworker/I:I
UPDATE 03.01.2015
I fixed the issue at the moment. I installed CM 11-20140823 after wiping and formatting data.
I installed the lowest number of Google Apps (here I chose Nano Modular Package: http://forum.xda-developers.com/showthread.php?p=44417509#post44417509 ).
I'm quite sure it's a issue caused by a unidentified google app, because when the phone was "clean", the screen kept turned off ALWAYS, unless I pressed the accension button.
Now that I installed ONLY Google Play and Google Services, the screen is ok.
So I will download only the most useful Google Apps, hoping that won't find the one infected (if I'm right about the cause of the automatic flash of the screen).
I also discussed about this issue here , and I discovered that many people are searching for a solution.
Maybe someone could confirm or contradict my theory.
I seem to have been bitten by whatever it is that's causing Note 8s to freeze. In my case, it seems to freeze when idle - case closed, always-on display showing a clock. Sometimes the digital clock - just stopped; the last time, the analog clock with the second hand ticking, but an otherwise unresponsive phone.
It seems like this is happening to other people, in a variety of other applications - and the only advice anybody is giving is to see what happens in safe mode, then uninstall applications one-by-one. All of which seems rather time-consuming, and counter-intuitive -- if a single App is freezing the system, that suggests on o/s or hardware issue -- the o/s should be isolating the rest of the system from app misbehavior.
Which leads me to wonder how one might track down what's actually going on. If this were one of our servers, I'd crank up logging and look at crash logs. But... those options don't seem to be available without rooting the phone. (Why does Google insist on making syslogs unreadable by normal users - that puts a big crimp in the ability to do any kind of real trouble diagnosis.)
Any suggestions on how to do crash analysis? Any tools that someone can recommend?
Any insight on the matter?
I have not had this problem, so I would not know how to tackle all down to pinpoint the exact culprit, but I would start by controling what apps I dont want to run in background, in maintenance>battery>always sleeping, I put all the apps I dont need to be in always running state, I would also try to unistall or freeze apps I installed just before the problem began, if you have bk disabler this is a rather easy process, as you can batch-disable/enable apps, in the end it is a trial-error exercise
You can use logcat extreme, Catlog or somthing similiar from playstore. But you need some knowless to see wat happend and root. Perhaps you can pull the log file without root to your computer with ADB.
Sounds like impending motherboard failure. My wife's S7 Edge started doing the same thing then one day it just wouldn't start up at all.
Common thing for Samsung phones unfortunately .... and if you're out of warranty they won't repair without a charge.