Related
Hey there,
I have my Vibrant for a good year now since it came out pretty much. Last week it just stopped charging out the blue. The battery is completely empty and shows a thermometer with a warning sign and stops charging seconds after its plugged in. So I assumed it might be a battery malfunction and I got my spare battery in as soon as I came home and tried charging - same problem. I think it is highly unlikely that both batteries fail at the same time. Therefore, I assume there is something wrong with the temp sensor in the phone. I saw a few people have a similar problem with the epic 4G, but the discussion got really side tracked by other issues. My phone is rooted, but I was running stock froyo, so that shouldn't be the problem or should it?
I just wanna know if anybody had the same problems and if there is a quick solution, I google and forum searched a while but as soon as you throw in the term battery it gets spammed with battery life discussions.I just checked my files I have on the phone, apparently I have the premium insurance - does that mean I just can go to the next Tmo store and get a replacement? Any feedback is greatly appreciated.
Phill
Well for your problem, i suggest you try a different rom and see if the problem persists... maybe its a bug
And as for insurance, you mail the phone in and pay a deductible, which should be like 135$ or so. They send you a refurb.. or if you say it wus lost, you dont have to mail in phone
Sent from a cell tower to the XDA server to you.
thanks for the quick reply. Is there a way to reflash without a battery?
I don't see it as a bad thing. If your phone gets too hot and keeps charging that's going to burn something inside. When my phone won't charge I know I have let it down. So it can cool down. But to fix your problem reboot the phone. You can keep charging it after it boots up
Sent from my SGH-T959 using Tapatalk
pro1st said:
thanks for the quick reply. Is there a way to reflash without a battery?
Click to expand...
Click to collapse
As long as your phone can run successfully for a couple minutes, i dont see why not
Sent from a cell tower to the XDA server to you.
Mine did something similar. I picked it up after putting it on the charger. It was hot and would not come on. I unplugged it and let it cool off for a while and it cleared up.
I got that message once...
Vibrant was in a car dock, with power.
It was *HOT* out and sun was hitting the back of the unit. (A/C on of course)
Google Navigation was running (display brightness max)
Google Listen was running
Bluetooth was passing music to a speakerphone
When I run the phone with that setup, the charger can't even keep up with the phone power needs. The battery level slowly drops. No question the phone is working hard.
This was a true heat issue... I removed the charger and turned off the display to let it cool off a bit. (I was almost home).
So the question again, is your phone hot or is it a false reading?
Robert
Hey,
I am sorry I didn't clarify the actual battery temp. It is normal - so its neither in the sun or in a too cold spot when I try charging it. The phone probably runs for one for a few seconds before turning off so there is no chance of the battery stats wipe. I think I will try to find an external charger and try to charge the batteries this way to have enough juice for flashing a new rom. Thanks for all the replies!
Does it charge the battery with the phone off? If not, I don't think a new ROM will help.
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
c0olcast said:
Hey there! Wondering if you got around to solving this. I've got a Vibrant doing the same exact thing. Battery being cool it sais that is overheating. Did changing the ROM solved it or not?
Click to expand...
Click to collapse
Sorry for resurrecting an old thread, but a resolution never seemed to be made here. Has anybody found a fix to this?
As of yesterday, my wife is having the same issue with my old Vibrant phone which she now uses. It's flashed with Bionix V 1.3.1 and Tigerblood overclock to 1.2ghz. This could be the issue, the Tiger Blood overclock, but I'm not sure. I'm out of the country for three weeks and currently she's left with a dud of a phone that keeps giving her the temperature warning in the triangle when plugged in while the phone is powered off followed by it stop charging. When she turns it on, she gets to the SD card check and then the phone completely freezes. Once in a while it's able to stay on for a minute or so before freezing, but more often than not the phone does not fully turn on and just goes frozen after a few seconds, sometimes at the Tigerblood logon screen before making it to the desktop. Me being 4000 miles away doesn't make it easier to help her but I've recommended she leave the phone unplugged, battery out for the night to see what happens. I also told her to take off her silicon case thinking maybe that has something to do with the overheating. Well after 7 hours of her letting it sit to cool off like that, with the case off, she plugged it back in and is having the same issues as yesterday. Absolutely no progress made. One of her colleagues said she should try leaving the phone in rice confused:) so she's giving that a go and another guy in a phone shop who she went to for advice after work said that the motherboard might need replacing. I'm convinced all it needs is to have the Tigerblood removed or reflash a rom onto it but there's really no knowing unless I have it in my hand.
Is there any quick fix to this problem without having to do all that? Surely there must be a way to charge the phone without it heating up and freezing up. She's tried plugging it into different rooms, on her laptop, etc, none seem to get rid of the temperature problem. I've had the phone since August 2010 and never had any issues with it. I also never once saw that temperature error message so was taken aback when she showed me it over skype. I just upgraded to the S3 and gave her the phone 2 weeks ago, but surely it shouldn't just die out just like that? Thought the Vibrants were made tougher than that?
Any help would be greatly appreciated. Much thanks in advance
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Update- Phone doesn't even turn on anymore, no signs of life
danny_extremex said:
Its most probably a kernel issue or a bug in the rom; so the only way to find out is to flash another kernel/rom..
P.s Vibrants are rock solid
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
polosprt009 said:
Will be looking into reflashing another kernel/rom when I get home in a few weeks time, but it must be noted that the phone has been showing no signs of life for the last few days now. After letting it sit out for 7 hours on the first night, battery out and everything, she went to plug it in the following morning and this time absolutely no notification came up. Not even a lighting up of the phone or anything. No signs of life at all. Every time she hit the power button nothing occurred. The phone still heats up and after a few minutes while plugged in and gets very hot to the touch again but no matter how many times she attempts to turn it on, nothing happens.. She's tried plugging it into her computer via usb, into electric sockets in other rooms, even in the bathroom in one of the 115 volt electric shaver outlets in the bathroom (we live in the UK currently), and none of these ideas worked. Still no signs of life. It has been this way for three days now and is frustrating as I can offer no advice to her to get the phone to turn on anymore.
What on earth can be the problem? Has this happened to anyone before? And is there a fix to this or can we consider the phone to be a paperweight at this point?
Click to expand...
Click to collapse
Some kernels require a certain amount of power to fully boot the phone up and will not charge until it has 5% battery or so. I personally think her battery may be unable to hold a charge or like I said before it doesn't have enough juice to boot the phone because of the kernel. There is a way to charge the battery with the phone off. You can use ANY kind of usb cord, I used an old printer usb cable when I had to do this. All you do is cut off the side that is not usb and strip the positive and negative wires(red and black), then place the stripped wires on the positive and negative connectors on the back of the phone and insert the battery (make sure it's a snug fit). Plug the usb end into your pc and charge the battery that way, DO NOT let charge for over 2 minutes at a time. Wait five minutes and do it again if you have to. If she gets it to boot up, I would definitely flash a new kernel first to see if thats how the problem originated.
Sent from my SGH-T959 using xda premium
If this device has gets completely drained, it is painful to recover. You will have to try possibly 100 times various chargers, removing the battery etc.
The screen stayed black with an occasional light, but wouldn't power on at all.
It finally worked but you really have to be tenacious.
2 batteries 1 smirk.
edit--
i'd still be messed in this case, unless one also had the standalone charger...
now i'm terrified of letting the battery drain!
Knock on wood...but I've never had this problem.
Sent from my ADR6425LVW using xda premium
u just have to let the led blinking light turn solid then give it a go and it should be good to go
Yeah I never had this problem and my phone has died several times. I just let the blinking light go solid and turn it back on. I did notice that my old LG chargers are a bit finicky with this phone though.
i though this happened to mine too. my phone died, i plugged my charger in but nothing happened. eventually the orange light came on, it just takes a while.
Thank you for something we already have threads on...search is your best friend...
Sent from my ADR6425LVW using XDA App
I have a standalone charger but it only charges to 97%. I hope it's not messing up my batteries.
Sent from my HTC Rezound
Just let it sit on the charger for a few minutes.
The light will blink for a while, but it will still charge. If after 10 minutes the LED is still blinking, unplug the charger and plug it back in.
Run mine dead at least once a week. Which should be common practice. Never a problem. You should definitely let it charge a while before expecting it to fire back up.
nosympathy said:
Thank you for something we already have threads on...search is your best friend...
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Don't be "that guy".
I exchanged my one-week-old phone yesterday because of this: my phone went dead overnight, so I plugged it in in the morning and got nothing (no lights or anything). I left it charging for about 20 minutes while I got ready for work and still got nothing. When I got to work, I stuck it on the charger again for about 3 hours, and still got nothing. I went to the nearest Verizon store to see what they could do about it, and they didn't even look at the phone, just replaced it.
Works for me, I guess.
Have had this happen twice now (with oem batteries). My problem was though, left them on the charger all day, then they wouldnt turn on or do anything.
sometimes i wonder if the people who said their phones never came back on, actually just freaked because it didn't turn RIGHT back on and frantically started plugging it into tons of chargers thinking all sorts of things could be wrong, when really nothing was.
I have never had a phone NOT come back on, and this is with 2 years of HTC phones (at least 2 dozen phones when you consider all the replacements for various things here and there) and not a single one has failed to charge back up.
not saying anyone is lying, but when something happens that were unfamiliar with, its easy to start getting freaked out.
Think about it, would a manufacturer make a device that has a high tendency to fully discharge, "break" should it actually discharge? Sounds a bit silly...
Ran mine sead before and recharged no problem. You just have to plug it in and wait. It's not gonna turn on immediately. Let it charge.
lithium630 said:
Don't be "that guy".
Click to expand...
Click to collapse
Someone has to be that Guy...we don't need 30 threads on the same topic cause people are to lazy to see if someone figuired something out before them.
Sent from my ADR6425LVW using XDA App
nosympathy said:
Someone has to be that Guy...we don't need 30 threads on the same topic cause people are to lazy to see if someone figuired something out before them.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
In almost every thread on here, someone has to complain and tell the OP to search. There are thousands of threads to go through. Even after narrowing it down with a search they could still miss the answer to their question.
No, this is a problem I've had as well, twice in fact.
The first time my battery ran down from 99% to dead because I was unaware that it lost and was searching for a signal. I couldn't get it to turn on after hours and hours of charging. I finally took it into a Verizon store, and they used a different charger to get it turned back on.
It happened again last night. I was downloading something, the signal was lost, and the battery died prematurely. I used the stock charger to charge it overnight, but when I woke up this morning, the phone refused to turn on. I charged it with my HP Touchpad charger, and it came on about five minutes later.
The stock charger failed to revive the battery BOTH times.
So my solutions are, 1. don't let the battery die. But things happen and sometimes it's unavoidable. 2. If the battery dies and you can't get it charged after hours, try using a compatible charging cord from a different device to get it moving.
Things that are unavoidable happen, but I make darn sure my battery never dies 100% after something that happened with my Droid Charge.
It was custom ROMed and all tweaked out etc and I fell asleep one night when it only had about 10% left. It ran all night and was off in the morning.
When I plugged It in and started it up, every single app started force closing on me. This had never happened before and it was so bad the thing was totally unusable.
Luckily, I had made a nandroid BU the day before and restoring it fixed it.
No idea how true this is, but I've read a few other posts with people having this issue and they found that if you pop the back, pop the battery, plug in, insert battery and replace back. Then you let it sit for 20 or so minutes and it should start up again. Love to know if this resolves the issue for those having it though.
I was running today while running my music and the RunKeeper app. After about 20 minutes, the whole phone died, although it was charged. Ever since then, it won't do anything unless plugged in to the wall charger, and even then, I have to hold the cord in, and it only stays on for about a minute before dying. It says it is 100% charged. The phone is only about 35 days old. Any suggestions are greatly appreciated. I'm at my wit's end!
Have a second battery laying around or easy access to see if it is a physical battery issue?
Sent from my MB855 using XDA App
hmmm....if you were running, possible water damage due to sweat????
Revision: May i say "liquid"damage
Where did you purchase it? Try taking it back and showing them that it refuses to turn on for some reason.
a common problem with many photons was a loose battery. as someone else said, if u got it wet from sweating . .. that would do it too.
jkibz said:
I was running today while running my music and the RunKeeper app. After about 20 minutes, the whole phone died, although it was charged. Ever since then, it won't do anything unless plugged in to the wall charger, and even then, I have to hold the cord in, and it only stays on for about a minute before dying. It says it is 100% charged. The phone is only about 35 days old. Any suggestions are greatly appreciated. I'm at my wit's end!
Click to expand...
Click to collapse
I had a similar problem with a Samsung after running. Sadly it was water related, and while I hate to point that direction ... that's the first place I would look. Pull the battery, let it dry out as much as possible and if possible (read you have one handy) try a different battery after a good few hours of drying.
The Samsung in the end had enough damage that I just ended up getting a new phone. Which brings me to the Photon.
Okay, so yesterday I charged my phone overnight, it was obviously charging, the red light was on. I woke up this morning, and BAM. No signs of life. at all. No "dim red light" or anything, i can't turn it on. I've tried everything, I tested the battery and realized that the battery does, in fact, have charge (~3.4-3.5v). I've looked at many many other threads, most of which are similar, very similar, except they have the red light blinking or dimly lit. My light won't even turn on when I charge it.
I tried that trick with command prompt where you type adb reboot-bootloader and everything, and it said "no device found". Does this mean that my phone is completely useless? Did it magically become bricked? (I have in fact rooted my phone, which is why I'm in concern, however I have s-on, which is supposed to protect from bricks right?) I haven't flashed anything in maybe 2 months. Can that even happen though, it works, but then suddenly it doesn't, because of a root problem? The only other thing I think i can say is that my phone drains battery like CRAZY. I was thinking about getting a new battery beforehand, and now im definetly considering it, but it shouldn't be the batterie's fault should it? it has a charge after all. Maybe the circuit is fried. Considering i bought it new from bestbuy about 5 months ago and was using the stock adapter and usb cord to charge it, do you think I'll get a replacement if there's no way to fix it?
Thanks for reading this, i know this must be such a nuisance with all my questions and everything, but my phone is really important to me and I don't want to make a mistake or anything with a phone I paid $300 for.
Any help would be greatly appreciated.
conez4 said:
Okay, so yesterday I charged my phone overnight, it was obviously charging, the red light was on. I woke up this morning, and BAM. No signs of life. at all. No "dim red light" or anything, i can't turn it on. I've tried everything, I tested the battery and realized that the battery does, in fact, have charge (~3.4-3.5v). I've looked at many many other threads, most of which are similar, very similar, except they have the red light blinking or dimly lit. My light won't even turn on when I charge it.
I tried that trick with command prompt where you type adb reboot-bootloader and everything, and it said "no device found". Does this mean that my phone is completely useless? Did it magically become bricked? (I have in fact rooted my phone, which is why I'm in concern, however I have s-on, which is supposed to protect from bricks right?) I haven't flashed anything in maybe 2 months. Can that even happen though, it works, but then suddenly it doesn't, because of a root problem? The only other thing I think i can say is that my phone drains battery like CRAZY. I was thinking about getting a new battery beforehand, and now im definetly considering it, but it shouldn't be the batterie's fault should it? it has a charge after all. Maybe the circuit is fried. Considering i bought it new from bestbuy about 5 months ago and was using the stock adapter and usb cord to charge it, do you think I'll get a replacement if there's no way to fix it?
Thanks for reading this, i know this must be such a nuisance with all my questions and everything, but my phone is really important to me and I don't want to make a mistake or anything with a phone I paid $300 for.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I'll do the best I can. Many people have had this problem and sometime using an external charger and or using a different battery has fixed the problem. If you can get a hold of an external battery charger and put the battery on it all night it should work. Post back with results.
This is, at least in my experience, the oddest crap for a phone to do.
Im working, phone is next to me on the charger. I receive and reply to a text, than a few minutes later press the top button on my mophie case to power the screen on to check the time, and it doesn't respond. At all, ever again.
I had been rooted and running CM for a solid few months without major issue. I had not made any changes, major or minor, to the phone in the previous several days.
At one point I plugged it into my computer. and got a message asking for QSUSB_Dload. (or something simiar). I tracked this down, downloaded and installed, with no change.
Im sending it back to HTC. In my reading I have come across posts from several people who had send unlocked phones in for this exact repair without issue.
I've also read a few people mentioning excessive time on a charger being the culprit, which got me thinking of the mophie juice pack. Before I use one again, I'd sure like to figure out what the bloody deal is.
MissDjinn said:
This is, at least in my experience, the oddest crap for a phone to do.
Im working, phone is next to me on the charger. I receive and reply to a text, than a few minutes later press the top button on my mophie case to power the screen on to check the time, and it doesn't respond. At all, ever again.
I had been rooted and running CM for a solid few months without major issue. I had not made any changes, major or minor, to the phone in the previous several days.
At one point I plugged it into my computer. and got a message asking for QSUSB_Dload. (or something simiar). I tracked this down, downloaded and installed, with no change.
Im sending it back to HTC. In my reading I have come across posts from several people who had send unlocked phones in for this exact repair without issue.
I've also read a few people mentioning excessive time on a charger being the culprit, which got me thinking of the mophie juice pack. Before I use one again, I'd sure like to figure out what the bloody deal is.
Click to expand...
Click to collapse
Need so much more info.
M7what?
CM10.what?
Hboot soff/on version?
What happened when you plugged it in?
What version of all the things?
Sent from my One using Tapatalk
ALL the things>?
Um...I didn't know anything came after the M7....? It's your standard HTC One, ATT. As it is now en route to the good folks at HTC, I cannot look at it to be sure.
Im fairly sure I was on CM10.2.
What other things would be important? I assure you I do not know the version number of all the apps that were on that bloody phone.
When I plugged it in, the computer made the I found something in my USB port noise...than just a second later played another noise. I had never ever heard it play that sound before.
It informed me that it was searching for those drivers I mentioned. When it couln't find them., I went out and got them installed. It didn't make a difference.
I tried to run the adb but it would not find the device. Small wonder, what with not having the proper drivers for it's current, jacked up state. I tried recovery., I tried mirroring the screen, nothing. the home and back lights are dead, LED is dead, screen is dead.
Yet., somehow, the computer recognizes something is there.
If anyone knows what the devil is did, I'd be pleased to know.
MissDjinn said:
Um...I didn't know anything came after the M7....? It's your standard HTC One, ATT. As it is now en route to the good folks at HTC, I cannot look at it to be sure.
Im fairly sure I was on CM10.2.
What other things would be important? I assure you I do not know the version number of all the apps that were on that bloody phone.
When I plugged it in, the computer made the I found something in my USB port noise...than just a second later played another noise. I had never ever heard it play that sound before.
It informed me that it was searching for those drivers I mentioned. When it couln't find them., I went out and got them installed. It didn't make a difference.
I tried to run the adb but it would not find the device. Small wonder, what with not having the proper drivers for it's current, jacked up state. I tried recovery., I tried mirroring the screen, nothing. the home and back lights are dead, LED is dead, screen is dead.
Yet., somehow, the computer recognizes something is there.
If anyone knows what the devil is did, I'd be pleased to know.
Click to expand...
Click to collapse
I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.
Sent from my One using Tapatalk
Most assuredly...
TheEgonSpengler said:
I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Most assuredly, the issue was not a dead battery. This I know to be true for several reasons --
60% charge when it went dead
On the OEM charger
left on the charger overnight with no change
no LED response when put on the charger.
MissDjinn said:
Most assuredly, the issue was not a dead battery. This I know to be true for several reasons --
60% charge when it went dead
On the OEM charger
left on the charger overnight with no change
no LED response when put on the charger.
Click to expand...
Click to collapse
The last charged state has nothing to do with the battery ability to discharge or recharge it can indicate the batteries health but is a piss poor measuring stick.
Batteries just go bad, 100% - 1% if a cell fails or something else goes wrong it's done no matter how much it's charged.
So no, you don't know unless you tested it.
TheEgonSpengler said:
I'm wondering if the battery wasn't dead. Not enough people are coughing up the fastboot getvar to be sure.
Sent from my One using Tapatalk
Click to expand...
Click to collapse
Sent from my One using Tapatalk