Android 2.2
Baseband: 2.12.00.09.11
Kernel: 2.6.32.15-g0f673ed htc build 149 #10
Build Number: Myn's Warm twopointtwo
Software Number: 3.30.651.2
The battery performance was decent till yesterday.
I flashed kernel netarchy-toastmod-4.1.9.1 and reset battery stats using clockworkmod.
I was on Fresh EVO when I updated Kernel. I noticed the battery dying rapidly.
Later, I flashed Warm 2.2 to see if it makes a difference.My battery drops 1% every minute. I have no WIFI/GPS/4G on. The screen brightness is at 10%. No other widgets running.
I am planning to flash Stock HTC Froyo Kernel - 3.26 base to see if it makes a difference.
Ideas and suggestions are welcome.
have you checked the awake time vs. up time?
it could be an app that is causing this drainage.
I see
Android System - 94%
Cell Stand by - 4%
Phone Idle - 2%
I havent made any calls yet.
Btw, my HW version is 004.
I am planning to flash CM 6.0/1 in the next hour or so..
rajas_evo said:
have you checked the awake time vs. up time?
it could be an app that is causing this drainage.
Click to expand...
Click to collapse
I agree that it sounds like a runaway app... but the 1% per minute seems harsh. The fastest I've been able to deplete my battery was something like 4 hours.
Reflash a new ROM and install 1 app then wait an hour install next app and wait an hour, etc etc.
I would also install an OS monitoring app to see what your CPU is doing during this time.
Some people had trouble with it. Try either NO-HAVS version or any 4.2.1. See my post here for recalibrating your battery correctly and some other ways to make your battery last longer: http://forum.xda-developers.com/showpost.php?p=9371294&postcount=10579
When you wipe your battery stats, the phone treats the battery as its full. I had a similar problem when I wiped stats and the battery wasn't completely topped off.
Follow the battery charging instructions to get the battery to 100%.
Reboot then wipe stats.
From your System being so high above the cell standby, I'd say there is a runaway app or a kernel problem from an incomplete wipe. I would suggest going back into recovery and wiping your cache and dalvik cache first to see if that helps.
cyberbrutus said:
I see
Android System - 94%
Cell Stand by - 4%
Phone Idle - 2%
I havent made any calls yet.
Btw, my HW version is 004.
I am planning to flash CM 6.0/1 in the next hour or so..
Click to expand...
Click to collapse
but what is the awake time vs. up time?
Menu > Settings > About phone > Battery
rajas_evo said:
but what is the awake time vs. up time?
Menu > Settings > About phone > Battery
Click to expand...
Click to collapse
Uptime is how long your phone has been on for since you turned it on. Awake time is how long either you've been actually using the phone or how long a phone has been keeping the phone awake (meaning the CPU working at full speed). If your awake time is more than the time you've actually been using the phone, something has your phone in a wakelock, preventing it from sleeping.
rajas_evo said:
but what is the awake time vs. up time?
Menu > Settings > About phone > Battery
Click to expand...
Click to collapse
Awake Time: 1.01.41
Up TIme:4.16.32
I am at 7% already
phajen said:
From your System being so high above the cell standby, I'd say there is a runaway app or a kernel problem from an incomplete wipe. I would suggest going back into recovery and wiping your cache and dalvik cache first to see if that helps.
Click to expand...
Click to collapse
I did clear cache and dalvik cache using ClockWork's recovery.
I dont get a confirmation when I clear dalvik cache. I was planning on switching to RA's recovery. I haven't found an easy way to do it.
Bielinsk said:
When you wipe your battery stats, the phone treats the battery as its full. I had a similar problem when I wiped stats and the battery wasn't completely topped off.
Follow the battery charging instructions to get the battery to 100%.
Reboot then wipe stats.
Click to expand...
Click to collapse
I was at 34% when I reset battery stats. I think you are right. I will try this right away.
cyberbrutus said:
I was at 34% when I reset battery stats. I think you are right. I will try this right away.
Click to expand...
Click to collapse
That's definitely your issue.
Product F(RED) said:
Some people had trouble with it. Try either NO-HAVS version or any 4.2.1. See my post here for recalibrating your battery correctly and some other ways to make your battery last longer: http://forum.xda-developers.com/showpost.php?p=9371294&postcount=10579
Click to expand...
Click to collapse
I flashed TwoPointTwo and the kernel was updated to 2.6.32.15-g0f673ed [email protected]#10. I think its NO-HAVS version..correct me if I am wrong
cyberbrutus said:
I flashed TwoPointTwo and the kernel was updated to 2.6.32.15-g0f673ed [email protected]#10. I think its NO-HAVS version..correct me if I am wrong
Click to expand...
Click to collapse
Stock kernels never have HAVS and they also have perflocks that prevent them phone from being overclocked or underclocked. You can disable the perflock by going into SetCPU, hitting menu, and using Perflock-Disabler.
Product F(RED) said:
Stock kernels never have HAVS and they also have perflocks that prevent them phone from being overclocked or underclocked. You can disable the perflock by going into SetCPU, hitting menu, and using Perflock-Disabler.
Click to expand...
Click to collapse
Got it..thanks.
Yeah, going back and reading, I'm an idiot for not thing about getting rid of the battery stats when its not at 100%. If you need any help with the charging fixes, there should be something in my sig.
phajen said:
Yeah, going back and reading, I'm an idiot for not thing about getting rid of the battery stats when its not at 100%. If you need any help with the charging fixes, there should be something in my sig.
Click to expand...
Click to collapse
I followed your recalibration tutorial.
Its like 1% every 4 minutes of usage now. I think I am good.
Thanks
Related
I just flashed MIUI last night and noticed that my battery is being sucked dry pretty fast. I suspected that it is due to sync being switched on. Where can I make adjustments to the frequencies of the sync?
Either from the app or Settings>Personal>Accounts & Sync
Although I didn't have ANYTHING setup last night when trying it and lost 6% in about 10 mins - something's not right
Try resetting your battery indicator http://www.miui-au.com/howtos/reset-battery-indicator/. It is also recomended somewhere on the miui-au.com site to not charge your phone while flashing because it is somehow disruptive for the indicator.
I know all that, I wipe:
data/cache
dalvik-cache
battery stats
rotation settings
before flashing ANY ROM. Battery life is still crap
Kirodema said:
Try resetting your battery indicator. It is also recomended somewhere on the miui-au.com site to not charge your phone while flashing because it is somehow disruptive for the indicator.
Click to expand...
Click to collapse
The weird thing is I wasn't charging the battery while flashing. I find it a bit surprising for MIUI 1.2.4 to be quite a beast in battery usage.
EddyOS said:
I know all that, I wipe:
data/cache
dalvik-cache
battery stats
rotation settings
before flashing ANY ROM. Battery life is still crap
Click to expand...
Click to collapse
What would you consider a good battery life?? I flashed to 1.2.4 and it seems to last me all day without any problems?BUt I have noticed slight 5%-8% drop in the 1st hour or so but then it stablises throughtout the day. Ive not tweaked my phone with setCPU and I dont intend to either.
Something is rly wrong with your MIUI. Anyway, never use that Kernel which comes with miui. Use Vork or Coutts Kernel.
pls download current widget from market and test how much mA it drains in "screen off". im using miui-au 1.2.4 r2 with vork kernel and im losing 1% per our with wifi, sync and gps on. it uses 4-5 mA with screen off.
With previous MIUI builds, and with my own ROM I'm using now, I can go from 7:30am til midnight and still be on circa 50% battery. This is with my normal weekday usage. It goes down to about 30% by end of the day on weekends as I use the phone more
This build drops 5% in a few minutes and I just don't see that as being any good
Midian666 said:
Something is rly wrong with your MIUI. Anyway, never use that Kernel which comes with miui. Use Vork or Coutts Kernel.
pls download current widget from market and test how much mA it drains in "screen off". im using miui-au 1.2.4 r2 with vork kernel and im losing 1% per our with wifi, sync and gps on. it uses 4-5 mA with screen off.
Click to expand...
Click to collapse
I don't need to download anything, the ROM was dropping battery with NOTHING setup except for Wi-Fi. I didn't even setup my Gmail account to get my contacts!!
I think I can skip the obvious as I know full well what I'm doing and never had this issue with previous MIUI builds, and I never use the stock kernel - I always go for a Coutts one before first boot
Hi all,
i'm new with DHD, i flashed Revolution rom and i have high battery drain.
I charged my phone untill current was 0 mA, deleted the battery info and reboot.
So i turned on only data connection and leaved about 8 hours sleeping.. from 10pm to 10am all sync are off.. the result is: -25%!!!
I'm trying to find the batterykillerapp but i can't do it!
If i type the code *#*#4636#*#* i can see only battery info, no battery history, if i try using Spare Parts the app crash
how can i find the app that sucks my battery life?
lilfo said:
Hi all,
i'm new with DHD, i flashed Revolution rom and i have high battery drain.
I charged my phone untill current was 0 mA, deleted the battery info and reboot.
So i turned on only data connection and leaved about 8 hours sleeping.. from 10pm to 10am all sync are off.. the result is: -25%!!!
I'm trying to find the batterykillerapp but i can't do it!
If i type the code *#*#4636#*#* i can see only battery info, no battery history, if i try using Spare Parts the app crash
how can i find the app that sucks my battery life?
Click to expand...
Click to collapse
Go back to the thread and look for the radio recommended for the rom. I'm pretty sure these radios are the main reason for battery drain
OR
What do you mean by battery drain? if it goes down fast when you're using your phone. That's not battery drain at all.
You can also go to OC daemon and set governor to ondemand so that the CPU doesn't stay on higher clocks.
i mean that battery goes down fast when i'm not using the phone! -25% in a night
sleep governor is on conservative and wake governor ondemand
lilfo said:
even if i never use the radio?
i mean that battery goes down fast when i'm not using the phone! -25% in a night
sleep governor is on conservative and wake governor ondemand
Click to expand...
Click to collapse
Tried wiping battstat?
Sent from my Desire HD using XDA App
ABorgh do you mean the battery calibration?
I'm going to do it again now that i've flashed the radio..
I tried to find a ROM for lite user. Can anyone give me information?
lilfo said:
ABorgh do you mean the battery calibration?
I'm going to do it again now that i've flashed the radio..
Click to expand...
Click to collapse
Make sure you have full battery before going into clockwork recovery and wiping battstat
Sent from my Desire HD using XDA App
Hi, is it possible to wipe batery stats without having root or custom roms installed? My battery drains very fast.
@niyesuh
When you enter Recovery , your screen will be black ,that means you don't have a custom recovery installed . You need to have Root & RomManager whit Clockwork Recovery installed in order to wipe battery stats .
niyesuh said:
Hi, is it possible to wipe batery stats without having root or custom roms installed? My battery drains very fast.
Click to expand...
Click to collapse
That can be depending on other stuff, like bloatware on a stock rom
Sent from my Desire HD using XDA App
Hey guys, something better with recommended radio!
I'm using the phone from 15 h 24m and i'm at 52%
I think there is still something to fix because in 8 of this 15 h the phone was in sleeping mode and the battery gone down around of 15%
From battery info in the setting menu i can see: Display (40%); System (15%); Standby (13%); Dialer (13%); Idle (12%); Voice Call (5%); Whatsapp (2%).
Any suggestion?
lilfo said:
Hey guys, something better with recommended radio!
I'm using the phone from 15 h 24m and i'm at 52%
I think there is still something to fix because in 8 of this 15 h the phone was in sleeping mode and the battery gone down around of 15%
From battery info in the setting menu i can see: Display (40%); System (15%); Standby (13%); Dialer (13%); Idle (12%); Voice Call (5%); Whatsapp (2%).
Any suggestion?
Click to expand...
Click to collapse
You have the best battery usage I have ever seen My battery lasts about 8 hours!
Sent from my Desire HD using XDA App
really? but is it normal that in sleeping mode i have peeks of 200/300 mA?? shouldn't stay between 3 and 8 mA??
lilfo said:
really? but is it normal that in sleeping mode i have peeks of 200/300 mA?? shouldn't stay between 3 and 8 mA??
Click to expand...
Click to collapse
How much in percent do your phone drain per hour?
Mine drain about 1-2%/H
Sent from my Desire HD using XDA App
now 1-2% me too, so it's ok? but peeks in the log means that something run in sleep mode, so i would find this app and kill it to have better battery perform
lilfo said:
now 1-2% me too, so it's ok? but peeks in the log means that something run in sleep mode, so i would find this app and kill it to have better battery perform
Click to expand...
Click to collapse
These peaks that you speak of can be the radio unit trying to find good reception. Try turning the data, LTE 3G and edge, off and see if it drains slower! But I don't see anything wierd with your battery usage or battery
Sent from my Desire HD using XDA App
mhhh... i think you right! i'm by bedroom the reception is not so good and phone always skip between 3ITA and roaming.. i'll retry in another room with better reception
lilfo said:
mhhh... i think you right! i'm by bedroom the reception is not so good and phone always skip between 3ITA and roaming.. i'll retry in another room with better reception
Click to expand...
Click to collapse
Try shutting the data off completely and then check! For more accurate results
Sent from my Desire HD using XDA App
ok thanks for the help
I've got another question.. do you know what is better for the battery life? Should i charge it from 0% to 100% every time or trying to stay from 30-70% or if possible 40-60%?
lilfo said:
ok thanks for the help
I've got another question.. do you know what is better for the battery life? Should i charge it from 0% to 100% every time or trying to stay from 30-70% or if possible 40-60%?
Click to expand...
Click to collapse
Remember the thanks button
Well lithium batteries fell best if the are fully recharged once or twice a month and then charging just whenever you feel like it really! like from 30 to 76 percent. They do not need so much looking after.
How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Thanks, I will try it. So far I was using Battery Monitor apk. However, I have no reference if my battery drain level is expected for that rom or not.
I'm also having issues with battery drain on JT... really strange. It seems to have drain when in standby, and when the screen is on it goes like crazy, I can't get more than like 20-30 minutes of screen-on time. I really like this ROM, it is pretty stable and works fine, no major bugs but the battery drain is crazy. I took a couple of screenshots. It seems that process Media is keeping it "awake" and causing battery drain. In all other ROMs I used (and in stock) I have never seen any other process except SCREEN using more than couple of percent of battery. Now this media process is using almost as screen! Any clues as what it is?
Also, I noticed that it discharges quickly when screen is on, but it also charges quickly! Something wrong with battery stats? It simply can't go from 20% to 70% in 10 minutes while charging?
xhejtman said:
How much does your Jellytime ROM drain from battery? Using battery e.g. Battery monitor widget, I can see 60mA drain when phone is standby. Seems to be a lot for me. I didn't find comparsion just subjective claims - high/low drain. 60mA is with wifi turned off, bt disables, no gprs/3g data, just standby. No application seems to be running. Battery stat shows that 60 % is display (but I can confirm that display is off), 40 % cell stand by and about the same amount phone idle.
Click to expand...
Click to collapse
Its about 1% per hour about the battery drain..quite good battery with usage
KeshavJave said:
Its about 1% per hour about the battery drain..quite good battery with usage
Click to expand...
Click to collapse
Hmm, could you provide mA value (battery monitor shows it in history in 10 minutes intervals..)
I can do five hours with normal use on a full charge..
These are battery stats for my DHD. The first one is standby over night with stok HTC ROM (2.3.5), the second one is with JellyTime ROM 9.1. It takes 10times more power.
marclooman9 said:
I can do five hours with normal use on a full charge..
Click to expand...
Click to collapse
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
xhejtman said:
That's not much. Was it better as long as you can remember with stock HTC ROM? I could do 2-3 days with normal use with stock ROM.
Click to expand...
Click to collapse
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
ai6908 said:
Wow 2 to 3 days? Last time I had a phone like that was back in non smart phone days...
Click to expand...
Click to collapse
Yes, but my cost for 2-3 days is: no gsm data, no wifi (or wifi for something like 5 minutes), no widgets except htc clock & weather, almost no background apps, few phone calls, moderate number of sms. (Yes I hear you saying, you don't need 'smart' phone , I do, I use some apps but not too frequently, so avg running time from 100% to say 10% of battery was 2-3 days, mainly depending on number of sms sent
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
perhaps try to install: http://play.google.com/store/apps/details?id=ccc71.bmw
it provides history of current consumption, that can tell whether it is a lot or not.
Btw, what do you exactly mean by "played for 10m"? What did you do?
xhejtman said:
Btw, what do you exactly mean by "played for 10m"? What did you do?
Click to expand...
Click to collapse
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
dalanik said:
Thanx for the tip, I'll try installing the app you suggest. "Played" means I turned the screens on louncher a couple of times to update all widgets, went into settings, looked at the battery stats etc. Maybe lounched foursquare and titanium backup, nothing really intensive... Here are shots from batterystats. Seems to me media service is doing it...
Click to expand...
Click to collapse
yes media service seems to be suspicious. It says, the phone was in deep sleep only half an hour for last hour while screen on was really only for about 10 minutes. I think the problem is in remaining time. I am not really familiar with bbs logs, maybe post the log into BBS thread here on XDA for help if you cannot figure it yourself.
dalanik said:
I had it charged to 100%. Then I kept it charging, went to recovery and deleted battery stats. I booted and when it displayed lock screen I unplugged. Then I played for like 10 minutes (screen on) and my battery went from 100% to 88% !!! A bit too much? I installed betterbatterystats so I hope I'll see which process keeps it awake (there's drain even when screen off)...
D.
Click to expand...
Click to collapse
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
xbiggyl said:
There is no need for wiping battery stats.
Once your phone recharges to 100%, battery stats reset by default.
Click to expand...
Click to collapse
I know, I read that somewhere, but just wanted to be sure This is really driving me nuts, I always have to be near charger
xbiggyl said:
You can try BetterBatteryStats to check what might be draining your battery (if any).
Here's the link to the beta version for xda users: http://forum.xda-developers.com/showthread.php?t=1179809
Click to expand...
Click to collapse
Ok, I figured out, what is causing high battery drain. It FM radio. After clean flash and basic setup, it consumes 10mA when standby. Which is twice more than with stock ROM, but seems to be acceptable. If I run and then exit Sprite FM radio app, phone starts to consume 60mA until reboot. After reboot, it is ok, until I run Sprite FM app again.
However, BBS does not show anything useful. Maybe because of FM HW keeps running? There is shown no SW battery eater..
I still can't figure it out Here's log of consumptuon in standby from last night, I have it set on profile manager to turn off data and set airplane mode from 1am-7am. Looks good to me, can someone confirm these are OK values?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:19:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:29:43|-7mA|57%|3945mV|21.0ºC|.0|0
2012/09/24|02:39:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:49:44|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|02:59:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:09:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:19:43|-7mA|57%|3945mV|20.0ºC|.0|0
2012/09/24|03:29:44|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:39:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:49:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|03:59:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:09:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:19:43|-7mA|56%|3935mV|20.0ºC|.0|0
2012/09/24|04:29:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:39:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:49:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|04:59:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:09:43|-10mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:19:43|-7mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:29:43|-13mA|55%|3925mV|20.0ºC|.0|0
2012/09/24|05:39:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:49:44|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|05:59:43|-12mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:09:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:19:43|-7mA|54%|3911mV|20.0ºC|.0|0
2012/09/24|06:29:43|-7mA|53%|3891mV|20.0ºC|.18|0
2012/09/24|06:39:43|-7mA|53%|3891mV|20.0ºC|.0|0
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
2012/09/24|07:20:44|-32mA|36%|4174mV|24.0ºC|.736|6
2012/09/24|07:30:44|397mA|75%|3933mV|26.0ºC|.3|2
2012/09/24|07:40:44|-61mA|73%|3784mV|26.0ºC|.76|0
2012/09/24|07:50:44|-121mA|63%|3779mV|26.0ºC|.450|0
2012/09/24|08:00:44|-233mA|44%|3730mV|26.0ºC|.998|0
2012/09/24|08:10:44|-125mA|37%|3769mV|27.0ºC|.200|0
2012/09/24|08:19:36|607mA|55%|3850mV|27.0ºC|.1|1
2012/09/24|08:29:35|611mA|64%|4187mV|28.0ºC|.130|1
2012/09/24|08:39:35|426mA|69%|4189mV|28.0ºC|.0|1
2012/09/24|08:49:18|136mA|94%|4087mV|27.0ºC|.8|3
But look at the 2nd attached screenshot, at the end of the graph - how fast it charges, isn't that unusual?
Code:
2012/09/24|00:28:43|587mA|60%|4182mV|34.0ºC|.258|1
2012/09/24|00:29:43|529mA|60%|4182mV|34.0ºC|.100|1
charging at rate 500-600mA, is it external charger? I do charging on ntb and it's up to 400mA when battery is not close to 100%.
Code:
2012/09/24|00:39:43|-61mA|60%|3869mV|32.0ºC|.256|2
2012/09/24|00:49:43|-11mA|59%|3960mV|27.0ºC|.0|0
2012/09/24|00:59:43|-28mA|59%|3957mV|25.0ºC|.0|0
2012/09/24|01:09:43|-18mA|59%|3960mV|23.0ºC|.0|0
2012/09/24|01:19:43|-8mA|59%|3957mV|22.0ºC|.0|0
2012/09/24|01:29:43|-10mA|58%|3940mV|22.0ºC|.0|0
2012/09/24|01:39:43|-13mA|58%|3955mV|21.0ºC|.0|0
seems to be of slight using or runnign backgroud processes this hour?
Code:
2012/09/24|01:49:44|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|01:59:43|-7mA|58%|3955mV|21.0ºC|.0|0
2012/09/24|02:09:43|-7mA|58%|3955mV|21.0ºC|.0|0
this is expected consumption, with stock HTC ROM I got -3 - -5mA, but -7mA is pretty good. With R10 I got -10mA, don't know why it does sleep less than it should.
Code:
2012/09/24|06:46:44|-210mA|53%|3740mV|21.0ºC|.0|0
2012/09/24|06:56:44|356mA|57%|4187mV|24.0ºC|.3|6
2012/09/24|07:00:44|-264mA|71%|3816mV|25.0ºC|.360|2
2012/09/24|07:10:44|-254mA|51%|3721mV|24.0ºC|.1000|0
what happened here? -264mA is a lot of power consumption, do you remember what did you do? Common usage should be around -100mA.
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Constantine. said:
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Click to expand...
Click to collapse
I think you maybe hurrying to a conclusion.
After you flash the flash the ROM, wipe battery stats in cwm. Then let the ROM settle ( atleast 2 charge cycles ) .
Then see if you have the same battery problem
Constantine. said:
My battery life is considerably worse on jellybean aosp roms (I tried both the 4.1 and 4.2 version) than it was with stock ICS, and stock jellybean with sense, I'm sure that the battery lasted at least twice as much than it does now. I'm getting around 7-8 hours with a screen time of 2 - 2.5 hours at maxiumum, screen brightness at 50%, location turned off. It's clearly a software problem since the battery life with stock rom is so much better. Something must be wrong since everyone is reporting great battery life with the latest jellybean aosp rom.
Click to expand...
Click to collapse
I'm on ice cold jelly 2.2 with the XML kernel #141repacked for the ROM. I get a steady 3 hours screen on time. Give that combo a try. Also the first few days the kernel and ROM have to settle so don't be too quick to judge it.
Sent from my HTC One X using xda premium
{< r o N o $ said:
I think you maybe hurrying to a conclusion.
After you flash the flash the ROM, wipe battery stats in cwm. Then let the ROM settle ( atleast 2 charge cycles ) .
Then see if you have the same battery problem
Click to expand...
Click to collapse
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Sorry for the replies, but: the battery stats wipe is useless...
The file that you've removed is a file which contains the statics of battery.
It has nothing to do with the battery life, Google has confirmed this.
In fact, in TWRP and 4EXT recovery this wipe there isn't.
However, i think you have to calibrate your battery with some charge cycles
Guich said:
Sorry for the replies, but: the battery stats wipe is useless...
The file that you've removed is a file which contains the statics of battery.
It has nothing to do with the battery life, Google has confirmed this.
In fact, in TWRP and 4EXT recovery this wipe there isn't.
However, i think you have to calibrate your battery with some charge cycles
Click to expand...
Click to collapse
Guich, what i talked about was not fixing battery, just fixing the readings.
Example : especially on AOSP roms, if u put on charge, after some time green LED shows (meaning charge full) BUT battery bar is stuck at a lower level ( Example 76 ) .
And the bar doesnt move forward even after you keep it on charge even longer.
So i tried a battery stats wipe in cwm and then when i booted back, it properly showed 100%.
So what i recommended was to delete previous stats ( of different ROM which were carried into this one).
So now the phone starts monitoring battery anew (with no cache).
Sorry if you misunderstood me.
R: [Q] Terrible battery life on jellybean aosp roms
{< r o N o $ said:
Guich, what i talked about was not fixing battery, just fixing the readings.
Example : especially on AOSP roms, if u put on charge, after some time green LED shows (meaning charge full) BUT battery bar is stuck at a lower level ( Example 76 ) .
And the bar doesnt move forward even after you keep it on charge even longer.
So i tried a battery stats wipe in cwm and then when i booted back, it properly showed 100%.
So what i recommended was to delete previous stats ( of different ROM which were carried into this one).
So now the phone starts monitoring battery anew (with no cache).
Sorry if you misunderstood me.
Click to expand...
Click to collapse
I think this fact is random.
In fact, all aosp rom that i tried didn't have this problem
And, teorically, this file was delete when you made a full wipe.
In fact in TWRP recovery there isn't the wipe for the battery
Sent from HOX
I can't fine the battery wipe in CWM
Constantine. said:
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Click to expand...
Click to collapse
How I could find batt wipe in cwm?
Guich said:
I think this fact is random.
In fact, all aosp rom that i tried didn't have this problem
And, teorically, this file was delete when you made a full wipe.
In fact in TWRP recovery there isn't the wipe for the battery
Sent from HOX
Click to expand...
Click to collapse
Battery stats file should be deleted each full charge, though I have noticed my phone crash (my fault messing about with UV) and then my batter jump from 8% to 45% which is quite a jump lol
Sent from my HTC One X using xda app-developers app
eezwanlee said:
How I could find batt wipe in cwm?
Click to expand...
Click to collapse
I believe its under advanced - wipe batt stats
I can't find it
Constantine. said:
Thank you so much! I have deleted the battery stats file in cwm and it is immediately obvious that the battery life has improved.I can't believe how easy the fix was.
Click to expand...
Click to collapse
Mr Hofs said:
I believe its under advanced - wipe batt stats
Click to expand...
Click to collapse
I'm familiar with CWM, but I cannot find it in advanced menu.
Is it because after I upgrading my HumberOS CM10.1 to AOSP 3.15?
I did a wipe clean. Everything. Fresh install.
It happened after I finished upgrading to AOSP ROM 3.15. My battery shows nothing even I charged it for a whole night.
Only 2% batt left while I'm typing this message. I have to connect my SGT7 to charger but nothing happened. It shows that it's charging but too bad, its not.
I've never encounter this problem before. It would be nice & I would be grateful if you sir can help me through this problem.
Thanks for replying.
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
TiTAN-O-One said:
Can someone tell me the exact steps for calibrating the battery again? I kinda forgot .. My CM9 battery still can't last for a day ..
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
jakelq said:
Well, try to discharge your phone until it fully drained, and charge your phone until it reaches to 100%, should be powered of,unplug, then use it the normal way, until it fully discharge and do the same, for at least 3 charging cycles.
Or charge your phone to 100% then before unplugging, go to /data/system and removed batterystats.bin.
I hope it will help, the first step is I think the most accurate, than using such apps.
Thank you,
Click to expand...
Click to collapse
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
honeyx said:
Best is to charge and discharge for a few times without whiping battery stats. It will calibrate itself. Whiping battery stats to incrase battery life was already proven several times to be a myth. The stats will be anyway overwritten completely after a few cycles. So whiping them even can make things worse till the new stats are filled.
However under some circumstates this might help, but you must take into account it can first drain more till the stats are filled and you get accurate readings. I only once whiped the stats while changing the battery from a LI-Ion to a LI-Polymer because the LI-Polymer is behaving a bit different.
More important is to care about the full gaugue, because this can show incorrect values and fill the battery stats with these. This is for example the case if pluging in the charger at 30% and rebooting and getting after the reboot for example 70% displayed. It´s simply impossible the battery gets charged by about 40% within 1 or 2 minutes while it´s booting. The same often happens when going into CWM recovery and rebooting afterwards. Therefore I always charge the phone to 100% before going into recovery and keep the phone pluged into the charger while for example doing a backup or flashing a kernel.
There are many reasons why the battery can´t last that long. For example apps or services keeping you phone awake, wifi or mobile data being enabled the whole time, or the battery itself going down the hills. For me wifi is draining a lot, even with a reduced voltage in the kernel. One of the services that can cause high battery drain is the media server and media scanner if it can´t handle the media type or index the media names due to some SQL prefixes included in the names.
But when speaking about the kernel it looks like Arco fixed the high battery drain issue in the final CM9. I flashed it last night and il looks like it´s draining just as much as if I were using RC2 or RC3 with Arcos stock 2.6 kernel.
Click to expand...
Click to collapse
thanked for the info on latest cm9 battery performance
TiTAN-O-One said:
Good stuff here! thanks! Gonna try these stuffs out!:thumbup:
Sent from my GT-S6500 using xda app-developers app
Click to expand...
Click to collapse
You might take a look on this one too when speaking of battery calibration:
http://forum.xda-developers.com/showthread.php?t=1460553
Calibration with apps by wiping battery stats is useless.
Battery in cm9 eol and cm9 rc3
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
w4nkh4iri said:
Does battery of cm9 eol same like battery of cm9 rc 3 with honeyx's kernel and also how long the battery can last from 100% to 0%?
Bcoz I feel like my battery drop frm 100% until 87% in about 1 hour use cm9 rc3 with honeyx 's kernel...
Sorry my English so BAD
Click to expand...
Click to collapse
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
honeyx said:
It´s nearly the same. Not exactly the same, but nearly the same, so it will not become better if you switch to CM9 EOL but probably a little bit worse. All depends to your battery health and how you are using your device.
I find the 2.6 kernel still a little bit better when it comes to battery life than the one in the final CM9, but since the differences are really small I´m already using the final release with a modified kernel.
This kernel has a few more optimizations for battery life and I will launch it quite soon after some more tests are done.
Don´t know how you are using your device and what apps are installed on your phone, but if your WiFi and Mobile Data is always on, there are a lot of apps running in the background and you are very often using your phone, your results are still very good.
Else better replace your battery with a new one, as there is no kernel that will turn a bad battery into a shiny new one.
Click to expand...
Click to collapse
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
w4nkh4iri said:
Ok,mybe i install all of apps that i use...Can i use ur kernel that ur modified with final cm9?? ..just wanna use it...and thanx
Sorry my English so BAD
Click to expand...
Click to collapse
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
honeyx said:
Sure, you just have to wait a bit till I release it as i need to test it for stability before launching it and am doing this for a couple of days to be 100% sure.
Click to expand...
Click to collapse
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
w4nkh4iri said:
Great,thanx u for share ur kernel..i can't waiting to using it
but i dont understand to battery life extender
" Use RootExplorer and go to: '/sys/class/misc/batterylifeextender'. Change the value in 'charging_limit' for example to 90 (default 100). This will set a limit for the capacity to which the battery will be charged. So in this example the battery will be charged to 90%.
----------------------------------------------------
After flashing the kernel whipe your cache and dalvik cache and fix permissions."
Mean that change value before flash kernel??
Sorry my English SO BAD
Click to expand...
Click to collapse
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
honeyx said:
No problem, but wrong thread. You can´t change this value before flashing the kernel as it doesn´t exist before flashing a kernel that supports battery life eXtender. So only possible to change this after flashing it.
Click to expand...
Click to collapse
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
w4nkh4iri said:
Sorry bcoz ask u in wrong thread. Mean that, after i flash kernel,go to rootexplorer and change it and last reboot...if i wrong please correct to me
Sorry my English so BAD
Click to expand...
Click to collapse
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
honeyx said:
Just change it without rebooting afterwards. If you reboot after changing this value, it will be reset to the default value (100).
So to permamently change this value on each reboot you need to use a tool that will do this for you at each booting. Don´t remember which app is actually supporting BLX, but there is one that will do this for you.
Click to expand...
Click to collapse
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
w4nkh4iri said:
So flash kernel and reboot.After that,go to rootexplorer and change value...but how about after flashing the kernel whipe your cache and dalvik cache and fix permissions???
Click to expand...
Click to collapse
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
honeyx said:
No. Go to CWM recovery. Flash kernel. Stay in CWM Recovery, whipe cache, whipe dalvik cache and fix permissions. Reboot. Then you can use root explorer to change the BLX value once it has booted.
Click to expand...
Click to collapse
Mean that,that BLX exist when after flash kernel and whipe cache,whipe cache, whipe dalvik cache and fix permissions.
Now,I feel like i see that how to use BLX. Thanx u.
So my English Bad