My phone (running barepop) keeps getting hot and dieing after about 3 hours I charge till 100% and then about a half hour later (no use) its at about 87%. Is there anything I can do? I t also gets extermly hot like 130-170°F I cleared my cache and started using greenify. Nothing seems to work any idea's? Should I just call Sprint and get a replacement?
I'd try a factory reset
Thats what I did it seemed to fix it.
Related
I have had my Rezound just over a month now. I have been having random crashes, it seems to be after playing 3D games. First time was about a week after I got it. I was playing GLWG for about a half hour. I noticed the phone was getting warm, but didn't seem too hot. The battery warning popped up, and when I tried to hit OK, the phone crashed, then went into a bootloop. After pulling the battery, phone still bootlooped. Ended up having to do a factory reset. Haven't had any problems since, but this week, the phone crashed while playing Monopoly. Still had about 50% battery when it crashed. After crashing, it went to bootlooping. I pulled battery for about 5 minutes and was able to get it to boot. Same thing happened a couple days later, and just today, it crashed at the very end of Antutu benchmark, during the SD read portion. Has anyone else had these problems, or do I have a bunk phone?
Sent from my ADR6425LVW using XDA App
Digbob said:
I have had my Rezound just over a month now. I have been having random crashes, it seems to be after playing 3D games. First time was about a week after I got it. I was playing GLWG for about a half hour. I noticed the phone was getting warm, but didn't seem too hot. The battery warning popped up, and when I tried to hit OK, the phone crashed, then went into a bootloop. After pulling the battery, phone still bootlooped. Ended up having to do a factory reset. Haven't had any problems since, but this week, the phone crashed while playing Monopoly. Still had about 50% battery when it crashed. After crashing, it went to bootlooping. I pulled battery for about 5 minutes and was able to get it to boot. Same thing happened a couple days later, and just today, it crashed at the very end of Antutu benchmark, during the SD read portion. Has anyone else had these problems, or do I have a bunk phone?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Could be that your GPU is loose or something goofy like that. Which is why after your phone gets hot it starts messing up. Take it apart and let it cool off naturally then boot it up again.
Hey guys,
Last night I plugged in my LGOG right before I went to sleep. About seven hours later I woke up, woke it up to check the time, then fell back to sleep. When I woke up again a few hours later, my phone was completely dead. No lights go on when charging, nor does it go into the charging mode that happens when the phone is off but charging. The power button does nothing at all. Connecting it to a computer does nothing. I have tried two different wall chargers and a USB plug, and have tried different outlets. The phone is rooted and unlocked. I haven't put any new apps or anything on the phone recently, however I have had a slight overheating issue lately. I don't think that that's what caused the issue though, as when I woke up for the first time and woke it up, the phone was not noticeably hot, and seemed to work fine. Any ideas or suggestions?
Edit: As suddenly as it stopped working, it has started working again, about two hours later. The notification sound buzzed, my phone turned on, and usual on start things happened. However I'm still extremely worried about it. Now that it's on, I assume there's more I can do to figure out the issue- suggestions?
These phones are terribly buggy when charging/when they die, IMO. Worst Android device I've ever had in that respect.
Probably just a fluke, tbh.
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
miller150 said:
Unfortunately it happened again- sent a message, put my phone away, when I tried to turn it on again nothing happened and it stopped working for five minutes.
Apologies for not mentioning this before, but I am using carbonrom, not stock. I've used it for several months with no issues, and have used the latest build for a week or two now without this issue.
Click to expand...
Click to collapse
Reboot into recovery and wipe cache+dalvik
Maybe the rom needs a little cleaning
Sent from my CM10.2 OGE973
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
miller150 said:
Tried wiping cache and dalvik, but didn't seem to solve the issue. Then my phone started having an issue it's had once before- it turns on for a few seconds, then the screen goes grey for about a minute, then returns to being on. After returning to being on, it acts like it's just started up- ie, there's superuser grant notifications, cpu set notifications, and all sorts of other stuff I usually see on boot. It essentially rendered my phone unusable, so I restored an earlier backup. This seems to have resolved it for now, I may have to wait before updating carbon again.
Click to expand...
Click to collapse
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
OMGMatrix said:
Either you have a bad phone (possible, LG seems to have some QC issues based on some of the crazy reports Ive heard fm other people on this forum [Mine's fine]), or it's all the startup **** that you have going.
Do you usually let it discharge to below 5%?
that's a stupid idea with any device, and seems to be especially damaging to our LGOG.
Click to expand...
Click to collapse
Have mine 2months been careful not to let the battery shut down on its own but thirds past Monday my car charger weren't bad and the phone shut down. Would not except a charge after that. Went to att and they sent me to a service center. They could not charge it either. They replaced it, now making sure my external battery backup its always charged. Do not want to do that again.
Sent from my LG-E970 using xda app-developers app
That sounds like that could actually be the issue. On the previous iteration of carbon I almost never allowed it to go below about 10%. However the new update seemed to be harsher on battery life and it slipped into the 1% range several times...
same thing happened to me running root box with no tweaks or anything. I woke up and the phone was off, been that way for two days now. it wasn't on the charger so its definitely possible that it died. I actually found this thread because I could've sworn there was a report of someone who had to do a battery pull. I'm thinking that's my only option now.
My HOX+ is less than two years old. My phone used to get incredibly hot for the past 6 months. So, I uninstalled most apps and disabled many; keeping only the necessary one enabled. For the past two weeks my phone would automatically get switched off when I am using Snapchat. I thought of factory resetting it but was heavily occupied by my studies. Yesterday my phone finally got switched off and refused to get switched on. It only switched on when I put it on charge (It was already charged, so it wasn't like battery had drained out). I switched it on and disabled almost all but half a dozen apps. But again after few minutes it got switched off.
Whenever I am trying to switch it on, it just boots till HTC screen not even the HTC One screen and gets switched off. Sometimes it boots properly showing the homescreen. I backed up all my data and went for a soft reset. It did take place after few attempts. But the problem persisted so I went for a hard reset using the boot menu. But the moment I select FACTORY RESET it just shows the HTC screen with the slider (yellow) on the top right corner filling up and then again shuts down.
Please help. I have never rooted my phone or used any apk outside Google Play store.
Are you sure that your battery isn't going empty? After 2 years this may happen to a battery (rarely, but can).
/\/\ said:
Are you sure that your battery isn't going empty? After 2 years this may happen to a battery (rarely, but can).
Click to expand...
Click to collapse
No no it isn't. The battery meter shows normal battery level. Moreover I am also doing it while the phone is on charge, still no response.
mine too
my htx one x+ is also shutting down automatically.... it all start when i charge it while its OFF and suddenly when my phone reches 50% it shuts down automatically..
and now even my battery is full it shuts down automatically... i dont know what to do :crying:
please help me.
HTC One X+ 64GB nvidia version
Hi XDA, wondering if anyone can help me out with an annoying problem.
I have a Galaxy Note Edge. Within about 8 months I've been experiencing random shut-downs.
Thinking it was battery related, I started there. The problem persisted. Thinking it was perhaps a wake-lock issue, I did a factory reset including cache clear, still have the problem.
Basically when I'm using the device it will randomly shut down. I could be checking my email or taking a pic, out of nowhere poof, off it goes. Battery will still say an arbitrary amount, today it was at 64%. But when I plugged it in, with the device off it said 0%.
I notice this happens often. If I charge my phone overnight it will stop charging at maybe 70%. Poor/wrong calibration?
Here's the thing though, even if the phone says 0% after shutting down, if I try to turn it on it will go into a boot loop for..well infinitely. Hours. So there's clearly still power. If I try to use my battery bank to charge it, it still won't get past the boot loop until I connect it to at least a 2.1amp charger.
I'm at a loss. There doesn't seem to be any obvious hardware issues. I've been scraping the interwebs for a good year but nothing has helped and I just live with it.
Running Android 5.1.1, stock, no dumb unoptimized apps. Someone please save my sanity? Cheers! E>
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
jshamlet said:
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
Click to expand...
Click to collapse
So far I have not seen either of these issues. However I did an immediate factory reset upon installing the 2.0 update. But only 50 hrs since install of 2.0 so will continue to monitor.
I've had AW 2 for 6 days and no random reboots in that time.
Well this is fun. I guess I need to blow it away and refresh it, maybe clean the contacts. I have had to restart nearly every day this week since the update.
Still no random reboots here.
jshamlet said:
I've noticed a couple times now that my watch is randomly rebooting or hanging since the upgrade to AW2. I did a factory reset, which improved things a bit (no hanging), but I still get the occasional RR. It appears to be related to charging, as it generally happens when I plug it in at night.
It's not a killer, but I'm wondering if it is just my watch, or if others have noticed it.
Click to expand...
Click to collapse
I've been getting these as well. Just out of curiosity, does your watch reboot into recovery, and then reboot back into AW after a shirt time period?
Electronicbrain said:
I've been getting these as well. Just out of curiosity, does your watch reboot into recovery, and then reboot back into AW after a shirt time period?
Click to expand...
Click to collapse
No, when it happens it reboots into AW immediately. In effect, it goes black, then shows the ASUS animation like it got restarted. I did clean the pins and I haven't seen it since, though. It may be that AW2 doesn't care for the intermittent power when you first attach the cable.
My zenwatch 2 has started constantly rebooting until it quickly drains the battery after aw2. It is completely unusable. I have a 2yr warranty through best buy and am likely going to return it if I cannot find a solution.
Have you guys done a factory reset since the update?
It took a factory reset and then calibrating the battery sensor after the upgrade for mine to settle down..
Mine settled down after a factory reset, but it still crashes if the cord is loose (too many power events). It also drains significantly faster than it used to. I have been getting home with 62% instead of the usual 75%. Not terrible, but not great either.
I do like AW2 overall, though.