Phone will not wake from sleep, needs reboot, massive battery drain - One (M9) Q&A, Help & Troubleshooting

So, a few things: First, I used Sunshine on my phone last Wednesday to put the newest T-Mobile firmware on my phone. Prior to doing these two things, this problem did not exist. I am on ViperOne 3.5, chose T-Mobile as my carrier and was very careful in setting things up.
First two or so times I would notice my phone was not waking up, so I held down the power button to restart and after it turned on there was a very large battery drain (30-50%). After this I decided that maybe the firmware was the issue, so I fastboot flashed a fullwipe version through fastboot (originally I had done a no wipe flash) and restored backup nandroid from TWRP. After that the problem persisted, so I thought maybe it was a rom conflict and did a clean install of Viper 3.5, thought everything would be good but while in the car it did it again. This time I caught it quick (I had used my phone maybe five minutes before and when I restarted the battery drain was less than 5%. But seeing as I've done a clean install of both the firmware and the rom now, I'm sort of at a loss for what to do.
Has anyone heard of this, or would anyone have tips on what to do? Can provide additional info if needed, just want to get this worked out. I've been lucky so far and it's done it while I didn't need power. If it were to do it during work when I can't check the phone for a while, it could lead to the entire battery being depleted.
::EDIT:: I should also add that this happened once when I was asleep, and I found that the phone would not charge when in this state, as the orange light was not on when I woke up and I had to reboot the phone. Again, extremely weird and it only started after Sunshine and firmware change, nothing else.

This "sleep of death" thing has happened to me a few times, though I have not seen the battery drain. I have not figured out what is causing it.

iElvis said:
This "sleep of death" thing has happened to me a few times, though I have not seen the battery drain. I have not figured out what is causing it.
Click to expand...
Click to collapse
I actually just caught it and tested some more out. Tried plugging it into a wall and it won't charge. Also tried plugging it into a computer and it will not recognize. The only two things I have changed are the firmware version, and running sunshine through it. I'm actually pretty worried since it won't even interface with a computer until rebooted. Also went from 90ish% to 77 in a matter of 15 or so minutes

Related

[Q] Lock ups and battery drain

I am hoping there is an easy way to troubleshoot and fix this issue. Every couple of days I can try to turn my screen on and nothing happens. I have to pull the battery to get it to come back up. When it comes up I notice the battery has dropped anywhere from 20-30%. I have tried a couple of different rom's. I am on the EL13 modem. I have tried the El26 and EL29 modem's but I have the same issue. I am not using any oc apps. How can I troubleshoot this and try to correct it?
When in doubt, backup, wipe, and flash the same or a different ROM. It's a bit tedious, but that usually fixes the problem. What ROM are you on right now?
I have done that. Was on caulkin's 2.8 now on the latest blazer. I believe it is related to the LOS bug. I just happened to be on a phone call when it happened again. It dropped the call and the screen went black but the phone didn't restart. I had to pull the battery and when it came up I had lost about 20% of the battery. Trying a different modem now.
There was a similar problem on the OG Epic...maybe this thread will help?
If it's not just a display issue (and something is actually draining the battery), I assume you've tried BetterBatteryStats? It usually works wonders for finding the source of wakelock problems.
EDIT: Actually responded to the question!
I have been trying to monitor this and it seems to be a different issue than what I thought. I thought it was related to the LOS but it isn't. My screen won't come and I have to reboot the phone. I think the battery level is just being shown incorrectly. I don't know why the screen won't come on. It is like it is asleep and won't wake up. I have been searching thru the forums and trying to monitor my phone processes to see what might be causing this. I have not found a solution yet. I have tried 3 different rom's so far and it seems to happen at least once a day regardless of the rom. I have wiped the phone and installed fresh. I have tried different modem versions and that didn't help either. Not sure what to do at this point.
when in doubt take it to sprint and get it swapped out.
im having this issue as well actually and i have to conclude that it's a battery display issue; my phone will be over 50% charged then drop as low as 8% when i reboot. i thought it went away with my last blazer flash but it still happens.
If it helps at all, I was/am running the MIUI rom and the phone would lock up on a nearly full charge at the same location. It was every time I walked out of class in the morning, the phone would just go black screen. I'd hold down the power, reboot, and wouldn't have that problem anywhere else. Hope this helps us find an answer.

Battery Issue on my G2

Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
louballs said:
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
Click to expand...
Click to collapse
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
HTCDreamOn said:
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
Click to expand...
Click to collapse
Thanks for the tip. I had already deleted the battery stats bin file from the system and rebooted and received the same results (assume thats what your fix does). I've also reinstalled the rom and had no issues. Ive done searches and found that SEVERAL other people with the G2 had this issue. Kind of surprised it hasnt yet been addressed on this forum. Back in 2011 Tmobile was asking for people to volunteer some info in order to fix it. Apparently nothing was ever done and when i call in (several times), no one seems to know what im talking about even when i point them in the direction of their own forums. I'm really at a loss and don't feel like paying out the a$$ for a new phone when I know this is not something I did.

[Q] Any ROM battery drain pain HOX

Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
goentillsundown said:
Me and my partner both have HTC ONE x's, Endeavouru, round a similar age, but her phone recently started draining battery.
Both running ARHD, with the same kernels. First I checked if apps were responsible, wiped and reflashed the ROM and kernel both.
This did not work, so then checked battery health with *#*#4636#*#* - showing the battery was in good health, but then replaced the battery anyway to eliminate any possibility of this being the culprit.
Now it's still giving massive drain - a charge up to 100% will last up to 5 hours of standby, with only mobile network activity turned on, all other radios off.
Been throughout the forums and other websites looking for any solutions to this problem but not striking any luck. Tried resetting the radio, changing it to LTE (Not even available where we are), and back etc, as one thread suggested, turned radio completely off and back on. Tried super cleaning the system before reflashing the ROM, tried a different kernel, an AOSP ROM, and still no luck.
It just all of a sudden started to do it, similar conditions to my phone, which makes it harder to pinpoint.
Any new idea's to bring to the table, open to any.
nb: Posted in wrong forum earlier, my bad.
Click to expand...
Click to collapse
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
suljo94 said:
try downloading wakelock detector and seeing what keeps the phone awake and then uninstalling/reducing its privileges
the privileges part can be done with xposed and a module called appops
Click to expand...
Click to collapse
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
Looks like faulty battery, try change the battery with new one and see what will happend
goentillsundown said:
Well an update to this thread...
Went to install wakelock on the phone after having it turned off for a few days, the battery was drained and now every time I try charging, regardless of what I use re ac/computer/original/aftermarket charging equipment, all it does is heat up to about 58 degrees C and stop charging - with phone off or on.
Sucks as it seems to be a manufacturing fault, but since I've rooted it, and purchased 2nd hand, looks like one for the rubbish bin
Click to expand...
Click to collapse
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
Thant said:
Looks like faulty battery, try change the battery with new one and see what will happend
Click to expand...
Click to collapse
in the OP he said that he did that already
suljo94 said:
check if your cpu is stuck at 100% or 1.5 ghz in trickstermod and could you post a screenshot of wakelock detector?
in the OP he said that he did that already
Click to expand...
Click to collapse
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Thant said:
Sorry I didn't see that. Then I am 80% sure the light sensor not working or working wrong. Must to check this. I am sure it is some of the sensors
Click to expand...
Click to collapse
Surely if it's the light sensor it would be irrelevant if it was turned off or on though, same with the CPU. I'm going to spend some time getting power into it today, charge, then put in freezer to cool it, and repeat.
Once some power is into it I'll start with suggestions, one at a time, and get some screen shots up, and logs of the current drain.
Thanks for the help so far, would be good to get it going again, instead of having a $350 paper weight.
An update:
Changed the recovery from Philz recovery to an older CWM recovery program, and now possibly just through coincidence the battery isn't super heating to the point it needs to live in the freezer to charge.
I have restored to stock ROM, and have a couple of pictures of the battery history, which are neither here nor there, apologies as I wiped a lot of things off, including my WLD pictures from the ARHD ROM.
I purchased trickstermod and had a look into the CPU settings, and nothing seemed out of the ordinary. Also turned on the dev options of graphic CPU usage on the homescreen - not really showing unusual signs of anything. About to flash the original recovery on and email HTC to see if they might feel sorry enough to accept it as a straight manufacturing defect, without evidence of where we purchased it (as it was a second hand phone off the net).
subscribing to this thread - I have the exact same issue. I have installed CM11 and ParanoidAndroid. Torched and Bubba kernel... turned off lots of stuff.
I have whatsapp, soundcloud and facebook as the only background running apps. not sure what's the issue
sensors drain battery
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Laccee said:
Hello!
I also have a similiar issue.
I noticed, after a while, that my phone keeps dying under 16-18 hrs on idle from full charge.
I thought it1s the battery, since my HOX is 2 years old. Someone suggested, to try some battery monitoring, so i got the battery monitoring widget, after for like 3rd time, the phone turned off overnight.
The problem, is the Light, and the acceleration sensors... they won1t let the phone go to sleep.
I tried turning off locations, and such, also auto rotation, and my back light was never on auto. it is set around 30%
Still, these sensors run, and consume battery like crazy. This started about 2 weeks ago.
I have a stock rom. not the original, since i thought flashing a custom rom might solve this, so i tried ViperX 4.1.1, the problem was still there.
After that, i reflashed an untouched original HTC JB rom.got the latest OTA update, and the problem is still there...
I don't have any apps running in the background, that should require these sensors to run. i always clear multitasking also.
Have Wifi on, but that barely consumes anything.
Any idea, i know this started on Gingerbread, and was supposedly fixed in ICS, but it's still happening to some ppl.
Any help would be appreciated!
Click to expand...
Click to collapse
I have checked all the sensors in the testing menu by dialing *#*#3424#*#* and they all turn off and on as required properly. I noticed yesterday that I've actually burnt out the charging system as it has got too hot at one point, so no use pursuing anymore. I will stick with my HOX until it too breaks in some way. Received an email back from HTC saying "Not under warranty, not our problem" after asking if they had had any phones with similar issues pass through.

[Q] Reboot problem when not charging

I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
manderson8898 said:
I have had my P607T for a couple of months now. It is box stock no changes. Over the last few weeks I have noticed that it will reboot while using various apps. (Fliipboard, Chrome, Clash of Clans, Papyrus...) They don't seem to all be heavy graphics or network. The only symptom is that the screen starts to flash then "bang" reboot (and trouble rebooting when not plugged in). It would not be too annoying except that it will loose wifi settings and the wallpaper. I have tried different wallpapers (saw a thread blaming the live wallpapers ) Unloaded some apps (had another phone issue with FitBit and HTC blink on my N4). I stay away from CoC (my base has been raided so often now ...). Any thoughts? I am really trying to like this tablet more than my old ASUS Transformer but this reboot and reset wifi is a pain.
Thanks in Advance,
marka
Click to expand...
Click to collapse
Have you tried a factory reset? I'd make tmobile replace it
was hoping to avoid the reset button. Tried it and still giving trouble it rebooted while restoring apps. I bought the tablet on ebay, I don't think TMO will take it back. oh well I'll keep poking about.
thanks,
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Wall-E said:
I experience exactly the same problem since the update to 4.4.2 (kitkat): The screen starts to flash, suddenly the tablet reboots. I tried a factory reset multiple times, also removed the SD card and reflashed the ROM via KIES, nothing helped so far. Also, even when plugged into the outlet for several hours the tablet didn't charge at all (I think it stopped charging when the screen saver kicks in).
A couple of weeks ago I filed a RMA request (my dealer sent the tablet to Samsung), yesterday I got it back. It was charged at 60% and when I plugged it to the outlet it actually charged (even when the screen went off). But after about one hour (the battery was still > 60%) the flashing reappeared and after a while the tablet started to reboot again. Interestingly the battery now showed only 2% and the low battery warning appeared.
I think the problem might occur only when the battery runs low (which happens very fast as something seems to drain the battery), while android still shows a much higher battery level . Never experienced these problems when the tablet was plugged in so far.
Click to expand...
Click to collapse
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
manderson8898 said:
At least I don't feel so alone with this issue... I have been paying more attention to my build up process since the factory reset. I found, the other night quite by accident, that when I logged in to Twitter the reboot started. So for the next few days I have left Twitter off the machine and it is doing better. I suspect that something is hitting the power drain (like you mention) and that causes it to have problems. In that thought I have also turned off the power saving mode and auto screen now just to add to the list of things I am avoiding.
Rgds,
Click to expand...
Click to collapse
Have you considered rooting and using root apps to stop the apps from being able to do such things?

Overheating issues with fulmics 5.3: phone reboots

I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!
Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.
I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse

Categories

Resources