Related
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Thanks, giving a go now.
Do you need root to calibrate though? I am on stock firmware and not in front of a windows machine to use ODIN.
Vlad the Cat said:
Turn off the phone and put it on charging. Once it beeps that its fully charged, quickly unplug the battery for 5-10 minutes. Should work and 'recalibrate' your battery
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
encima said:
So.. I have googled the crap out of this problem and seen loads of issues raised, but nothing solved.
I am coming from a Dell Streak and grabbed me a galaxy s 2 from craigslist a couple months back.
It has been running fine and I have tried a few roms/kernels and a few days ago I got the following error:
When charged to 100%, I get the notification to unplug, when I do, it sticks. No big deal but even when the phone battery has dropped to around 80% it stays.
It does not go into MTP mode or think it is plugged in via USB. Although, before this problem originated, the phone continuously vibrated between charging and not, when not plugged in.
I have calibrated the battery, tried a mixture of roms/kernels and I am now on unrooted stock. The problem still occurs and sometimes it does not recognise a USB connection, like today.
Probably worth mentioning that when turning on (and not plugged in) the phone does not turn right on, just boots into the battery screen and flashes between the battery charging and the overheating symbol.
Anyone got any ideas?
Click to expand...
Click to collapse
i am actually having the exact same problem FYI im using exynos extreme rom 7.2 i think nt sure its getin worse before it used to detect usb mode somrtimes now it dosent!
encima said:
OK, charged to 100% and got the full notification.
Left battery out for 10 mins and whacked it back in.
Turned on and it went to the overheating sign again.
Booted into the samsung recovery and I can boot into android from there.
Battery says it is as 88, cannot calibrate as I do not have root atm.
Any ideas?
Click to expand...
Click to collapse
Get root and use the battery calibration tool from the market. The best idea so far. I suggest rooting with CF-Root, its fast and easy - its basically still your stock kernel but just with root.
If you really need the warranty or you'r scared of root you can install cf-root, calibrate the battery, then re-flash a stock kernel (unroot)
Sent from my GT-I9100 using XDA App
If i helped you, press thanks. Thanks.
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
One thing to note is that this seemed to happen around the time of buying a dock for the samsung from Amazon, by Kidigi. I plugged the phone in to the dock without a USB cable connected to the dock and the dock LED lit up, making the phone think it was charging. Is this likely to have caused it/messed up the micro usb forever?
Thanks again guys!
well i think ive figured out what the problem was
Its due to overcharging or keeping the charger connected after battrey is full which has caused a hardware damage
im not sure if this is true but this is the closest explanation i can get the phone shows connected to charger even when diconnected only when i keep it connected for long time even after its battrey is full my usb connection has completely stopped working
---------- Post added at 01:56 PM ---------- Previous post was at 01:49 PM ----------
encima said:
Done and done.
Calibrated, even bought a new battery. Tried various other roms and appears to be an issue. Phone knows when USB is plugged in but does not seem to recognise the unplugging of the charger. And stays at 100% for a while before dropping down to like 80.
Thanks again guys!
Click to expand...
Click to collapse
well that the same problem with me when it shows connected to charger at 100% i restart it then the phone drops to ~80% battery although its 100% which makes the app battery monitor widget think i have a 1977mah battery while i have the standard 1650mah battery this must be the extra 20% which disappeared after the restart for me
I thought it may have been an overcharging problem, although no other phone I have owned has had this problem.
I let the battery charge all the way down (it stayed at 1% for about 3 hours) until it shut itself off. I left it on the side and it created a clicking noise, it was trying to turn the phone on as it knew the battery was in, even though it was depleted.
I plugged it in via USB to charge and it tried to turn on straight away. Shut it down and charged by plug until the 100% notification then turned on.
Still the same problem but one of my battery widgets warned that the battery was over voltage for a while before calming down.
If the phone cannot be off with the battery in, what could be causing that?
encima said:
If the phone cannot be off with the battery in, what could be causing that?
Click to expand...
Click to collapse
It has been known to be caused by a defective circuit board for the USB connector.
So, it needs a samsung return, I assume?
i have the same problem with overheating and usb plugged when there is nothing connected
i changed the usb port from the phone but it still having the problem!!!
i will try to put a new battery and see if it work and after post a reply
Gidday - This morning I woke up to find my phone had switched itself off during the night while on charge.
Last night I put my phone to charge through USB connected to my PC in sleep mode. I've been charging the phone like this since I got it 3 weeks ago and its been working fine.
When I woke up in the morning I found the phone off and when I gave the power button a short press expecting it to show me the time all I got was a battery charging symbol.
When I went to bed I had the standard "Clock" feature running that comes standard with the Neo so it acts like a bedside clock and I always have the Wifi on when I'm at home.
No other applications were running in the background apart from the normal stuff but I'm quite concerned that the phone turned itself off while I was sleeping because I use the alarm feature to wake me up when I need to go to work and I know these Android phones do not wake themselves up to run the alarm.
Any ideas what could be causing this?
Now this is very funny you say this because this happens to me,,, but I'm convinced I turn it off myself,in my sleep my partner confirms lol
But seriously could of just been a reboot
As long as it don't happen again it should be no great consern ''unless you sleep in for work'' lol
Sent from my Xoom using xda premium
I heard charging like this(from night to morning) is not good for the battery.The owner of the shop where I brought my W595,Neo V specially told me NOT to do this,as he said this can reduce both battery life and phones life.Anyway don't get that much concerned about itself switching off mate after only happening it once.But if can in future don't charge like that.
lol kormatoes ,I on the other hand when ppl call in night sometimes I was told that I just answer it and instead talking keep it beside my pillow thinking it was alarm and go back to sleep xD
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Thanks for your comments guys.
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged? either way I've been thinking that charging via usb is better for the battery because its a lower energy input and therefore charges the battery slower/cooler which in turn should make it last longer (just guessing here - no science to back this up)
Then there is the having it plugged in while at 100% - I've noticed that the phone somehow disconnects itself and stops charging the battery when at 100%. I noticed this today when I started my phone after its surprising shutdown = the battery was fully charged (because it had been plugged in all night) and the battery display refused to show me that the phone was plugged in (when it was) so I turned on the flash light feature and blasted some music to drop the %tage down and sure enough as soon as the percentage dropped below 100% the indicators on the phone started to show the batter was charging (both via the lightening bolt in the normal battery icon and also on my battery monitor which tells me if its charging and how much longer it will be charging for).
I'm looking forward to seeing if the phone is still on tomorrow when I get up.
Any more ideas much appreciated - once might not sound like much but if the alarm/phone had the potential to be even the slightest bit unreliable then I'm going to have to go back to the old alarm clock. At least with my Nokia I could even switch the phone off and the alarm would still chime (we've all experienced this with the old school phones) but I notice that android hasn't managed this yet.
kiwiBratwurst said:
Was the phone fully charged when you woke up? If not I would guess something went wrong with the laptop..
I've never left my phone plugged into a laptop for charging, I always use the wall plug overnight.. And don't worry, plugging your phone in every night is not bad for your battery it control's the charge and drops down to 98% when it gets to 100% before charging again.. This trickle effect on a li-ion battery is fine (would have been bad for nicad or nimh tho) and your using a laptop usb which only delivers about 500ma that's a really nice slow (low C) charge rate, li-ion and li-poly batteries love to keep topped up, what they hate is to be discharged to much. (my 2c)
If you're really worried about this (random shutdown) happening on a work day then use the wall charger the phone came with.. Just to eliminate any other factors that might have contributed to it turning off (use the laptop on your days/nights off to try and replicate the fault) would be interesting to figure it out what caused it..
Kiwi
Sent from my MT15i using xda premium
Click to expand...
Click to collapse
Thanks for your thoughts Kiwi (I've only just figured out who this is ) - The laptop was in sleep mode and from what I've experienced the only thing that works when in this mode is the usb ports - the Wifi and the Bluetooth shut down and I'm guessing that the processor mostly shuts down too? guessing here?
But even so what on the computer might cause the phone to crash?
hilfordjames said:
I'm not sure why charging it via usb is going to do it any harm? or was the guy in the shop trying so say that its not good to have the phone plugged into the charger for hours on end once it gets fully charged?
Click to expand...
Click to collapse
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
But even so what on the computer might cause the phone to crash?
Click to expand...
Click to collapse
Normally if phone crashes it reboots right ? instead switching off ?
Thilina said:
Sorry if my earlier post was confusing,he told me its not good to have it plugged into the charger for longer periods of time after its fully charged.I too normally charge it with pc as phone came with one usb cable + charger plug with usb port & usb cable is always attached to my pc.Anyway about that keeping it for the whole night is bad theory I'm not sure if its correct or wrong but I prefer not keeping it plugged in for like 6-7 hours everyday while it only need 2-3 hours maximum to fully charge.
Normally if phone crashes it reboots right ? instead switching off ?
Click to expand...
Click to collapse
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
sdk16420 said:
I've noticed that when you reboot while plugged in, it might just go right into charge mode. Try turning it on, and then plug it in righ thereafter. Likely it will not boot, but go to the charge animation.
Can't try it myself, phone's in for repair
Click to expand...
Click to collapse
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
hilfordjames said:
Hmm interesting theory - but I've tried it and the phone has restarted : (
Probably a good thing but still no closer to finding the solution except I'm wondering if it was because my ROM memory was pretty much full? So in case it was I've moved a few things from System apps to User apps in the hope that the phone wont switch off by itself again.
Click to expand...
Click to collapse
If you're rooted, I can recommend Link2SD.
HilfordJames and I have discussed this in length already so this is more for other people's benefit..
Link to sd can be dangerous, as can forcing apps to sd that don't offer the choice normally, app developers block the option to install to sd for a reason, that is usually because the app accesses services that can become corupt or crash if the app is suddenly ejected from the phone (like when you mount the sd card on the computer) so its best to leave those apps on the internal memory.
The most likely reason for the overnight shutdown would be (as you said) that you had filled your system memory up with user apps.
Sure enough once you've deleted all that bloatware from the system you have heaps of room just begging to be filled in the system partition.. But you gotta leave some room in there (about 60-70mb should be enough)
I think another thing could be if your computer somehow woke up in the middle of the night and accessed (auto mounted) your phones sd card, sounds unlikely but I've had laptops run scheduled updates in the middle of the night when they were supposed to be "asleep" if this happened and you had an application running off sd card that uses phone services (like Wifi, bluetooth etc) this may have crashed the phone.. And as it was plugged into power remained shutdown.. Once again (AFAIK) these apps should be installed on the phone not sd card. (games and similar apps are fine on sd card)
Just a couple of theories, but I think we are on the right track
Kiwi
Sent from my MT15i using xda premium
Yip all good.
Since transferring a lot of the files/apps back to user memory I've not had the phone auto shutoff and I've tested it by leaving it on the CPU at night as well and it seems fine - although I now charge it from the wall charger if I'm working the next day just to be on the safe side.
So last night before I went to sleep, my NT had about 40% battery life left in it. I'm currently running the final alpha build of CM7. I've been experiencing really bad wifi loss issues and have kept the 'Never' option enabled under the wifi sleep policy (thinking that would help hold the connection).
I woke up to find the NT was turned off. Figured that was odd as I was only asleep for about 5hrs. I turned it on and then noticed it got into the OS and then died. I did see the battery icon was red briefly.
I then plugged it into the wall and it was boot looping. I saw the 'n' logo pop up, screen went black, 'n' logo, etc. etc.
After numerous attempts of holding down the power button for 20+ seconds, holding power+vol down for 10 seconds, plugging it with or without an sd card into the wall and computer, nothing is happening.
The computer does see something as I'm hearing the common connected/disconnected tone from the USB port. Now I'm noticing that plugged into the wall, the 'n' on the cable stays orange. It never turns green.
Did it go 'poof' in the night somehow?
[EDIT] Ok after leaving it plugged into the wall for about 15mins, it suddenly turned on but had a google framework FC error. Yeah, not sure what I should do at this point. It appears to be charging...
It's been noted by others that if the power level goes below 15% you mustn't turn the device off if you don't have the original charger nearby. If it dies you need to charge it with the original charger for a bit before it'll power back up.
I assume this means that you can't run it off the cable while you've got a completely dead battery. That kind of stinks but isn't too surprising, a lot of devices are like that.
So does that mean that if the device is <40% of battery I need to plug it in if I won't be around it for a while? Not sure I'm cool with that. Battery life was great all day yesterday but somehow it dropped 40% in under 5hrs while asleep.
I can't really say much as I haven't dealt with it personally. People were talking about it in a couple threads about the NT's charger and unique 12 pin cable.
Here's what I understand from what I've read:
You can run it until it's empty all you like. You'll just need to use the Nook's factory charger (or a compatible 2A charger with bridged D- and D+ pins) AND (this is the important one) the factory USB cable to charge it.
If you run it until it dies you have to charge it for a little while before it'll turn on again, BUT you have to use the original cord and charger. It won't charge off of a regular micro USB cable nor will it work if you're using a 2A or smaller charger that doesn't have the middle two pins bridges (the Apple UBS chargers won't work nor will your PC's USB ports, for example).
The NT will charge, albeit slowly, if connected with a third party cable or USB charger (without the data lines D- and D+ bridged), but not if the device's power has been depleted.
So I suspect something sucked up a lot of juice while you weren't using your NT. Not a huge deal, but definitely annoying. Plug it in for 15 minutes and you can get rolling again.... BUT only if you're using the original charger and cable. Lovely isn't it? It's not a huge problem but it is annoying. I wish you could at least use the device with a dead battery while plugged in.
I just mention the charger/stock cable thing because I'm sure someone will probably see this post in the future and may be having that particular problem resuscitating their NT.
Cool, yeah I don't specifically set out to run it down to zero but since the device is clean with minimal stuff running in the background, it's difficult to know when this might happen again. I assumed I'd wake up with like 20-25% battery left. The framework FC is also something I'm concerned about but maybe it was just a fluke.
Ah well, really do appreciate your input and I'll be sure to keep the stock cable/adapter on hand when I'm on the go.
Battery showed fully charged, I rebooted to do another CWM backup and then when it came back up it showed 84% charged. Lol. And this pic made me laugh even more. Time to get that lady from Poltergeist involved I think...
The Google Framework force close is typical of stock rooted NTs. I don't believe it ever did any harm to anything though. Just that it sometimes appears on reboot.
I'll ask one additional question as to not make another topic since it's related.
Opinions on battery calibration with the NT? That was one of the reasons I didn't charge it last night as I wanted to fully run it down and then fully charge it back up. Does the NT require this with a new rom install? That pic above shows the battery gauge clearly wasn't correct initially.
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
ckevinwelch said:
Your battery is draining overnight because wifi is running the whole time (as you stated in your first post).
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
That's what I obviously thought of at first but it didn't drain nearly as much when I was using it throughout the day. The only thing I can think of is maybe the fuel gauge itself was wrong from the start, which refers back to my calibration question.
My GS2 has the sleep policy set to 'Never' as well and only loses maybe 7-8% after being asleep for around 7-8hrs and it certainly uses more juice in sleep due to the cell communication, etc.
Hi all,
I have recently come across a problem which I cannot overcome by myself and I would really appreciate your help on this!
Phone:
Galaxy S2 (3 UK)
FW:
CM9.0.0
Description of problem:
My phone will not charge the battery. When connected to a charger, it turns itself on and immediately turns back off as there is not enough charge in the battery.
Events leading to problem:
My phone has been functioning perfectly for about 5 months (on CFW) before this happened. I had noticed that my phone ran out of charge abnormally quickly one day before this problem occurred. I did not suspect anything, and put it to charge overnight. The next morning when I woke up, the battery was out of charge (while plugged to the charger!) and the phone was abnormally hot at the area above the battery connectors. During this time, the phone would not turn on. I then unplugged the charger, and let the phone cool down. After cooling down, the phone was able to boot into the OS, but turns off immediately after that due to low charge in the battery.
What I have done so far:
Following suggestions on this thread: forum.cyanogenmod.com/topic/36648-galaxy-s2-empty-battery-boot-loop/
I suspected that my phone's firmware/kernel had somehow been corrupted. I then stripped a USB wire according to the thread, and attached it to the appropriate battery connectors allowing me to power my phone and flash the FW+Kernel via ODIN. I have since then flashed various firmwares in this order in attempt to recover my phone: Lite'ning v3.6 > Stock (3 UK Branded) > CF-Root Kernel > CM9.1.0.
Current state of phone:
I managed to charge my battery a little via my stripped USB cable, and started up my phone. After booting into OS on battery without charger connected, I have found that the phone will not charge the battery when connecting the charger while the phone is on.
However, if the OS boots automatically when connecting the charger while the phone is off, the battery status will be "Charging", but the charge goes up very slowly. (6% in 20 minutes?) What's even more weird is that if I take the charger off during this time, the phone immediately turns off. While the phone is sort of "functional" now, I'm really afraid that it will recur if my battery ever goes flat again.
I'm sorry this is such a wall of text, but I'd really like to hear your opinions on this. Thank you so much for reading
Did you solved the problem?
I'm with the same problem.
tim8871 said:
Hi all,
I have recently come across a problem which I cannot overcome by myself and I would really appreciate your help on this!
Phone:
Galaxy S2 (3 UK)
FW:
CM9.0.0
Description of problem:
My phone will not charge the battery. When connected to a charger, it turns itself on and immediately turns back off as there is not enough charge in the battery.
Events leading to problem:
My phone has been functioning perfectly for about 5 months (on CFW) before this happened. I had noticed that my phone ran out of charge abnormally quickly one day before this problem occurred. I did not suspect anything, and put it to charge overnight. The next morning when I woke up, the battery was out of charge (while plugged to the charger!) and the phone was abnormally hot at the area above the battery connectors. During this time, the phone would not turn on. I then unplugged the charger, and let the phone cool down. After cooling down, the phone was able to boot into the OS, but turns off immediately after that due to low charge in the battery.
What I have done so far:
Following suggestions on this thread: forum.cyanogenmod.com/topic/36648-galaxy-s2-empty-battery-boot-loop/
I suspected that my phone's firmware/kernel had somehow been corrupted. I then stripped a USB wire according to the thread, and attached it to the appropriate battery connectors allowing me to power my phone and flash the FW+Kernel via ODIN. I have since then flashed various firmwares in this order in attempt to recover my phone: Lite'ning v3.6 > Stock (3 UK Branded) > CF-Root Kernel > CM9.1.0.
Current state of phone:
I managed to charge my battery a little via my stripped USB cable, and started up my phone. After booting into OS on battery without charger connected, I have found that the phone will not charge the battery when connecting the charger while the phone is on.
However, if the OS boots automatically when connecting the charger while the phone is off, the battery status will be "Charging", but the charge goes up very slowly. (6% in 20 minutes?) What's even more weird is that if I take the charger off during this time, the phone immediately turns off. While the phone is sort of "functional" now, I'm really afraid that it will recur if my battery ever goes flat again.
I'm sorry this is such a wall of text, but I'd really like to hear your opinions on this. Thank you so much for reading
Click to expand...
Click to collapse
Whew that was long.. but anyway, i suggest you get the external battery charger, maybe it will do you good.
Have you tried going back to stock and doing a full reset?
Sent from my GT-I9300 using xda premium
Have you tried a different battery?
I have a stock ATT HTC One that seems to have a ghost in it. I received this unit with a completely dead battery and after charging several days it finally started. The battery only showed about 30% charge but it was enough for me to install and test a sim card. Everything worked fine so I shut it down and forgot about it. Recently I picked it up again and charged it. I have it showing 83% on the battery but it will shut down within a minute of reaching the lock screen after start up. It does this no matter what I am doing with the phone. I tried plugging it in to my computer USB and it immediately shuts down and won't restart until I unplug it. Before this when it was working it would show a discharge status once it was plugged in to USB but my computer would recognize it and the phone recognized my computer. If I turned off the phone while plugged in it would flash the red LED and then it would glow steadily until it was unplugged. A battery check indicated that the battery was taking a charge at this time I would really appreciate any direction or suggestions as to what to try yo fix this
Thanks in advance and I really want to thank everyone who does all the great work here.
hammerhead8599 said:
I have a stock ATT HTC One that seems to have a ghost in it. I received this unit with a completely dead battery and after charging several days it finally started. The battery only showed about 30% charge but it was enough for me to install and test a sim card. Everything worked fine so I shut it down and forgot about it. Recently I picked it up again and charged it. I have it showing 83% on the battery but it will shut down within a minute of reaching the lock screen after start up. It does this no matter what I am doing with the phone. I tried plugging it in to my computer USB and it immediately shuts down and won't restart until I unplug it. Before this when it was working it would show a discharge status once it was plugged in to USB but my computer would recognize it and the phone recognized my computer. If I turned off the phone while plugged in it would flash the red LED and then it would glow steadily until it was unplugged. A battery check indicated that the battery was taking a charge at this time I would really appreciate any direction or suggestions as to what to try yo fix this
Thanks in advance and I really want to thank everyone who does all the great work here.
Click to expand...
Click to collapse
I have only read one other issue like this and it ended in the phone being sent back to HTC, the partition table was corrupt if i remember right.
hammerhead8599 said:
I have a stock ATT HTC One that seems to have a ghost in it. I received this unit with a completely dead battery and after charging several days it finally started. The battery only showed about 30% charge but it was enough for me to install and test a sim card. Everything worked fine so I shut it down and forgot about it. Recently I picked it up again and charged it. I have it showing 83% on the battery but it will shut down within a minute of reaching the lock screen after start up. It does this no matter what I am doing with the phone. I tried plugging it in to my computer USB and it immediately shuts down and won't restart until I unplug it. Before this when it was working it would show a discharge status once it was plugged in to USB but my computer would recognize it and the phone recognized my computer. If I turned off the phone while plugged in it would flash the red LED and then it would glow steadily until it was unplugged. A battery check indicated that the battery was taking a charge at this time I would really appreciate any direction or suggestions as to what to try yo fix this
Thanks in advance and I really want to thank everyone who does all the great work here.
Click to expand...
Click to collapse
Hi, I saw your problem with your HTC One and it's the same problem that I'm having. Can you tell me the cable and charger you used to charge your phone? I've had it plugged in for 12 hours now and all it does is flash the red led. what does the led look like when it's actually charging? I'm suspecting that i'm using the wrong usb cable and charger.
Thanks,
It's supposed to be solid red when charging. Solid green when fully charged
Sent from my HTC One using Tapatalk