(Qualcomm varient, I believe) [XT1768] Moto E4 - abnormal CPU, very low battery - Moto E4 Questions & Answers

I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup

TheNupster said:
I apologise in advance if this has already been discussed elsewhere, because I have been unable to find said topic if it exists.
My problem:
I have a Moto E4, bought from Republic Wireless in 2017, shortly after its launch. Up until last week, I have had no serious problems with it. This last week, however, I suddenly have had 50% reduced battery runtime, in addition to noticably slower performance.
After some quick digging, I determined that the culprit is not an app, but the OS (battery stats under settings places "Android System" around 70% of the battery's usage). I installed a CPU monitoring app, and discovered that the CPU speed was stuck at the max 1.4 GHz (it never scaled down) with an idle utilization of 25%. Although I am unable to see the utilization of each of the 4 cores, I believe one of them is running a code loop. Restarts, and cache, app cleaning have had no effect thus far.
As I have done no more digging (I am on vacation and haven't had much time), I would like to know what next steps I should take. I have not performed a factory reset, but it is one of my next options for when I return home.
I do not want to root if I don't have to, but I know how to do so if it's absolutely required.
Thank you in advance, i know this post is lengthy...
~Nup
Click to expand...
Click to collapse
A factory reset is probably the next step if you prefer not to root. Also try to identify the source with a monitoring app like BBS or GSAM (I prefer the latter). You'll need to grant a few extra permissions via ADB on an unrooted device to get the full picture. GSAM walks you through the procedure via the overflow (3 dot) menu. Good luck.

I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?

TheNupster said:
I installed GSAM, used my PC to enable permissions, and checked the app after awhile. Once again, it's showing "Android system" as the main CPU AND battery hog, at over 74.6%. I would attach a picture, if I could figure out how to do it... (Please tell me how, I feel dumb). But that's what I have done this far. When I get home, I'll work on factory resetting it.
However, I am still worried that a factory reset might not fix the problem, since it is with the Android system. If all else fails, would it be possible to reflash the OS? The phone shipped with Republic Wireless software, so I would need the ROM from them..... And I would probably have to ask them for it. But that is only if reset fails to fix my problem. Is a reflash even possible...?
Click to expand...
Click to collapse
If it's the 1768 then the retail firmware should be fine (I'd say preferable even). Unless you need that extra software that is.

After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)

TheNupster said:
After factory resetting my phone, I reinstalled everything. BUT, to my surprise, as soon as I installed Snapchat, the same problem BEGAN HAPPENING AGAIN. I used GSAM, expecting to see Snapchat this time. Yet, it still said Android System was hogging the battery.
So I uninstalled Snapchat.
Surprisingly, the problem ceased to exist.
To be sure, I reinstalled Snapchat. The problem appeared. Uninstalled, problem disappeared.
So it appears that a factory reset might not have been necessary, but I'm wondering what aspect of Snapchat was causing the core overload. Regardless, I am never using Snapchat again, until I hear word of this problem being looked into/fixed. (I did capture and send them a bug report, but that might be of no help regarding this situation)
Click to expand...
Click to collapse
Did you grant permissions (via ADB) to allow GSAM to disambiguate resource consumption on an unrooted device. Try using Greenify to rein in bad app behaviors. Works a treat on rooted devices and *should* be effective on user installed apps if unrooted.

I'll try that. And yes, despite using my laptop to give GSAM permissions, it only showed Android system as using the power. I'll install Snapchat, see if the problem appears again, open GSAM, and give it some time. I'll also install the other app and set that up too.
Between those two, I should be able to determine if Snapchat is causing this issue; and if so, what part is. (Phone is unrooted, because I don't want to void warranty (Motorola needs to give me the key to root, and I don't want to do THAT just yet) so we'll see what happens)

Okay. After extensive testing, the phone has finally "cooled down". Snapchat no longer hogs battery, and now I get more battery life than before this problem even began. I wonder if, somehow, somewhere, a system file became corrupted, instead of Snapchat causing the problem...
Whatever the cause, a full system reset forced the loop to break.
Now I'll use Snapchat (and every other app) with caution now... I have a CPU monitoring app running 24/7 (it uses almost no battery)
Feel free to close this thread

Related

[Q] Battery drain/idle/standby?

Right, no matter what, I'm getting battery drain in stand by. No sync, Google now disabled, no mail, no location reporting/history etc. and yet I'm getting weird battery readings. In the pic below you can see, I'll let it idle for a couple of hours and the battery will drain. Then I'll use the n10 and the levels will spike. BBS shows that the n10 is awake for about 4 hours but the partial wakelock and kernel wakelock nothing untoward. I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
yets said:
I'm reluctant to root as I dont want to void my warranty but is any one facing similar issues?
Click to expand...
Click to collapse
You can unroot and relock your device. Rooting should not be a warrenty issue.
See: " [NEXUS 10 TOOLKIT V1.3.0] Drivers, Backup, Unlock, Root, Flash, Mods + MUCH MORE"
http://forum.xda-developers.com/showthread.php?t=2001868&highlight=unroot
Features mentioned among many: "* Unlock/Re-Lock your Bootloader"
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
EniGmA1987 said:
You will not lose warranty just by rooting the tablet. Nexus devices are pretty much made to be unlocked and Google provides the tools themselves to do the unlocking. I have heard of other people get warranty stuff done even while their tablet was rooted. This is because warranty is for hardware defects, which are not caused by root. If you have software problems then yes, those are to do with rooting. But normally you can fix software issues simply by finding a better ROM that has more bugfixes.
Also, that is some really terrible battery life. My tablet loses 1% every 7-9 days while idle. CM10.1 ROM from CraigGomez (November build) with KTManta kernel.
Click to expand...
Click to collapse
Is it worth getting in touch with Google? I've had it since just after xmas? I'm about to factory reset it for the second time this week.
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
EniGmA1987 said:
Why do you need to factory reset it so often?
I would root it, install a custom kernel, and run better battery stats to try and see what exactly is causing such a huge idle drain.
Click to expand...
Click to collapse
I'd rather not factory restore it, this is my second time doing it. I'm starting from the beginning like it's a fresh install, just using the Google apps only to see if there are issues there and then adding more until I'm comfortable.
I want to root the tablet only as a last resort as I'm attempting to see if it is an app or it is the battery. I'd rather not brick it or void warranty only to find out it is the battery and then be unable to get a replacement.
There must be somebody that has similar problems?
So, factory reset, this is after 24 hours; This is not kosher. Stock apps. Only thing syncing if you can call it that was Google now. No syncing or anything. Purely from stock apps with updates. Stock battery graph says that it's not awake but stats say it's awake for 19 hours.This doesn't even come close to advertised idle/stand by time. Surely I should return it? I was adamant that I wouldn't complain but I didn't pay so much money for it to come out with this as stock performance.
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
EniGmA1987 said:
That is massive usage from Android OS. Something in there is causing a wakelock, which means it is probably a software problem. If you were rooted and had better battery stats installed then it would tell you exactly what the wakelock was from. The built in Android battery info just gives it a generic "Android OS". It looks to me like that sudden sharper downhill slope is the point which the wakelock started. Although that is a bit steep drain before that point too. The point before the sharper decline section looks closer to a non-deep sleeping device stuck at its lowest frequency, but it had to have been sleeping if the device says it was only awake for 14 hours. Still, that 14 hours is a wakelock. Probably from the kernel. Cant say what it is exactly unless you have a better app installed
The Google Services thing is probably Google Now sucking up battery. It tends to do that.
You can either continue to diagnose this problem from the software/firmware or you can just send it back if you want.
Click to expand...
Click to collapse
Thanks. To be fair I think if purchasing such an item, you shouldn't have to become a developer/hacker to study such an issue. Haha! I've used Google now when I first got the tablet and not understanding what it was had it enabled and get there was no battery drain to such an extent.
Fair play to Google, they've agreed to send me out a new one. It reached a point where I couldn't enjoy using the tablet and everything was a test to see what could be causing the issue.
I won't bad mouth Google, as I understand that things do become faulty and these items are complex enough. On another note I called up the RMA team in American (I googled the wrong number) and the two ladies were more than helpful. I don't know how anyone has problems with them. Maybe it was my British accent that did it!
So, I've got a replacement and so far it is not displaying the same issues. It got me thinking about when my original problem started and I think it started when it was updated to 4.2.2. This model comes stock 4.2.1 and it's prompting me to update. Should I bother? Was I just unlucky? Is there a specific way to ensure that the update is a clean update?
yets said:
... This model comes stock 4.2.1 and it's prompting me to update. Should I bother? ...
Click to expand...
Click to collapse
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
3DSammy said:
Upgrade to 4.2.2 as it's more stable, especially with the Chrome browser but there are additional bug fixes that address overall stability. A rule of thumb is to install new apps one at a time so you can judge if it causes instability.
Click to expand...
Click to collapse
Yeah, I kind of did that when I factory reset it, I just loaded up the stock apps, desynced everything, logged out of everything that wouldn't be used, disabled Google Now and location settings, rebooted and it was still iffy. Before I sent it back I left it for a day and the battery stats were going up and down like a roller coaster. Could it of been a faulty battery? I would like to update but I'm so wary of the problem coming back.
You can also install, free from the playstore, "Bootlog Uptime" which tracks crashes and sometimes provides crash related information from the Android logs. It is very handy when you are trying to determine the cause of a force close, freezing or general odd behaviour.
You may have been unlucky. I have had great battery on all 4.2.2 some ROMs/kernels make a difference.
Sent from my Nexus 10 using XDA Premium HD app
So, after a few days my new Nexus 10 started displaying exactly the same issues as before and I had just about ruled everything out. I used BBS again and looked at the stats, with PowerManagerService being the main culprit but the numbers in Partial wake locks just didn't match. There were very little wakelocks but something was still draining. I looked at the CPU and for most of the CPU was running at 200hz in deep sleep. I just couldn't figure it out and looked at the Running apps and there was only a few but one remained constant throughout all my tests and that was the Settings app. I took a punt and stopped it and cleared it from recent apps. Lo and Behold, the drain has disappeared and the battery doesn't drop at all in idle.
Excuse my noobiness, I didn't know that Android treated Settings as a separate app? On my Samsung S3, this isn't the case, once you leave settings it closes it and suspends it causing no drain.
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
EniGmA1987 said:
200MHz in deep sleep doesnt make sense. Cause deep sleep is different than a MHz value. If you are mostly on 200MHz then that means something on the tablet is not letting you sleep properly.
Click to expand...
Click to collapse
Sorry, didn't make myself clear. BBS was saying that tablet was running at 200mhz preventing it from deep sleep and that thing causing it was having the System Settings app not closing. Hope that makes sense and helps people in the future.
Well that is certainly an interesting find. If you restart the tablet and dont open settings does the tablet sleep fine?
Yes, if you restart it and avoid going into settings, it sleeps happily only waking sync if you have any. It has been idling for about 10 hours without dropping.
I've attached a picture and if you compare to the one I posted at the start of the thread you can see a clear difference. There was a point where I forgot to close Settings and you can see the drain (middle of the graph).
Somehow I don't think this is normal. It dropped almost 30% at home while I was at work. Google now is disabled but groove IP running. No apps that should be sucking battery, but its mostly the android OS. Any thoughts?
Sent from my Nexus 10 using xda app-developers app
Probably the exact same thing as the guy above me. Doesnt look like you are deep sleeping one bit.

[Q] Please help me find the cause of battery drain

My phone's battery has been sucked dry way too fast since ~may 25.
I am and have always been on stock rom, and I only rooted the phone this weekend in order to use BetterBatteryStats and Wakelock Detector.
I estimate that during a day of heavy use for me before the end of may, the battery usage cannot have been much above 5%/h
According to BBS the phone used 6.4%/h over 7h30m this morning with less than a minute of screen on-time.
None of these things have helped significantly:
Disabling automatic syncing
Setting location mode to "device only"
Uninstalling EVERY third-party app except these most essential: Authy, Barcode Scanner, BetterBatteryStats, Dropbox, DSB Wildcard, LastPass, Sleep as Android (and addons), SuperSU.
Factory reset
*Upgrading to Android 4.4.3
Disabling WiFi to see if that would make a difference
Disabling mobile network data
Using recovery mode to wipe cache
My conclusions (please correct me if i'm wrong):
The drain is not caused by any third party app that I have removed without seeing an improvement
The drain is not caused by Google's location service or account syncing
The cause is not Android itself. I used 4.4.2 for 6 months without problems, and I only upgraded to 4.4.3 last week
The problem is independent of location (WiFi and cell towers). During the 7h30m when I collected the data below and got the corresponding graph, I was both at home, at work and commuting between the two, and I can't see any difference on the graph.
The problem is not related to the runtime, because i used ART almost since it was released with android 4.4 and after the factory reset I have used Dalvik
My suspects:
The issue started while the new version of Google Play Services was rolling out. Maybe it ****ed something up?
Batteries consist of multiple "cells" right? Maybe one of them (about 50% I think) broke?
I have uploaded a logfile from BetterBatteryStats below. That data was collected with account syncing disabled, location mode set to "device only" and only the third-party apps mentioned above installed.
Please contribute with any relevant insight or idea, and don't hesitate to ask for more info or propose experiments, to narrow down the possibilities.
Thanks
Styrkefuglen said:
My phone's battery has been sucked dry way too fast since ~may 25.
I am and have always been on stock rom, and I only rooted the phone this weekend in order to use BetterBatteryStats and Wakelock Detector.
I estimate that during a day of heavy use for me before the end of may, the battery usage cannot have been much above 5%/h
According to BBS the phone used 6.4%/h over 7h30m this morning with less than a minute of screen on-time.
None of these things have helped significantly:
*Disabling automatic syncing
*Setting location mode to "device only"
*Uninstalling EVERY third-party app except these most essential: Authy, Barcode Scanner, BetterBatteryStats, Dropbox, DSB Wildcard, LastPass, Sleep as Android (and addons), SuperSU.
*Factory reset
*Upgrading to Android 4.4.3
Disabling WiFi to see if that would make a difference
Disabling mobile network data
My conclusions (please correct me if i'm wrong):
The drain is not caused by any third party app that I have removed without seeing an improvement
The drain is not caused by Googles location service or account syncing
The cause is not Android itself. I used 4.4.2 for 6 months without problems, and I only upgraded to 4.4.3 last week
The problem is independent of location (WiFi and cell towers). During the 7h30m when I collected the data below and got the corresponding graph, I was both at home, at work and commuting between the two, and I can't see any difference on the graph.
My suspects:
The issue started while the new version of Google Play Services was rolling out. Maybe it ****ed something up?
Batteries consist of multiple "cells" right? Maybe one of them (about 50% I think) broke?
I have uploaded a logfile from BetterBatteryStats below. That data was collected with account syncing disabled, location mode set to "device only" and only the third-party apps mentioned above installed.
Please contribute with any relevant insight or idea, and don't hesitate to ask for more info or propose experiments, to narrow down the possibilities.
Thanks
Click to expand...
Click to collapse
Have you tried wiping cache and dalvik cache in recovery? Give them a wipe and let's hope that stop the battery drain.
taodan said:
Have you tried wiping cache and dalvik cache in recovery? Give them a wipe and let's hope that stop the battery drain.
Click to expand...
Click to collapse
Hey taodan, thanks for the suggesion. :good:
I forgot to mention that I have used ART almost since it was released with Android 4.4, but I haven't changed the runtime since i did the factory reset.
So I have had the battery draining issue with both runtimes, which makes me think that the it is not related to the runtime I'm using.
I have tried wiping cache from recovery at least once, but I can't remember if I did that before or after the factory reset.
Do you still think that wiping dalvik cache will help?
I will update the original post with the info I forgot here.

[Q] Verizon Lollipop update - Battery life has decreased exponentially

Good morning Everyone,
I received the OTA update to lollipop on Tuesday night. Since then, I've noted the following:
Upon successful completion of the update, I was prompted to update google play service. I don't know for sure whether it actually updated but it did take a very long time to do anything. The phone was largely non responsive at this time.
The phone seems to be a little laggy since the update.
My battery life has tanked. I used to get close to 36 hours out of the battery. This has since decreased to 6 hours.
I do see another user experienced issues with google play services. I have tried clearing the cache on both the google play store and google play services and rebooted as was suggested in that thread, though I was not prompted to update it. I'm running version 6.5.99 (1642632-438) of the google play service.
The main concern is the lag and the battery life. Does anyone have any ideas as to what might be going on?
S79
sonnet79 said:
Good morning Everyone,
I received the OTA update to lollipop on Tuesday night. Since then, I've noted the following:
Upon successful completion of the update, I was prompted to update google play service. I don't know for sure whether it actually updated but it did take a very long time to do anything. The phone was largely non responsive at this time.
The phone seems to be a little laggy since the update.
My battery life has tanked. I used to get close to 36 hours out of the battery. This has since decreased to 6 hours.
I do see another user experienced issues with google play services. I have tried clearing the cache on both the google play store and google play services and rebooted as was suggested in that thread, though I was not prompted to update it. I'm running version 6.5.99 (1642632-438) of the google play service.
The main concern is the lag and the battery life. Does anyone have any ideas as to what might be going on?
S79
Click to expand...
Click to collapse
Sounds like you might have some sort of file corription os something, i just installed 5.0 lollipop yesterday aswell and everything on mine works GREAT and my battery life has gotten way better then when i has kitkat, if i was you id o reflash lollipop on your device and im sure that will fix your issues.
DopeShow said:
Sounds like you might have some sort of file corription os something, i just installed 5.0 lollipop yesterday aswell and everything on mine works GREAT and my battery life has gotten way better then when i has kitkat, if i was you id o reflash lollipop on your device and im sure that will fix your issues.
Click to expand...
Click to collapse
Thanks DopeShow. It's good to know this isn't necessarily a system wide issue. I'll try reflashing as soon as I can.
sonnet79 said:
Thanks DopeShow. It's good to know this isn't necessarily a system wide issue. I'll try reflashing as soon as I can.
Click to expand...
Click to collapse
Yup, No Problem. Anytime, im sure youll have it running perfectly after you reflash 5.0
DopeShow said:
Yup, No Problem. Anytime, im sure youll have it running perfectly after you reflash 5.0
Click to expand...
Click to collapse
I'm backing up my data now.
My S5 is not rooted. What method would you suggest I employ to reflash? I'm guessing recovery mode but wanted to get your thoughts.
My battery life is horrible on 5.0 too... I'm not rooted, so it is hard to tell what is killing it...
Just shows up as android kernel and Android system in GSAM battery program. They are taking over 2x more battery than the screen is.
Might need to factory reset at some point...
sonnet79 said:
I'm backing up my data now.
My S5 is not rooted. What method would you suggest I employ to reflash? I'm guessing recovery mode but wanted to get your thoughts.
Click to expand...
Click to collapse
You can Odin either an OA8 tar from Sammobile or Odin a NK2 tar then OTA to NK7 and OA8. Both of these don't require root. Also, I'd suggest factory resetting once you flash a tar, as it should improve battery and it might be required to boot.
First thing to try to fix the battery drain is boot to recovery and clear the cache partition. If that doesn't work then a factory reset will be necessary to fix it. I have personally always done factory resets after system updates dating back to Froyo. Just helps to clear everything up.
Thanks for your suggestions guys. I booted to recovery and performed a factory reset. Early indications suggest battery life is greatly improved. I'll post back in a day or so to give you a final verdict.
I hope very few users suffer from this, but if so I trust this information is helpful.
I can't say I have really noticed a decrease in battery life, but I have noticed it takes longer to charge now.
I watched movies and television shows on my device yesterday, all day. Started with a full charge and got almost 8 hours of screen on time before I plugged in. Batter still had 12%. This was with stock non-rooted version of Lollipop. Seems comparable to what I was getting on KK.
I also had issues when updating to Lollipop. I had issues with Google Play Services, and I ended up having to do a factory reset of the phone.
For the most part I have had no trouble with apps force closing or anything like that. But I have had horrible battery drain as well. When I am not using my phone, it seems that the battery life maintains pretty well. But when I use it even for not intense tasks - browsing news apps or something like that - it drains really quickly. I'm lucky if I get 6-8 hours of use per day. I used to be able to last a solid 14 hours of decent use before I had to recharge.
Any thoughts what could be causing it after I did the factory reset? My phone is not rooted.
same problem
Non-rooted S5 and after lollipop update it is chewing my battery and generally laggy (slow response to screen press). Even getting force closes on apps. Backing up now for a factory reset. Hope it helps.
Edit - 3/5/15 Factory Reset and reloaded all apps. Still working through all my website logins and settings. Not enough time to know if it fixed my battery issue but feels like the lag issue is fixed. Only been a day and initial thoughts is a reset was the cure. Will check back after the weekend with an update.

[Solved] New High CPU Usage, Battery Drain, Overheating, etc.

Woke up this morning to my S7 Edge being extremely hot. I immediately took it off the charger because I thought the battery was maybe overheating, but it now appears to be a CPU usage issue. It will not go below 50% usage (often staying at 90-98%. The phone is continuously hot and battery drains ~1%/minute without usage. I have tried restarting the phone multiple times without change. Any suggestions would be welcome.
Update: the issue appears to stem from an Oculus automatic update. Uninstalling the Oculus app solves the issue. Read more here: https://goo.gl/Mt5FJy (thanks AVKillah)
High CPU and battery drain
I woke up to the same thing this morning. Phone running hot (processor-based problem, not the display or the charger). Have rebooted several times. It doesn't help. I can't find the offender app. Android processes are taking up most of the battery usage according to the battery monitor. This has never happened before.
Anyone have a fix?
Same here! Just late last night before bed.
The phone is running hot, lagging, keyboard constantly closes.
Trying to install anything hangs forever. Reboots and ram clears are not helping.
Haven't tried full cache wipe yet
Already tried full cache wipe through recovery. No change. Thinking about factory resetting but I have so many settings that would be wiped out...
Ultra power saving mode helped. Don't know if it's temp yet but at least while i was in it and for the moment since i just came out
xdathekilljoy said:
Ultra power saving mode helped. Don't know if it's temp yet but at least while i was in it and for the moment since i just came out
Click to expand...
Click to collapse
Ultra power saving mode did help too. Booting in safe mode was also a solution for me, but you can't use any apps in safe mode so it's really pointless. It's also hard to narrow down the problem since I haven't downloaded an app in weeks and the only thing hogging resources is the android system.
I'm having a similar issue with performance and phone running hot. I am suspecting it is related to the PH1 update (noticed you have it as well). Device has been performing very poorly lately .
Factory reset has so far resolved the issue. May be related to PH1 update as I took that a couple days before this issue occurred. Will keep this thread updated if problems reappear.
So for the others affected is it all the same?
I havent taken any updates or changed my rom.
Nothing that changed that i can think.
Just that we all started experience this either this morning or before falling asleep?
I am having the same problem. It started this morning. I thought it was the copy of "Disconnect Pro Privacy and Performance" I got from the Galaxy App Store, but it persisted after uninstalling that. In the battery usage last when you select "Android System" it shows a list of the processes, and GearVR was on the top.
I tried to log in, but if forced an Oculus update which just hung on the install. I uninstaled all the VR stuff I had and froze the Gear VR Services app. That seems to be the culprit for me. It just kept trying to install an Oculus update that wouldn't go.
Phone is back to cool and normal battery drain so far. Will update if that changes.
Sent from my SM-T710 using XDA Free mobile app
AJswimmer said:
I am having the same problem. It started this morning. I thought it was the copy of "Disconnect Pro Privacy and Performance" I got from the Galaxy App Store, but it persisted after uninstalling that. In the battery usage last when you select "Android System" it shows a list of the processes, and GearVR was on the top.
I tried to log in, but if forced an Oculus update which just hung on the install. I uninstaled all the VR stuff I had and froze the Gear VR Services app. That seems to be the culprit for me. It just kept trying to install an Oculus update that wouldn't go.
Phone is back to cool and normal battery drain so far. Will update if that changes.
Sent from my SM-T710 using XDA Free mobile app
Click to expand...
Click to collapse
Hmmm. I did notice an oculus update. And that annoys me cause it auto updates and i dont think you have control cause the other parts i have auto updates off.
But the core can update at will
Apparently there is an article or few about it.
Apparently it is as AJswimmer described with the oculus update
xdathekilljoy said:
Hmmm. I did notice an oculus update. And that annoys me cause it auto updates and i dont think you have control cause the other parts i have auto updates off.
But the core can update at will
Click to expand...
Click to collapse
Fun fact... I woke up this morning and because I hadn't disabled the "Gear VR SetupWizardStub" and "Gear VR Shell" as well they had auto-reinstalled Oculus and it, in turn reinstalled a bunch of VR apps. After re-uninstalling things again and freezing the last couple VR things my phone is continuing to run cool and with back to normal power drain levels.
Yeah apparently it is Oculus. Uninstalling mine.
samsung-galaxy-s7-s7-edge-and-other-galaxy-phones-overheating-and-draining-battery-after-update-uninstall-oculus-app-to-fix-it.htm
AVKillah said:
Yeah apparently it is Oculus. Uninstalling mine.
samsung-galaxy-s7-s7-edge-and-other-galaxy-phones-overheating-and-draining-battery-after-update-uninstall-oculus-app-to-fix-it.htm
Click to expand...
Click to collapse
Alas, that appears to be the issue. Unfortunately I factory reset my device before figuring this out. Probably needed a refresh anyways (probably not). Live and learn haha.
soninja8 said:
Alas, that appears to be the issue. Unfortunately I factory reset my device before figuring this out. Probably needed a refresh anyways (probably not). Live and learn haha.
Click to expand...
Click to collapse
I opened oculus and took the update that way and all seems fine now
Why am I unable to disable my gear vr apps? Trying to do it through settings-applications
Sent from my SM-G935V using Tapatalk
I'm not sure you can through the normal settings menu. I used EZ Package Disabler to do mine.
Sent from my SM-T710 using XDA Free mobile app

Help! Note 4 freezing, crashing and constantly rebooting.

Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Actually iv seen an existing thread which appears to match my issues, so iv installed wakelock on the phone for now which seems to be helping a bit, time will tell, however this isnt a solution but more of a work around, but im still thinking this could be a motherboard issue myself, however, as i think this phone is over 2 years old, i doubt samsung will replace the component, nor would they necessarily believe me if i turn around to them and say its the board that needs replacing!
Terry6680 said:
Its been a long time since iv been this stumped, about a week ago my phone started acting very strangely, laggy performance, freezing randomly and occasionally rebooting itself, now its getting worse, getting to a point where the phone is probably rebooting itself 5-6 times a day, iv uninstalled every app, iv factory reset it, wiped cache, replaced battery, removed the SD card (in case of file system corruption) using Samsung Smart Switch did an emergency flash back to original Rom, installed every troubleshooting app out there, monitored RAM and CPU usage, all i can see is that the CPU suddenly spikes to 100% with no real reason, i cant link any particular app or process thats causing this, all of the cores on the processor appear to be coping with no faults.
The only thing i can think of thats causing this issue is either iv got a pending hardware failure on the board, or possibly bad blocks on the nand memory, however i cant see any simple way of determining this without rooting and using the likes of ODIN or other 3rd parties etc - linux commands etc.
I dont want to root it particularly if i can help it as i was thinking about selling it on to mazuma or the like and let them sort it out instead, but i think i might have to bite the bullet and try it.
Can anyone suggest anything that i might have missed?
Click to expand...
Click to collapse
Deleted...

Categories

Resources