TLDR: Skip to TLDR near the end!
Well, this is probably the tipping point that will make me demand a new phone from Magenta, because this is getting out of hand. My phone will periodically stop charging, for seemingly no reason at all. Usually its when it has relatively low power already that it decides it doesn't want to recognize the cable being plugged in.
Usually, I will just pull the battery and drain the remaining power via the power button, put the battery back in and all is well. Lately, it happened that it stopped charging and didn't respond to battery pulls, then got so low that it refused to even boot (flashing empty battery icon). This lasted about a day and after I had went into the T-Mobile store (Which they MADE me drive 30 minutes to the store to be there in person so they could hand me a piece of paper saying they'd mail me a new unit. Bull**** in and of itself.) the phone decides it wants to start charging again. After a few more frustrated battery pulls and doing nothing new with it.
When I get my new phone (no new battery), I put the battery in that one and use it, and all seems fine. This one has worse screen bleed (top left corner was pretty much a spotlight), but I'll take that for a working phone at this point. A few days ago I was just heading out on a 3 hour trip for a short vacation when the phone reboots on me while I'm listening to podcasts. Never had this happen with the other 2 G2X's I've had. Yesterday, the thing decides to stop charging as well, but a battery pull while the device was still on did the trick and it charged again.
Once I got home I figured I'd use the original G2X, as that has everything still on it, and migrating those app settings and data is a pain. Also, if it has worse bleed, reboot problems, and the same battery issue, its worse than what I already have.
(TLDR)
Now to my current problem. The phone, once again, stopped charging and has again discharged to where it wont boot. My questions:
1) Is there a way to recover my battery without just letting it sit and praying it charges again?
2) What is the underlying issue here that could cause this? Bad software? Bad hardware (in the phone itself)? Bad battery?
3) What is the best way about getting a new phone for free (or as close to free as possible), preferably an upgrade like the Sensation 4G? I don't want to deal with my local store, as they have been proven to not know ****, and the first line of defense on the phone isnt much better.
Well i am not an expert here but Just by process of elimination it seems to be the battery. They gave you a new phone and not a new battery and now it is doing the same thing. It has to be the battery so I would go back to the store and tell them that they gave you a **** phone as a replacement and it was the battery that was the problem the whole time. They shold be able to give you a new phone and battery. Tell thewm the screen bleed is terrible and the phone yoyu had was really good except for the battery issue. Maybee someone else can give a second opinion about that battery though. Dont just go on my words I am not a pro. Good luck man.
Charlie
Related
as i said in the title when i use wifi i get a about 2-5 mins of use out of it, but then it will cause the pda to shut down, even when i have full battery and its plugged in, and it wont completely turn back on till i plug in a charger, occasionally even this wont help for a while, i also have had some problems with the battery, like sometimes it wont be recognised by the pda so it wont turn on and will show the red light when i try to charge it, could that cause this problem?
Sounds like new battery time.
My last one used to die if I had the backlight on for more than a few mins, it lasted a year (the original battery).
Got a new cheap one from eBay, seems to be going fine with good battery life.
thanks i thought this was the problem so i bought a new battery last week, still hasnt come yet though
Hi
i have the same prob too, but when i plug it into the charger it won't turn off!!!
this is an actual common problem possibly residing to a specific batch load or maybe more. the problem will get worse and in short it's not a battery it's a mainboard problem with a sensor or a part that becomes hypersensative to heat. I think it's part of the same circuit that shuts the device down if the cpu or battery overheats but I can't proove it yet. I've had 2 of these phones so far. 1 3 got t-mobile t swap for an mda vario 2 at the time as the phone wouldn't stay stable for more then a few minutes. same result with 2 like 4 like replacements they sent me. ifinally said enough I want the closest thing tech spec wise to it. the 2nd one was my wifes which she barely used now that shes moved on to a different phone I've started playing a bit with it as it's over 12 months old. and I put it back into the box and up on a shelf as soon as it started doing the rebooting thing like the first one. NO WONDER ORANGE START DISCONTINUING IT AS WELL DID T-MOBILE UK.
UPDATED :
After reading a few of the posts aftr mine, I set out on a mission to determine the more exact reason for this cause. I found the unlike most mobile e.g: sony, lg, nokia etc. this phone would nout power on from the mains adapter without the battery. I figured initially it must have been the manufacture thinking this is not a laptop and the mains adaptr was intendd to charge batteries and then run the device. this also prevents data loss or file system corruption incase your mains charger comes loose from the device while playing. however I found that by putting my finger (when your finger tips are lightly moist and conductive) over the battery terminals on the device it would infact power on and work. now in light of this there are 6 terminals to make conduct with the battery the outter 2 on each extreme end are your + and - . the 2 inner ones are likely then to be battery voltage sensor and battery temprature.
so I said great way to test a theory. I unplugged the mains charger and started downloading files from my pc to the memory card over wireless. this of coarse caused the battery and the device to heat up very quickly. within about 10 minutes it did as expected and shut off. then when pressing the power button could not make it back to the main today screen either it would shut off on the windows mobile splash screen OR it would shut off during the first splash at bootloader.
I then removed the now very warm battery and put my finger on the battery terminals making sure the 2 center pins were touching my finger. voila th device powered on and booted up just fine. I then went back to doing file transfers and it never shut off on me again as lon as I held my finger on the battery terminals. in short I fooled it into thinking the battery was there but but that the temprature was fine. wm6.1 from ranji's 7.1 could tell there was no bettery to charge but the temp sensor was fooled. conclusion: the reason 2 replacement handsets in the past sent to me by t-mobile conitune to fail was not infact an internal problem that was main board related it was the battery incorrectly sending wrong temp info or a faulty battery that was getting to hot and the manufactures own safty device was shutting the device down to cool off the battery. this would be why in the past I would be able to just leave it off and eventallly it would work again. I felt like such a fool but at the same time I felt good that I got 1 traded for a vario and that now all I need to do to fix my mda pro is t get a new battery. I am man enough as you can tell to say wheni was wrong and I was. in light of this new info I would recommend the device to others but if you start getting random shut downs and turn offs during internet over wireless or gprs and the device is wamr ask your provider for a new battery or replace it yourself maybe even with a larger capacity one as it will likely resolve your problem. I know there are other posts i've done about this subject and I HOPE that those that have read them read this update as it applies to all htc universals regardless what branding they fall under.
enjoy in knowing new things
cj
i got my new battery today, all seems well, it even solved a problem or 2 i didnt even think were caused by the battery
cyberjak said:
this is an actual common problem possibly residing to a specific batch load or maybe more. the problem will get worse and in short it's not a battery it's a mainboard problem with a sensor or a part that becomes hypersensative to heat. I think it's part of the same circuit that shuts the device down if the cpu or battery overheats but I can't proove it yet. I've had 2 of these phones so far. 1 3 got t-mobile t swap for an mda vario 2 at the time as the phone wouldn't stay stable for more then a few minutes. same result with 2 like 4 like replacements they sent me. ifinally said enough I want the closest thing tech spec wise to it. the 2nd one was my wifes which she barely used now that shes moved on to a different phone I've started playing a bit with it as it's over 12 months old. and I put it back into the box and up on a shelf as soon as it started doing the rebooting thing like the first one. NO WONDER ORANGE START DISCONTINUING IT AS WELL DID T-MOBILE UK.
UPDATED :
After reading a few of the posts aftr mine, I set out on a mission to determine the more exact reason for this cause. I found the unlike most mobile e.g: sony, lg, nokia etc. this phone would nout power on from the mains adapter without the battery. I figured initially it must have been the manufacture thinking this is not a laptop and the mains adaptr was intendd to charge batteries and then run the device. this also prevents data loss or file system corruption incase your mains charger comes loose from the device while playing. however I found that by putting my finger (when your finger tips are lightly moist and conductive) over the battery terminals on the device it would infact power on and work. now in light of this there are 6 terminals to make conduct with the battery the outter 2 on each extreme end are your + and - . the 2 inner ones are likely then to be battery voltage sensor and battery temprature.
so I said great way to test a theory. I unplugged the mains charger and started downloading files from my pc to the memory card over wireless. this of coarse caused the battery and the device to heat up very quickly. within about 10 minutes it did as expected and shut off. then when pressing the power button could not make it back to the main today screen either it would shut off on the windows mobile splash screen OR it would shut off during the first splash at bootloader.
I then removed the now very warm battery and put my finger on the battery terminals making sure the 2 center pins were touching my finger. voila th device powered on and booted up just fine. I then went back to doing file transfers and it never shut off on me again as lon as I held my finger on the battery terminals. in short I fooled it into thinking the battery was there but but that the temprature was fine. wm6.1 from ranji's 7.1 could tell there was no bettery to charge but the temp sensor was fooled. conclusion: the reason 2 replacement handsets in the past sent to me by t-mobile conitune to fail was not infact an internal problem that was main board related it was the battery incorrectly sending wrong temp info or a faulty battery that was getting to hot and the manufactures own safty device was shutting the device down to cool off the battery. this would be why in the past I would be able to just leave it off and eventallly it would work again. I felt like such a fool but at the same time I felt good that I got 1 traded for a vario and that now all I need to do to fix my mda pro is t get a new battery. I am man enough as you can tell to say wheni was wrong and I was. in light of this new info I would recommend the device to others but if you start getting random shut downs and turn offs during internet over wireless or gprs and the device is wamr ask your provider for a new battery or replace it yourself maybe even with a larger capacity one as it will likely resolve your problem. I know there are other posts i've done about this subject and I HOPE that those that have read them read this update as it applies to all htc universals regardless what branding they fall under.
enjoy in knowing new things
cj
Click to expand...
Click to collapse
just a reply to kick this into attention as will be important to a lot of people I bet
Timeline/Events
1. Broke my Evo's screen
2. Got a replacement from Asurion (crappiest insurance company ever...ever)
3. Recieved new Evo in the mail.
My new/refurbed (not sure if it's new or refurbed) Evo, when I have it plugged in, says it's charging. But the battery percentage continually drops like it's not charging. The phone will die if I just leave it there plugged in. But the kicker is, it's charging, If I do a battery pull/turn off the phone after it's been charging for a bit, and restart it, it'll come back on fully charged.
It lasts the same time on a full charge as before, it's more of a minor inconvenience, but the one thing that this disrupts is my alarm clock. It will always die before the morning when I plug it in at night.
Is anyone else experiencing this problem?
My phone is rooted, but it was doing this before root.
Another quirk, It will display full battery, or 1 battery tick gone, until it just shuts off dead with no warning of low battery.
bump
bump, i really need help with this.
Try a hard reset, flash a stock ROM, flash a custom ROM and send back for replacement. Those are your options as i see them, in that order. It could be that the battery is faulty or it could be a software problem. Luckily either one or both can be ruled out, especially if you have a spare battery you could try?
Good luck.
I have done all of this except for send back for replacement. I do have a spare battery, but it does the same thing. I really don't want to send this back for replacement. It seems that this isn't a hardware issue, it's definitely software. IDK... I'll mess around with it a bit more, and then we'll see i guess.
sometimes when my evo is charging, the lightning bolt will disappear from the battery icon while the orange light remains on. the battery status says discharging. if i unplug it and plug it back in, itll charge. this has happened with two evos ive had, two different batteries.
i think i blame my usb ports on the pc
whobeyou said:
Timeline/Events
1. Broke my Evo's screen
2. Got a replacement from Asurion (crappiest insurance company ever...ever)
3. Recieved new Evo in the mail.
My new/refurbed (not sure if it's new or refurbed) Evo, when I have it plugged in, says it's charging. But the battery percentage continually drops like it's not charging. The phone will die if I just leave it there plugged in. But the kicker is, it's charging, If I do a battery pull/turn off the phone after it's been charging for a bit, and restart it, it'll come back on fully charged.
It lasts the same time on a full charge as before, it's more of a minor inconvenience, but the one thing that this disrupts is my alarm clock. It will always die before the morning when I plug it in at night.
Is anyone else experiencing this problem?
My phone is rooted, but it was doing this before root.
Another quirk, It will display full battery, or 1 battery tick gone, until it just shuts off dead with no warning of low battery.
Click to expand...
Click to collapse
You can tell if it's refurbished if you go into the phone app and dial ##786#. It will tell you if and when the phone was refurbished, how long it was used for, and the first time it was ever activated. Those can't be wiped. Has to be done on a Sense ROM though because it uses the EPST app AOSP ROMs don't have.
Hi guys,
I recently ran into this problem after I woke one morning to my alarm clock blaring for about half an hour, the phone was pretty hot but not unbearably hot. I took out the battery and left the phone to cool down til trying to boot again, when I did the phone booted fine but it soon shut off again 5-10 seconds into loading into android. I assumed the heat knocked the charge out of the battery / something went wrong with the reading of the battery (as it read like 85%) so I just plugged it into the charger and left til it said it was full. It doesn't shut off by itself and works fine while on the charger regardless. But as soon as I unplug the phone dies within a few seconds. So I turned off the phone and let it charge overnight, woke again to the same issue and the battery reading 85% again. Before I booted back up though I tried the "Wipe Battery Stats" thing in CWM hoping that maybe it would fix it after I fully charged but it made no difference. Also I found that the phone is able to run off the charger when I severely underclock it to 250MHz but obviously it's too damn slow for every day use at that speed. As soon as I clocked it up to 480MHz it had the same issue again. I forgot to mention I was rooted with CWM, unlocked bootloader and on stock rom. After this I decided to revert to my pre-root back up rom from CWM and I still had the same issue.
The final thing that seems to make it work is removing the sim, I tried booting this morning without sim and the phone functions flawlessly even while under a heavy stress test without turning off. So I tried inserting another sim, this one not active. Issues start up again...
Any Ideas guys? Seems to me like if the phone is pulling "too much power" the phone auto shuts itself off. But then the SIM thing perplexes me, not really sure how it all affects.
Lastly, do you think I can still claim on my warranty? I've had this phone for just under a month and it's still in perfect condition... I really don't want to switch back to my chopped and screwed Motorola Flipout. But atleast that thing could handle the overheating pretty damn well. Also I didn't get this on contract I bought it outright from a reseller as a prepaid phone.
In the Netherlands, the warranty for a phone battery is set to six months by law, just contact HTC, and find out.
Sent from my HTC ChaCha with CM9 using XDA app.
I have had the p900 for about two years now. Rooted it some time ago and installed CyanogenMod without any problems. But just recently, when I tried to reset the tablet, it got stuck on twrp. I thought I would let the battery drain and see what would happen afterwards, but now I can't get it to turn on anymore, even though I let it charge. The tablet really doesn't do anything anymore, can't go into download mode and it isn't regocnized by my computer either. So I think it's bricked, but since I'm not really the most tech savvy person, I thought I'd ask here... Could anyone tell me if this sounds like it really is bricked, or if there is still hope?
I'm wondering if your battery discharged too far down, basically killing it. Once that happens, it no longer holds any charge. I've seen that happen on an older battery (actually happened on one of my laptops!). You could try removing the back of the tablet and disconnecting the battery and reconnecting it after a few minutes, then putting the charger back on and see if you get lights. (if you're going to do that, might as well have a new one in front of you and just replace it - easy to do, and Amazon has batteries for a decent price from a few different vendors - just did that to my Note Pro last week. Youtube it for directions, it's easy if you are patient. I used this one, http://www.amazon.com/dp/B00N4KRSVW and it is working well - even got rid of the flickering screen around 50% power and below...
I'm having an issue with a 3 year old Google pixel where the phone is no longer bootable due to it dying anytime it is turned on. Symptoms started about a year ago, the device would occasionally die randomly when opening apps especially with a camera like Snapchat. The issue was originally very infrequent but got more and more common until every app that is opened would kill the device if not plugged in. At this stage anytime the device died it wouldn't use to boot until plugged in. About 4 months ago it started dying even if it is plugged in and now it refuses to boot rom or stay alive in recovery long enough to even decrypt the device. Device is also unstable if plugged into a computer as it constantly reconnects and disconnects. The really odd part about all of this is booting into fastboot works just fine and it will stay in fastboot as long as it's plugged in. I'm thinking I'm gonna have to tear down the device and replace the battery manually but I'm not 100% sure if this is the cause so I'm asking here for confirmation first. Any advice would be greatly appreciated as I need to get data off the device to move to my new pixel3
EDIT: Well, f*** me, after looking through q&a section for 2 minutes I found other people have started having this issue around same time frame as me and it turns out the problem is the motherboard is shot which I was also thinking in the back of my head but didn't want it to be true. I'm so not spending $300 to replace the Mobo of a 3 and a half year old phone, but I do need to get the data off of it. My understanding is that adb DOESNT work over fastboot so I think I'm gonna try to plug it into my laptop and see if I can get twrp alive long enough to get any kind of filesystem access.
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
uaDPJ said:
Honestly, it sounds like the battery is just dead. The phone dying at X% when using snapchat is like the first sign that the battery is getting weak and can't push out the required power. The way you described it, it just sounds like it got progressively worse until the battery is complete trash. The batteries are like $5-15, so might as well try it if you think you can do it without breaking the screen. I just did it for mine.
Click to expand...
Click to collapse
It's not the battery. Many other sources confirm that this is a motherboard problem. At first it definitely seemed like a battery problem given original symptoms but at this point there is a wide range of random symptoms that point to the board being shot.
On a brighter note I've managed to keep the device alive in twrp long enough to pull data off by plugging into a computer. Wall charger would cause it to die despite charger working fine with several other devices
A bad battery can leak onto the board and fry the board, so you may both be right.