Recently went to CM14 from CM13, did a clean install of it, but in the last few days, my phone has been getting REALLY hot, and the battery is draining completely in about 2 hours. Right now, I'm trying to see what's the best way to find out the culprit. Checked the running apps, and there's nothing unusual. Just facebook, whatsapp etc. Any suggestions as to how to start finding out what's causing it?
edit:
ok so I've made some progress by changing apps to be battery optimised and clearing the cache from a few apps. New question, if I wipe cache/dalvik from twrp, does it clear the cache from all apps?
Try installing a custom kernel... The same heating issue i have been experiencing in cm14.1 has been resolved through this...
Related
Anyone heard of an issue where apps in internal storage just start fc'ing then are essentially deleted? I am running cm6 rc2 which I flashed about 6 weeks ago. I haven't had too many issues outside of the bugginess of the ads launcher which I replaced with launcher pro. This afternoon, I try to start up dogcatcher and it immediately force closes, I tried to access the podcast I was looking for through music mod and that fails as well. I thought I might need to reboot, but when I get back into the system two more apps fail as well as the original failed apps not working. Curious, I look in my application list and the apps are mostly gone except for a few apps that show the generic market app icon, which I take to mean corrupted apps. I was able to go into titanium and restore some of the apps to work again, but I have had a pop up stating mytracks has stopped working, but I haven't even started mytracks since the reboot. I guess what I am worried about is If my phone's internal storage is failing? Is it even possible? Any suggestions?
Sent from my Nexus One using XDA App
I had the same thing happen, everytime I rebooted more apps would become corrupt, I was worried that my internal storage was failing, so I wiped everything and started again from scratch, and haven't had a problem since.
When you say start from scratch are you talking about reflashing cm6? I had been holding out since I have been reading about a lot of issues with the 6 stable version.
I formatted the phone, deleting cache and dalvic cache, and then reinstalled. I was using CM6 at the time so reflashed it, did everything by the book to be sure and it has been smooth sailing since.
Only time I have ever had this issue, on the N1 or G1 was after flashing a ROM and not wiping. Sometimes I could get away with it, sometimes not. Wipe and reflash is what I would do.
Hey Thanks guys.
I went ahead and wiped everything and started fresh with cm6 stable.
I am not sure what was going on . I had done a complete wipe and install from stock to rc2 and it worked great for 4-5 weeks. The only thing I could think of was possibly an issue with K-9 mail. One of things I saw happen fairly regularly (3-4 times a week) after rc2 was installed was that K-9 would suddenly just fc. That in and of itself wasn't too weird, but every time it would fc I would get a low space notification right after, where I kew I had 40-50 mbs of space free. Memory leak or something? Dunno.
All weirdness aside, so far CM6 stable is running great...
I've seen this happen when my the /cache filesystem was full. ('App not installed' , FCs etc). Run a 'df' command in a shell to check.
Clearing the cache would be a temporary solution. Moving the /cache to the sd card using DarkTremor Apps2SD is a permanent solution.
I currently have 178 apps.
Hi,
My HTC one is running the android revolution rom for a couple months now, however recently I notice that at night my phone get super hot and the battery drains quick.
Has anyone else ran into this problem?
poisonsushi319 said:
Hi,
My HTC one is running the android revolution rom for a couple months now, however recently I notice that at night my phone get super hot and the battery drains quick.
Has anyone else ran into this problem?
Click to expand...
Click to collapse
weird you might want to flash the newest revolution rom, my guess is that there is an app running in the background. game perhaps? i would just recommend a fresh install with 4.2.2 =D
Sounds like you have some naughty apps or system processes misbehaving, you need to find out which ones they are, try installing the watchdog app and set it to monitor system processes as well.
Also a good one is wakelock detector.
John.
Verify the rom your flashings MD5 checksum.
To eliminate any apps that may be causing your phone to get hot, do the following.
Go to your internal memory and clean up anything that you do not need, so pics, music and videos i would keep, or copy them off, delete everything else that you don't need. *Make sure you leave a working ROM to flash on your memory* (I personally do a good clean up every third flash, so i delete every folder and just leave the ones i mentioned above and a flashable rom of course)
Reboot to recovery and perform a full wipe (Data, cache and dalvic cache)
Install your rom.
Don't install any extras at all
*Do not restore anything whatsoever*, no advanced restore and no titanium
Allow the phone to boot and don't install any apps, just sign into your Gmail and keep it like that for a day.
No overclocking / underclocking no undervolting / overvolting of any kind, keep it on stock kernel.
Turn off unwanted wireless connectivity when not in use, ie: GPS, NFC, WiFi, Mobile Data.
If your phone gets hot after that then I would say that it could be a problem with your handset.
When it's charging or your running an app the phone will get hot, thats a given but if you follow what i've written then your phone shouldn't get too hot.
Good luck m8
Use this app and see which apps getting energy
See your battery life result
https://play.google.com/store/apps/details?id=com.gsamlabs.bbm&hl=en
Sent from my GT-I9300 using xda premium
My theory is that it's bad install. It happened to me on few occasions.
Hey Guys,
First the relevant data
Galaxy S3 LTE I9305
ROM: Carbon Rom KK 4.4 (CARBON-KK-NIGHTLY-20140701-1234-i9305.zip)
Kernel: Standard Carbon Kernel
Problem Description:
The phone reboots itself sporadic and then gets stuck at bootlogo. It is completly sporadic so sometimes it is when i am using it heavyly sometimes just when i end a call or want to do something else not intensive.
The only solution then is to go to recovery, wipe cache and dalvik cache and the reboot. The phone the rebuilds the dalvik cache and crashes a few times while the process.
But there are some more strange things going on:
- Battery
The battery is almost fully charged, when the phone crashes and reboots a few times while rebuilding dalvik cache the battery show up empty suddenly! Phones turns off and only turns on when plugged to charger and then shows battery level 0% when running again. The charging process begins normally from there.
Sometimes the battery shows empty as described above but when i restart the phone again and rebuild dalvik cache it's on its old state (almost full).
- Kamera
When i take pictures, sometimes the camera shows some red stripes all over the stored picture or even in focus mode. Then the screen starts flickering and phone crashes as describes above.
- PIN
When crashed and running again after some tries to build dalvik cache, sometimes i enter PIN to unlock sim card and nothing happens. Then the screen starts flickering again and it crashes. Procedure start again then.
- Charger
When the phone crashes and i plug it to the charger before rebuilding dalvik cache, it runs through without any errors like it should.
What i tried so far:
- Other ROM (AOKP, CM, other Carbon Rom builds)
- wiped everything (really everything on internal storage) and clean install
- reflash after crash (dirty)
- reflash after crash (wipe)
- leave phone with just a few apps after clean install (thought it could be one of my apps)
- recording a logcat (aLocRec and logcat reader) but the problem here is as the logcat is stored in memory it's not accessible after crash (reboot).
What i want to try next:
- try getting a logcat via adb and hope it crashes while logging
- other kernel (don't want to try this, would be last option).
Does anyone have an idea?
Thanks!
Dark Smile
One idea may be a bad battery which may cause inconsistent power supply and all kind of strange errors. Especially because, as you write, with charger = stable voltage source things look good.
Cheers,
Axel
Thanks for the tip s3axel, i'll buy a new one when i get off work and try it.
I just ordered a original battery from here:
http://www.trade-shop-online.de/ori...galaxy_i9305_galaxy_i9305-p-29153.html?ref=20
I'll give feedback when arrived and tested.
Good luck
Unbelievable, it was the battery! No problems with the new battery. Thanks for your advice s3axel
Sent from my GT-I9305 using XDA Free mobile app
I was experiencing exactly EVERY one of those issues besides the battery jumping to zero. It would even crash when opening messaging, chrome, contacts, literally everything crashed it.
I tried everything that you tried, and was about to logcat from my computer too lol.
And without looking it up I had the idea, maybe its the battery and it just cant support the changes in power needs, maybe I should buy a new battery!
Thought, nahh... ill try some more things first. Then boom! Reading this post I felt like I wrote it!
This thread just blew my mind!!!
I got my nexus Monday and have noticed terrible battery, I know it's not broken in yet but I installed gsam. Sure enough I have a wake lock, I believe that's for music but I'm not playing music. I do have a pebble, but I don't think it should cause it.
I'm stock rooted, still encrypted
Seems to be a bug with it not releasing media wakelocks. I have the same issue. Any media app (pandora, youtube, podcasts, etc) will get a wakelock when being used but closing them isn't releasing the lock. A reboot clears it up but definitely an issue.
akellar said:
Seems to be a bug with it not releasing media wakelocks. I have the same issue. Any media app (pandora, youtube, podcasts, etc) will get a wakelock when being used but closing them isn't releasing the lock. A reboot clears it up but definitely an issue.
Click to expand...
Click to collapse
Well that's pretty lame, I'll give it a try thanks
I have this exact wakelock at times and along with the "Mobile Radio Active" issue between certain apps i don't hardly use and the Mobile Radio stays active 3-4x my total screen on time
Other than a reboot i can't get it to go away!
akellar said:
Seems to be a bug with it not releasing media wakelocks. I have the same issue. Any media app (pandora, youtube, podcasts, etc) will get a wakelock when being used but closing them isn't releasing the lock. A reboot clears it up but definitely an issue.
Click to expand...
Click to collapse
I've uninstalled youtube and play music since. Making sure that only sounds going off are notifications. It just sits and runs. even if i reboot it just sits and runs.
Rebooting doesn't even fix it for me
fryingpan0613 said:
Rebooting doesn't even fix it for me
Click to expand...
Click to collapse
same here same here. no matter which rom. or stock.
That's "OK Google" always listening for your voice I believe.
ohhdavid said:
That's "OK Google" always listening for your voice I believe.
Click to expand...
Click to collapse
Nope, don't even have that activated
Sent from my Nexus 6 using XDA Free mobile app
yeah i've uninstalled all media apps and froze some more that haven't fixed it. Just not sure what it is.
I'm close to giving up on this
Any updates?
1) I give up
2)its always my top app drainer
3)I don't know how much it really sicks out of the battery but it is annoying.
4) here are my results
5)I will continue to monitor threads like these in hope
Have a goodnight guys. Here's my stats from today.
Very similar issue for me
I think I may have fixed mine. I'm on pure shamu beta 2.9. When I first installed it I didn't have the adspd drain. After installing all my apps I had it. I tried uninstalling a bunch of apps to see if it was one of them but that didn't work. I think its a problem with installing a custom kernel. I have been able to reliably stop the drain by going into recovery, flashing my kernel (I've tried with lean and sensei) and making sure to wipe dalvik and cache before rebooting. I've tried installing without wiping dalvik and cache and the drain comes back.
rlsroufe said:
I think I may have fixed mine. I'm on pure shamu beta 2.9. When I first installed it I didn't have the adspd drain. After installing all my apps I had it. I tried uninstalling a bunch of apps to see if it was one of them but that didn't work. I think its a problem with installing a custom kernel. I have been able to reliably stop the drain by going into recovery, flashing my kernel (I've tried with lean and sensei) and making sure to wipe dalvik and cache before rebooting. I've tried installing without wiping dalvik and cache and the drain comes back.
Click to expand...
Click to collapse
It's an issue on the stock kernel as well. Wiping dalvik (which no longer exists) and cache have no impact on the kernel in any way.
akellar said:
It's an issue on the stock kernel as well. Wiping dalvik (which no longer exists) and cache have no impact on the kernel in any way.
Click to expand...
Click to collapse
It may be just the act of resetting and doing the app upgrading after the dalvik/cache wipe even though I have only been able to reproduce it after installing a kernel. And have only tried it on the pure shamu ROM. Just letting y'all know what worked for me. I don't understand android well enough to know why or what this is. Haven't heard any other solutions though.
Pure shamu is the only ROM or stock image that it hasn't started up immediately for me. Most people don't see it if they don't install the gsam root companion.
Hi Everyone
Bit of help please.
Having problems over the last 20 days or so. The phone keeps powering down completely at random.
I had flashed No Root Stock Debloated/Deodexed N6 ViPER|Atmos Audiophile 1.6 and after a week the above started.
Fully wiped (including data) the N6 and re-installed from a OTG USB through TWRP. After a week the same random shut-downs began again.
Another full wipe and installed ver 1.7 from the above and within a couple of days the shutdowns started again.
Today thought a different ROM may be the answer. Full wipe and tried [MMB29U/Q][6.0.1][STOCK][OMNI][MOKEE][CMTE][LAYERS] FLUENCE HD9 and the shut-downs are still here.
Seems to be getting worse.
Not using layers or anything abnormal - nova launcher and popular apps, nothing strange. No Kernel optimizations.
Really stumped as to what I have done. Wondering if I have a HW fault rather than custom rom or apps. Going to un-root, lock the BL and give Google stock image a go, unless anyone has a suggestion.
TIA
Any water damage that you can think of? Any parts of the phone getting extremely hot?
You could try ordering a new battery, and see if that fixes the issue, as it is not a software issue.
I'm also having a similar issue, but it occurs when trying to open camera and having relatively low charges(%20). I could not pinpoint my issue exactly but generally complete shutdowns caused by battery problems(temperature, voltage, mis-feedback). Like flyeyes says it is probably a defected battery unit.
Grab some logcats or a crash message. Without them the only thing I can advise is that it is one of your apps causing it or a hardware issue.
Have you tried complete stock firmware from Google with no customizations? If so, does it happen then? If it happens on complete stock from Google you might be looking at a hardware issue. If it only happens on custom ROMS after you set them up, then it might be an inconsistency with whatever apps/changes you make to it.