Related
Hi All,
Got this funny problem since I have flashed TNT WM6.1.
My mobile battery shows some funny traits.
1. It can suddenly go off (even if the bar is at 87% or 63% or 30% or anything of that sort)
2. Once it goes off, it gets into a loopback of restarting the device, goes upto the screen where WM6.1 logo appears and restarts again.
3. The only way I can then get it restarted is to get it to plug to a powersource.
4. When I plugin it shows within 5 min that the battery is fully charged.
5. I use audio manager a lot and its like every 30 seconds 1% of battery is gone.
Have search through the forum but haven't found anything like this.
Anyone has face a similar problem and found any solution?
Any help will be much appreciated.
I am on SPL/IPL 3.08.
Time for a new battery....
I ran across the same problem. It turned out that the terminals on the battery were seriously worn down so much that the battery couldn't hold a charge to safe it's life let alone mine!!!! I went to a battery store and replaced the muthaf^$#a!!!!!
Go grab a new battery and you'll be electric sliding again in no time!!!!
Thanks Trej3k. Much appreciate your response.
Yeah
Had the same issue.
Replaced the battery ... and now everything is fine.
Now I don't expect 5 days without recharge but at least 2 days.
Along with the new battery I bought an battery charger so now I can use two batteries.
The nice thing is that the old battery is lasting at least as the new one, Maybe because of the charging more regularly and not so frequently and because both batteries never go in usage when they are hot of charge.
Try your thing
Aldo
I had the same problem pretty soon after I flashed my ROM for the first time. I would charge to 100% and then browse the Internet or take a call, and the device would reset within a couple of minutes b/c it would think it was out of power. The timing may have been a coincidence; I don't know. I bought an extended battery and everything works fine now.
mikey5 said:
I had the same problem pretty soon after I flashed my ROM for the first time. I would charge to 100% and then browse the Internet or take a call, and the device would reset within a couple of minutes b/c it would think it was out of power. The timing may have been a coincidence; I don't know. I bought an extended battery and everything works fine now.
Click to expand...
Click to collapse
I had the exact same problem right after flashing to wm6. I really wonder if it's a coincidence.
I ordered a new battery today because I have exactly the same problem. I also apeared after flashing WM6.1 a while ago an became worse with time. Since my battery is 3 years old, it could also just be a battery at its end of life...
Regards,
Rudi
Hi people. I'm having battery problems since I bought my TP. I tried many ROM and Radios combinations and the problem persists.
Also tried discharging the battery and long charging while turned off (3 consecutive days) as recommended by some members here in xda.
Nothing solved. What could it be? A hardware problem (TP itself) or only a bad battery? Whats more likely?
I would like to know where can I buy an original spare battery to test this. Anyone know?
Thanks in advance!
google.... Here's one, but it's a yahoo page. Take down the oem # and start from there. Also, i think there was a little booklet that should have came with your tp about accessories... http://www.wirelessground.com/htctprooembatt.html
what about using non-official batteries? its risky? because there are batteries for TP for about 5 usd
You know that it will drain battery as long as it is in "sleep-mode" and not entirely powered down. You have to press the powerbutton for 3-4 seconds and then it asks you if you want to power off.
Mr.Sir said:
You know that it will drain battery as long as it is in "sleep-mode" and not entirely powered down. You have to press the powerbutton for 3-4 seconds and then it asks you if you want to power off.
Click to expand...
Click to collapse
Of course, I mean my TP has a abnormal batt drain with normal use... the batt lasts less than 12h. I unplug it 10am and the battery is finished before 10pm depending on use.
have you by any change changed the TF3D theme?
i made my own theme, but i get the impression that battery drains much faster now. watched the battery fall from 21% to 18% in 3 minutes without doing anything besidesscrolling between TF3D tabs.i think themes might be making more use of the 3d accelerator and drain the battery..
I'm using default theme from ROMeOS v1.20
respider said:
Of course, I mean my TP has a abnormal batt drain with normal use... the batt lasts less than 12h. I unplug it 10am and the battery is finished before 10pm depending on use.
Click to expand...
Click to collapse
yeah.. agreed..the bat is so fast drain. never have this problem with athena.
respider said:
Of course, I mean my TP has a abnormal batt drain with normal use... the batt lasts less than 12h. I unplug it 10am and the battery is finished before 10pm depending on use.
Click to expand...
Click to collapse
Oh, I´m sorry
Do you have it turned on all the time in locked mode? Or do you put it to sleep/standby when you not use it?
Mr.Sir said:
Oh, I´m sorry
Do you have it turned on all the time in locked mode? Or do you put it to sleep/standby when you not use it?
Click to expand...
Click to collapse
Standby when not in use. Actually, while I dont use, the battery drain seems normal, maybe 2 days or more. The problem is when I use it.
respider said:
Standby when not in use. Actually, while I dont use, the battery drain seems normal, maybe 2 days or more. The problem is when I use it.
Click to expand...
Click to collapse
I have the same problem... When I dont use it (stand by mode) it lasts 2 days, but when I use it is lasts 12h maximum...
Tried everything.
Dont know what to do...
thats sad =(
maybe Ill try one of those alternative batteries in ebay
How about upgrading the Radio Rom!? I have found since going to 1.02.25.28 and having ROMeOS² v1.21 my battery life is much better than stock Roms of both!!
Its something worth trying and easy enough to change back...
Has there been any good solutions? My battery life is starting to annoy me.
Maybe I'll pick up a second battery and charging cradle thing for it...
That's one thing that I liked about the instinct...
I think we need a Stock TP to compare it to .. I know when I bought mine for the first day or two without adding anything to it, I didn't notice an issue with the battery. Now that I've installed tweaking software, theme, etc - battery drain is definitely noticeable. I'm thinking it may have to do with one (or more) of the programs we put on the phone.
Anyone here have a completely stock TP with a battery problem?
viper_campbell said:
How about upgrading the Radio Rom!? I have found since going to 1.02.25.28 and having ROMeOS² v1.21 my battery life is much better than stock Roms of both!!
Its something worth trying and easy enough to change back...
Click to expand...
Click to collapse
tried all radios available in wiki page (except .11 and .16)
but that was with romeos 1.12 and dcs, I'll give a try for .28 with romeos 1.21
but I'm pretty sure that the problem is hardware, since many people use romeos 1.21 and radio .19 and dont have problems...
My phone had a very short battery life when it was bone stock too.
I'm afraid to see what it's like now with the tweaks!!!
mine is original stock TP batterry..but also facing the same problem. in average have to charge twice in a day..and the charging takes a few hours. so my phone is only running on battery for not more that 15 hrs in a day..
I'm hoping now thats its a bad batch of batteries problem and not a phone itself problem
I'm having a simlar issues. Put my TP on off/standby (single press of power button) at around 10pm, on flight mode enabled, all appliactions closed via task manger. Battery was at 80% when I did this. My TP's low battery alert woke me up at 4:30am at 8% charge.
My Blueangel used to last several days in the same state out of it's cradle without needing to be charged!
I to am hoping it's just a duff battery.
UPDATE: Seems I was being a twonk! I had unchecked the Auto-Shutdown option for a game I was playing and forgot to turn it back on, so my TP was turning on at midnight to do it's housekeeping and not shutting down again properly.
I still don't think my battery life is normal though, may try the following:
Some Chap said:
Found this on Sprintusers.com: It's an 06 post, but I wonder if it's still an issue. Found here http://www.sprintusers.com/forum/showthread.php?t=175896
Received the below from my Sprint rep.
It has been brought to my attention that there is a glitch in Windows Mobile phones that has been there since WM5… Apparently when a phone is first used the firmware looks at the charge on the battery as a reference point as to how long to charge it for until it is completely charged. So for example, if you have a WM phone that has a half charge on the battery when you first plug it in the device will only ever charge up 50% of the battery. You need to basically set the phone to put that marker in place when the phone is completely dead to gain the most battery performance you can.
Here is the best practice for doing this:
----------------------------------------------------------
1. Let the phone completely die on battery power.
2. Plug the phone in and charge for only about 5 minutes (just long enough it can boot up completely)
3. Perform a hard reset of the device, this is done differently depending on the phone model.
4. Then place the phone on charge for at least 8hrs.
---------------------------------------------------------
This should reset that marker that the operating system places on the battery charge cycle and will allow the phone to completely charge the battery rather than only a % of a full charge. This procedure can be done at anytime and I would suggest having your customers try this process first before returning a device based on battery life issues.
Click to expand...
Click to collapse
I charge my battery overnight. I'm guessing this is bad for the battery but how bad? And is there some app or something that will stop the charge once it hits 100% while still plugged in? Thanks
I believe the phone has overcharge protection circutry in it already
has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.
JDMr2 said:
has anyone noticed that, with the new radio, it takes longer to charge and sometimes it doesn't even reach 100%. however when i reboot it, it actually is at 100%. The the batter indicator isn't as accurate anymore.
Click to expand...
Click to collapse
yes i have, i wanna say its because its not an official mod, but im using the jf update? maybe its build specific, which one you using jd?
i thought i was the only one to notice
I've used the sapphire radio update w/ 5.0.2Hr5 and the new ADP radio update w/ JF1.5. I noticed this with both combinations.
I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?
I highly doubt it has anything to do with overcharging since it's not a hardware issue.
LOL! It's never been accurate at all with any software build or radio combination. I can charge my phone all the way and pull the battery and reboot and get an accurate reading then. The battery life and measurement has been the biggest flaw with this phone. It hasn't gotten any better with a new build or ever will, imo.
wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.
I'm running The Dude's ADP 1.5 and I noticed also that it takes a lot longer to charge the phone.
Normally if I plug it in, it was fully charged in 2-3 hours. Now it takes more than 5hours
John5788 said:
I am noticing this as well with JF's build
So what is the deal? Is the phone actually fully charged after 2 hours and the meter doesnt actually realize it? will this cause any problems with leaving the phone charging in the wall and overcharging?
Click to expand...
Click to collapse
I am also seeing this same issue. I unplugged my phone from the charger at 11am and it was 100%. At 12:45 it was down to 87%. I fell asleep by the pool and woke up and it was at 52%, this was around 3p. I went home and charge the phone. I looked at it around 5p and it was at 72%. I rebooted the phone with Call+Menu+End(thanx JF, Dude took this out his buld) and it was at 100% when rebooted. It may be that TMOBILE branded G1's may have a underlying hardware/software issue which does not allow the OS to fully read the battery. My assumption and im just taking a stab at this is that possibly since ADP 1.5 features processor frequency change (ie, 528mhz to 384, 122 when sleeping) it may be reading the battery when at 528mhz and then when it drops to 122mhz the phone cant write to the RAM or somehow it gets lost b.c on refresh it reads 100%. I may not know anything about what I wrote but its just a stab at an idea. Maybe someone can do some testing to see what happens internally between ADP and RC33 and/or G1 & ADP.
JDMr2 said:
wasn't THIS bad when i had JF1.42 RC33. it was just when I updated to Haykuro's or JF's 1.5 builds. An example will be where I begin charging my phone at 5% and after 3-4 hours, it'll only be at ~65%. I reboot the phone and it automatically fixes itself to 100%. It normally only takes ~2hrs for my phone to charge to 100%.
Click to expand...
Click to collapse
I agree... it HAS gotten worse with 1.5 builds. It takes for ever to charge up to 100% (especially if you have something running in the background. it might just be the overclocking that's doing it). After rebooting, it will give a more accurate reading. I've noticed also (with all builds) that if you reboot with the charger plugged in... it will give you a false, higher battery reading than if you rebooted with it not plugged in. If you get (or suspect) a false reading, pull the battery while phone is on and let it sit idle for a couple seconds and then reinsert and power on. That should be pretty accurate but it seems most false readings happen while the phone is charging. One way to get around this without rebooting to make sure that it's fully charged is to charge the phone while its off. Just remember green light means 90% or higher and not 100% like ALL other HTC devices. That is part of the problem itself....
if the light turned green when it is charged 100%, alot of these false readings would not be happening. I know that sounds silly but the OS/hardware have to judge when its at 90% even when it's powered off. Kinda more complicated than just orange light when charging and green when fully charged (like all other HTC devices). Instead we have to go from red flashing to red to orange and to green. Maybe that makes sense to some? I don't know for sure... it's merely my long-winded theory about the crazy, ****ed up battery life for this otherwise fantastic device, lol! Sorry for the loooooooonnnnnng reply...
I have dudes. 93 and that's when I ran to the issue you guys are talking about. I happened to just install a battery widget and thoughy that's why it had to reboot for accurate reading it hasnt been long to recharge after uninstall. The other builds all seemed accurate to me. It also seems like my battery doesn't last as long with the new radio but at the samew time it seems that it quickly drops out of the 90's and 80% range but sticks in the lower ranges longer. I don't know why with all of our technology laptops and phones can do the carziest things but only for an unreasonably short amount of time...
I drained my battery letting the phone die, took the battery out, put it back in after a min or so, and began charging. It seems to have fixed the long charging issue. It fully charged my battery in ~2.5hrs. I'll report back if the battery life lasts just as long as it charges.
Well, this was interesting... Since day 1, I have had great battery life and have not experienced what everyone else has been experiencing.. An occassional lock-up/reboot, but nothing major.
A couple of weeks ago, I switched to a backup battery (andida). Things have been going well w/ that battery. Yesterday, I updated cwm.. While the andida battery was out, I decided to switch back to the stock battery for a while. Then, the following items took place all within a few hours of use, which I have not experienced.. ever before:
- Battery temp running high.. Andida constantly hanging around 22.2 - 23.2. Stock was hitting around 43 until i rebooted the phone, then dropped to 40. It is currently running at 36.
- 2 shutdowns. I could not boot the phone past the LG logo after the shutdown. Was able to boot into CWM though > went to shutdown > tried to boot, same thing. Had to pull the battery in order for it to boot.
- Received a phone call, answered, but the phone kept ringing during the entire phone conversation.
- 2 screen lockups. Could slide the unlock, get the haptic feedback, but that was it. It would not unlock. Had to reboot.
- 1 black screen of death? Total black screen with the task bar displayed. Was able to go into settings, pull down the task bar, etc. Background was blacked out. Reboot, fixed.
- Can not get gps. Was driving for 5min trying to get a GPS lock, nothing. Opened up GPS test and not a single satellite showed up in the list.
- Finally... and worst of all. Last night I plug in the phone for a couple of hours. As I'm going to bed, I disconnect the usb from it.. and take a glance to see where it charged to - 100%. I go to bed at around 1:30am. I wake up at 7:30a, turn on the screen of the phone, and it gives low battery warning. It's at 2%. I reboot the phone to make sure. It's at 1%.
So idk.. maybe something was stuck running. I'll find out here shortly after this charge is done.. but I am seeing a major difference in the operation of the phone after putting the stock battery back in. I had not experienced this when I was running the stock battery in the past. (I had an occasional lockup/reboot.. but not to this scale.. and I had always had fantastic battery life. Every single time I unplugged before bed and had 100%, I would have 98% when I woke up).
Suggestions? Changes were updating to the new CWM 4 and putting the stock battery back in. Running Bionix RC1..which I have been running for a while. I'll let this sucker charge up and see what it does. Maybe I should wipe the batt stats?
yeah wipe the batt stats. possibly try cm7 its really stable now. i know it doesnt have the a2dp but every else works. i would say another kernel also faux's or morific work fine. use setcpu if your going to oc. if you choose to flash another i would do a complete wipe of everything then install so hopefully the problems wont pop back up in the new flash. i read in one of the thread that if your battery is dated 3/2011 it will have issues but the 4/2011 or whatever will have less reboot and freezes issues may wanna try getting a replacement if you wanna stick with bionix until krylon does an update.
The andida battery doesn't have a temp sensor, so it's worthless for testing temperatures.
well, idk.. who knows what the crap happened. I charged to 79% and unplugged. 2.5hrs later, I'm still at 72%. That's around 3% an hr. Last night was 17%/hr.. Something happened last night.. Man, I'd love to know what took place.
Either I had an app going wild all night, or the battery really never charged.. and the 100% was deceptive. It's just nuts how all of these probs all of a sudden surfaced right after cwm 4 and putting the stock battery back in. They never surfaced b4 on the same ROM and with the same battery that I used for weeks and weeks.
O'well....
schmit said:
well, idk.. who knows what the crap happened. I charged to 79% and unplugged. 2.5hrs later, I'm still at 72%. That's around 3% an hr. Last night was 17%/hr.. Something happened last night.. Man, I'd love to know what took place.
Either I had an app going wild all night, or the battery really never charged.. and the 100% was deceptive. It's just nuts how all of these probs all of a sudden surfaced right after cwm 4 and putting the stock battery back in. They never surfaced b4 on the same ROM and with the same battery that I used for weeks and weeks.
O'well....
Click to expand...
Click to collapse
I know, it is just weird but it does happens from timr to time.
God bless you my brother in Christ
I see that you are a Jesus Freak just like me
Sent From My Stock G2x
When the battery is less than when it removed,After some time and putting it back will be full power display
SORRY FOR MY BAD ENGLISH
You should wipe battery stats when doing any major rom change (stock to custom or between different roms).
Battery will always be wonky the first time before a full charge/discharge on the rom unless it is 100% and battery stats are wiped.
Typically what I do (on CM7), is when I wake up the phone is at 100%. I download the latest nightly while I'm in the shower. Jump out, it starts to flash. When its done and booted up, I wipe stats then unplug the phone and go to work.
I don't always wipe stats. But with all of the battery tweaks and fixes he's done, I will occasionally.
I very rarely ever completely turn my phone off, but last night I decided to turn it off right before I went to sleep. My battery was down to 25% right before I turned it off. When I woke up this morning the phone would not turn on. So I decided to plug it into the wall charger to see if it would help. Well the phone did turn on after I plugged it in and to my surprise the battery was showing as 0% charged which is why it wouldn't turn on without being plugged in.
So, that means that something drained my battery from 25% to 0% while the phone was completely turned off. What in the world would be running while the phone is turned off that would drain the battery like that?
So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.
MusicMan374 said:
So this has happened twice now. I'm running on ARHD 4.1.0 w/ Bricked 1.0.
My battery will be running normally, normal drainage, etc., and then it'll just drop from 90 to 70% in less than an hour, and normally drain for another hour or so, and then at around 60% just die. I can't attach a screenshot since normal screenshot apps aren't working and the stock function keeps producing invalid images, otherwise I would, but it literally just looks like it got to 60% and instantly dropped to 0%, there's just a vertical line of missing percentage. I took my phone out of my pocket, expecting it to be around 40 or 50%, and it wouldn't turn on. When I hooked it up to the charger, it took a good 5 or more minutes to even respond to the power button. Do I have a bad battery or just incredibly out of whack battery stats? I have never had this problem with an android phone before, and I thought for sure one full charge overnight would fix it, but I guess not because it happened twice. Any suggestions?
Edit: I use an app called battery snap to monitor the battery level and temperature with a widget, I checked a snapshot history while it was charging and for a few seconds it was at 0.002 volts. But then it jumped back up to 3.897 or something around there. That doesn't sound very good to me.
Click to expand...
Click to collapse
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e
claudenegm said:
I don't know much about this, but I don't think battery stats have anything to do while the phone is dead. Even if it does, the phone would at least respond after a minute or two, not 5..
My suggestion is that you can order an Anker battery which is kinda cheap ($15 I think) and try.
You won't loose anything
Edit: Try wiping battery stats, do a full charge, fully discharge and fully recharge again and see if it helps (In your case I don't think this will help, but huh, let's hope ;D)
Sent from my HTC Sensation Z710e
Click to expand...
Click to collapse
Thanks, I'll try it. I flashed the new cm7, since I just got tired of sense woes. I read battery life on this was amazing, and I'm hoping it was just a bug with the kernel/rom I was using. Battery stats would've been wiped when I wiped for flashing this ROM, so I'll do a full battery cycle and cross my fingers. My only thought is that maybe, if the battery stats were screwed up enough, it thought it was at 50 or 60% but really it was more like 10%. I remember having issues after I flashed the custom kernel, where before I flashed I was at 70%, and when I rebooted I was at ~10%, and I was like what the hell? So it ended up dying on me, but then I turned it back on and it said 50% or something around there. And then it functioned as normal until it died again, for real that time. Hopefully it was the kernel causing the issue. I'll run a few tests with this and see. If it is the battery, I'll try t-mobile for a warranty replacement of the battery.
The battery measurements seem to be really quirky on this phone. When the phone is idle it seems to drain anything from 50ma to 400ma for no particular reason. You cant really rely on the % too closely
Yeah, I've found the percentages to be pretty inaccurate. Hardly an hour and a half on the battery and it's down to 84%. I did play a game for like 10 minutes and the screen has probably been on for 20 or so, so that's not incredibly unreasonable. I'm just waiting for that dropoff to 0%, if that happens again I'm thinking it's hardware, because I'm running an entirely different ROM and kernel right now.
So it just happened again, went from 42 to 14 after reboot, had to remove battery and reinsert to fix. But other people have reported this issue on cm7. So, I'm thinking maybe that it's an issue with android 2.3.5 or the kernel for it, since it's happened on both arhd 4.1 and cm7, both 2.3.5 roms. I'm going to try and flash faux's cm7 kernel over it and see if it fixes it. May or may not, might be a long shot but worth a shot, I'd rather not switch roms for a third time in the same day.