[Q] SRF 1.2 charging issues - Epic 4G Q&A, Help & Troubleshooting

Whenever I charge my epic overnight it always reads 100% when I take it off the charger but a few minutes later it will drop down to ~30%. It charges fine after that though. Could this be a problem with undervolting? I've also got my I/O set to noop if that might be the issue.

Have you calibrated the battery? There is some argument as to the validity but that seems to be the common first and last answer needed.

Yeah, I've calibrated the battery on more than one occasion with no luck

What about deleting your battery stats in CWM? Though many consider this part of the "calibrate your battery", some don't do it.

The other thing I have seen recommended alot is to get CPU Spy and make sure it is going into Deep Sleep and get Spare Parts and look for any Wake Locks that are running down the battery.

I just checked cpy spy and it seems to be going into deep sleep properly. I also set all voltages/clocks to default and the problem still persists.

There's no wakelocks either. Any ideas?

With a battery that is almost dead go into cwm go to advanced and clear battery stats. Charge your phone to 100 %. Clear stats again. That should fix that for you. I had to do this with another rom I tested . Not sure which rom.

Related

Quick Battery Drop in Initial 10%

Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
chillmeow said:
Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
Click to expand...
Click to collapse
I spoke to RMK as well as others about this in IRC, doesn't look like anything we can do, deep in the HTC code I guess.
I have the same issue using SkyRaider 3.1. Battery is 100% then after 5-10 minutes drops down to low 90s. It bothered me at first but after several days of moderate to heavy use and still having almost 50% battery left at the end of the day, I just figured it was some kind of bug when reading the battery level at the beginning. How is your battery life overall? If it's like mine, then i wouldn't worry too much about it as long as it's lasting longer. I'm using the 1750mAh battery from Sedio.
I was having the exact same problems until I went back to stock everything and bump charged. Took the OTA for 2.2, rooted, custom recovery, bump charged, wiped stats and cache and now I'm good to go. I usually dont think crap like this works but it made a huge difference in battery life and stopped the 100-90% problems I was having.
KB
I found this on EVO forum, but I don't know how his solution works. I personally don't think this would be the solution.
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=704272
I am using the 1500 mAh battery.
My battery life is uptime around 24 hours and awake time around 6-9 hours depending on usage.
so you're not having the issue anymore, after going back to stock (non rooted) with the official OTA 2.2?
KB Smoka said:
I was having the exact same problems until I went back to stock everything and bump charged. Took the OTA for 2.2, rooted, custom recovery, bump charged, wiped stats and cache and now I'm good to go. I usually dont think crap like this works but it made a huge difference in battery life and stopped the 100-90% problems I was having.
KB
Click to expand...
Click to collapse
KB Smoka, so you don't have this problem anymore?
Do you think format the phone and wipe all the data will help?
Have anyone tried formating the phone?
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
superchilpil said:
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I did bump charge this phone, but it still drops like crazy.
I'll try this out tonight.
Thanks!
Is this a once time fix thing or do you have to do it every time you charge?
bump charging 4 or 5 times in a row (basically bump as many times as you need to to get it to where the light turns green withing a minute of 2 or plugging it in again) and then wiping battery stats solved this for me... kinda.. i still have to bump twice, but after that it'll stay at 100 for a good while and work it's way down normally, no jumping 10% down..
superchilpil said:
I've searched and found that the cause is the phone saying the battery is charged fully when its not basically so to fix this after it goes to 100% while the phone is one then u should turn it off and let it charge fully from there
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That is bump charging. Something htc is unable or unwilling to fix.
The issue has been known for a while and you have to 'bump charge' every time to avoid the 5-10% drop.
Here's their response about fixing the "bump charge".
"Dear **********,
I understand you would like to know if an update has be released to help get a full charge on your battery without having to bump charge it. At this time we have no information about any updates being released to help resolve this issue on your device. If an update is released for your device you will receive a notification on your device that an update is available.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number ************.
Sincerely,
Victor
HTC"
melophat said:
bump charging 4 or 5 times in a row (basically bump as many times as you need to to get it to where the light turns green withing a minute of 2 or plugging it in again) and then wiping battery stats solved this for me... kinda.. i still have to bump twice, but after that it'll stay at 100 for a good while and work it's way down normally, no jumping 10% down..
Click to expand...
Click to collapse
Do you bump charge every single time you charge right now? It's pain in the butt if I have to bump charge everyday.
Yup every day. 4 or 5 times is way overkill though. Just charge phone until green, turn off (don't need to unplug), wait until it turns green then do the plug/unplug one more time.
ufvj217 said:
so you're not having the issue anymore, after going back to stock (non rooted) with the official OTA 2.2?
Click to expand...
Click to collapse
Went to stock (official OTA), rooted, custom recovery, bump charged, reset stats and cache and I'm good now.
I charged it to "full" while it was powered on. Once the light turned green I turned the phone off, charged again until the light turned green. Took about 25 minutes. Powered up in recovery wiped battery and cache and now I'm good. The key is after doing all this you have to let the phone completely die.
If you're wiping your battery stats after a bump charge, you will have this problem every time you don't bump charge.
If you wipe your battery stats after it goes green without a bump charge, you won't have this problem.
This is because the software thinks the bump charged battery levels equal 100% charge. A bump charge adds approximately 10 percent of charge.
Formatting your phone or any software changes won't actually do anything other than wipe your battery stats while your phone is not at bump charge levels.
vantagejuan said:
If you're wiping your battery stats after a bump charge, you will have this problem every time you don't bump charge.
If you wipe your battery stats after it goes green without a bump charge, you won't have this problem.
This is because the software thinks the bump charged battery levels equal 100% charge. A bump charge adds approximately 10 percent of charge.
Formatting your phone or any software changes won't actually do anything other than wipe your battery stats while your phone is not at bump charge levels.
Click to expand...
Click to collapse
I'll try this instead! I don't want to bump charge everyday! It's too troublesome.
chillmeow said:
Hi all,
I am puzzled by my problem. I am using Virtuous 2.7 + King's BFS kernel #4.
My phone battery will drop quickly from 100% to 92% right after unplugged from the power cord. By quickly, I meant I did not use the phone, killed all tasks, and battery will drop to 92% literally in minutes.
Bump charging, wiping battery stats, wiping dalvik cache, killing all tasks are not helping at all. I don't have SetCPU, but someone in the forum mentioned they have SetCPU, and it is not helping either.
Is anyone having this problem? Does anyone have any idea on how to solve this?
Please help.
Thank you!!!
Click to expand...
Click to collapse
The reason this happens is because the battery gets charged fully to 100%, and then is allowed to slowly drain back to 90% (or so) before it's charged back to 100% again. This is how Lithium batteries are charged.
Try this: charge the battery to 100%, and immediately disconnect it after it's full. Notice how the battery doesn't drop to the low 90's immediately.
The reason "bump charging" appears to work is because there is no drain on the battery, since the phone is off. It goes to 100% and stops.
There's nothing we can do code-wise to fix this; it's just how the battery technology works. Keeping it fully charged at 100% while on would damage the charging capacity of our phones.
Btw.. wrong forum.
Solutions in search of a problem
Let me preface this by saying that I’m not an electrical engineer, or any sort of expert on phone hardware, but I think a couple issues are being confused. I’ve seen many posts about this battery “problem” here and elsewhere and an important point is being missed. People are confusing what the battery is actually doing with what the phone SAYS the battery is doing. They are NOT the same thing. The battery is a physical device and it will do what it’s going to do.
Battery life is a function of battery quality, initial state of charge, and demand. If you want the battery to last longer, look at ways of reducing demand. What applications are in use? How long is the screen on? What brightness level? Overclocking and undervolting settings? All these will affect ACTUAL battery life.
At lot of the “solutions” discussed have nothing to do with conserving energy use, but have everything to do with messing with how the phone REPORTS the state of charge. A good example is the issue of the initial drop reported by many users during the first few minutes after unplugging the charger. I see this on my own phone. If the phone is “taught” that 100% charge is when it is totally crammed with juice and plugged in as well, it’s not surprising that there is a good bit of voltage drop (+/- 10%?) right after unplugging. Does this mean there is a problem? NO! It’s just the battery doing what batteries do. A lot of the suggestions about wiping battery stats and such have nothing to do with saving energy. They are ways of fiddling with how the phone REPORTS its condition under various circumstances.
My advice: if you are happy with how your battery lasts, over the course of a day or so, then learn to relax, crack open a cold brew, and revel in just what a great phone the Incredible is. If your battery isn’t lasting as long as you need it to, then look at ways to save power or get a larger capacity battery. Tweaking the battery meter function is simply a feel-good exercise and won’t get you any actual improved performance. END OF RANT.
I can confirm that my gf's phone and my good buddies phone(both were never rooted) have never had a problem with the phone charging up slow first off(both phones charge about 1% per minute). And since they accepted the OTA, have not had the problem of charging to 100% and quickly jumping down to 90%. For instance, the other day my buddy charged his phone while on to 100%, played a game for about 2 minutes and closed it, battery was at 99%. Now I have tried and continually try every possible solution to my battery dying quick and charging slow, but am realizing that this must just be the cost of customizing my phone to my liking. And at least for the moment, a stock 2.2 DINC is just not an option for me.
larsrya8 said:
The reason this happens is because the battery gets charged fully to 100%, and then is allowed to slowly drain back to 90% (or so) before it's charged back to 100% again. This is how Lithium batteries are charged.
Try this: charge the battery to 100%, and immediately disconnect it after it's full. Notice how the battery doesn't drop to the low 90's immediately.
The reason "bump charging" appears to work is because there is no drain on the battery, since the phone is off. It goes to 100% and stops.
There's nothing we can do code-wise to fix this; it's just how the battery technology works. Keeping it fully charged at 100% while on would damage the charging capacity of our phones.
Btw.. wrong forum.
Click to expand...
Click to collapse
Sorry that I posted in the wrong forum. I thought this is related to the kernel or ROM I am using (Which is development right????).
Not to question your knowledge about the "battery technology", but why is it only happening to certain people? Nowadays most device are using Li-ion battery, why this phenomenon do not occur to all devices?

Battery meter/stats causing all kinds of issues

So I've been dealing w/ this little issue for the past few months where I can tell that the battery meter isn't reading correctly when the battery starts getting super laggy, slow to respond to inputs, etc. I've also experienced the same issues that I've read about here on the forums where after resetting the phone, I get drastic changes in before and after readings.
Just today I decided to search for the process to properly recalibrate the battery stats...jesus christ, there are opinions everywhere! Out of all the ones I've read, I've never understood the repeated charging and depleting cycle, THEN resetting the battery stats. Isn't the purpose of the battery stats to teach it to learn how to use the battery, so why wouldn't we be resetting the stats from either a completely dead or completely charged battery, then doing the power or draining cycles a few times?
Either way, I completely killed the battery lastnight, reset the stats and charged it w/ the phone on but in airplane mode. Unplugged for a moment, plugged it back in, LED went from red to blue within a few minutes. Did it one more time since I read random suggestions about "boosting" the battery like this. I then powered the phone off and did the same thing. During use today, the meter has been steadily dropping, maybe even a little faster than I'd expected, but I chalked it up to the phone learning.
Now the issue I'm having it that the phone froze about three times after doing the resetting and charging. Now mind you, this has happened before immediately after I flashed Syndicate w/o even touching the battery stats before or after a fresh ROM/Kernal installation, so I'm not goint to immediately assume it's because I may have done the battery stats steps incorrectly. At this point, I just want a truely accurate reading...none of the sluggishness when it says 29% then resetting takes it to 9% and the screen goes dim, the freezing the phone gets when it goes below 15%, etc.
There must be one, solid, concrete way to do this battery meter thing that doesn't involve everyone getting into a pissing contest about who is right, who is wrong, getting into a long speech about lithium battery blah blah blah. I just want a meter that reads accurately, period.
I agree. I have heard several methods to calibrate a battery but not one concrete method. I have read that its bad to run a Lithium ION battery all of the way down. Then I read that its the best way to condition the battery. Anyone with the proper method to calibrate the battery and make the reading the most accurate will get some "thanks" from me.
Sent from my SPH-D700 using XDA Premium App
While I can't say the meter was dead accurate when stock, at least it doesn't give me the issues I've been experiencing. There must be a way to find out how Sammy does it.
I find that the charge to 100 on, unplug, charge to 100 off, unplug, charge to 100 on, then turn of and clear battery stats from cwm works. I have no logical explanation why but i notice a significant battery boost and fture efficiency. Only reason it gets screwed up is flashing something new, but when I redo the process I get the same battery efficiency back. Also make sure any flashes don't activate syncing. I flashed something that turned mail syncing on and it was killing my battery.
My opinion on the whole battery deal is do nothing. These are lithium ion batteries, they have no "memory" effect. About the only way you can hurt them is to deep discharge them repeatedly or overcharge repeatedly. I don't feel there is a need to fully cycle 100%-0%-100%. Or charge off, then on, then unplug, blah blah blah... That probably just overcharges the battery anyway.
A while back I tried monkeying around with all those tips and tricks people post, didn't seem to do anything for my life. After a week or so of normal use the phone seems to learn your battery anyway. I say just let the phone do its thing, spend your time playing with cool apps or something.
No offense Insanity, but did you even read my post or know what batter stats does? I know Li batteries don't have a memory, its been stated before in nasseum. Battery stats is an application that tells or phones how to properly read the charge/discharge rate of the battery. Please don't take this thread down the "memory" blah blah blah road, because that's not the issue here. My battery is perfectly fine, I'm trying to find out an unbiased, educated, personal-opinionless and concrete way that battery stats need to be programmed, ie the way Sammy does it since I didn't have this problem until I started flashing roms.
All I'm saying is don't do anything, the phone will learn. When I stopped clearing battery stats every time I thought there was a problem I stopped having drastic drops in my battery meter after rebooting like some people have run into.
I haven't cleared battery stats in months now, my battery life is great and my phone doesn't lose mass amounts of battery randomly on reboot.
I also stated in my OP that I've been on this rom for a few months, if not even longer since I've been bouncing back and forth between Syndicate and Bonzai. Point is, months later I'm still having the issue, so clearly something isn't calibrating correctly, hence my creation of this thread.
Even if the battery stats are wrong/improperly calibrated/whatever you would call it I don't see how that would lead to lockups. Are you getting FCs at all? Maybe there's some data corruption at play? Is your filesystem journaled? When the phone locks up are you able to logcat?
The lockups I'm referring to only happen after I reset the battery stats, then it stops after a day or so or charging and discharging...it just never reads the battery correctly even after repeated usage. No FC's, phone just locks and a battery pull is the only way to stop it, journaling is on because the risk of FC's isn't work the slight speed increase and I honestly have no clue about how to check and/or post logcats.
m5james said:
I honestly have no clue about how to check and/or post logcats.
Click to expand...
Click to collapse
Make sure debug mode is enabled on your phone before it locks. When it locks plug your phone into your PC. Try from a DOS prompt inside a directory with the adb executable:
adb logcat > filename.txt
Let it run for a minute or so then ctrl-c to break out of it. If the phone is in fact completely locked it won't work, but its worth a shot to try to get a behind the scenes look at what's going on when your phone pukes. If you notice it lagging or something that makes you think its about to puke, try to get a logcat of that too. Use different file names when you logcat so you don't overwrite the old one.
issues with battery meter
Ive had the same exact problem. Its been fine since september when i got the phoen and even through flashing the phone. Everynow and again it will have a large drop after flashing but i typically have written that off as the power it takes to flash. Now after ec05 and this gingerbread leak, may battery stats is unreliable. It will stay at a certain percent until my battery dies. At any given moment i never know how much battery is left.

New Battery Theory - Bad Percentage Reading

Hey all, so I have a different theory on the GNex battery issue but I'm not sure how to test it. It also might explain why there has been such a discrepancy in people's battery stats.
My theory is that there is something wrong with the way ICS/GNex is charging/reading/identifying battery information. Here are a few of the reasons why I think this is the case.
1 - My phone will occasionally charge absurdly fast, like 20 percent in 10 minutes... but then it will die equally as quick. My first thought was that the phone just charges and discharges quickly... BUT
2 - After charging for, say an hour, when I do a battery pull and let it sit for a minute or two before putting it back all of a sudden my super quick battery charge to 62% is now only at 37% (actual numbers that happened to me tonight). So why did I do a battery pull...?
3 - Because I noticed that after 10 minutes my phone had gone from 62% to 56% and I thought that was absurd. Once I did the pull and was back to my (as I like to call it) normalized battery percentage I have only dropped 15% in 2 hours and that includes heavy data usage on maps, navigation and texting. And another strange thing
4 - I have actually seen it go the other way! I once was around 30%, rebooted the phone and it jumped to 50%. Now that I'm thinking about it I often see weird fluctuations in my battery reading. One minute it will be 28%, then I turn it off and turn it back on and it will be 29%. Oh... and for those of you wondering
5 - This has happened both on a stock rom, rooted stock (although not like that would make a diff) and a custom rom ARHD. But still there is one last question...
6 - Why is there so much disparity on the issue? My theory is because this battery madness is so unpredictable you, you don't know when you get a normalized charge or an inflated charge. And lastly...
7 - I think it's gotta be a SW issue, why else would Nexus S owners be seeing the issue as well? (So that's good news... hopefully).
Soooo, that's my little rant. I think part of the problem is people are getting distracted by all these other theories with kernel drivers and etc because of the absurdly high Android OS issue (although in all fairness my theory could be more misdirection).
So why post? Well if people could try their luck validating/disproving my theory I would really appreciate it!
Here's what I'd like (and what I am going to do).
Charge your battery for an hour, if it charges really fast note the percentage.
Optional: Play with the phone for a while and see if it discharges quickly.
Do a battery pull, let it sit for a sec and put it back in and note the percentage.
If the percentage is significantly lower (10+%) start using the phone now and note the time to discharge.
Thanks!
EDIT: Also a good thing to mention, I am not disagreeing about the Android OS bug - I think that's also very real and something I have experienced as well. BUT if you look at the other battery thread you'll see a lot of people posting battery success images with high Android OS utilization. I think it could be an indication of multiple issues contributing to a negative experience.
Oh and I submitted a bug report to Google.
http://code.google.com/p/android/issues/detail?id=23311
I've also noticed crazy battery drop after reboots or pulling battery. Easily drops 10%+ at times. Reminds me of my great blackberries back in the day
Sent from my Galaxy Nexus using xda premium
all good here. i'm very pleased with the battery life.
while there may be issues with the stats, the wake times are real for some users - as well as the heat generated (indicating the cpu is working) when the phone should be sleeping.
There is no question there are either bugs in ICS that cause wake locks to get stuck, or badly written apps that keep it awake that didn't keep awake froyo/gingerbread.
Agreed on the wake lock. In fact I really should have quantified that in my original post - I too have that ridiculous Android OS utilization.
I updated my post - you make a good point.
Charged to about 21%. Pulled battery and rebooted and reported about 31%. Running ARHD.
EDIT: Pulled battery again and rebooted and reports 20%.
I realized mine was charging extremely slow so I decided to turn it off and let it charge faster. It was only at 48% when I turned it off but as soon as the battery indicator showed up with the phone off it appeared to be well over halfway charged, I would've guessed close to 75% but I didn't think to turn it back on and see..
edit: I did charge it fully with the phone off then wiped battery stats in cwm before rebooting into the OS after this. Since then it seems to be charging normally and reporting the correct battery level
To prove this theory, I think you should check the reported voltage of the battery and compare that to the percentage meter. Most battery apps/widgets use the old Android "battery info" screen to report this data. There very well may be a problem with the GN/ICS meter, but to be sure there has to be some constant to go back to.
These batteries drop like a rock from full charge to something like 87-88%, and again from around 37-38% to zero. It's just the battery technology, perhaps exacerbated by not having enough battery stats to adjust the % meter.
As far as I know, an app/widget that reports battery voltage will do so from the information being provided by the battery circuitry itself, so it's not subjective or adjusted in any way like a meter will be, making it a far better correlation point for the discussion.
djp952 said:
To prove this theory, I think you should check the reported voltage of the battery and compare that to the percentage meter. Most battery apps/widgets use the old Android "battery info" screen to report this data. There very well may be a problem with the GN/ICS meter, but to be sure there has to be some constant to go back to.
These batteries drop like a rock from full charge to something like 87-88%, and again from around 37-38% to zero. It's just the battery technology, perhaps exacerbated by not having enough battery stats to adjust the % meter.
As far as I know, an app/widget that reports battery voltage will do so from the information being provided by the battery circuitry itself, so it's not subjective or adjusted in any way like a meter will be, making it a far better correlation point for the discussion.
Click to expand...
Click to collapse
I use current widget to tell me my voltage, as I don't pay attention to the meter. On a stock LTE battery, you should cap out at 4.203V
Voltage meter sounds like a reasonable way to approach the problem. I'm definitely not an expert on battery stats though - what should the voltages read? I know it caps at 4200mv, but what is the min?
Also how does mv relate to mah?
m0sim said:
Voltage meter sounds like a reasonable way to approach the problem. I'm definitely not an expert on battery stats though - what should the voltages read? I know it caps at 4200mv, but what is the min?
Also how does mv relate to mah?
Click to expand...
Click to collapse
mv stands for millivolt which is a measurement of voltage. Examples you may have heard before are 9v battery, 110 volt wall outlet.
1mv = 1/1000 volt OR 1v = 1000mv, so you can see a mv is very small compared to a volt.
mAh stands for milliampere-hour and, in layman's terms, is a measurement of battery capacity, specifically how many hours a battery will last if the device it is connected to pulls a known amperage.
So, if a device pulls 500mA and the battery is rated 2000mAh, then generally the battery will last 4 hours (2000mAh/500mA). There are numerous other factors in the equation such as temperature, age of battery, etc. that can affect the battery life.

Battery Meter or Voltage Meter problem?

My G2 gets ghastly battery life. I've tried Juice Defender and I've recalibrated more times than I can remember. Most notifications are turned off and I'm conservative about powering off the various radios when I'm not using them. It wasn't always like that. I felt like I was getting most of a full day on one charge and loving it for many months, but something happened last summer I think. Maybe dust or moisture affected the phone. I've got a total of six batteries and three external battery chargers. No battery whether it's the OEM original, 1500mah spares that were amazing before, or the new 1800mah evo shift 4g batteries I tried out, will last more than about four hours from full charge to the 15% warning sound.
I've tried only charging in the phone. I've tried rotating batteries charged in the external chargers. Like I said, I've tried calibration scenarios of various kinds.
Last night, I took a fully charged 1800mah battery and put it in my phone and then charged the battery in the phone. The orange led never turns green when the phone is off. When the phone is on, I can just barely get the led to turn green at about 91% (starting from what should be a full charge that is reported as 80% by the phone). This takes a good 10 hours of charging. As soon as I woke the phone this morning, the battery meter started dropping while the phone was still plugged in. After unplugging, the meter drops to 80% in a matter of a few minutes.
Like I said, I tried juice defender. It only helps a little but the cost is waiting for the data radio to reconnect every time I wake the phone. I thought BT was the culprit for a while, but now it really doesn't matter if I leave it on or turn it off.
At the other end of the charge, the phone can run for several hours when the battery is supposedly between 1 and 3%. I know we are told to start charging again at 15% but my phone drops to that level in 3-4 hours of regular use. I haven't seen the phone report 100% charge on any battery in six months time, but it runs and runs at 1%. This is what bugs me. Is the phone just mis-reading how many milivolts are coming out of the battery? Why can't I complete the first step of calibration (charge overnight to the 100% mark)? Is there a hardware component that can be causing this or should it be entirely fixable in software?
Thanks for any ideas or tips
Did you wipe battery stats?
Sent from your phone
waxinpoetic said:
Did you wipe battery stats?
Sent from your phone
Click to expand...
Click to collapse
Yes I have many times but thanks for the suggestion.
Figured so.. Too bad, would have been too easy. I'm starting to see some batttery drain on my desire z now too. Im wondering if mine is a radio issue.
Sent from your phone
waxinpoetic said:
Figured so.. Too bad, would have been too easy. I'm starting to see some batttery drain on my desire z now too. Im wondering if mine is a radio issue.
Sent from your phone
Click to expand...
Click to collapse
I changed radios and did RIL matching last fall based on other's comments about better battery life, 4G and GPS. While I've had faster GPS locks and maybe better 4G performance, my battery life did not improve. It may have even gotten worse.
Today I'm trying out some different CPU governor settings. The CM 7.2 RC1 default is 'interactive' and I wouldn't normally touch those settings. I think the powersave governor helped a lot, but the phone became almost unresponsive. Trying 'conservative' now. I should have read This long ago, but just got around to it today. I might invest in the SetCPU app as well.
OK, I can count on a good six hours of normal use if setCPU is holding down the max cpu frequency at night or when the screen is off. I'm still tweaking. Today, the phone crashed while playing music over A2DP and tracking a run with runkeeper. I think it needs to tick faster than 368Mhz when the screen is off.
Are you seeing improvement? I changed radios and like you havent seen much improvement. But I am a little better off than you are. My battery drain is terrible (1-3%per minute) only when connected to the internet (4g or wifi) or using navigation. If the screen is off, or if Im using non-internet apps I seem to get regular battery use. Good luck with your cpu settings.. I have ordered a new battery, but I doubt it will solve my issue. I may try tweaking my settings too soon, but Id better research more.
Just wondering do you have SuperCharger V6 installed? On my Desire Z I had some serious battery problems just as you mentioned. After I would flash my ROM (wiping the caches + reinstalling) my battery life would return to normal. But whenever I would flash SuperCharger v6 my battery life would spiral out of control. My suggestion for a ROM that handles battery life fairly well is Andromadus Audacity B2, just make sure you download and flash GAPPs (google apps). For example running that rom I have been getting very good battery life, approx. 16-20 hours of battery life with moderate use) with default CPU settings and data always turned on. I'm sure if you use Juice Defender to control your data you'll get above average battery life.
Note: Andromadus is an ICS (android 4.0) ROM
Qwerty_Uieo said:
Just wondering do you have SuperCharger V6 installed? On my Desire Z I had some serious battery problems just as you mentioned. After I would flash my ROM (wiping the caches + reinstalling) my battery life would return to normal. But whenever I would flash SuperCharger v6 my battery life would spiral out of control. My suggestion for a ROM that handles battery life fairly well is Andromadus Audacity B2, just make sure you download and flash GAPPs (google apps). For example running that rom I have been getting very good battery life, approx. 16-20 hours of battery life with moderate use) with default CPU settings and data always turned on. I'm sure if you use Juice Defender to control your data you'll get above average battery life.
Note: Andromadus is an ICS (android 4.0) ROM
Click to expand...
Click to collapse
Thanks (and thanked) Ive been waiting till ICS roms are bug free and having working cameras, but I think I may just jump on it now. My battery issues are untenable at the moment on a CM7 based rom. Thanks for the advice.
I was seeing some improvement due to SetCPU profiles. However, now if I have GPS and Bluetooth on so that I can listen to music and track my run in runkeeper, the phone seems to 'crash' after about 35 minutes or so. The battery meter shows that the battery takes a nose dive and I think the phone shuts down at 1%. If I restart the phone, it might say I have 30 or 40% charge left but then it drops rapidly again. It seems like it hates the warmth of my pocket. If I let the phone out in the cool air like on my desk, I can reboot at get back to 60 or 70% even though it was just saying 3%. I'm not running SuperCharger.
I'm trying to find cheap G2s for parts on ebay now. Maybe I can at least test out my six batteries in a different phone to see if any of them are shot. They all seem to have the same problems in my phone.
This will be my final update. I bought a used G2 off ebay. The same batteries I used before now show as fully charged when I expect them to be fully charged. I will be getting a feel for general battery life over the next few days, but I expect battery life to be roughly the same. I just won't have to guess at what the current battery level really is.
I'm seeing now that the new phone will show a 60% charge when the old phone shows 15% for the same battery at about the same time.
The new phone shows 100% when topped off but if I put the topped off battery in my old phone, I see 75-80% charge.
I may try sending the old phone to HTC depending on what they offer for repair services.
revwillie said:
I bought a used G2 off ebay. ... the new phone will show a 60% charge when the old phone shows 15% for the same battery at about the same time
Click to expand...
Click to collapse
I think what's happened to your old phone (and mine!) is that the onboard voltmeter chip is reading low. I've compared the on-board mV reading to a multimeter-measured battery voltage and what the phone reads as 3.9V the multimeter gets 4.2V (a fully charged Li-Ion battery).
Who knows what's behind it, but it seems like a hardware problem to me.

[Q]battery not fully charging

Hello.got xperia m before 4-5 days.its with cm11 and i got an issue with battery.when i charge my phone close i can see that it is 100% charged.but when i open it it drops to 95% fast. Same thing happens if i charge it open. When i replug the charger it goes to 99% normaly but after it takes much time to go 100%. Is this normal?i also try calibrating battery removing battery.bin and also tried removing battery for 10min.no luck at anything
AggelosGR said:
Hello.got xperia m before 4-5 days.its with cm11 and i got an issue with battery.when i charge my phone close i can see that it is 100% charged.but when i open it it drops to 95% fast. Same thing happens if i charge it open. When i replug the charger it goes to 99% normaly but after it takes much time to go 100%. Is this normal?i also try calibrating battery removing battery.bin and also tried removing battery for 10min.no luck at anything
Click to expand...
Click to collapse
It looks like it has some wear. Because you're probably out of warranty by flashing another ROM, may be it's a good idea go searching for another battery. If I'm not mistaken, there are some 1900 mAh batteries arround compatible with Xperia M (the default one being 1750 mAh).
But you can try to turn airplane mode on, then go to Settings > Performance > CPU and setting maximum CPU speed to 486000, as well as the CPU governor to powersave, then checking the option to restore these options every boot. Level brightness down to the minimum.
Now, let it charge to 100%, disconnecting the charger, after. See if it drops. If it still dropping, it's battery wear. Of course, the time it lasts depends on how much time you spent with screen on and what tasks are you performing, i.e.: if you're playing Fruit Ninja right after disconnecting the charger, with medium brightness, it's not imposible to drain 7% right at the first three to five minutes.
Well, may you post a screenshot of battery usage graph?
prppedro said:
It looks like it has some wear. Because you're probably out of warranty by flashing another ROM, may be it's a good idea go searching for another battery. If I'm not mistaken, there are some 1900 mAh batteries arround compatible with Xperia M (the default one being 1750 mAh).
But you can try to turn airplane mode on, then go to Settings > Performance > CPU and setting maximum CPU speed to 486000, as well as the CPU governor to powersave, then checking the option to restore these options every boot. Level brightness down to the minimum.
Now, let it charge to 100%, disconnecting the charger, after. See if it drops. If it still dropping, it's battery wear. Of course, the time it lasts depends on how much time you spent with screen on and what tasks are you performing, i.e.: if you're playing Fruit Ninja right after disconnecting the charger, with medium brightness, it's not imposible to drain 7% right at the first three to five minutes.
Well, may you post a screenshot of battery usage graph?
Click to expand...
Click to collapse
Well i put it last night and it charged 100% and battery drops normaly. I thing that this is happening only when i charge it closed...
Charging it closed? Locked?
Well, it's strange because sleep should save battery.
Anyway, looks like your battery has some damage. It's a good idea to take someone's battery to test it out, or bringing it to some place where they replace batteries (I know, it's a horrible english formulation, but back here, in our yellow and green country it does make sense, since there's a lot of Asians and Paraguyans selling all that stuff right in the downtown streets, but you'll have to check out for a place that can test it for you).
You may well take it to Sony, but they'll charge you for everything that they replace. Still, it's the best place to ask for a test. Not so much, here in my city, because store workers are, in general, a bunch of semi-cultured people who knows nothing about handset techinal aspects, just waiting for the time to take the bus and go home. Well, just sayin'... Good luck!
Ok.battery seems to work fine.phone charges to 100% and it holds 5h and 45min of gaming with low brightness.i charged it full,removed charger and i go to sleep.when i woke up (after 6h50min) phone was still 100%.i guess that the phone wasnt charging full cause of the way calibration i did by removing battery.bin....
AggelosGR said:
Ok.battery seems to work fine.phone charges to 100% and it holds 5h and 45min of gaming with low brightness.i charged it full,removed charger and i go to sleep.when i woke up (after 6h50min) phone was still 100%.i guess that the phone wasnt charging full cause of the way calibration i did by removing battery.bin....
Click to expand...
Click to collapse
It happens. This morning I used my phone for 40 minutes after disconnecting it from the charger. Minimum brightness, CPU throttled to powersave/540 Mhz max. settings and it still managed to get down to 94%. It turned out that the GPS were turned on, for some unknown reason. I turned it off and back on, and it went working correctly (i.e. working only when wheater update required it). Indeed, the screen itself does suck a great amount of power, and the screen kept on for nearly 90% of this 40 minutes. So I got to correct myself, also and apologize for my over-sugestion.
Cheers!
P. Pinheiro

Categories

Resources