Related
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
So my replacement Tilt isn't working either, so they're overnighting me a third one. In the meantime, I haven't sent back my original (RLoDed) Tilt, so I thought I'd play around with some of your theories.
skuzz said:
Another thought I had. After the tilt goes into red brick death mode, has anyone tried plugging it into power, battery installed, and then holding down power+camera(all the way) and then pushing in the reset button on the bottom? This may trigger it to go into flash mode - although I kinda doubt it'll work. Worth a shot! Might be able to reflash it back to life! Holding down power and camera while it boots is how you manually force it to get in the Red/Green/Blue firmware flash mode. If it let us do that much when the device bricked we might have a snowball's chance in hell of getting them working. I didn't think of trying it before I returned mine tho. D'oh!
Click to expand...
Click to collapse
I didn't know what to try besides installing the battery and SIM card and trying to push down the power, camera, and stylus buttons (I knew I was doing it correctly, because I had to use this to return my second Tilt to factory specs). No response whatsoever! This thing is deader than a doornail. Except for the red LED, of course... that works REALLY well whenever it's plugged in.
sWuRv said:
I think I just figured out how to fix it!!!!!!! I was tinkering around and got my red light brick to turn on!!!! I'm not sure exactly what fixed it so here's everything I did-
1. Removed the storage & sim cards.
2. Took off the backplate.
3. Removed the battery.
4. Bent these 2 pins up a little bit:
5. Put the battery in at an angle, so that the power leads were connected, but the metal shielding plate on the back of the battery was not touching:
6. Hit the power button (with the battery still "halfway" installed) Bam, green light of life.
Somebody please confirm this. Meanwhile I'll be copywriting this process so anyone who performs it owes me 10 bucks
Click to expand...
Click to collapse
I appreciate your enthusiasm, but the only thing I can confirm is that this did NOT work on my RLoDed Tilt. Tried it several times in various ways. I think you just seriously lucked out!
As such, I'd also have to vote against stickying this... for now.
Best of luck, all... if not actually in fixing your RLoDed Tilts, then definitely in avoiding the $500 service fee if AT&T discovers we voided our warranties.
alright i will confirm this too....my phone was truely RLOD..... i did the same thing that these guys did just jammin the battery in and out and it "jump started the phone"
exact process used
Moto Razr charger
hold down power button
"bounce" battery on and off the contacts for the battery a good 100 times or so
green light apeared after the red light started to flicker a little bit..... tis as if you were giving the phone CPR or something
im not going to call this a fix all i know is that the phone was RLOD and now it is working....battery is at 54% right now and i will post back in a bit to see if it has risen at all....
no smell arising from device
running origional rom but have had other roms on there (alex's)
hard SPL still installed on device
SPB phone suite is the last software that was installed on the device
reg tweaks installed as well, the usual ones no sms, hsdpa enabled blah blah blah
that is about all i can provide....the unit was on the computer overnight charging....when i woke up it was RLOD....and i was sad....i did have the ATT store replace the battery for me as well dunno if that had anything to do with the issue...
in the time that it has taken me to write this the battery is now at 55% so it is charging.....on wall charger with MOTO razr charger
ok lets take a little closer look at what happened within the past little bit....
after gettin the device all up and running it was behaving very oddly.... it would go through multiple attempts to connect to the data network for various reasons....after showing that it was at 55% on the charger it went back down to 54%... i pulled it off the charger and took it into the other room to do something......within 10 min it was down to 46%....now having a data connection my blackberry connect should have a valid network connection....but it did not... not sure why...
the best that i can conclude is that it was trying to connect to so many things all at the same time that it exhausted its self that fast....
so the question is how many people out there that have RLOD are running the BB connect software on there devices and have made REG edits to the data connection time outs and the HSDPA mod availability
editing those settings together may confuse the device and make it think that it has to connect to too many things at one time....
just another thought process that i thought that i would throw out there...
here are some things on the my device that would use the DATA connection and automatically initiate the connection on the device rather than you opening a program forcing it to connect such as Internet explorer
GPS update
HTC home weather tab
SPB weather tab
Blackberry connect
SPB insight....RSS Reader
text messages going in and out....my phone sees quite a few of those
Edit/Delete Message
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
i had the same prob..took out the batterly wiped the four contact points on the phone (might of pushed them down or up) and put battery back in and worked..
I believe sWuRv was onto something. My Tilt had the RLOD today. I tried everything, even what he suggested above to no avail. So I called warranty and got my replacement on it's way, express shipping waved and all. So I decided to everything I could think of to try and get the thing back on so I might be able to back up my data again.
I started fooling with the battery, like sWuRv suggested but I moved it all around at 45 degrees or so pushing the power on button. I noticed while it was plugged to the USB with red light on that every now and then the red light would flash when I moved the battery so the contacts moved (while holding the battery at that 45 degrees). I started getting the light to go yellow but it would not stay. So I unplugged from the USB and kept trying it while pushing the power button. It eventually started and I was able to back up to my SD card. One thing I can tell you is that this process caused the phone to get hot and smell like electronics burning a little. There is definitely a power problem inside.
I have no idea how or why this worked but it did. I think I will still take the replacement even though I have to figure out how to swap my fancy invisible armor clear protector skin.
I'll try and update on whether this phone dies again or what until I get the new one.
rlod
I tried messing with the battery in a variety of ways for 30 minutes with no sucess. RLOD stayed solid.
RLOD
Holy shoot............After bouncing my battery up and down about 40 times my phone came to life!!!!!!!!!!!!!!!
Reseating the battery and/or sim/storage cards is hardly a revolutionary procedure. Its Cellphone 101.
you guys are LIFE SAVERS. I have been on this forum for about a month now and I finally found a reason to post. I haven't posted because I always find my answers. I just wanted to thank everyone, as I have been on the phone with Amazon.com (where i got my tilt), went into an AT&T store and was on the phone with HTC tech support ALL day trying to resolve my red light issue. Unbelievable that all I needed to do was give it some "battery CPR":
UGHHHH. Well i found reason to make post #2. The fix lasted less than 5 minutes.
this did not work for me
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
"Not the Mama", OR, NOT THE BATTERY
rotohammer said:
These stories remind me off all the bad batteries/no powerup of my Motorola Q and those of others. My mother is on her 4th Q and I know its the battery, but the store just swaps out the whole phone. I've seen batteries last as little at 2 weeks, especially if let run down to empty at any point.
My questions are, is this just a bad battery problem? Does anyone with RLoD have a spare battery to try? If these batteries fail in the shorted condition, will they over draw power from the phone and mess up the charging circuit?
Roto
Click to expand...
Click to collapse
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
cushcalc said:
I certainly don't believe it's a bad battery problem. I had 2 spare batteries, fully charged with separate docking charger - none of the 3 batteries made any difference once I got the RLOD.
Click to expand...
Click to collapse
Very good, thanks for the insight!
I finished a call yesterday and then dropped my phone on to the pavement cos I was a bit drunk... Anyway this caused my phone to go from working fine (all be it with pants battery life) to just flashing the red light. Fixed it today. I tried the methods prescribed in this thread without success although I did not persevere for very long. I then put a spare battery in to the phonea and bingo the orange light comes on, phone boots up and it's now happilly charging. Note that I charged the old battery for several hours before trying the fix. Pity nobody seems to know what the problem actually is. I wish HTC would let us know....
sWuRv said:
There have been a few other people who have now fixed their RLOD's. Confirmed it was done by messing about with the battery. If you have revived yours, please post your method in here so we can compare them and eventually pinpoint the fix. Thanks.
Click to expand...
Click to collapse
I had a similar problem with my old iPAQ hw6515, and a Motorola V3. The contacts on the battery don't spring forward as well on an older phone as they do when it was new. I shimmed the battery. I did this by taking a business card and holding it against the opposite side of the battery from the contacts I traced the battery's profile and cut it out. I scotch taped my new shim to that side of the battery, then re-inserted it. This forces the battery up against the contacts better and in many times resolves inoperable phones, failure to charge, and spontaneous rebooting issues.
-Jay
My replacement tilt (first one had a bad USB connector) died Sunday.
Had it on the charger, looked down, red LED. Back of phone was pretty
warm. Pulled the battery, SIM, memory card, slammed the battery onto the
battery contacts rapidly 5-6 times, put the SIM, memory, battery back into
it, and it charged up. Did a hard reset. Battery was 100% charged, I turned
it completely OFF when I went to bed. Got up, battery was 0% drained!
Red LED again. Did the rapid thingy with the battery again, orange charge
light came on.
Called at&t warranty replacement. When I told her I had a red LED, she didn't
even ask me to do anything else. She just asked for the IMIE number and shipped me another one.
Maybe the 3rd one will be the charm LOL.......
I'm beginning to think that HTC doesn't stand for "high tech computes" but
"high tech CRAP"....
Maybe you guys got the margin of error productions? I know its really unlikely that you could get them again after a replacement but it is possible, and it maybe your computer. What do you think could be making this things go crazy? Overly protective anti-virus, I know, I know but it could do things secretly and screw around like mine does and wont let me into sites I have been on before on the same app no changes . . . Well I hope you luck.
ok I just tried everything you guys said, but it didn't work for me
so as some of you have stated it must be the battery, so what I did is put it between my hands for about 1 minute and put it in and it worked again!
really weird... must be the heat?
well hope that helps the research
Cheers
Jay
I've had my Tilt for about a year now. I just had to replace a cracked screen about a week ago. It now randomly turns offs, usually when there is some sort of data connection like surfing the web or talking on the phone. It seems if I'm just messing around w/basic features on the phone it stays on just fine. The battery is at a good charge. I've noticed that when I have the phone plugged in it works fine, but as I said the battery is showing a charge of 50%+ when this happens. Anyone know what this could be? Thanks.
Hmmm,
My guess would be that you did not 'stick it together' correctly after changing the screen - seems like a hardware part is in contact with another where they shouldn't! When turning on your wifi or other hw modules, your device might experience a power leak or overload through that - can finally also be the screen. Was it an original HTC KAISER part?
Junner2003 said:
Hmmm,
My guess would be that you did not 'stick it together' correctly after changing the screen - seems like a hardware part is in contact with another where they shouldn't! When turning on your wifi or other hw modules, your device might experience a power leak or overload through that - can finally also be the screen. Was it an original HTC KAISER part?
Click to expand...
Click to collapse
I'm not sure on the part, I bought it new on ebay.
Same Here
This has been happening to my Tilt as well. While unplugged on a phone or internet connection it just shuts off. Sometimes it take several attempts to get it to boot again or I need to plug it in to get it to boot at all. I was wondering if it was a faulty battery but I haven't tried replacing it yet.
jqman said:
This has been happening to my Tilt as well. While unplugged on a phone or internet connection it just shuts off. Sometimes it take several attempts to get it to boot again or I need to plug it in to get it to boot at all. I was wondering if it was a faulty battery but I haven't tried replacing it yet.
Click to expand...
Click to collapse
Dirty battery contacts, or contacts not making sufficient contact because they're too low, might cause that.
I had this problem two ways- WM 6.0 with spbshell would just lock up and turn off, could never figure out why. Removed spbshell and it was good.
Lately I had a problem where a 6-month old Seido extended battery was shorting itself out when I would grab the phone or twist it a certain way. Dropped old battery back in it, no issues.
-G
jqman said:
This has been happening to my Tilt as well. While unplugged on a phone or internet connection it just shuts off. Sometimes it take several attempts to get it to boot again or I need to plug it in to get it to boot at all. I was wondering if it was a faulty battery but I haven't tried replacing it yet.
Click to expand...
Click to collapse
This is exactly what mine does. The battery fits a little lose on the left side, but the contacts on the right side are touching and intact.
randomly turns off
im having the same problem. my phone just turns off when im on the phone or if im texting someone. It even turns off when i push my power save bottom on. I need help.
I have the same problem. What I've noticed is that it doesn't do it when it's plugged to the charger, but it turns off when it's running with the battery only.
My findings:
- Using it like a PDA no problems running on battery (no using any phone function)
- On a call,when it's running on the battery it turns off
- Using a Data conection or Wi-Fi when it's running on the battery it turns off
* On a call w/charger plugged in no problems
* Using Data or Wi-Fi w/charger plugged in no problems
I hope that's a battery related issue. I'm going to try to replace the battery and let's see if it fixes the problem.
Problem solved. New Battery
Tilt Battery
I'm having the exact same problem as jqman, I've had my Tytn II for more than a year now, and it has been great. For the past month it has started turning off randomly with no forewarning. I can charge it all day, the second I take it off external power and try to do anything from surfing the web to taking a call it just randomly shuts off. It may be a battery problem, because it sometimes shows low battery power immediately after disconnecting from the charger, but there was nothing that led up to this. The battery was fine one day, and then the next completely gone. Also, there is no oxidation on the battery contacts, and it seems in tightly (not loose at all). The back cover is also very steady, as I've had a plastic casing for the past year, and only recently took it off because of this problem.
I find it hard to be believe that it's a software or hardware problem - just suddenly after a year. I hard reset the phone and updated the ROM and it's still happening.
Any ideas/suggestions? Should I buy a new battery (is one year a al battery life)? Are generic batteries as good as the originals or should I only get the original Dynapack?
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 have been loving my Nexus since I got it on the first day it was available, but a couple days ago it started acting very odd. The phone will intermittently "die" while the battery is still mostly full. The phone will shut down, and if I try to restart it the screen displays the empty battery symbol and will not boot. As soon as I plug the phone in, though, it will boot up immediately and the battery charge icon while the phone is off shows as almost or completely full. When I boot the phone back up it looks like it has 90% or so.
Has anyone else seen this issue with the N6? The phone is completely stock 5.0.1. I purchased it through Sprint, but as far as I know it's exactly the same as all the rest of them.
http://forum.xda-developers.com/nexus-6/help/nexus-6-att-powering-off-t2976509/page2#post58179998
Same problem here, still no solution. The Amazon thing didn't help for me. Maybe this thread gets some more attraction. Would really love to get this fixed.
I, too, am having this issue which began yesterday. It started as soon as I took it off the charger and the gauge read 100% for about 2 hours straight which was unacceptable since I was using it for just about the entire 2 hours. During that time, I kept checking the battery stats and it kept saying that it was unable to retrieve the battery statistics (or something like that). Then it finally died on me. Now it keeps dying at 80% and charges back up to 100%, only to die again
Sounds like a faulty battery
Sent from my Nexus 6
Same as me, this is the exact same thing that happened to my S4 where the battery expanded............
need to send mine back because of this, together with the back cover lifting off.........
mediaman123 said:
Same as me, this is the exact same thing that happened to my S4 where the battery expanded............
need to send mine back because of this, together with the back cover lifting off.........
Click to expand...
Click to collapse
The back cover thing is also indicative of expanding battery
My nexus 6 is doing the same thing shuts down at 90% and will not start without being plugged into a power source. I love my phone but hate this problem. Someone help please !
jjjjjoeeeeee said:
My nexus 6 is doing the same thing shuts down at 90% and will not start without being plugged into a power source. I love my phone but hate this problem. Someone help please !
Click to expand...
Click to collapse
Try the fix mentioned here:
http://forum.xda-developers.com/showthread.php?p=60409122
Do you notice any bulging of the rear cover? If so, RMA immediately. This is an indicator of a defective battery if the above mentioned fix doesn't work. Also grounds for RMA.
Evolution_Freak said:
Try the fix mentioned here:
http://forum.xda-developers.com/showthread.php?p=60409122
Do you notice any bulging of the rear cover? If so, RMA immediately. This is an indicator of a defective battery if the above mentioned fix doesn't work. Also grounds for RMA.
Click to expand...
Click to collapse
awesome, no bulging at all so hopefully it does the trick.
thank you very much!
Hello all, I hope this finds you well. After having my Droid since the month it came out, I am finally having an issue I cannot seem to resolve. My phone will not charge, stuck at 16%. It took a fall the other day, so I think that did it, but it was in a lifeproof case (always has been) so there was no damage to the outside. When it is plugged in, it shows that it is getting power, but not charge. Is this just a battery issue, possibly? Any help would be appreciated.
BEDickey said:
Hello all, I hope this finds you well. After having my Droid since the month it came out, I am finally having an issue I cannot seem to resolve. My phone will not charge, stuck at 16%. It took a fall the other day, so I think that did it, but it was in a lifeproof case (always has been) so there was no damage to the outside. When it is plugged in, it shows that it is getting power, but not charge. Is this just a battery issue, possibly? Any help would be appreciated.
Click to expand...
Click to collapse
Try wiping battery stats
HOW TO: Wipe Battery stats to improve battery life
coming form other android phones, ive learned to wipe batt stats in recovery to get the best life. normaly i wind up seeing voltage @ 100% a little over 4.260v now on our phones we dont have that option, and i noticed while trying out diferent...
forum.xda-developers.com
Tom
Thanks for the advice, but I found the issue after studying my phone and other information on the net. What happened is my phone took a hard drop and it broke the connection to not only the QI charging coil, but more importantly, the temp sensor attached to it as well. Your phone will not charge without a working temp. sensor, end of story. When I removed the QI/Temp unit from a spare and installed it into my daily driver, everything started working perfectly again. Heads up for all of those who, like me, refuse to give up on our Droids. Best of luck going forwards!