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.
I got my Nexus 7 at I/O this year and I've been happily using it for nearly a month now. I don't know if my device differs in any way from one you can get form google play other than the white back.
Last night I was plugged into my wall charger at around 14% battery and playing SongPop with my girlfriend when my screen just shut off. It was like when you hold the power button on a laptop and BOOM, everything is black. It wouldn't turn back on so I unplugged it and plugged it back in. Got a charging screen so I let it set for a bit.
I came back maybe 15 minutes later and I was at 9% battery, which was odd given I plugged into the wall at 14%. I played with the phone for maybe 30s after boot and it happened again, I saw some weird artifacts on the black screen as it quickly shut off and the speakers played an awful crackly screeching noise. Plugged it in again, came back a bit later, still at 9% and played with the device again, same issue only after a little more time.
I'm currently at work with my N7 plugged into my Galaxy Tab 10.1 charger and charging it from 0 to 16% currently. The device is on but I haven't been touching it (and I don't plan to until it's at 100%).
Has anyone else had this issue?
I cant tell if it's some way I'm touching the device that's causing it to shut down hard, some issue with the battery or charging that is causing a rapid battery drop or even a short in the way I'm holding it when it's plugged into the charger?
I don't really want to deal with ASUS warranty returns already, though I have been unable to find anyone else with the same issue through google, so I turn to you for advice and similar stories.
Mine did the same thing the second day I had it. Now it won't boot. I'm waiting for Google to send me a new one.
Sent from my ADR6400L using Tapatalk 2
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
TrevSo said:
Mine did something similar last night. It was at about 6% battery charge and all of a sudden the screen just went black. I went and plugged it in, but it wouldn't power on completely (the screen was on but there was nothing there). I started seeing really thin, small green lines running down the screen. I turned it off and on a couple of times, and finally it booted up. I left it plugged in for awhile, and I just took it out at work to use a bit and everything seems perfectly fine. I wonder if there are some firmware issues with the power management or something. I was all set to put in a return with Google, but it appears to be okay. I'll keep a close eye on it for the next couple of days (I've only had it for a week).
Click to expand...
Click to collapse
After leaving mine off and charging at work to 100% it seems to be working fine. I used it all last night with no issues. I haven't tried wiggling around the usb cable yet in the port to see if that caused any issues.
Firmware issues sounds about right, some sort of low battery safety feature or something? Who knows. I'll update this thread if I continue to experience problems. I'm already past my ability to return to Google so I'm in no rush to warranty to Asus and lose a development tablet.
Recently updated from CM9 to jcsullin's CM11 (11-20140409). Most everything seems to be ok aside from an unusual battery issue, and I don't know what it's coming from. I've attached a screenshot with some battery stats to help out, but I can describe what was going on in this particular instance.
I've had my touchpad sitting on the touchstone nearly 100% of this time (only time it was not was when I picked it up and immediately returned it). At some point, loaded up and was playing Breach & Clear for a while. Finally stopped playing, and upon exiting, battery was reported at 1%. Now, I get that some things can drain the battery even while on a charger, but we're talking a span of maybe 60-90 minutes. At this point, I picked the pad up and the battery immediately went up to 100%, and I dropped it back onto the touchstone.
This is the second time I've had this happen. Yesterday, it actually shut itself off due to low battery when I picked it up. I turned it right back on, and it was reporting 100% (recovery also reports 100%). This morning, I reflashed the A6 firmware in case that was the issue, but it does not seem to have had any impact.
Really could use some advice here. I suspect the battery is more or less staying charged while on the touchstone, and that this is something related to bad reporting or (worst case) a defective tablet.
Thanks for any help.
Just a quick update. Shutting off the touchpad before leaving work, during the shutdown process, I saw the battery % drop from 100 to 0. As I was getting out the touchpad at work and turning it on, I got the battery-with-question mark symbol. Placed it on the touchstone and it booted itself. I decided to take it to recovery, and pulled it off the touchstone. Now, as I watch, the battery is changing % wildly. 100%, 29%, 0%, 67%, back to 100%, 0% again...
Really don't know what's going on. Did not have this happen on CM9. Could really use some help.
Edit: I just threw on a random game while off the touchstone to see what happened. Everything seemed normal, battery ran down to 93%. Exited the game, turned off the screen, and two seconds later it was shutting itself off with 0% battery. Immediately turned it back on, and it shows 93% again.
Did you do a clean install? Does the issue persist after reflashing?
Fresh install, used tptools to wipe and repartition the tablet, no WebOS, CM11 only. Reflashing A6 didn't help.
Still unresolved, possible more problematic.
I rotated my tablet from landscape to portrait and back (while on the touchstone) and it decided to shut itself off.
If anyone knows of/has similar issues (fixable or note), I'd really like to hear about it. Will be disappointed if it's dead, but it's better than spinning my wheels on it for something I can't resolve. If I have to buy a new tablet, I'd like to get it over with.
Edit:
Been a bit since I posted this, but I let the tablet sit for a bit. The battery stats are pretty crazy. Note that I've left it on the touchstone this entire time. I don't get why it's doing what it's doing at all. See newly attached screenshot.
there are 2 possibilities
1. your battery is ****ed, hardware issue, you cant fix unless you replace the battery
2. software issue, but from what you described, seems like you installed properly, so i would suggest to boot into webos (u gonna have to reinstall it), and use it for a few days to see if you get the same problem
- if you do get the same problem, then it's 100% ur battery is ****ed
- if no, then ur cm11 is messed up, try another rom
Ah well. Was hoping I might be able to fix it without any wipes.
I would think if the ROM itself was the issue, others with jcsullins' CM11 would have problems as well. Looks like that's not the case at this point. Perhaps I'll just retired the tablet and get a laptop.
Thanks for the input.
Hi, did you get anywhere with this?
I've got occasional battery percentage glitches on Jcsullins CM11 that I didn't get with the previous WebOS/CM9 setup. See attachment.
Sadly I don't have the time or motivation to launch a huge investigation by flashing ROMs, etc... Looking like I'll just restore WebOS and sell.
At this point, I can't get the thing to boot. I've had it on a charger for a month or two now. I've got the blinking home button. It booted once, but I wasn't in a position to hook it up to a computer and try to wipe it. I've not really put any energy into fixing it since.
I plan on getting it back on the touchstone at some point, and setting it next to my PC. If I ever get it to boot, I'm going to try to get webos back on it first thing, and go from there.
Thanks for the reply. I'm questioning the amount of time I'm spending tinkering with this 3.5 year old device when new tablets are so cheap.
Touchpads are still making a reasonable amount on eBay so sadly I think it's time to just restore webOS and move on. Shame because it runs 4.4 pretty well, at least as good as my Galaxy S3.
I have a Moto X 2013 that, after replacing the battery with a supposedly new, OEM battery, refuses to charge past 3%. This phone is rooted and was rom'd with the Nougat xPerience rom, but I tried flashing it with Nougat Lineage as a troubleshooting test.
I replaced the battery last night without incident, and the phone booted and seemed to behave fine, and the battery had about 30% charge. The only issue I found immediately after replacing the battery was a battery app installed on the phone saying the battery hasn't been charged for -19000 hours, or something a long those lines (I can't remember exactly what it said, as I did not install the app, my friend did who I was fixing the phone for. I just remember it was some outrageously large negative number.). Thought it was weird, and maybe thought it was a software issue, so I booted to TWRP and wiped the cache and dalvik. Rebooted the phone, and the app reset to something along the lines of 500 hours. That is a bit more believable.
I plugged the phone into my laptop to let it charge (as it was the only way I could charge it at the time), my laptop saw the Moto, and the Moto said "Charging..." and "Android Debugging...", and thought it was working. I had to run an errand, and when I returned about an hour later, the phone hadn't moved a drop up or down. My laptop was asleep, so I assumed maybe it just stopped charging when my laptop shut off, and I was exhausted myself so I just let it sit on standby all night.
Morning came, and the Moto is dead. I plug it into the wall charger I was just using to charge my v10 with (brand new cord, made for data transferring and charging that I used once before with the old battery), and head to class, hoping it'll charge. Guess what? It didn't charge. Well, it did a little. It went up from 0% to 3%, and sat there. Annoyed, I unplugged and replugged in the phone. It came up with the white battery charging screen, switched to the Nougat "N", vibrated, then went to a black battery charging thing. Once there, the battery icon went up two squares, the screen flashed, and the phone died and stopped charging, then repeated itself a few more times until it went silent.
I started to think maybe my brand new cord was screwing up, so I grabbed another one I had and plugged it into my desktop. I had read on another thread that sometimes you can force the phone to jumpstart charging by plugging in the phone and holding down power + volume down for upwards of two minutes. I tried this, and it charged enough that I could turn the phone on again, but it wouldn't charge enough to do much more. I left it plugged into my desktop for a few hours, not allowing the desktop to fall asleep, and yet the phone was still not rising above 3 or 4% despite the fact that it says that it is charging. Oh, and the phone was on the whole time if it was plugged in, but the moment I unplugged it (Like the one time it got over 5%), it immediately shuts down.
I know I'll probably just have to buy another new battery for the dumb thing, but I am just curious to see if there is anything I can do to fix this, just because I cannot currently afford to buy another new battery (and my friend, who this phone belongs to, is getting impatient on getting it back.)
Thanks for any help!
I have the same problem, charging topping out at 3% with a "new" battery.
Did you change the battery? Did it work?
Thanks for your feedback.
(FYI, this phone is running the stock lollipop firmware.)