I got a bootloop experience this morning after tethering my tablet on a freshly charged tbolt, few minutes later my phone died and stuck in a bootloop, there are times i can go to bootanimation sometimes it goes up to HTC screen and dies, I can go to HBOOT but before i can do anything the phone dies.
Im a little bit scared about this situation because i bought my phone 2nd hand, so im not sure if i can go to verizon and have my phone repaired or replaced.
Good thing i have a 2 extra battery and an external charger i bought from ebay, I swapped the battery and my phone is back to life, it seems like the GB roms are not charging the battery properly and reporting that the battery is around 80-90%
I just checked the jcase thread few minutes ago, so as a safety precaution i reverted back to froyo.
Im not sure if the radio is the one to blame or maybe the rom doesn't charge the phone correctly thus giving a wrong battery reading saying its fully charged then it will not hold enough charge to boot up the phone making an illusion of a stuck bootloop.
Tethering seems to keep popping up in accompaniment with this bootloop phenomena... Maybe I'll stay away from it for now just in case!
Im saying that its probably not a bootloop but a wrong battery info/charging on the gingerbread roms. Since LTE drains battery a lot plus putting the phone in adhoc wifi stresses out the battery a lot.
I noticed my bolt took FOREVER to charge on GB. Luckily I have 5 batteries lol and I was able to revert back to froyo on a fresh battery before I had any major problems. Although, i did get stuck in a loop and the phone would not even turn on at all. This lasted about ten minutes. Scary as hell cuz I generally am in full control of this thing
Sent from XDA Premium on Thunderbolt
I didn't experience the bootloop problem before I reverted back, but I did notice this morning that after charging all night on GB, my battery showed 83%. I thought that odd, so I wiped by battery stats thinking it was out of sorts since I only had been running GB for a few days. Just my experience with Gingeritis VIII for what it's worth.
Good call!
I had a similar situation while on BAMF GB. After being on the charger all night, I unplugged my phone around 06:00 with 99% charge. By 07:30 it was completely dead.
I have been trying to figure out how the hell I burned through a full charge in less than 2 hours but now I am thinking it probably wasn't actually charged.
Sent from my ADR6400L using Tapatalk
on gingersense roms, my battery life was truly awful. and the phone heated up a lot too.
Related
last night i had my tbolt charging. the phone was off while charging, and it was left plugged in for a few hours beyond the led changing over to green.
after i unplugged the phone and went to turn it on, well... it wouldn't turn on. i did feel the initial vibrate i always get right before the htc screen comes on, however, the screen never came on. i ended up having to pop the battery out and then after putting it back in the phone booted normally.
however, now it seems as though my battery is draining way faster than it has been. i've had the phone a few weeks and the battery has been properly conditioned. after taking it off the charger at approx 2:00am this morning, a mere 10 hours later (whilst completely in standby for the entire time) it's already down to 83%.
what gives? could this just be an accuracy issue with the reported levels? i've read about fully charging and booting in to recovery to reset battery stats. or is it a far worse issue and something has happened to my phone that's damaged the battery in some way?
btw, i'm rooted and running das bamf remix 1.7 with imoseyon's leankernel (running in normal mode with swap enabled).
just a quick update:
after some moderate use (texting, web browsing, downloaded a few market apps) the battery continues to drop much faster than it ever did before. i'm using wifi at the moment.
Have you cleared battery stats lately?
Sent from my ADR6400L using XDA App
no, but i'm going to do just that tomorrow after work when i have a chance to fully charge the phone.
one other thing i just realized that may be contributing to the problem though... my g/f was playing around with my phone and she signed into latitude. doh!
Took the plunge and rooted my bolt on Saturday following the guide in this forum using adb. All was ok, no custom Rom, just rooted. Battery seemed to be about the same. Put the phone on charge Saturday night and was fully charged Sunday. All working as it should until Monday morning. I got the phone off of the charger and battery(2750 ma) was only14%. I freaked a little and charged the phone on the way in to work. The charge only got to around 34% and would discharge very fast when unplugged. I had read somewhere to cycle power while charging to correct errors in the reporting of battery levels, so I tried that and got different numbers every time, but not able to get a full charge.
To make a long story short, I could not get my batteries ( stock or extended) to charge. I tried imosys (forgive me if the name is wrong) on the stock Rom and even flashed the Mr2 radio and installed das bamf ginger remix without any luck. Battery would not charge under any condition. Woke up to a dead phone this morning and had to install the other battery to get the phone un rooted.
The phone is now charging as it should with both batteries.
Any ideas why the phone would not charge?
Also used 4 different chagers during the process.
you should try calibrating the battery
since you have root, you can download and run BatteryCalibration by marosige (app author shows as NeMa in the market). simple app, instructions on the launch screen.
Don't you have to have 100% battery to calibrate?
I could not get the batteries to full charge.
The Batteries were definitely discharging faster than the charger could maintain, or there wasn't any charge applied to batteries at all.
I've had mine charge at a glacial pace before and discharge so fast you could watch the percentage numbers drop just holding it in your hand for 60 seconds. Personally, I don't call a phone charged if it's on. Turn that badboy off and make sure fast boot is off as well. Even with ROMs and kernels that charged horribly, turning that thing off put juice in it in a hurry. I never had any luck getting any BAMF ROM to charge quickly, no matter the kernel I used. (I tend to use the same kernels with the same versions of android. Ziggy's for Froyo, dreamkernel for GB.) Both of those have proven to charge nicely, even if I'm wirelessly tethering the thing. I don't know what the big deal is with battery calibration and all that. I only had quirky battery charging right after I made the mistake of wiping my battery stats. Same thing happened with my dInc. I wouldn't wipe battery stats unless I had a VERY good reason, and swapping between my 1300mAh and 3500mAh battery all the time in my dInc wasn't nearly a big enough reason.
The phone was off when I put it on the charger Sunday night, and no battery left on Monday morning.
Is there a way to "undo" a bad battery calibration?
I am asssuming that when you flash a new kernel or a rom that that resets everything, At least it seems that way when I unrooted the phone.
I will probably try rooting again when I have a little time to mess around with it.
dbjones59 said:
The phone was off when I put it on the charger Sunday night, and no battery left on Monday morning.
Is there a way to "undo" a bad battery calibration?
I am asssuming that when you flash a new kernel or a rom that that resets everything, At least it seems that way when I unrooted the phone.
I will probably try rooting again when I have a little time to mess around with it.
Click to expand...
Click to collapse
Just being rooted should have zero effect on battery charging. Next time you root, do a Nandroid backup before you flash anything (ROM, Radio, or Kernel). That's standard practice for pretty much anyone that regularly flashes.
I'd re-root, nandroid, then flash whatever ROM you want....Some of the older GB Sense kernels had a "slow charging" bug, which has since been fixed. Check out the Kernels post on the dev board, the newest kernel has fixed the slow charge bug.
Alright, before you tell me to remove batterystats.bin and move along read this carefully.
I've had my HTC Legend for about 8(?) months now. Around the same time, my mum also bought one. I rooted mine, flashed CM 7.0.0, up to the newest nightly now. She left it as she got it, only upgraded to Froyo when the update came out. Everything is working great, except for the battery statistics.
Around 4 months ago my mother first complained about her battery not charging to 100%. It got worse over the weeks, and the battery level also started dropping faster and faster. It has gotten to the point where, when she gets it off the charger in the morning, it's around 52% (Even though it's been charging for forever, and should theoretically easily be on 100%). After about 5(!) minutes of using the phone, it will have dropped to a 2% battery. Battery life, however, is hardly suffering. She can just walk around with a 2% battery for the rest of the day. Obviously the batterystats are totally ****ed up. After 2-3 months my phone started doing the same, except it does it less severe. I can only charge to 50~60% as well too.
Around this point, I started looking around, and found about how android saves it's battery levels. I rooted and flashed my phone, and using fake flash, I booted into Clockwork recovery, mounted /System (S-on phone, can't edit system when phone is on, still no s-off for hboot 1.01..) and removed the batterystats.bin. I did in a couple of ways now, including the build-in option and using Android Commander. My phone, however, still won't charge past certain numbers.
Now my questions to everyone here is: Did anyone else have problems like these? Any solutions you'd like to suggest? Are batterystats/total voltage also saved somewhere else?
I'd like to point out that the battery itself is not damaged or anything. When my mum's phone had these problems, and mine didn't yet, we tested her battery in my phone, and it would charge to 100% just fine, and the levels weren't messed up.
Her problems started around the time she flashed Froyo from the official update. I can see how flashing a new rom messes up the batterystats.bin, but apparently that's not the only file being wrong?
Any suggestions are VERY welcome.
Tl;dr: Phone battery won't charge past 50% or so, battery level drops to 1% in 5 minutes.
EDIT 1: My mum send her Legend to HTC to get it ''fixed'' THREE weeks ago. She got it back today, them saying it was fixed. After a good 10 hours in the charger it still won't go to 100%, and after 30 minutes the battery levels dropped from 70% to 1%. I think it's quite shocking how HTC can say something is fixed without even trying to charge it to 100%.
you can try this, can't hurt
Turn your phone on and charge it for 8 hours or more
Unplug the charger
Turn your phone off and charge it for one hour
Unplug the charger
Turn on the phone and wait 2 minutes
Turn your phone off and charge it for one hour
Unplug, turn it on and use as normal.
Hitmax117 said:
you can try this, can't hurt
Turn your phone on and charge it for 8 hours or more
Unplug the charger
Turn your phone off and charge it for one hour
Unplug the charger
Turn on the phone and wait 2 minutes
Turn your phone off and charge it for one hour
Unplug, turn it on and use as normal.
Click to expand...
Click to collapse
Thanks for the reply,
sad to say I've already followed steps like these atleast three times. Including charging without entering pin, when off, when on, etc etc. Still, thanks for the suggestion.
no such problem yet ... but i'd be interested to know if you were able to resolve it... it cant be a coincidence both you and your mom 's battery levels acting up.
QkSi1ver said:
no such problem yet ... but i'd be interested to know if you were able to resolve it... it cant be a coincidence both you and your mom 's battery levels acting up.
Click to expand...
Click to collapse
Could be so, but I don't think we're the only people in the whole world to have this problem. I'll keep this thread updated with any information I might stumble across and any other solutions tried. If anyone could tell me where the maximum values for the battery are stored in android it'd be great, seeing how deleting the batterstats.bin file didn't help, there must be another file in android tracking battery..
Hi,
so you're not alone. My Legend is showing the exact same symptoms.
I bought my Legend used via ebay and the seller told that the battery won't fully charge. No problem i thought, just buy a new battery.
Even with the new battery it won't charge more than 60% and it decreases to 10% in 5 minutes.
Just had a test. Even with 60% power at the beginning and 10% after 5 minutes it still was working for 80 hours!
unfortunately i don't know when the probs started to occur. My legend is also with the official Froyo flashed.
regards
Mario
DRAGandDROP said:
Hi,
so you're not alone. My Legend is showing the exact same symptoms.
I bought my Legend used via ebay and the seller told that the battery won't fully charge. No problem i thought, just buy a new battery.
Even with the new battery it won't charge more than 60% and it decreases to 10% in 5 minutes.
Just had a test. Even with 60% power at the beginning and 10% after 5 minutes it still was working for 80 hours!
unfortunately i don't know when the probs started to occur. My legend is also with the official Froyo flashed.
regards
Mario
Click to expand...
Click to collapse
Everyone seems to have this problem since Froyo. HTC fixes it by replacing the motherboard, which basically means they replace 90% of the phone... So basically, there is no real fix around. :/
seem like hardware fault..
kmc30 said:
seem like hardware fault..
Click to expand...
Click to collapse
Could be so, but it seems strange as the problem starts occuring after flashing to froyo. [Even though going back to eclair doesn't seem to fix it..]
So just the other day my phone would start randomly rebooting and it only seems to do it when the batter power is lower, like less than 50%. Ive been running the same rom (mikrunny 1.7) for well over a month and have had it oc'd the whole time to 1.5 and never had an issue before now.
It was doing it last night again. It was around 55% when it started. I left it turned off for a bit while we drove home from the bar and when I got home and rebooted it and now read 7%. Shut it back off and let it charge off over night. Booted up this morning and its now at 80% when it was definitely showing the green light saying it was fully charged.
So battery going bad or do I need to recalibrate it? Already ordered a HTC oem battery from amazon (it was 7.50, didnt realize they were so cheap!) so hopefully it is the battery and not something else.
kilik64 said:
So just the other day my phone would start randomly rebooting and it only seems to do it when the batter power is lower, like less than 50%. Ive been running the same rom (mikrunny 1.7) for well over a month and have had it oc'd the whole time to 1.5 and never had an issue before now.
It was doing it last night again. It was around 55% when it started. I left it turned off for a bit while we drove home from the bar and when I got home and rebooted it and now read 7%. Shut it back off and let it charge off over night. Booted up this morning and its now at 80% when it was definitely showing the green light saying it was fully charged.
So battery going bad or do I need to recalibrate it? Already ordered a HTC oem battery from amazon (it was 7.50, didnt realize they were so cheap!) so hopefully it is the battery and not something else.
Click to expand...
Click to collapse
Once you get your new battery it would be easy to see if the battery can be the issue. I have 3 batteries myself and I notice once that one of them was always causing my phone to random reboot. I color coded all 3 batteries to keep track of them and I notice that anytime the "red" battery was in the phone it would reboot while below the 50% mark.
I have replaced that battery and haven't had this issue, I'm rooted running a stock kernel and ROM so I could say that it may have relation to the battery.
I tried to get alogcat but nothing would show because the log would clear at boot. It can be a reaction to an inconsistency on the batteries voltage.
Are you on newest radio? I flashed the updated radio and started getting random reboot. I flashed back to radio 2.08, all reboots stopped.
I was having this problem with two separate ROMs until I reverted radio.
Sent from my ever-changing, ROM-loving EVO 3D (via Tapatalk)!
So lately my 1.5 year old Galaxy Alpha running Lollipop (never rooted or modded) started having poor battery life. It used to shut off at 1% battery life. But started to die at even 15% recently. Now this past weekend I was on vacation and a few times the phone died at approx 35% and wouldn't turn back on without a charge first. And when it did come back on the time and date were very!! far off although I was in air plane mode but still seemed odd. A few days later I had it plugged in over night as I always do and saw that the phone was very hot in the morning in my hand. I unlocked it and a notification was up. Cant remember word for word but something along the lines of "battery too hot to charge". It would not charge, I've tried to pulled the battery and reinsert it etc. The odd time it will show on the screen that it is charging but it is stops very quickly. Is this normal for a 1.5 year old battery? Will a new battery solve this problem? I've had no issues with the charging port on this phone. The only problem I've had with this phone is the fingerprint scanner but I've opted to just not use it.
Basically I am hoping someone else has had similar symptons. I hope its not hardware and hoping its as simple as a new battery. But hate to order one and wait a week to find it hasn't helped. Thanks so much for reading this and hope to hear from you guys!
jond84 said:
So lately my 1.5 year old Galaxy Alpha running Lollipop (never rooted or modded) started having poor battery life. It used to shut off at 1% battery life. But started to die at even 15% recently. Now this past weekend I was on vacation and a few times the phone died at approx 35% and wouldn't turn back on without a charge first. And when it did come back on the time and date were very!! far off although I was in air plane mode but still seemed odd. A few days later I had it plugged in over night as I always do and saw that the phone was very hot in the morning in my hand. I unlocked it and a notification was up. Cant remember word for word but something along the lines of "battery too hot to charge". It would not charge, I've tried to pulled the battery and reinsert it etc. The odd time it will show on the screen that it is charging but it is stops very quickly. Is this normal for a 1.5 year old battery? Will a new battery solve this problem? I've had no issues with the charging port on this phone. The only problem I've had with this phone is the fingerprint scanner but I've opted to just not use it.
Basically I am hoping someone else has had similar symptons. I hope its not hardware and hoping its as simple as a new battery. But hate to order one and wait a week to find it hasn't helped. Thanks so much for reading this and hope to hear from you guys!
Click to expand...
Click to collapse
I've had mine since it was released and have never had a heating problem, even with the original battery.