Related
I have been getting pretty bad battery life recently, and now it's gotten to the point where I could leave the phone plugged in all day, come back and it will only last about 20 minutes.
So I went to AT&T and picked up a new battery, and I popped it in and left it plugged in overnight. When I checked on it last night it was up to 35% charging, now this morning, after being plugged in all day it's at 6%!
If I unplug the phone, it gives me the battery critically low warning immediately and then soft resets.
I am not sure what to do here. I read some stuff on here about doing a hard reset and then charging, or another one said let it charge while in bootloader mode, I really dont know how to go about this. I dont want to have to send the phone in for service because then I have to revert everything back to how AT&T had it first.
Any ideas on this would be appreciated. Thanks!
EDIT: Awesome, and since the battery level is under 50% it will not let me do the ROM update back to the AT&T stock ROM.
Check the usb port. It is rather easy to bend one of the gold connectors and the battery won't charge. You could still get a connection with your PC with the usb and not get a charge if you bent the right one.
You can flash VIA the SD card if you Charge is too low.
But I wouldn't recommend trying with less than 40% battery with your draining problem.
If the battery goes out during the flashing problem, you would have a pretty nice Paperweight.
I had the same problem. Try a different charging cord! They don't last long
Brickcity said:
I had the same problem. Try a different charging cord! They don't last long
Click to expand...
Click to collapse
You know what I had it plugged into the computer for a while with the new battery and I think it took the charge okay.
Also, I just gently used the stylus to poke around at the usb connector on the phone (as I have done as many others have in the past, and tried to do a soft reset in the dark and wound up putting the stylus in the USB port instead of the reset hole, but up until now I never had any issues). It seems to be charging again after doing that. I'll have to keep an eye on it and really baby that USB port, lol.
I do have a spare charger from my old HTC Wizard, I'll try using that one again if I have any more issues. I wound up reverting to the official ATT rom now as well just in case I need to get it serviced, and it really makes me appreciate the hard work people put into these custom ROMS because the stock one sucks, lol.
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
I take care to exit unused applications, etc, but this still occurs. In fact, I have tried rebooting to ensure nothing is left running in the background. Oddly, it occurs EVEN WHEN PLUGGED INTO THE CAR OR USB outlet... Most often this occurs when I'm using the device for navigation, so GPS, and DATA will be on. The notice has also popped up during other applications. It has happened when using LTE but also when LTE is disabled.
Is this something that everyone is experiencing? If you are, can you please post your Service provider, your SPECS, any mods, or if you have made any progress in stopping it. Lets see if we can track this down.
Mad Medik said:
I frequently receive a notification pop up indicating something like, "that the device power consumption currently exceeds the supply. Please plug in."
Click to expand...
Click to collapse
That's strange. I've never seen a message like that. It doesn't sound like something native to Android / Sense, do you have any battery monitoring / power control apps installed that could be giving this message? How long does your phone last on a charge if you don't plug it in?
I've seen that error before. I wasn't using the USB cable and charger that came with my phone and that cable was damaged in the USB socket. Have you tried other plugs?
Sent from my HTC Raider X710e using XDA App
The reason you are probably seeing that on car or USB charger is due to then not proving the right amount of power. If you have the screen brightness set high and using navigation it uses quite a bit of power. Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Sent from my GT-I9000 using xda premium
Ive had that happen once when I was playing a really graphics intense game. I was over at a friends house and had it plugged into his computer to charge and was showing him how much better a game looked on my phone than his and it did that. I was using the 3 usb ports on the front of his tower, and he also had his phone and a headset plugged in that front hub as well, and since that hub is powered by one connection on the motherboard I just figured the 3 devices (mainly the 2 phones) were just drawing too much power at the time.
I have had it happen when I was playing a graphics intensive game while plugged into USB on my computer, but never when plugged into AC or car charger.
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
I would find someone with a vivid and try on it, maybe the battery is dead.
Sent from my HTC Vivid via Tapatalk
Mad Medik said:
Thanks for the replies. Good to know it is not just my device.
Unfortunately, my problem has compounded. While I was using it last night, plugged into a USB in the car, it drained enough to shut itself down. I let it sit for a bit and tried to boot it up again. It quickly shut off again. I plugged it into the HTC wall charger over night. When I got up in the morning, it still wouldnt turn on. I tried pulling the battery, replacing it and plugging in again. The LED lights up orange for about 4 seconds, goes off and stays off. It wont turn on.
I left it plugged in for the day while I was out, and nothing. It still won't power up. I notice the battery is cold, further indicating to me that the issue is that it is not being charged at all (rather than a charged battery in a dead device).
I have tried two different USB cables and tried both the wall adapter as well as the computer USB port. Nada... Unfortunately I don't know anyone with a Holiday, so I think I will have to go to the store tomorrow and see if someone will be kind enough to charge my battery in a store phone for an hour or something...
Anyhow, once I get it running again, I want to avoid this in future. I currently have it Network unlocked, and Bootloader unlocked. I have installed CWM Recovery 5.5.0.4, and Rumrunner Beta 11. There was talk that a version of CWM Recovery was not allowing the device to charge while it was off. I am thinking that this is perhaps the culprit in my case. Although I thought that was for 5.0.2.7 (or something similar)?
Any input would be appreciated.
Click to expand...
Click to collapse
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
rquiett said:
Most USB and car chargers usually only provide I believe a half amp where as most phones like a charger that users 1 amp.
Click to expand...
Click to collapse
It looks like this is bang on. Apparantly computer USB ports for USB 1, 1.1 are minimum 200 mA with 500 mA recommended. Not sure about USB 2.0. Interestingly there is a proposal for USB 3.0 to allow for 20 Amps or more so you could easily power a laptop and other devices through a USB connection.
The HTC Holiday draws something more than 500 mA and presumably a max of 1 Amp as this is what the included HTC wall charger is rated for.
Anyhow, I guess I will have to pick up a new car charger, because the USB port in my car only pushes 500 mA max, and same for my current car charger.
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
jebise101 said:
Make sure you have beta2 of the recovery which resolves this issue, I too have the Bell Raider and have yet to see this error. I'm running stock with bloat removed and rooted with beta2 recovery. Just go in the recovery if you do not see beta2 written in the CWM header you don't have the latest.
Click to expand...
Click to collapse
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Mad Medik said:
I noticed that when I would remove and reinsert the battery with the device plugged in, the orange light would illuminate for about 4 or 5 seconds, then go off. In the hopes that this meant that the battery was charging for that brief period, I repeatedly removed and reinserted the battery for about 10 minutes this morning, trying the power button each time. It finally booted up. I turned the screen off and left it alone to charge. A few hours later I checked on it and it is up to about 1/3. Anyhow, putting that out there as a last resort if anyone else has a similar problem.
Thanks. After I let the battery charge right up, I will check that. (I don't want to tempt trouble by rebooting until I have finished a charge). I thought I had the latest version but maybe I borked something in the update.
jebise or other Bell Raider users: Were you able to use the ph39IMG method of flashing? I have had no success with it; I got an error that it was for the wrong type of device. I deleted the zip and used the next method listed in the superguide. However, now I get a series of errors relating to not finding ph39IMG when I boot into HBoot.
Thanks
Click to expand...
Click to collapse
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Pirateghost said:
if you use the fastboot method to flash the recovery, you dont need the PH39IMG. the 'error' messages you see when you boot into HBOOT is normal. every time you boot into HBOOT it looks for the PH39IMG.zip on your sdcard
Click to expand...
Click to collapse
jebise101 said:
PH39IMG.zip did not work for me had to use fastboot. As PG states its normal to get those errors, because it looking for PH39IMG.zip and can't find it.
Click to expand...
Click to collapse
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Mad Medik said:
Thanks for clarification on the "normal" errors I should expect. Im not a total noob, but feel like it, switching to HTC. I understand I can use the fastboot method and have done so. But do I have to? The PH39IMG.ZIP would be much more user friendly. So, why would I be getting an Invalid Device error with the PH39IMG.zip from the superguide post? Is it specific to the AT&T Vivid or something?
Anyhow, after all the problems I was having, I decided to wipe/factory reset and restore from a Backup made in CWM recovery right after installing Rumraider for the first time. I am just waiting for the device to reboot (has been on the HTC boot screen for about 10 minutes now... :-/
Click to expand...
Click to collapse
once you have done your recovery you dont need to do it again until you update the recovery with a newer version. its a one time thing, unless you relock stock RUU the device.
the ph39img.zip was configured for at&t vivid. you would probably need to modify it for any other holiday device.
if you are restoring from a backup, did you make sure and flash your boot.img from your backup first? otherwise you will be stuck at that HTC screen for a lot longer....just boot into HBOOT and flash the stock boot.img
Hello, I've been using my htc vivid since about march last year, and I recently rooted it, flashed Kanbang and added wajee's desensed rom. Things have been going smoothly until recently, I attempted to change roms to xperiense (Also by wajee) and I'm now stuck booting up at the splash screen, I can access my boot loader, but I can NOT preform a factory reset, Please, if anyone here can help me I would seriously appreciate it.
If the recovery program is not showing then you need to clear the catch if the recovery still don't work try to reflash the recovery or even a different recovery . If that don't work relock the bl and run the stock ruu and start over , the hansoon tool kit makes this a breeze and you will be back where you where in a few minutes.
I can access the bootloader, and I forgot to mention that If I plug it in to my comp it does not seem to want to charge, it shows the light for about 5 seconds, then the capacitive buttons will vibrate if pressed, but nothing displays, I have to boot into the bootloader without it plugged in then plug it in.
Yea pull the batt and boot into hboot , then select fastboot plug the phone then it should say fastboot USB , running the ruu will fix any errors you have so you can start fresh ....just remember never pull the plug while the ruu is running .
Well, Thanks for trying to help, but the batter will NOT charge and is dead, I'm ordering another OEM battery soon, Thanks for the help but I've read and this actually appears to be the problem, again thanks you for trying to help.
No problem , if ya need anything don't hesitate to ask here someone can always help out .
Are you sure the battery is kaput? Have you tried charging it with a wall charger? HBOOT doesn't support charging BTW, and USB won't charge unless the phone is ON and in the OS (or in TWRP recovery which DOES support charging).
Pull the battery and leave it turned off, then plug in the wall charger. You should get an orange LED and presto, it's charging. See if you can power up after an hour or two. If it spends two hours on the wall charger and still isn't charging, then it's either A) your battery, or B) Your charge port. I had the charge port die on my blackberry torch. Thought it was the battery too until I borrowed one from a mate and swapped things around.
ess.boyer said:
Are you sure the battery is kaput? Have you tried charging it with a wall charger? HBOOT doesn't support charging BTW, and USB won't charge unless the phone is ON and in the OS (or in TWRP recovery which DOES support charging).
Pull the battery and leave it turned off, then plug in the wall charger. You should get an orange LED and presto, it's charging. See if you can power up after an hour or two. If it spends two hours on the wall charger and still isn't charging, then it's either A) your battery, or B) Your charge port. I had the charge port die on my blackberry torch. Thought it was the battery too until I borrowed one from a mate and swapped things around.
Click to expand...
Click to collapse
I've left it charging for about 1 and a half hours and the led goes on briefly the shuts off after a little, the phone won't go into hboot now
If you want I can send you my battery fully charged and send it back after we figure out if your battery is bad , I don't use it I have two extended packs I use just lmk .
Bigtjmc said:
If you want I can send you my battery fully charged and send it back after we figure out if your battery is bad , I don't use it I have two extended packs I use just lmk .
Click to expand...
Click to collapse
Thanks for the offer but I have a bro with the same phone who lives nearby so I'm going to see if I can borrow it tomorrow for a few minutes, if it works, my new batter is in the mail, if not, I'm going to talk to at&t and see if I can get the phone replaced.
It keeps claiming I have the wrong version (The Ruu) any chance of a link to the most up to date one?
Ok so a short few weeks ago I plugged my phone into a generic charger to charge for the night. When I woke up the next morning the phone was off. I tried all of the button combinations and even the official charger and nothing changed just the occasional flash of the green LED. Fast forward to yesterday... I got in my eb40 battery and put it in the phone. Plugged it in and it gave me a green light that flashed for two seconds when I put it on the official charger, but it still will not turn on...
Is there anything I am missing or is my phone just dead for good?
Try getting a factory cable to charge with. Not the oem one a factory one.
Sent from my PACMAN MATRIX HD MAXX
Kinda related. My Dad's AHD started randomly rebooting when it was being charged. It ended up being his USB cable had a short in it. I gave him one of my backup Moto cables and it works just fine now. His lesson should have been "Don't leave my cord tight at a weird ass angle coming from the dongle" but it really was "My son will just give me a new one if I screw this one up".
Night before last I used a friends generic wall charger on my AHD running PAC and it took forever to charge. 8 hours went from 56% to 97% and it was pretty hot too. The only generic charger I've used with my AHD that actually worked just fine is a cheap ass Dollar Store car charger with a USB port on it.
In my experience with Moto phones, only use Moto Wall Chargers & Moto Cables, but generic car chargers with Moto Cables seem to be just fine. My Moto Bravo and Defy don't like non-Moto wall chargers either.
My suggestion would be the same as post 2, only when you get that cable, in fastboot mode, do a full factory reset and flash your previous stock firmware (assuming it was ATT 4.1.1), root/unlock it if necessary, flash Bell or Mex 4.1.2 with Myth/Fastboot/RSD, do whatever. With a factory cable you can flash with 0 battery and be OK (it powers the phone directly from the USB port).
Thanks for the tip. I will look into either buying one or making my own factory cable. Yall Rock!
One last question before I set about my quest. Can I make a factory cable from any micro usb cable?
Yeah, just use a high quality one.
I got a factory cable and plugged it in to my comp. Nothing happened. I guess my phone must be dead.
Side note: If i take the battery out and plug it into my comp with the regular usb cable the green light comes on and my comp registers it as a usb input device. Does that mean anything to anyone?
Can you measure any voltage across the battery termiinals? Does the battery look in good condition?
The first thing I did was put a brand new battery in it. The old one was starting to get ripples like it was swelling. Once I get home I will try and get a reading off the battery terminals though.
Update: Just got home. Battery is reading a solid 3.7 on the multimeter.
I guess its time to retire my poor little Atrix HD... it was barely over a year old
If any one can think of anything else to try, Please feel free to post your ides. I will check back here often to see if there are any new suggestions.
springduck said:
The first thing I did was put a brand new battery in it. The old one was starting to get ripples like it was swelling. Once I get home I will try and get a reading off the battery terminals though.
Update: Just got home. Battery is reading a solid 3.7 on the multimeter.
Click to expand...
Click to collapse
This, maybe?
Last night while using my Atrix HD with 4.3 CM 10.2 nightly from maybe 2 weeks ago, my phone froze. After hitting the power button repeatedly the screen finally went off. Now it wont turn back on, it had plenty of battery life left, I tried 2 chargers to try to get an led reading response, nothing. Strange coincidence out phones went out so near to one another.
Yea it really sucks. I loved this phone. Now im stuck using my X10 for a year till I get an upgrade.
Hi.
I've had an HTC One M7 sitting around for years. I gave it to my mom after I bought a Nexus 6P, having used the One for three years. She got another few years out of it, but then the charging port started giving her trouble. The phone wouldn't always charge, and she got frustrated with it, so she put it in a drawer and let it die for good. I retrieved it from her, but not before it was kaput.
Today, I installed a replacement battery that I'd ordered and managed to bring the thing back to life. At first, it wouldn't take a charge at all, but I wound up getting it going by plugging in my Nexus 6P charger with my Pixel 2 XL USB-C to USB 2.0 adapter and running a USB 2.0 to mini-USB cable from that to the phone.
When I turned on the phone after letting it charge for a while, it had 55% battery, but I noticed that it was getting stupid hot.
So, I shut it down and kept charging it, this time having switched to a 5V 1.5 mA charger instead of the 3 mA Nexus charger. After it had cooled down, I booted it back up again and the battery gauge read 5%. ???
Any idea what the problem is? The charger shouldn't be an issue, right ... because it's not quick charging since it's not plugged into a smart USB-C cable (at least as far as I can figure). I suppose the battery could be junk; it's older than the one that had been in my phone (the date stamped on it is a month prior to the date on the original). I'm at a loss, though.
I'd appreciate any ideas.
UPDATE:
When I booted into recovery (the phone is unlocked, rooted, and s-off), TWRP told me that my battery was 45%, whereas the OS was reporting 5%.
I booted back into the OS (5.0.2) and it showed 20%. With the charger connected, it soon dropped to 17%.
I booted again into recovery, which now showed me 8%. I again plugged in the charger and it showed the (+) to indicate charging, but the percentage then dropped to 7%. It never climbed.
I turned it back off, let it charge for a while, then booted back into the OS. It showed 12%. I decided to shut it down and unplug it, as it was late. This morning, I plugged it back in and left it for a while. Upon booting it up ... battery was still at 12%.
So, I did what this guide (https://forums.androidcentral.com/v...ry-charger-reset-procedure-htc-one-m7-m8.html) recommends. The phone is now on and charging and, at last check, it was up to 27%.
There are plenty of variables, here: the phone is old; it's been defunct for years before I revived it yesterday; the replacement battery was from the month prior to the stock battery (perhaps irrelevant); the charging port is sloppy and the cable needs to be "just so" to work; the OS is a de-bloated factory AT&T image that I used to de-brick the phone after I'd wiped the original OS before I had the opportunity to make a Nandroid backup (ergo: I wonder if Sense is (part of) the problem).
If anyone wants to take a stroll down memory lane with this phone and spitball with me, please feel free.