Related
So, my battery has been draining ridiculously fast and I think I found the culprit. For some reason, my TF is running at 100% awake time. This isn't the case with my friend's TF, so it can't be normal.
My TF is not rooted or anything, so I don't know how this came about. Any ideas on how to clear this out?!
Thanks!
Have you tried a factory reset?
Sent from my captivate BLAZING on firefly 3.0
Factory Reset should indeed help, as I believe it's a rogue app or service that's keeping your device awake.
It would be a better idea to try and troubleshoot which app/service is the culprit so you can make sure it doesn't happen again.
To do this, search XDA for 'bathisgb.apk', which is a modified version of the "Spare Parts Battery History" function, and this will show you which processes are keeping the device awake. Run the app, then choose "Partial Wake Usage" from the dropdown list, and if any have large blue bars, those are your culprits.
Hope that helps!
I have Battery Monitor Widget app and SystemPanel to monitor. The only app that I discovered to be consuming more battery than I minded was Skype. I uninstalled it but it seems that the Awake time is still going. =/
Nobody else having/had this issue?!
I did have this issue and ran the battery history app referenced above. My problem seemed to be with Google Voice. I installed the version from XDA for honeycomb.
Now I need to figure out which is worse. Shorter battery life or no text message from the device.
I was having this issue as well... not sure if your still looking, but here is a link that helped me.
http://forum.xda-developers.com/archive/index.php/t-905650.html
I updated all the radios, prl, ect
Then wiped data/cache/dalvik
Then wiped ALL
then flashed the same ROM
ALL of this before rebooting using RA recovery.
Also, when checking the progress, make sure your not connected USB to your computer!!
Hope it helps someone....
I was having the same issue (100% awake time), and the problem for me was simple. I was using the Lock Screen App (Kenneth Cheng), which I am still successfully using on my android smartphones, and that app seems for unknown reasons unable to put the Honeycomb on sleep like it does with previous versions of android.
I was also thinking at complicated scenarios, did factory reset the TF twice etc. but always used to install that app among the firsts ones cause it saves the hardware power button from aging to quick (which happened on my HTC Desire).
If you are using any app of that kind, it might be your answer too.
stnel said:
I was having the same issue (100% awake time), and the problem for me was simple. I was using the Lock Screen App (Kenneth Cheng), which I am still successfully using on my android smartphones, and that app seems for unknown reasons unable to put the Honeycomb on sleep like it does with previous versions of android.
Click to expand...
Click to collapse
Damn, I like Lock Screen too. Did you manage to find another app that does the same thing without causing the Transformer to not enter sleep?
EDIT: nevermind, it looks like "Screen Off and Lock" doesn't have the awake bug that Lock Screen app has so using that on my Transformer now.
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
XanoZuke said:
Hello everyone!
I've been having excessive wakelocks from "wakelockmanager", check out Wakelock Detector stats on the attached image. I'm using CleanROM 1.5 with Galaxy Gear connected all the time. Anyone else experiencing this problem?
Thanks!
Click to expand...
Click to collapse
I've done some other tests and I only see the wakelocks when I'm connected to the mobile network (with or without data). I use my Verizon Note 3 on GSM/WCDMA.
Sent from my SM-N900V using xda app-developers app
Any follow up on this? Having the same problem all of a sudden
Do you have Android Firewall and/or XPrivacy XPosed module?
I have T-Mobile Note 3 with stock ROM and I noticed this battery drain also when I have both installed. I actually have these wakelocks within 3 hours after rebooting.
- WakelockManagertimeout (runs 808 times)
- WakeLockManager (runs 1107 times)
So maybe it is something that is universal rather than restricted to a particular model (Verizon, T-Mobile, etc.)
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
fookea said:
I actually just installed xprivacy and rebooted. So far I don't have the wakelock anymore but has it within 6 hours or so after the first reboot... Frigging strange I can't pinpoint what it is even in BBS.
Click to expand...
Click to collapse
Probably the Android Firewall then. Some networking related process must be running in the background that intercept network request from the application.
However, if OP doesn't have these 2 apps, I am not sure what caused the excessive wakelocks...
Wakelock Detector quit working for me on 4.4.2. It crashes shortly after opening the app and giving it SU permissions.
i don't have Android firewall at all. I did deny some location and wakelock permissions in AppOps and it's better now. I'll post some pictures with the apps i have maybe we can compare them and find the culprit this way.
https://mega.co.nz/#!dIl3mRoa!XK4Yg1Dh-9E-AXgoA5BAIJm9qV-Y6QA2ewGU_JMuDUk
https://mega.co.nz/#!JZFm0RLY!V4Pu8elpJJN8Ufk8_k3qj-P1yoY_zruuv07wV84EM8A
https://mega.co.nz/#!tEUwVT4T!-UQPZdIGhCHgbvRvSe57l2i4ccPegRmUjDtr2OlCXoM
https://mega.co.nz/#!dF9jDDBY!sLRsk5b_Nur22gADlKx6vG7NcJ9T81lU5E0QpQXkOhA
Ignore the obvious ones like facebook and games.
I solved my issue. I ran Catlog and found that the csc was causing me a lot of wake locks. I have ORO CSC and flashed a SIN CSC. Somehow it was constantly trying something in the background. I deleted all the CSC folders except the common one and everything is back to normal. Also my Android OS and Android system are low now. The folders are located in /system/csc. I do advise backing them up in case something goes wrong.
Hope this helps
Recently purchased the Amazon HD 8 and thanks to everyone that contributes to this board (whom I would sincerely like to thank for all their hard work) was able to root and install Google Playstore. I subsequently installed ROMtoolbox Pro. I froze most of the Amazon apps that were running based on the list from a previous post that outlined what they found was safe to hide, or in my case, freeze.
While everything seems to work well (occasional freezes and unresponsiveness that I can live with as I assume its looking for an app or something that has been disabled) but what I can't live with is the battery drain. Its ridiculous. I saw in a previous thread that someone seemed to think Kingroot was the source of the battery drain. I actually have uninstalled Kingroot but I assume that the changes that it made are still running somewhere to maintain the root status.
Has anyone else experienced severe battery drain?
Well, I went ahead and restored to factory default. I re-rooted, used SuperSume to remove the kingroot install and used "hide" command to remove Amazon bloatware instead of using app dependent "freeze. It seems to be doing ok now. I passed on the nova launcher for now just to see how it does.
I'm betting it was Kingroot causing the extreme battery drain. I was down to 50% from 100% in 15 minutes of light web browsing and reddit app before I did all this.
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
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