Related
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
[edit Jul-1-2014]
New Google Play Services 5.0 is now out, and its APK can be downloaded and installed just by searching for it in Google. It's reported to cure the problem for some, temporarily or permanently. It's recommended to try it first, before going with the suggestion below.
[previous post contents starting here]
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
[edit Jul-13-2014]
The fix might stick for some, and some will find the battery drain coming back after several days. I'm over a month with it, and everything is still fine. However, the results are mixed.
Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
What needs to be done:
1. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
2. Press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the app page, it's listed as disabled and has 0kB data usage.
3. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
4. Reboot the phone. You should see no crashes at this point.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that this works, I didn't even clear data.Just disabled android device manager, uninstall google play services, enabled android device manager, re-install play services and finally reboot
Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.
I have just tried that thing you posted, will see how the results are in a few days.
One thing I noticed after upgrading to KK is night time for about 8 hours the battery drains 10% while in JB 4.3 it drains about 20% or more.
But the usage draining is similar to JB in KK. Will see if this thing works. Don't like to go to barebones CM11 cause I will be missing on the many features of the phone.
Let's see
It s working here too!
At first, I didn't even thought I had a problem but I looked in the processes and saw this f... Google service running.
Now my batterie last even better than when I was on 4.3.
Thanks
Jack_R1 said:
Thank you, I completely forgot about Android Device Manager blocking the app disable. With your permission, I'll update the instructions.
Click to expand...
Click to collapse
No Problem. I found out that this method only works as long as you don't reboot the phone after the fix, otherwise you'll need to do the whole process again. Mine went well until I waited till my battery was fully discharged before charging, hence forcing a reboot which play services started misbehaving again
I just realized a new battery drain problem, the Xperia social services keeps draining my problem
grim_ripper said:
I just realized a new battery drain problem, the Xperia social services keeps draining my problem
Click to expand...
Click to collapse
Oh yes, I have all these disabled. Perhaps this is why I had to restart the phone a couple of times already (changing SIM cards back and forth), and the original Google Services problem didn't come back.
Jack_R1 said:
You've probably seen a ton of complaints on the bad battery life after KitKat upgrade. Google Services is seen at 90+% in battery stats, and the battery is discharging very quickly.
Factory reset is reported to cure the problem. Many are disabling Google Location services. There's also a workaround suggested by Sony, to disable backup and interest-based ads, or uninstall the latest Google Services.
However, there's no need to resort to the above, a much "lighter" solution may work. I've attempted it on my father's ZR and it worked.
Thanks to grim_ripper for mentioning steps that I forgot.
What needs to be done:
1. Go to Settings / Security / Device Administrators, disable Android Device Manager, if enabled.
2. Go to Settings / Apps, disable Google Play Services. It'll ask you to uninstall all updates, agree to it. After disabling it, some of other phone services might crash. Don't mind it.
3. This step might not be required according to the feedback from grim_ripper, however I'll list it "just in case": press "Clear data", or "Control data usage" and then "Clear all data". Make sure that in the Google Play Services app page, it's listed as disabled and has 0kB data usage.
4. Re-enable Google Play Services. Hangouts will immediately ask for its upgrade, get into Google Play Store and upgrade it.
5. Reboot the phone. You should see no crashes at this point.
6. In case you want Android Device Manager to function - go to Settings / Security / Device Administrators and enable it.
That's it, Google Play Services battery usage will be back to normal, and battery life seems even improved over JellyBean.
Click to expand...
Click to collapse
I confirm that it works. At least for a week or so - after that the GogglePlayServices problem appeared again....
Dont helps in my case too.
At first it seems that it works, but after a day the google services are again over 75 prozent or so.
Thinking of going back to 4.3 or hoping that a fix will come soon.
Is it necessary to factory reset after update to kit kat to encounter the battery drain problem?
I had these problems and the only save cure is to disable the location services. Some times you would think a solution helps but stucked with an empty Phone suddely is a bad thing.
Sent from my C5503 using XDA Premium 4 mobile app
Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.
Lemmi1 said:
Is something known of a fix from Google for the google services?
I ask cause since yesterday evening the akku works normal in my case. Dont see the google services as first in line of accu consumption like before. Seems that everything works fine again.
Click to expand...
Click to collapse
After I disabled the location service I see the android system in the second line. And the google services almost at the bottom line. The battery usage still not very good.
Been through several reboots by now, everything enabled, location is used, the problem didn't return, on both mine and my father's phones.
The only thing worth noting is my phone configuration - not rooted, STAMINA mode disabled, Low battery mode disabled, Queue background data disabled, Location-based WiFi enabled.
Waiting patiently for the next Sony update.
OK, the method seems to be obvious.
Does it need to be repeated after every reboot?
I also do not understand why installing the latest Google Play (after removing it the way it is written here) is not bringing the problem back .
Thanks anyway.
By the looks of it, the issue might be caused by user data being present already in Google Services since before the KitKat upgrade, but this is some type of data that's not necessarily present once it's deleted. Maybe some sort of duplication / overloading of data from multiple places, and this changes the order of loading.
one word: AMAZING
after this all the lagging of UI and keyboard is removed.
I was intending to install CM11, but after this fix I think I will stay with stock ROM
Ok this worked well for a couple of days including the UI lag fix but now Play services is destroying my battery again. I'm fed up with my ZR (Bluetooth issues and all) Just ordered a Nexus 5 yay!
Sent from my C5502 using Tapatalk 2
New Google Play Services 5.0 is out, if it didn't reach you yet - you can install it. It stops the battery drain.
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.
I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Okay here's an updated seems to fix the issue......
I disabled the WiFi location settings, download clean master -- https://play.google.com/store/apps/details?id=com.cleanmaster.mguard -- and seemed to have fixed the issue so far.
Keep you posted as the day goes on.
After you updated, did you do a factory reset? If not, and before you do, what apps do you have installed? You might have an unruly app that's just constantly running. I hear Google Fit hasn't been too friendly...
Since Google services is pretty high on the usage list, it could have something to do with syncing errors or maybe problems with updating Google Play services/Play Store. Make sure you have the latest versions.
Google Play services (6.5.85) - http://www.apkmirror.com/apk/google.../google-play-services-6-5-85-1589008-438-apk/
Google Play Store (5.0.38) - http://www.apkmirror.com/apk/google-inc/google-play-store/
Also, unsync any services in your Google account that you aren't using.
Don't forget to turn off extraneous radios like WiFi (if you don't use it for location), GPS, NFC, and Bluetooth when you're not using them.
If all else fails, factory reset and pay attention to the apps that are being downloaded. Uninstall garbage and disable what you can't uninstall, but don't use. Hopefully this helps.
EDIT: Seems you fixed it. Nice! Well, use this as a reference for your next step if things don't stay behaved.
Anfeldt24 said:
I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Click to expand...
Click to collapse
Clear cache and reboot. If you still have the problem, do a factory reset. Also, has the phone stabilized? Have you been through a couple of charge/use cycles? There could be a load of background processes setting up for the first day or so.
Seems the Qualcomm battery guru is a culprit as is the xfinity WiFi app.
Motorola said do a factory reset but I don't want to if something else can be done.
Think it's fixed by the WiFi location and the clean matter app showing the apps that kill the battery.
Here is a great article about asps that keep restarting in lollipop. It's a bug in ART. Google is working on a fix.
http://www.androidpit.com/android-5-0-lollipop-bug-apps-frequently-restart-in-background
Another great way to help save battery. http://www.androidpit.com/android-5-0-lollipop-problems-and-solutions
Best method... Root and use greenify...
Sent from my XT1092 using XDA Free mobile app
I'll post my battery drain/overheating story just to join the fray...i updated to Lollipop 4 days ago and I have had to charge my S5 at least a dozen times. I have tried power save mode, disabling every nonessential app and anything else I can find in the forums.
I used to get 15-16hrs of battery life (6am-10pm) with charge to spare, but immediately after the update my CPU sits maxed (monitored by Micro CPU Monitor) and constantly overheats (GSAM Battery Monitor). The phone went from 95°F to 105°F in 10min with standard use. I only had it overheat one other time in the last year (on my dash in the summer). I hope Google/Verizon will replace my battery because this abuse of it is going to shorten the life considerably!
See screen shots from the last charge at 4pm to now (10:15pm) all while UNUSED and in powersave mode plus battery at 107°F (a new record for me)!
I really don't want to reset the phone and lose my app settings, plus it seems to be hit/miss with other's issues. Any suggestions would be great.
Seems hit or miss.
Not sure what to tell you but try making sure you're Wi-Fi isn't always searching for locations when not connected. Seems this is a huge problem for many as Verizon threads and Android forums are filling up. I don't have an S5 but will keep looking for the fix.
Quick read-
http://www.gottabemobile.com/2015/02/09/verizon-galaxy-s5-lollipop-update/ many are having this issue but not all.
Posted from my Moto X 2014
i am facing similar problem with my moto g2 if you find any solution please let me now
same problem to me also friend if u found any solution for it please mail to me [email protected]
After the EMUI 9.1 update if the phone is on screen lock for more than about 5 minutes, when we use the fingerprint reader to unlock the phone it plays the Notification Sound.
It never happened on 8.x or 9.0 and the sound really gives my wife the ****s (it's her phone).
I contacted Huawei support but as usual they were useless, gave me some settings to change (Settings/Sound/More Sound/Disable Screen Lock). It was already set to Disable, and always has been.
Their next suggestion was to do a reset of phone settings, that did nothing. So their final suggestion was a Factory Reset which "may help remove any software bug causing this issue". Really, resetting might remove bugs?
Has any else had this problem and managed to find a way to fix it without doing a factory reset?
I would bet it comes from an app (or apps) that is put to sleep/hibernated by the battery optimizer and throws suspended notifications once the phone is unlocked. Something in the "Apps -> Battery optimization" or "Battery -> App launch" or even "Battery -> More battery settings -> Stay connected when device sleeps" settings. You can also try and assign different notification sounds to different apps just for the fun of it, and check what exactly triggers that notification on unlock.
arty_a said:
I would bet it comes from an app (or apps) that is put to sleep/hibernated by the battery optimizer and throws suspended notifications once the phone is unlocked. Something in the "Apps -> Battery optimization" or "Battery -> App launch" or even "Battery -> More battery settings -> Stay connected when device sleeps" settings. You can also try and assign different notification sounds to different apps just for the fun of it, and check what exactly triggers that notification on unlock.
Click to expand...
Click to collapse
Thanks for your suggestions arty_a, I'll dig around to see if I can find anything like this.
There was a thread on the UK Huawei Community pages relating to this but it was shut down just after I found it and sent the info to Huawei support, so that avenue closed.
Worst case scenario is I actually do a factory reset; I grabbed the Bootloader Unlock code from the Huawei site before it shut down but she hasn't felt the need for the phone to be rooted, so I've held off. I'd rather solve this by finding out what the cause is, than do a full wipe and if it is caused by an app, find it come back after they are all reloaded. As there are a lot, having to do each one separately and wait 5min to unlock and learn if it's the culprit is too tedious for words!
Will update here if I learn anything useful ...
Well the hint from arty_a got me on my way. I disabled all the Battery Optimised apps but that didn't help, however I noticed after a noisy unlocking there was a notification ... turns out 9.1 was complaining about the GPS not being on for Location Services. As to why it doesn't always do it is anyone's guess (especially Huawei's).
Blocking the notification for this seems to have ended the problem, finally.
We have always been in the habit of keeping GPS off until we need it, a carry over from owning HTC Desires way back when GPS ate battery like crazy. OK not so bad on the P20 Pro, and never an issue until the 9.1 updates.
Thank you arty_a for pointing me in the right direction!
Glad to help, and thanks for posting your full solution, it might help someone in the future.
arty_a said:
Glad to help, and thanks for posting your full solution, it might help someone in the future.
Click to expand...
Click to collapse
That's what I like about the spirit of XDA ... a community that helps the community; glad to have participated and learned something in the process.
It's been nearly a month now and not one instance of the unlock sound so she is thrilled. One of the consequences of the damned sound was she'd often put the phone on silent. Of course when I phoned she didn't know, causing many a heated exchange.
Problem solved, marriage saved! :laugh:
Now just waiting on the OnePlus 8 launch to replace my S5, not long ...
Hello everyone, I'm just curious to know if anyone knows how to fix this issue: when I unplug my phone and shut the screen off right after, my phone simply freezes in the state that its in. I know its frozen because if I have my flashlight on it stays on and nothing responds (touches, buttons, fingerpring sensor, etc), but it will not freeze if I have music playing for some reason and the only way to get access to my phone again is to forcefully restarting it (by holding down power for about 10s, which is really annoying). If anyone can help me with this I would really apreciate it. Ps: my phone is a Moto G6 (ali). I know that doing a factory reset fixes it, but right after I re root it and install my apps it starts doing it again. Below is a screenshot with all my root apps.
IuriP said:
Hello everyone, I'm just curious to know if anyone knows how to fix this issue: when I unplug my phone and shut the screen off right after, my phone simply freezes in the state that its in. I know its frozen because if I have my flashlight on it stays on and nothing responds (touches, buttons, fingerpring sensor, etc), but it will not freeze if I have music playing for some reason and the only way to get access to my phone again is to forcefully restarting it (by holding down power for about 10s, which is really annoying). If anyone can help me with this I would really apreciate it. Ps: my phone is a Moto G6 (ali). I know that doing a factory reset fixes it, but right after I re root it and install my apps it starts doing it again. Below is a screenshot with all my root apps.
Click to expand...
Click to collapse
I have this exact same problem. I have 2 moto's. It occurs on both of them. Never happened till I rooted.
You should disable all of those apps ( especially substratum) and see if the problem still happens. Then if it doesn't, activate one by one till it happens again. Then with the culprit found, look in internet if it has any conflicts to another app you have installed. If you find maybe they have like a patch to download or a modified version. If not you'll have to let one of them go. Or maybe there's no conflict with any other app and it's just that one misbehaving. Disable all other apps and let only the culprit activated. Does it still bug? you can try reinstalling the app or uninstalling it.