Related
i have a a100 with the latest flexreaper rom installed and im stuck with a pretty serious issue:
a couple of days ago the tab was acting real slow and sluggish and getting bad battery life didnt think nothing of it so i just rebooted a couple times and left it alone . all was good untill the battery hit 10% and i plugged it up using the factory ac adapter. the next day (maybe 6-7 hours later) i went to turn it on and nothing no vibrate no screen flash nothing; other than the power button turning blue as i pressed it and it would stay on for a couple hours but still no other response from the tablet.
im at my wits end on what could be wrong and now i got my wife with her foot on my neck till i get it fixed. can anyone help me?
ive tried to do a hard reset with the reset button tried to boot into recovery /bootloader no dice
(also my home button flashed a couple time i pressed the power button) dont know if its relevant but wanna get as much info out as possible
wondering if anyone can help me...
frenize said:
wondering if anyone can help me...
Click to expand...
Click to collapse
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
pio_masaki said:
It may take awhile for someone to see this and form something to try, random bricking for no reason is rare, its almost always some error by the user. However have you attempted adb connection to it? Leave it powered off, connect to the PC you used to unlock the boot loader then power on. Does the PC make the USB connect sound? Does the Acer vibrate? Did the home key blink again?
It really sounds like your boot partition is wrecked which wouldn't normally happen outside of flashing. If boot loader is trash then it won't know what to do and just sit there. No recovery or anything else.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
frenize said:
it made something like the connect sound but instead of the regular duh doom sound it did a dadadoom (kinda hard to describe the sound) but it was faster than ive ever heard the connect sound before which is weird. the tab didnt vibrate and it seems the home button blinks when the tab is dead and needs recharged
Click to expand...
Click to collapse
Yeah I know that sound it means USB connected but error for some reason. Its been shown if this thing dies all the way down it wont read the battery correctly and probably needs to be sent in. Before that I personally would unplug it open it up and remove the battery for awhile, maybe an hour then put it back and plug it in. But thats me, not the advice I'm giving. If you have warantee on it use that.
The batteries on a lot of devices and laptops etc have something of a fail safe, if the voltage drops below a certain point it trips to prevent cell damage, however it renders the battery useless.
I haven't searched out much past that if a reset is possible by us, but it seems the pack is trash after or needs sent in.
Since this is a sealed unit you void warranty opening it (well unlocking the boot loader did too) so you can't send it in for repairs without paying for it.
I hope someone can jump in and help figure this out, and prove me wrong.
Tapatalked from my Galaxy S II.
Weird, This exact same thing happened to me. Used it in the morning and now after work it won't turn on. I had already tried disconnecting the battery, but hadn't thought to leave it disconnected for an hour. My tablet has been running the leaked ICS since it came out and The last factory reset it had was about a month ago. It was working fine up until this. The power button seems to be responding correctly, the issue is that after the LEDs light up, there is no vibration or display. I hope someone can help us with this issue.
EDIT:
It won't connect in ADB mode. It will only appear on my computer as an APX device and since there is no vibration I am unable to boot into fastboot. Any help or suggestions? All the threads I have found have involved booting into fastboot.
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
same thing here.
max69power said:
i am also having this problem. i set ti backup last night to save to box i turned it on this morning it.worked set it on the charger came back to a frozen screen. I turned it off now just a black screen it turns on or the home button dose but nothing comes up on the screen
Click to expand...
Click to collapse
I have been using ICS the leaked one, and last night I was goint to check my email and it did not turn on, I though the battery died. I plugged to the charger and this morning I tried to turning it on but it failed. I did the reset pin but nothing. I connected to the computer and it was recognized as a APX device and installed a driver ACER Picasso USB recover but i cant access anything. I am a nob. Thanks
A100 blackscreen
i am also having this problem. last night. just a black screen it turns on or the home button dose but nothing comes up on the screen. :crying: Help!!!!!!
Has anyone tried holding the power button for a while? Laptops do this too, if someone felt ventures, try taking the battery out and hold the power button. No promises, might work.
sent from my ICONia
same here
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
If the screen is blank while powered on its in failsafe mode, in other words is bricked, has to go to Acer.
Tapatalked from my Galaxy S II.
This just happened to me a few weeks ago as well. If you are still under warranty send it in to Acer, thats what I did. I just got an email saying they had fixed it and were sending it back for free!!
At the time I was on the 9/02 JB build. I wonder if this issue is caused by faulty hardware or if it is an issue that was made by rooting and unlocking it? I don't know enough about this stuff to answer that though, but it does make me think whether I should root/unlock it when I get it back or leave it stock.
Also thanks Pio_masaki for helping me a few weeks back wasn't sure if I was even going to send it in until you said they most likely won't be able to tell.
I highly doubt they even CARE when sending these in. They will void for physical damage most likely.
tshm55 said:
Having the exactly same issue, here...
I also tried to hit the hardware reset button and it does not help.
Click to expand...
Click to collapse
Ohmygod,
Same here, but it's 3 years ago. Sorry for digging the topic. Still no hope? I still keep the tablet and have just buy another refurbished mainboard to replace but still no vibrate and blacksreen still there.
Hi, new here but I've been lurking for a while.
I followed Powerpoint's guide to instal CM10 on my KF2
http://forum.xda-developers.com/showthread.php?t=2105077
Everything was running great and has been since I first loaded version 3 a few weeks ago, and last week i went to version 4 of powerpoint's rom with no problems. Then a couple days ago after i had been browsing the internet on it for maybe 30 minutes, I set it down and when i came back the screen was off and wouldn't turn back on. so i figured the battery was just dead, so i plugged it in to the wall charger. At first the charge/power light wouldn't come on at all. Then after several plugs and unplugs the orange light started to come on but would only stay illuminated for 30 seconds-ish. So I tried it on my phone charger and the orange light came on and stayed on, so i decided to let it charge overnight. The next morning the light was still glowing orange so I unplugged it and tried turning it on, but still nothing happens. But when I plugged it back in afterwards the light came on green. now it has been plugged in for almost a day with the green light on but it still wont turn on.
Anyone else have this problem? Any ideas what i can try? for obvious reasons i can't exactly ship it back to amazon lol
p.s. I have a final on friday and the text book for that class is on the kindle. So urgent responses will be greatly appreciated.
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
docnougat said:
Nevermind guys, I figured it out. Power button for 20 and it booted right up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
I've had this a couple of times on both 10.1 ROMs. As you stated the only way I got it working was to hold the power button for 20 secs, then power on normally.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
docnougat said:
It just happened to me again, seems to be a recurring problem. Anyone have a clue what's causing this?
on a side note, perhaps this problem could be dealt with simply by installing a battery management app like juicedeffender. any thoughts?
Click to expand...
Click to collapse
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
agreed, if it was happening while i was trying to do stuff it would be problem. As it is though, I just consider it a minor inconvenience. Glad to know I'm not the only one experiencing this though.
iytrix said:
Wow, for once I can completely and knowledgeably help with almost no guess work!
The issue is Sleep of Death.
The cause is unknown, and due to the nature of how to reset it, it's been difficult to get logs. It happened to FMK not too long ago and last I heard he was going to get the logs (to find what causes this) and get those to Hashcode to look at potential fixes.
It's not battery related....well in the sense that, if it happened, you reset the device, and looked at the battery, it should be at a similar level to what it was before.
TO FIX
You guys were right on fixing it mostly.
If you ever press power a few times and it won't turn it, don't bother fretting about it. Just do the hard reset, which is holding the button down for 10 seconds. After you do that the device will reset to the point where if you just press the power button once, it will boot up like normal.
I would hold it down for about 15 seconds just in case, or if you have headphones it, you can here when it does the reset and can get used to the timing.
I would say....in a few weeks with the device, I've had the issue around 5-6 times.
I've also NEVER had it happen while I'm doing things, so it hasn't caused issues besides making me a wait a bit before using the device, which is good. If it happened during doing things I would want this fixed ASAP, but so far, no major issues.
Click to expand...
Click to collapse
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
fmkilo said:
I wouldn't call it a fix. I would call that a workaround. We need a fix, and I think if anyone could get an effing log to hashcode of it happening, we could fix the problem. I think it is a kernel problem, what with the recent merges and such. I think something is incorrectly copying from kf1 to kf2... if anyone understands what I'm trying to say, it makes sense..
Click to expand...
Click to collapse
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
chronicfathead said:
I wonder if pulling the log cat via adb would work, I.e. wait till it goes wrong' then connect it to a PC to pull the log. The issue is its very random and being at a PC to do it when it goes wrong could be tricky.
Sent from my Amazon Kindle Fire2 using Tapatalk HD
Click to expand...
Click to collapse
or you could have kmsg being written to a file during it...
the hard reset (power button for 20s) clears memory
Hello guys,
I tried to search for a similar issues but I couldn't find anything similar so please bear with me.
My KF sometimes shuts down overnight. In the morning then I have troubles to switching it on again (clicking the power button, holding it for longer periods of time...). It usually helps for the tablet being connected to the charger, but it takes a few tries to turn it on. After I managed to turn it on again, for example yesterday, it had 80% of battery left.
I am using CM nighties and this is happening already for some time.
I am also using juice defender, I am not sure if that is relevant.
Do you have any suggestion, what could be the cause of this? Maybe a suggested alternative rom? Or some logs I can check? I think the powering on troubles bother me more than the shutting off overnight since I always think it won't come back on anymore.
Also, not sure if relevant. If I try to turn it on and it doesn't, sometimes the button flashes orange. After a few tries it turns green and powers on. Not sure if I am now not only confusing times, when it was simply out of juice.
P.S. On a different note, just curious, does anyone know how if there is a rom with working mic already?
Thanks in advance.
jkb
Yes, I sometimes have the same issue with the power button - in fact it happened to me this morning where I went from about 60% charge to 16% with a sudden power drop.
Not sure why this happens. I thought it was a bad battery so I changed it but am still getting the problem every now and then.
Sent from my Nexus 7 using xda premium
the only thing that i can think of is that during the middle of the night a soft-reboot happens and it cant boot back up into the system. this would cause it to sit there and continually try to boot up. this would use a lot of cpu and a lot of power. as for why that drains battery while being plugged in, well i cant help you on that.
Thanks for the input. I've wiped dalvik, cache and the system and installed hashcodes AOSP Jelly Bean (http://forum.xda-developers.com/showthread.php?t=2041694) and at least it survived this night without shutting down so maybe this helped. If I come across the same issue, I will update this thread with new info.
Thanks again,
jkb
Check this out:
amazon.com/gp/help/customer/forums/kindleqna/ref=cm_cd_pg_pg139?ie=UTF8&cdForum=Fx1GLDPZMNR1X53&cdPage=139&cdThread=Tx2JSJNEOWHGOIT
Sounds like a hardware issue, and Amazon has been replacing those of customers who buy new from them.
Mine has this issue too. I KNOW it has battery power, and is still on, but the screen won't turn on. Only solution is to plug in power, then hold down the power button until it shuts down hard. Then turn back on.
I'm returning mine because of it.
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
jokob.sk said:
Thanks for the info. I am still hoping this is a software issue.Regrettably I am outside o the US and thus replacing it is nearly impossible. I will see, if the issue returns with the new rom and will update the thread if it happens again, just for your information.
Click to expand...
Click to collapse
Try going to the WiFi settings and selecting 'never' for keeping WiFi on during sleep. This seemed to work for me.... So far it hasn't happened again.
Sent from my Nexus 7 using xda premium
I think this is the bug I am experiencing:
Shutdown bug stalls out the shutdown. Looks like the device is off, but it's still powered draining battery. Currently requires long power button press to fully shutdown after the screen is black (about 15-20 seconds).
from the 3.4 kernel thread (http://forum.xda-developers.com/showthread.php?t=2264563). I am not sure if cm 10.1 nighties contain this kernel, but the description is pretty much spot on.I couldn't test the fix (holding the button for 15-20 seconds), since I already changed roms, but if someone experiences the issue again, he can post if this works and which rom and kernel they are using.
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
pwrdbykimchi said:
This happens to my Kindle Fire device as well. It just randomly shuts off and it won't come back on until I do a hard shutdown then turn it back on. I currently have AOSP Jelly Bean 4.2.2_r1 on it.
Click to expand...
Click to collapse
Yes, it happened again to me with the same ROM, but it happens less often. I will try the updated kernel once it is finished.
On May 27, 2013, Hashcode listed the known issues of the current kernel on his website:
Sound / MIC debugging
Deep sleep issues with “omapdss_dpi” device
SmartReflex shutdown loop fix.
Charging driver / OTG improvrments
Click to expand...
Click to collapse
Looks like they've been identified and are being resolved. :good:
While playing Lionheart Tactics on my TabPRO (while connected to the charger) it suddenly turned off, and won't be powered back on using the power button. It's not an issue of flat battery, as the battery was on close-to-100%.
I was wondering why this happened and what I may do to fix it. Please help.
Hold down on the pwr button .....keep holding it down
amityg said:
Hold down on the pwr button .....keep holding it down
Click to expand...
Click to collapse
Thanks a lot. That did the trick.
Why does this happen?
Sent from my beastly SM-T320
Not sure as to why. It has only happen once with mine. I had to hold the pwr button down for almost 30 sec.
@amityg how do you came up with that way of fixing it?
Sent from my beastly SM-T320
Had to try something...as it would not turn on. It work for me and when I saw the post that someone's else had the same problem , had to share!
amityg said:
Had to try something...as it would not turn on. It work for me and when I saw the post that someone's else had the same problem , had to share!
Click to expand...
Click to collapse
Thanks a bunch. This worked for me. Is this a recurring issue with many users, or am I just one of the lucky few?
turned off
loosefalcon said:
Thanks a bunch. This worked for me. Is this a recurring issue with many users, or am I just one of the lucky few?
Click to expand...
Click to collapse
i just had the same problem . It went off last night and wouldn't turn back on . i was reading here that he had to hold down the power for almost 30 seconds.it also worked for me thanks.
For me worked as well . At first actually recovery boot worked as well, but after a point not anymore. Thanks for the posts.
The still existing problem is that, the tablet (running on M12) turns off spontaneously couple of minutes after it switched to sleep mode (with display forced on, it does not happen).
Any similar issues?
I doubt the tablet is "powering off" its more like it's freezing up perhaps a hardware issue or overheating ...etc, holding the power button for 20 sec causes the tablet to force shutdown (like hitting breaker switch on a powerstip or holding down the power button on a computer), where if the tablet was already shutdown you would only need to hold it for 5 sec.
Anyways if its just a software freeze and not a hardlock you might be able to catch the problem in logcat or dmesg if you have adb access and root (since you mentioned CyanogenMod you probably do) , just monitor the logs as you are using the device and when it happens look at the messages for an explanation.
power off
sometimes I have to hold down the recovery buttons for 45 seconds for it to turn back on
To clarify something here, the tab pro's were made in february as premium line and in a couple of months later were the Tab S tablets been released.
That means that all the pro tablets has been reduced in price really fast.
Many people bought this tablets while thinking that they had premium tablets.
This tablets are unfortunately having multiple annoying and mostly unique issues.
I haven't experienced any of those issues on any other devices.
Issues like:
- Problems with slow recovery
- Annoying noise when doing high end tasks.
- Problems with official fully working cm releases.
- Several random issues.
I think i know why there has been released a new ( Tab S ) tablet serie so fast.
Maybe it was even based on economic tactics
Sent from my i9100 running gingerbread.
otyg said:
I doubt the tablet is "powering off" its more like it's freezing up perhaps a hardware issue or overheating ...etc, holding the power button for 20 sec causes the tablet to force shutdown (like hitting breaker switch on a powerstip or holding down the power button on a computer), where if the tablet was already shutdown you would only need to hold it for 5 sec.
Anyways if its just a software freeze and not a hardlock you might be able to catch the problem in logcat or dmesg if you have adb access and root (since you mentioned CyanogenMod you probably do) , just monitor the logs as you are using the device and when it happens look at the messages for an explanation.
Click to expand...
Click to collapse
Thanks for the tip. I started to use logcat couple of weeks ago. Then my tablet is turned off suddenly again as i described before. When i looked in the log-file, i saw high camera activity just before it turned off. My interpretation for that was "the Smart Stay + is the cause". I uninstallted it nearly two weeks ago, since then my tablet stays on as it has to . Thanks again for the tip .
Hey guys
I was super happy with my Australian Telstra M9 until an hour ago. I plugged it with 3% of battery in for charging and turned it off to speed the process up. When it was off the charging icon showed up just as usual. After a few hours I came back, unplugged the phone and it flashed 100% for a second. After that - nothing! It just won't turn on! I pressed every button and every possible combination of those. I plugged it back in for a bit and connected it to my laptop. But it's not even recognized. I googled for a bit but found no solution. I rooted the phone a couple of weeks ago but didn't do anything like that today. No updates, no new apps only some WhatsApp and 9gag.
What do you reckon? Is it bricked? Will I get a replacement and how long will that take? I have to leave Australia in 9 days so I'm quite on a schedule. -.-
Does anyone have any advice?!
Cheers Max
Edit: is there a chance to recover the data? I'm traveling and forgot to back anything up. Some of the data is quite important. And do you think I'll get into trouble because of the root?
No clue, try a different charger maybe.
I tried three different charges plus my laptop. Neither of them worked. Is there gonna be any way to rescue the data from the internal storage or will the just wipe it after they repaired it?
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
Hold power + volume up button will work in most cases.
TBH, don't really know what happened to you. Did you flash custom rom, recovery? or only root?
I didn't know that. I only new power + vol down. And I didn't hold it for a minute. I did nothing but flashing TWRP and root the stock rom. I didn't even change much with the root and only use it for titanium backup and adaway. That's why I was so baffled, when the phone suddenly "broke" because I didn't do anything unusual to it.
MrDuvet said:
Oh my god!!! Thank you so much! I have no idea why but after a minute it booted up just fine an all my data are still there. I'm never ever gonna forget a backup anymore. But what happend? Why did it start again? Battery is down to 50% so it seems it has been running all night and was stuck at some point. What can I do to avoid this from happening again? I don't wanna get a heart attack every time the phone won't turn on
But for the moment I'm alright! Thank you, thank you, thank you!
Click to expand...
Click to collapse
I'm glad you got your phone up and running. I know exactly how you feel, I had the same thing happen to me. I thought mine died when the screen went black after I flashed a kernel. Its always scary when the phone won't respond.
The phone was likely frozen. Power + Volume Up forces the phone to reboot after being held for a while. It could be some weird software issue due to the rooting and TWRP, but no one can say for sure. It might happen again but now you know how to reboot it If you really want to avoid the possibility of problems, you probably want to run stock and not root the phone or change bootloader... but what's the fun in that?
You're right no risk no fun. I'm actually waiting for cm so running stock is no option anyway
Thanks for saving me lots of headaches
FYI - I thought I had bricked mine as well - no flashing activity in a couple of weeks, all good chargers. Even made an appointment for repair.
Read the "hold power and vol up for a minute or two," and was like... nooooo... 10 seconds is the max you'd do that for... but tried it... bam, worked like a charm at ~45 seconds for me. Got into HTC FTM mode in which no option worked (reboot to bootloader, simlock, couple of others seemed to just pop immediately back to this weird non-download menu). Holding power for a while after that reset the device. Working now.
Thanks for the thread... been doing this for five years and this is the first no-charge no-response event I've had
lyall29 said:
I would try holding the power and volume up button for at least 2-3 minutes. If it does come on, as soon as you feel it vibrate, move your finger down to the volume down button and hold it until you get into download mode. Then boot to the bootloader and then recovery and restore a nandroid.
Click to expand...
Click to collapse
Worked like a champ, thanks a ton! :good:
Hi All,
About a week ago my M9 powered down while on charge and then wouldn't power on again. No response at all from the standard power button but only holding it for a few seconds at a time.
I knew the buttons to hold to enter bootloader and after several tries it powered on again.... It then ran for a couple of days with no issues.
Then a couple of days later had to power off the phone on a flight - same issue - wouldn't power on - dead.
It took several attempts to bring it back to life. I'm now in a position when every time I power off the phone it just doesn't want to come back on? Thought that it may have been a custom rom issue or a kernel issue - have tried changing both (painful experience by the way - having to wait for the phone to decide when its ready to wake up "when it feels like it after each new installation) but the problem is still there.
I have also found that entering bootloader using the power button and volume button isn't the only solution to "waking up" the phone. Just holding the power button for 10-60 seconds has the same effect - but it sometimes takes several attempts over several minutes - its very random.
Does anyone else have this recurring problem every time they power off? Does anyone on "stock" have the problem?
I'm starting to think that maybe its hardware rather than a software issue?
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Bricked M9
iElvis said:
Try turning off the phone, plugging in the charger, and holding all three buttons for two minutes.
HTC has recommended this as a fix for battery issues like the slow charging bug. Apparently it clears all the battery settings and recalibrates it. The phone will reboot repeatedly while you're doing this, but that's normal. Keep holding the buttons.
I have seen HTC phones do this in the past when the battery system gets confused.
Click to expand...
Click to collapse
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
sausje85 said:
Best to run a logger like BetterBatteryStatsor GSam Battery Monitor to find out what is draining it
Click to expand...
Click to collapse
I am unaware of any way to do this if the phone wont turn on - it's dead.
aairlinepilot said:
I am unaware of any way to do this if the phone wont turn on - it's dead.
Click to expand...
Click to collapse
Ah you cannot even get it charged anymore?
I know HTC phones had an issue that when they are completely drained, they seem to be dead, even not charging or anything. Yet if you keep them in the charger, eventually they would show as charging and being able to turn on again.
aairlinepilot said:
My M9 is not quite 6 months old - ALL stock. Went to bed last night , M9 quick charger plugged in with green light and phone power on - just in airplane mode. Woke up 4 hours later and found the phone dead.
I tried 1 button, 2 button, and 3 button holds for 5 minutes each, plugged in and not plugged in - still dead!
Any help would be appreciated.
Click to expand...
Click to collapse
Leave it in connected to the stock charger overnight and see if that helps. If not, you might have a hardware fault and need to return it for warranty service.
I too thank you most profusely!!