[Q] won't take a charge - Sprint HTC One (M7)

Ok Random thing but my phone and the wife's phone won't take and or hold it well... we've tried multiple chargers, cords, no luck....used gsam battery on mine and it only shows a charge after reboot but then didn't...mines running a custom Rom the wife's is stock... Is this a random fluke or something that just happens after time and age?

Might be time for a new battery.

Randomly the past day or two...it's been bad... Might be, had two put two batteries in my pick up truck Monday lol

Related

Tilt wont turn on or charge. Shows red light when plugged

Noobie addicted to flashing. The headline says it all. After about 5 -6 different flashes (mostly different ROMs), it wont turn on. And instead of the yellow light that shows when charging, it's a red one, and pushing the power button does nothing. PLEASE HELP!!
Ditto.... And I haven't had time to do any flashing (plenty of time for streaking, tho). lol. When did yours have this problem? Mine just happened last night. I have babied this one like there is no tomorrow, so there's no reason for it to just quit.
FWIW, mine happened the first night I owned it when it was completely standard (ie no flashing at all). All I did was plug it in to the charger. When I woke up the next morning it was as you described. The store reps tried every combination of new charger, new battery and new SIM card with my phone but in the end they gave me a new phone.
This is bizarre - the same thing happening to all of us on the same night?!?
I woke up late this morning because my phone alarm didn't go off. Upon inspection, I realized that it hadn't charged and was completely dead even though it was plugged in all night.
Now plugging it into the wall or into a USB port results in a red light, no charging. I can't even turn it on although it's directly connected to power.
I've flashed several ROMs, but I've been running Dutty's 7B since it was released two weeks ago or so - I doubt that's a factor.
Help? Anyone?
Ummm, ok this is really fawkin freaky...add me to the list. Running dualtouch 1.1. Hung up the phone, went back to it an hour later...dead as a doornail. Wouldnt charge, got the red LED. Luckily I'd only owned it for 27 days, so I returned it to my local AT&T store and got a new one....too many people on the same night for this to be an isolated incident...same as other users, babied it like, well, an overpriced cellphone . Methinks there is something afoot!!!
Deleted by author
Add me to the list.
Ok, this just happened to me just now...
MY 400$ PHONE JUST QUIT!!!!!
Not even 4 days old and it just gave out...
My standpoint (im a techie nerd) is this:
I charged my phone on my moms blackberry charger (~500mA)
The kaiser needs 1A to charge, so i only had half the power i was told...
When I had 89% I really had 44% and it drained really fast. So when I got home it was around 53% meaning I only had about 2% battery left (understand?) and when i pulled it out of my pocket...nothing, it wouldnt turn on SO I FREAKED OUT!!!!!!
I called HTC and they said to try a new battery, so I am going to go to the ATT store tomorrow and try another battery.
O and the reason is,
when Li-ion batterys get really low, they cease to produce the charge needed to keep the miniport active, thus resulting in any attempt to charge as futile.
Thats why you need to take out the battery and 'jump start' it by stripping a usb cable and putting the corresponding wires on their terminals (red + back -)
which will forcefully charge the battery and allow the miniport to become operable again. At which point you can resume using the HTC OEM charger (1A output at 5v) to resume the full charge. No other charger will suffice.
Im am going to try this now, you guys too and report back!
Dismissed!!!!
But my battery is fully charged...
tyeo098 said:
Add me to the list.
Ok, this just happened to me just now...
MY 400$ PHONE JUST QUIT!!!!!
Not even 4 days old and it just gave out...
My standpoint (im a techie nerd) is this:
I charged my phone on my moms blackberry charger (~500mA)
The kaiser needs 1A to charge, so i only had half the power i was told...
When I had 89% I really had 44% and it drained really fast. So when I got home it was around 53% meaning I only had about 2% battery left (understand?) and when i pulled it out of my pocket...nothing, it wouldnt turn on SO I FREAKED OUT!!!!!!
I called HTC and they said to try a new battery, so I am going to go to the ATT store tomorrow and try another battery.
O and the reason is,
when Li-ion batterys get really low, they cease to produce the charge needed to keep the miniport active, thus resulting in any attempt to charge as futile.
Thats why you need to take out the battery and 'jump start' it by stripping a usb cable and putting the corresponding wires on their terminals (red + back -)
which will forcefully charge the battery and allow the miniport to become operable again. At which point you can resume using the HTC OEM charger (1A output at 5v) to resume the full charge. No other charger will suffice.
Im am going to try this now, you guys too and report back!
Dismissed!!!!
Click to expand...
Click to collapse
Sorry to tell... but when this happening you need a repair. I got this problem 2 times with my Wizard. It's a hardware problem.
I did all the tricks you can mention but at the end it needed a repair.
I had some luck after the second time i got a compleet new MOB from T-Mobile SHOP Sales-Manager (Utrecht).
It sounds like the problem is with the Kaizer... so far everything overhere is OK.
I use only the org. loader and USB-port on my computer. Don't use a other loader than that !!!!
Just wanted to add my name to this list...
I've had my Tilt about 2 days. I haven't flashed it, but I have run several cabs on it...I didn't have it on charger when I went to bed, when I woke up, it was off. The only thing I did different than the rest of you was I tried to turn it on before I put it on the charger and it came back on saying that the battery was critically low or whatever, so then I stuck it on the charger and it seems to be ok now.
I could see it being a hardware issue, just seems weird that so many people had it on the same night, and under such different circumstances.
Also, first post...this site is great and you are all smarter than I ever hope to be
okay lets try this...remove batt....let phone sit for a few minutes. plug into power source without batt. unplg again....then plug again. while plugged into power source...put batt in...then remove...then in again. then hit the reset button. ofcorse this has nothing to do with anything. but if it was me i would try anything lol....lets see what happens.
rzanology said:
okay lets try this...remove batt....let phone sit for a few minutes. plug into power source without batt. unplg again....then plug again. while plugged into power source...put batt in...then remove...then in again. then hit the reset button. ofcorse this has nothing to do with anything. but if it was me i would try anything lol....lets see what happens.
Click to expand...
Click to collapse
lol....good one.
No wait....I must hold back the epicaricacy, don't want this happening to me as well
A moral dilemma you have caused here with your post...
(Good luck to everyone who's experiencing those problems )
H.
lesevich said:
lol....good one.
No wait....I must hold back the epicaricacy, don't want this happening to me as well
A moral dilemma you have caused here with your post...
(Good luck to everyone who's experiencing those problems )
H.
Click to expand...
Click to collapse
lol also...does the phone come on with just the power cable plugged in and no batt? im curious to know about that. the latest version of kaiser tweak has a bunch of power settings. if the phone does come one...load up kaiser tweak and get in there to see if you can mess with the settings to fix this issue.
rzanology said:
lol also...does the phone come on with just the power cable plugged in and no batt? im curious to know about that. the latest version of kaiser tweak has a bunch of power settings. if the phone does come one...load up kaiser tweak and get in there to see if you can mess with the settings to fix this issue.
Click to expand...
Click to collapse
Well, speaking for those of us with the problem, the phone won't come on WITH the battery installed and the cable plugged in... I GUESS I could try it w/o the battery... would that even work normally?
I'm desperate.
drokkon said:
Well, speaking for those of us with the problem, the phone won't come on WITH the battery installed and the cable plugged in... I GUESS I could try it w/o the battery... would that even work normally?
I'm desperate.
Click to expand...
Click to collapse
key word desperate!! lol anything works when you're desperate...give it a try. if not then we'll move on to hard resetting and see where that leaves us.
This same thing happened to me a week ago. I hope you guys have your phones on contract from AT&T, because I took mine back to the store after 2 months of use (took great care of it, no drops etc.) and they put me in contact with customer support.
Great experience with support - they will ask you to take battery out, examine the battery contacts, ask if it was dropped or put in water, ask if you tried another battery and finally ask about hard reseting. Since the device doesn't even power on in this case, hard reset isn't an option.
The tech rep imediately told me it sounded like a hardware problem and shipped me a new phone overnight. They send you a reconditioned phone (it looks brand new) without a battery or stylus or back cover. You use your old battery, cover and stylus and send back your brick with the enclosed shipping label. As long as it gets back to them in 14 days and is deemed by them not to have been dropped or damaged, you don't get charged for the replacement device. Worked like a charm for me...but we'll see in a few months time if this same problem crops up again. Fingers crossed...
P.S. They will initially quote you $12 to upgrade to overnight shipping, but make sure to tell them that the phone is for business use and you need it quickly and they should upgrade the shipping for free. Worked for me!
By the way - I never flashed a different ROM on the original phone. (Stock AT&T ROM but soft reset before bloatware intallation) So don't think it has anything to do with flashing too many or the wrong ROM!
Red light.......
I called HTC and they said something got smoked inside.......I called warrenty dept. and they shipped me a replacement.......I think this is weird too.....oh well such as life.......
Did you have to ship the smoked one back?
Kind of a dumb question yes, but if no, poke around inside to see if you cant get it working again.
happened to me too. i'm pretty sure its a hardware issue.
This happened to me as well. I'm glad there is a thread to address the problem!
The one thing I noticed that is different about this new kaiser I have is that the battery is made by DynaPack, the battery in the kaiser that has this issues was a Samsung battery.
May this be the culprit?

(Not) Brick - Didn't Calibrate Battery After ROM

Right off the bat, my Revo is non-responsive, no buttons will light, backlight, vibration, sound, and of course no splash screen since the screen isn't lighting. The only sense that it is partly there is after a time connected to USB/wall charger the battery warms as if it is charging. Yet, there is no indication during charge on the screen, it stays totally black as described above.
I have been poring over forum posts, CWR threads, and the like, but have come up short on a method of reviving this puppy. thecubed had posted something that seemed promising but doesn't work for me here. At all steps, the phone remains non-responsive and connecting it to the PC yields no mass storage connection. The only step I have abbreviated is letting it charge for an hour since the phone had charged about four hours since it shut down.
Two evenings ago, I flashed from Revolt ROM 1.0 to 1.1. It was successful but since I had just gone through battery calibration and running my battery down until the phone shut down the day before when I flashed it to 1.0, I was hoping (naive?) that I wouldn't have to do it this time (yes, naive!). So, I left the phone on all night, on the wall charger.
I was using it the next day and at one point, while using it in a low reception area, browsing the web, it rebooted on me. No biggie, had that happen in the past. After reboot however, the battery level seemed different so I wanted to get it topped off then calibrate. 1-2 hours later I noticed that the calibration app was showing the mV lower and capacity was at 70%. The battery felt unusually hot. I shut it down, removed the battery and cooled both battery and phone in a small fridge to accelerate the process (was near time to leave work).
Next boot was I recall having an extra FC, one beside the CarHome normal FC with Revolt ROM 1.1. This boot the battery showed maybe 20% capacity so I said "screw it" and deleted battery.bin with the battery calibration app (I recall the mV was low, in the 3600 range). I discharged it on the way home and left the display on to run the last couple percent down. It appeared to try and shutdown but ended abruptly. That was the last time I saw any life from my Revo.
The day after its first and only ever root, I did have an odd occurrence which I posted.
Boot Trouble - Rooted After Phone Downloaded OTA, Not Installed
That time, I had not installed a ROM yet but the phone got itself into a boot up funk. Removing the battery, connecting to wall charger, watching buttons flash ~5 times, disconnecting (which stopped the flashing lights), then battery in, power on... success! I was hoping that would happen this time around but I haven't been able to.
Full history, being my first root, I used S1C successfully, installed Titanium Backup (ran system and app backup), and RevoToolkit. The phone did download the OTA but I never let it install, instead selecting to delay it by 24hrs when it asked to install. Fearing that deadline and getting one more warning that it wanted to reboot and install the OTA, I went ahead and installed the Revolt ROM 1.0. All went fine, no drama. The next afternoon I thought going to 1.1 was going well too, until this brick hit me.
My hope of hopes is it's just a bad battery and the phone won't respond because the mV is too low. Reading thecubed's comment in his first link (above) how recoverable this phone is lends me hope.
It sounds like a bad battery. I would take it to a verizon store and see if you can try a different battery. If it still will not boot then they should warranty it out for you.
Sent from my VS910 4G using XDA Premium App
P.s. I never do anything for my battery. I charge until full then use until empty. Yesterday with moderate tI heavy use I made it from 6am until 8:30 pm
Sent from my VS910 4G using XDA Premium App
Thanks for the responses. I will be going to VZW shortly to figure this out. This phone is maybe two months old so hopefully the battery is the answer *fingers crossed*
Impressive battery life! At my office, I'm in a bit of a metal cubicle area and a bit low on signal strength. My phones will sometimes use up the battery trying to keep connected, it seems, so I am usually plugged in most of the time.
While I have your ear, thanks for the great work on Revolt ROM. I am very happy with it and look forward to its future development
Good news and bad.
The good news was they swapped in a new battery and the phone worked. Having the warranty, it didn't cost anything.
The bad news is that it looks like there may be another problem. On the way out of the store the battery was indicating 1% so I quickly got it on the charger in the car. Driving home, about 10 minutes later, I got a warning for battery temperature. Thinking the low battery may just be taking a charge and getting hot from that, I turned the car A/C on full, took the back cover off, and kept the phone in the cold air.
In about two minutes, just feet from home, I noticed the display was off. Faintly I could see the battery charge symbol that shows when the phone is powered down and charging, but the backlight was off and I couldn't see if there was any color or animation to it.
As soon as I shut the car off and the power quit, that faint display disappeared, full black, dead. Now it seems it is behaving exactly the same. I haven't fiddled with it much, holding out hope of hopes it can be started and maybe recovered.
Could calibrating the battery at the wrong time have caused something like this? Do batteries have a safety lockout if they overheat? To be fair, I was running an intensive app at the time, Waze GPS. Maybe the battery didn't keep up and the phone decided it was too low and shut off. I will post back after letting it sit, cool, hopefully charge, and see what comes of it.
My phone is behaving exactly the way you describe too. A couple of days with Revolt 1.1, and this is the only problem. I had my phone hooked to a lithium ion usb battery pack all day, and it showed "100%" while hooked up, but as soon as I disconnected the battery pack, the battery icon changed to red, then it refused to boot like the situation described in the Revolt 1.1 thread in Development. It also would not go into charge mode on the battery pack, but when I came home and hooked it to a genuine AC adapter and it went into power-off charge display. I'm going to give it a few hours on the charger before I attempt to boot it again, and I'll report back.
Still no luck. I haven't charged it too much yet for fear that it isn't charging properly. Seeing the new battery work for about 20 minutes yesterday lent me hope that if I figure out how to get a fresh battery in or just shell out for another new one, I can have a window of opportunity to change ROMs and see if that has anything to do with it.
This morning I got out my digital multimeter to measure the battery pos to neg and am getting nothing (unless you consider 0.01v something). I tested my old LG clamshell's bulging, old, and damaged 1000mAh battery and it reads 3.99v but couldn't keep my old phone up (lacks oomph now).
Comparing that battery to the Revo's, they have the same four contact pattern but different connection scheme which just stops contact when test fitting. After shaving down its casing on the bottom a little bit, it was just enough to make contact. Using four hands (yes, I am very talented ) to hold the phone, hold the test battery properly, and hold the power button, I was able to get the power-up vibration and the first LG splash screen. We lost it after that but that's likely due to the very weak test battery and/or losing contact while holding it in the Revo.
Since the spankin' brand-new battery is now reading zero, I'm left second guessing my decision of not shutting the phone down when I got the temperature warning. Maybe these batteries do have an internal protection to prevent runaway failure and it too is trash. I have no experience with this otherwise so this is just guesswork.
I'm contemplating rigging the new battery into my old LG phone to see if it can tell it "all clear" and charge it up. I'll post anything I find out here. Any other suggestions are highly welcome. Still, last ditch, I'm pretty certain I can set up another ROM to flash on the SD ahead of time, get another battery, and Clockwork to test another ROM if it's the phone or ROM. I may have had 20 minutes of uptime on the last battery.
I think I've gotten to the bottom of my problem. It's a syndrome of things that I have hopefully untangled.
First off, I had been messing with Power Manager, and wanted the phone to not sleep or timeout the display when plugged into both AC and USB. I figured that would help when I'm plugged into the computer, but it was probably a bad choice.
Yesterday I was out on a boat, which probably put me into a weak signal area, causing the phone to expend extra energy staying locked on a tower. In addition, I had plugged it into the external USB power pack, and thrown them in a bag together. This did two very bad things: 1) It allowed heat to build up from both the charging and 2) it invoked the "USB powered" Power Manager profile which kept the display active which created both additional heat AND crazy battery drain.
Here's what I think happened:
1. The battery overheated
2. The USB battery pack couldn't charge as fast as the display and radio could suck it out -- so five hours in that mode BOTH drained the internal battery AND tapped into about 30% of the external battery pack.
3. The USB battery pack will not provide enough initial juice to restart a flat-dead, overheated phone, or the firmware "knows" it is hooked to USB and refuses to start the phone -- for some bizarre reason.
So, I think my phone demonstrated normal behavior for a flat-dead, overheated phone, and hooking it up to AC brought it right back to life -- after about 5 hours of continuous charging. The battery also got very warm during charging -- more than I recall feeling ever in the past.
I'm hoping there is nothing that software power management could have done to physically damage the battery, but I assume Verizon would claim it could -- as part of the reason they forbid system modifications, and therefore withdraw their warranty if you modify.
At this point I think I have dodge a bullet, and my phone is fine -- other than a few of the quirks others are seeing in Revolt 1.1 (Phone occasionally FC, etc.)
Good to hear your phone is fine. Seems like mine is too as posted above but time will tell. I got the Revo battery set up and charging on my old phone. It seems to be connected well enough. The phone complained the first try that there was no battery but my second try has it displaying that it is charging. The battery isn't warm at all but maybe that's due to a different charging rate for the old phone's 1000mAh battery vs. the Revo's 1500mAh. Or, it really isn't connected perfectly. We shall see.
Success. The surrogate charge setup got the Revo battery up to 4.11v and indicated charge complete. The Revo completed a full boot on the battery and appeared normal.
Not normal was quick heating (still unsure of the cause). Going straight to Battery Calibrator, it indicated 68% and around 3.7v and falling. Not wanting to push my luck, I shut it down. Battery now read 3.9v. Not bad but it sure seems to be getting drained quickly which would explain all the heat. Going to set up later and see if I can get it back to stock and see if the behavior persists.
I don't know how to fix any of your issues but I would like to say thanks for giving such a detailed display of what you've been doing to fix this problem should anyone else run into this issue. Also, That picture in you one post: That is the most jerry rigged set-up to charge a phone I have ever seen in my life and I love it. Good luck getting your phone working I hope everything turns out for the best.
You're welcome. It was a bit of impromptu brainstorming with some fellow tinkerers that helped come up with a way to test charge the battery. Having it come back to life
I've come to a conclusion. Somehow, I think when the battery overheats, it must internally soft protect itself. Charging it on the old phone reset it and then it worked again on the Revo. Why the old phone works and not the Revo, unsure. That would at least explain why the battery tested at zero volts before the charging rig.
After many starts and stops on my Revo now, I have found that what was heating up first was the casing of the phone. I'm guessing heat conduction of heat from the processor as it wasn't the display which was set to minimum brightness (those are the main heat sources, right?). Looking into Settings > About > Battery Stats, it only showed Android System at 98%. It seems like the processor got locked into some some high power continuous use situation which survived reboots.
The battery gets hot later due to the high consumption and proximity to the hot casing (processor), especially with the back on. Withing 1-2 minutes from start, the sides of the phone would be quite warm and after 5 minutes becomes concerning. It seems that's why the battery was never able to get to 100%, but instead its percentage was always falling, phone over consuming greater than charge rate.
With the processor going full tilt, battery cover on, protective case on phone, sitting in a warm car without A/C, that got the battery too hot within 20 minutes. It was a similar situation with the prior battery when the problem cropped up.
I don't know what the cause of this predicament was in the first place however. The phone was plain stock, then rooted, later flashed Revolt 1.0, then Revolt 1.1. Between Titanium Backup, RevoToolkit for CWM, basically nothing unusual, I have no idea how it happened. Maybe I should have done Decrap first since I've read others doing such. Thinking back to my first post/thread, I had a boot issue and only had rooted, Titanium, and RevoToolkit, no ROMs yet.
And, don't get me wrong. I'm not placing blame anywhere, just documenting my "progress." There was a time I was on Revolt where it wasn't behaving this way. I am left without a solid conclusion as to the cause.
How to avoid the battery drain?
I had a similar situation, downgraded and then installed Revolt 1.3. Can't say what did it, but the battery got hot and drained so far it would even start charging.
I got the battery charged on the old phone, and the new one, with Revolt 1.3 is working. But I'm not sure how to make sure the overheating/draining problem doesn't occur again. After 10 minutes the phone is starting to get hot again, battery is down to 57%. With the phone on or off, it does not charge the battery, even with an AC wall charger. With the phone on, it indicates 57% charge, with the phone off, the battery icon just sits at red, no charging is happening. I erased the battery stats in ClockworkMod, but is there anything else to do? Any other ideas?
It sounds like Haxid had it happen and he got back to LG stock and unrooted, all good.
http://forum.xda-developers.com/showthread.php?t=1233668
Mine happened again this time totally dead battery. Trying to get some charge in it now to boot and remove cwm so I can take it to verizon.
Decrap 1.0 rom this time w/ CWM
I do not believe it is the rom. It has to be an app or hardware.
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Bait-Fish said:
Were you having spontaneous reboots? That's when it happened to me, after a spontaneous reboot.
Good luck. Hope it all works out.
Click to expand...
Click to collapse
No my phone is actually super stable it just is sucking battery like its candy. Been off charger only 1 hour right now and its down to 83%. It has to be an app doing it but I have no idea which one. The phone shows 64% battery usage by android system.
When mine was hogging battery, same here. All I saw was Android process.
just to add my 2 cents here. I noticed my phone draining like crazy, I tried everything, then I changed the battery. boom. everything is now stable. I'm going to try to exchange that battery I think its my drain and reboot culprit.

HTC Vivid Wont Turn On!?

Soo my phone just died and I plugged it into the charger. I left for like 10min came back and it didnt turn on.
I plugged out the charger and put it back in, then the orange like would light up for about 5 seconds then turn back off. Right after that my home, menu, back, and search button would vibrate everytime id touch them.
I tried to take out battery for 5min then insert it back in and turn it on.
Still a blank screen.
Everytime I plug in the charger into the phone. Light would come up, go away, then buttons vibrate.
Anyone have a solution for this problem?
Will be much appreciated! :good:
Funny you ask, my phone did the exact same thing for about 3 days. Was afraid to take it in since it's rooted, however figured it was worth a shot, took it in, let them take a look. They didn't bother checking the phone other than putting in a code to show the battery stats. Declared it was a faulty battery and was still under manufactured warranty so they ordered and shipped me a brand new battery. Matter of fact I just received it today and am now typing from the very same phone. It's just the battery
Sent from my HTC VIVID.
etownrider89 said:
Funny you ask, my phone did the exact same thing for about 3 days. Was afraid to take it in since it's rooted, however figured it was worth a shot, took it in, let them take a look. They didn't bother checking the phone other than putting in a code to show the battery stats. Declared it was a faulty battery and was still under manufactured warranty so they ordered and shipped me a brand new battery. Matter of fact I just received it today and am now typing from the very same phone. It's just the battery
Sent from my HTC VIVID.
Click to expand...
Click to collapse
I dont think I have a warrenty. Do you really think its the battery?
One time it successfully turned back on. I cant remember how I did it... lol
Yea its definitely the battery. I left it plugged in alllll day and nothing. It would flash for 10 seconds then turn solid for 5 then turn off. Bottom buttons would have that haptic feedback. But screen wouldn't turn on. I put the new battery in about 3 hours ago after getting off of work (they fed exed) it. And it has worked ever since. P.S. If you have att you are always under the standard manufacturers warranty for one year from purchase date. It doesn't hurt to call and ask or take it in.
Sent from my HTC PH39100 using xda app-developers app
It cant be possible, because ive actually got it turned back on before....
It just seems like everytime my phone dies I have this problem.
and it takes forever to get it to work again..
Well if it's the battery just order an anker battery off amazon. Anker is actually a great company and I have 2 anker batteries right now as spares as well as an external anker power bank for instant charging purposes.
Sent from my HTC Flyer P510e using XDA Premium HD app
zRadiz said:
It cant be possible, because ive actually got it turned back on before....
It just seems like everytime my phone dies I have this problem.
and it takes forever to get it to work again..
Click to expand...
Click to collapse
Yea probably the battery. HTC will most likely send you a new one for free if you let them know what's going on. Or just go to your local AT&T/Bell/Rogers/etc store and they'll get you a new battery.
http://forum.xda-developers.com/showthread.php?t=1717766
http://forum.xda-developers.com/showthread.php?t=1479060
http://forum.xda-developers.com/showthread.php?t=1531208
http://forum.xda-developers.com/showthread.php?t=1694017
http://forum.xda-developers.com/showthread.php?t=1769616
http://forum.xda-developers.com/showthread.php?t=1652689
http://forum.xda-developers.com/showthread.php?t=1732268
http://forum.xda-developers.com/showthread.php?t=1754534
EDIT: I have stopped looking for these threads. The more I look, the more I find. If the above threads don't convince you that there is a serious issue with the vivid, then adding more of the same problem will no longer help.
I have added this thread to a growing list of similar threads. Please read the other threads and see if your issues seem familiar.
From what I understand... Don't let your battery run out on this phone. Some Vivids kill batteries.
Solution? None yet.
1. Buy a new battery once a couple of months-ish, until someone figures out why some Vivids are eating batteries. YMMV
*OR*
2. You might invest in a external charger and see if that can bring the "Vivid munched" battery back to life. YMMV
I vote to thread merge the above threads if this proves to be the issue.
I've had my battery die several times with no issues. Of course since I have backup batteries and external chargers I just swap the battery and its all good
Sent from my VTC HIVID using the xda app
I had a similar problem a couple of months ago. Battery ran out, so I put my phone on the charger. Orange light came on for maybe 3 seconds, then the orange light would continually flash, must have happened all night once and it didn't gain any charge... Every night afterwards for about a week it was doing the same thing, only way I could fix it every time was to alternate battery pulls with unplugging the charger until the orange light stuck on. It took half an hour to get it to stay on sometimes.. But, since I've been using my new battery I've had no problems at all, even with the old battery, I try to circulate batteries all the time.. I'm at a loss as to what's causing my (old) issue. Lol, just remembered something silly and probably unrelated, but I think the problem stopped around the same time my original battery went through the wash.. I know I shouldn't be using it, but it seems to hold charge better as well this is not a recommendation to go out and run batteries through a washing machine cycle though ;-) just saying
Sent from my De-Sensed HTC Vivid using xda premium
So stupid these batteries. My dad's vivid hasnt had this issue, mine has, it did the exact same thing, I put my battery in his it wouldnt charge, put his in mine, it booted. I bought a new battery. White HTC vivid.
glad I found this thread I am having the same issue on my vivid. I unplug and pull battery but when trying to reboot orange light flashes a couple seconds and I just get feedback from the keys. I got it to work yesterday but I went ahead and turned it off and now I am back to nothing. See if replacing battery works. Do any other HTC batteries work or only ones specific to the vivid?
Potential Fix
Alright, had same problem as the OP and got my phone to turn back on by following these steps:
Plug in the phone, (get the brief orange light / Softkey vibrates) and let sit for about an hour.
Remove phone from charger.
Remove battery from phone.
Wait for about 30 seconds.
Insert battery into phone.
Do *NOT* plug the wall charger back in yet.
Attempt to power on phone.
Mine fired up to the HTC logo, and I was able to plug the charger back in. When it got to the home screen I had 28% battery life, so I'm pretty sure its charging even though its not turning on.
I'm not trying to suggest it isn't a bad battery. Or hardware. Or the universe hating you. I'm just letting you know what worked for me in the hopes it helps someone else.
Also, I haven't had the luxury to try and replicate these steps as a 100% success rate. I'm really not trying to let the phone die completely.
I just posted the same question about this strange thing a few minutes ago, only to realise someone was having similar problems.
I'm located out the US so i'm hoping one these shops have a battery for this phone.
I'm going to try g33mt4z method and try battery pull with the power on and see if that helps cause i have no other alternative for a battery if non is on island and I'll have to order one online
thanks
G
Clockworkmod does not work for power off charging...
Switch to twrp
Sent from my Vivid 4G using Tapatalk 2
Ok guys I think I got it.
What I did was
Take out the battery
Put the batter back in
Plug in the charger
When the light come on hold down Vol down and power button
When phone boots to bootlader choose recovery
you will get white HTC creen, leave phone plugged in for a while 30 mins or so
then while leaving charger plugged in attempt to power phone pn
phone should boot regularly
Finally.... don't let phone battery run down or get external charger or change to twrp as one person suggested.
I'm just glad that I was able to get my phone booted, as I live outside the US can't go to an ATT store and HTC phones aren't the most popular here.
I'm wondering if I should order a battery from Amazon just in case

Captivate - Phone won't read a charge past a certain %

Howdy XDA. Figured its about time I made a post here.
Had a cappy for a year and a half now. Love it to death. In the past... 2 months though, I've noticed the "max" percentage of its battery seems to be dropping.
I ran Froyo2.2 for the longest time, and at some point the batt wouldn't charge past 95%. I was fine with that, until the max became 89. Then 85. Then 70.
So then I bought 2 new batteries. 1800mAh ones. Got a nifty universal charger from the same manufacturer. I charged a battery to full in its own charger, popped it in, expecting my problems to go away. Booted it up... 79%. Okay... improvement I guess, but thats still not what I wanted.
So then I recalibrated, erased the battstats file, recharged, drained, recharged, drained. No difference.
Tried recal with the OEM battery, no change.
Tried charging OEM with new charger, nothing.
New battery in old charger. Nothing.
Two new batteries, one charged in the new charger and one charged in the phone, no change.
So then I flashed a new rom, CM10 HellyBean. (Love the ROM by the way, beautiful)
Booted it up with a new battery, same thing. Okay, need to recal again, new ROM.
Recalibrated, whole 9 yards, no change.
Repeated above attempts, no change.
Well so then I decided to just live with it for a while and watch for differences, and about 2 weeks pass, i wake up... and new batt #1 is stuck at 34%. I grab New Batt #2 off of its respective, manufacturer matched charger base, and pop IT in, 48%.
I grab the OEM battery, which has remained untouched and fully charged for 3 weeks, pop THAT in... 19%.
So I'm at a loss here. I've tried recalibrating 3 different batteries, 2 of them bought specifically because of this, 2 different USB cables on at least 3 different USB charging bases, OEM cable and base included, new ROM with all previous steps repeated, and not one thing has produced a positive result. Heck, its simply gotten worse.
Tell me, XDA, is my beloved Cappy at its end?
EDIT:
Oh yeah, also tried taking the OEM battery, which if its % was indicative of its mAh level... put it around 350mAh... and rigging it via test cables to an old samsung phone that usually took 650mAh batts... and it read it as full. I don't know if thats simply because I took a 1700mAh batt and rigged it to a 650mAh phone, or if it sheds light on the current issue, but I forgot to add that.
This is a sad story.
Does the phone shut off when it reaches zero, or does the battery drain progress slower than one at the same percentage being read correctly?
Just wondering if the % is being read wrong, or the charge of the battery...
It does shut off when it hits 0%. At around 20% it reports itself as fully charged, and waiting longer past that i've gotten it to... 33%. It got to 60 one day, but I've been unable to reproduce that result.
From 33%, it drops to 20 within 2 hours, then it takes another 3 or so to hit single digits, and from 7% down, it'll drop to like... 2%, then go up to 5%, and then back down finally to zero with a total run cycle of around 12-16 hours.
Took it to a phone repair place, they said the OEM and one of the new ones was bad (and they damaged one of my new ones, gee thanks. Glad you didn't charge me for the help) and that the charger port was fine.
Then they slapped it on the charger, waited til it got to 20%, said it was fine, and home i went knowing that they didn't do a damn thing except pull a "did you plug it in" with my phone.
I don't know what its deal is. It operates normally, but it just doesn't report normally at all.
Did anyone find anymore info on this. My wife's Cappy does this. A random drop of about 25-40% of battery from out of no where.
RamblingBarba said:
Did anyone find anymore info on this. My wife's Cappy does this. A random drop of about 25-40% of battery from out of no where.
Click to expand...
Click to collapse
You might need a new battery. That Cappy is 3years old.
You can also download BetterBatteryStats to see what triggers the battery drain.
BWolf56 said:
You might need a new battery. That Cappy is 3years old.
You can also download BetterBatteryStats to see what triggers the battery drain.
Click to expand...
Click to collapse
It's the same song and dance. New battery and several paid or free apps to check it. It's very random and I think it's in the ROM somewhere as it relates to this device. Next move is a kernel flash.
Sent from my NookColor using xda app-developers app
RamblingBarba said:
It's the same song and dance. New battery and several paid or free apps to check it. It's very random and I think it's in the ROM somewhere as it relates to this device. Next move is a kernel flash.
Sent from my NookColor using xda app-developers app
Click to expand...
Click to collapse
You'll need to use BBS to find out what's causing it. We can't help you by just guessing :/
what's the reported battery voltage when it stops charging?
sent via carrier pigeon, jungle drums and smoke signals.

Charging problem

So my HTC One does something really weird sometimes and im afraid if this keeps going on something bad will happen to it.
since i got 5 months ago this has happened like 4-5 times. and i charge it every night. so, sometimes when I charge it and go to bed I wake up and check the phone and even though it was charging when I left it it has only charged for like 20% and even though its connnected to the charger the charging icon wont show. plus the phone is too hot. and i dont mean warm or hot on the back. I mean too hot to touch everywhere, not only the back. Everywhere it has aluminium its too hot. this has only happened 4-5 times and I immediately take it off the charger wait a bit to cool off and then start charging it again and everything is fine. While its hot no warnings pop up and the phone works just fine, but its extremely hot and even though its connected to the charger it doesnt charge. why is that?
bump
Hey,
This might be a problem with the charger.
Try using the original charging set provided with the phone.
Is there anything you do with the phone that may be considered out of the normal when you charge it?
Worst-case scenario, this might be a hardware fault. In that case you should be able to claim it under warranty.
Good Luck
Something similar happens to me on occasion. It'll be plugged in but when viewing in/out mah, it actually shows it's draining. Less than when it was unplugged, but still draining although it says ac plugged in. (using battery monitor to view btw). When it does that, and it's left plugged in (like overnight), it's abnormally hot when I check it. I have to unplug it and then plug it back in (sometimes a few times) before charging levels go back to norm.
Sent from my HTC One
It happened on me for 1 or 2 times as well, the only different is mine is not really hot. After i flashed custom rom, it seems everything is fine. I guess maybe there are some bugs in the original rom. Now i am using the rom based on google edition. Good luck
I am using the original charger and it does this but it also have done this with a samsung charger i have used some times. something else that I noticed is that when I'm charging and using the phone sometimes the battery percentage drops.

Categories

Resources