Develop Bugs

[Q] What is your average battery draw and CPU usage

Ok EVO nation!
Here's my scenario. I'm running a fresh flash of MikFroyo 4.5 and Netarchy's 4.2.2. cfs nohavs. With almost nothing else running on the phone.
So far I've seen a the stand-by battery drain hover around 100-180mA, with an occasional dip into the 50's. The CPU usage is always just below 10%.
I've seen references all over the forums about users claiming low 40's and idle CPU usage around 3% and I'm wondering WHY I'm not able to achieve the same thing.
Now I've done all of the standard battery tweaks, tried various kernels, and can remember a time last fall when one kernel I flashed seemed to give me incredible battery life.
So...Let's hear what your average stand-by battery drain and CPU usage is.
(And any thoughts you might have about my battery situation)

Get 4.3.2 with more havs. It'll drop the voltages nice and low. When I had mikfroyo with netarchy 4.3.2 with setcpu screen off at 128mhz I had about 30-40 idle drain.
Sent from my (insert daily ROM name here) Evo 4g

I wouldn't worry too much about your idle current draw unless you're having a battery drain problem. The issue with the current draw methodology is it's taking the current consumption that instant in time. Unfortunately, you can't monitor instantaneous current draw without affecting the reading itself.
If you idle for an hour or two (or 5), and your battery only goes down 0-1%, i'd say you're in good shape. Also, it helps if you specify what software you're using to monitor these values with? Mine is based on Battery Monitor Widget (bmw).
Edit: There's more to cpu tweaks than just kernels. Along with kernels, there are governors, and then there are governor parameters. Each will directly affect your battery consumption and cpu load.

I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?

fsmith3x said:
I'm definitely having a battery drain problem. At idle, it's falling 3-4% per hour, according to the Battery Monitor Widget.
I've got SetCPU set to 128min/998 max with Conservative scaling, and I've one profile enabled for Screen off settings of 128min/128max.
I did notice that when I try to set the min cpu to 128, the clock speeds jump all over the place. But if I set the min cpu to 245 it quiets right down.
Perhaps I a have CPU that's become finicky?
Click to expand...
Click to collapse
I had an issue similar to this where my battery would drain quicker than usual when the CPU min was set at 128 and having a screen off profile of 128/128. I think the problem stems from just setting the CPU way too low and having it use more power to bring the phone 'up to speed'. From my personal experience, I think you'll still be just as good setting your mins to 245, but by all means you're more than welcome to continue experimenting with 128

First off, you need to determine if you have a wake lock issue. Use "spare parts" to see. Look in the battery history, partial wake lock section. It will show you what programs are causing wake lock, and what amount of time they are in a state of wake lock.
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
All it takes is 1 misbehaved program, or even a particular setting within a program to cause wake lock. If that is the cause, then regardless of what your sleep settings are, the phone will still draw the battery down quickly.
You can also look in "/sys/devices/system/cpu/cpu0/cpufreq/stats" at the time_in_state file using a text viewer/editor. It will show how much each cpu frequency is being utilized. I don't recall what unit it's in. But the point here is that if your 128/245 Mhz values are lower than your upper mhz values, something is not right.
The governor parameters will control how much cpu swing is occurring under various load. That is, if you're reading an email, there's little reason for the cpu to be pegged at 998mhz. These parameters control the thresholds (contingent upon which governor is used) at which the cpu scales up or down.
Edit: Each value in time_in_state represent 10ms, or .01seconds. So multiple each value below by .01 to get actual time in seconds. If you notice, the total time in us equal to my awake time of 7h36m, not total uptime.
Mine looks like this
Code:
Mhz cycles seconds
128000 1264017 12640
245000 201083 2011
384000 72728 727
422400 4 0
460800 133450 1335
499200 0 0
537600 72174 722
576000 53479 535
614400 78771 788
652800 38230 382
691200 0 0
729600 87258 873
768000 29579 296
806400 98273 983
844800 18476 185
883200 0 0
921600 599503 5995
960000 0 0
998400 2821 28
Total 2,749,846 27,498
27498seconds = 458min = 7.63h or 7h37m.

gpz1100 said:
Example, my phone was last off the charger 42 hours ago (awake time 7h36m), battery still at 32%, and should last the remainder of the day so long as I don't do too much data. My two biggest wake lock listings are Android system at 1h26m, and my email at 20m.
Click to expand...
Click to collapse
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Anyway....
Good morning gang!
I gave this a couple of days for the fresh install to settle in, and hopefully let it learn how to use the battery more efficiently. But it's still a power hungry beast.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
For those of you who like numbers, here's some stats for you. Do you see anything that raises any red flags?
Looking at Spare Parts, in the wake lock section, I see these values.
Android System: 9m9s
UID 10020: 54s
Facebook: 39s
Voicemail: 30s
Mail: 14s
Maps: 11s
Tasker: 9s
WidgeLocker: 6s
Other Usage...
Running: 36.1%
Screen on: 16.7%
Phone on: .9%
Wifi On: 100%
Wifi Running: 100%
The values from my 'stats' file:
128000 0
245000 84095
384000 20371
422400 9
460800 0
499200 127
537600 4743
576000 100
614400 9
652800 75
691200 4238
729600 0
768000 23
806400 1358
844800 2439
883200 0
921600 0
960000 976
998400 18361
1036800 0
1075200 0
1113600 0
1152000 0
1190400 0
1228800 0
1267200 0

fsmith3x said:
gpz1100, Please describe your setup and usage. I'm curious to know how you're getting that kind of battery life.
Click to expand...
Click to collapse
My setup is as described in the sig. The only additions would include custom conservative governor settings of 80/55/10 % on the up/down/freq steps thresholds; min/max cpu of 128/921 Mhz respectively. I don't use setcpu, tasker, or anything similar. Background updates is on, but nothing is checked (no gmail, facebook, etc.). I used to have email push enabled (using k9 mail), but decided to turn off push altogether, and just poll the server manually when I need to check email when away - little reason to getting emails as they come in if I have access to a computer at the same time.
I have found that even with wifi, the quality of your voice signal drastically affects battery life. I'd say I have average signal, (3-4 bars most of the time) for voice. However, sprint provided an airave because data speed is terrible here. A byproduct of the airave is it provides excellent voice signal. So, just with that in place, consumption while the phone is sleeping/idling is reduced by a good 10-20% over connecting to the tower directly. I'd say most of my usage is voice, some texting/emailing, and on occasion, heavy browsing. No games or videos, no facebook/twitter. It's hard to quantify use, but I think that's the bulk of it.
Yesterday I calculated it's use ate 3.9% an hour, based on battery % / time unplugged.
Mind you, I made 2 short phone calls yesterday, and checked my Exchange mail a few times throughout the day. No Angry birds while I'm trying to sort out batter life.
It's still using 100-150mA in standby, and it seems like the governor (SetCPU) is working like it should.
Right now the battery is at 97% and has been off the charger for 1.5 hours. That's 2% an hour. Which isn't bad, but I doubt the average will be that low by the end of the day.
Click to expand...
Click to collapse
What you need to keep in mind, is that unless you're using an sbc kernel, your battery may or may not stay above 90% for too long after being removed from the charger. Unfortunately, battery consumption is not constant. Demand on the battery is changing depending on what the phone is doing. Also, 1.5 hrs really isn't a large enough time period to draw an accurate average from. Based on your cpu usage below, it indicates your device was actually on for 22 min.
Your wakelock numbers don't look bad, but the data is inconclusive. The question is, when these readings were taken, what was the up time, and what would you say was the time with the screen off (rough estimate is the diff between uptime and awake time). Leaving wifi on is a good idea, as it draws much less energy than using 3g.
One number that does seem surprising (assuming total run time of 1.5h's since removed from charger) is your running % of 36.1%. If the phone was not used during this time, that seems excessive. In fact, looking at the next value, screen on - 16.7%, would suggest that 20% of the awake time was when the screen was off.
I would start by disabling or uninstalling(if you use titanium backup, the FREEZE) tasker and widgetlocker. Running % - screen on % = % of time spent not sleeping even though the screen is off - things like receiving email, performing weather updates, etc...

Lowest vsel

Just curious, what's your lowest vsel?
Mine are currently set as: 18/300 - 33/600 - 39/800.
Sent from my MB525

On 2.1 my 300mhz waz 14 but now im on 2.2 i av to use 16 but heres mine 300/16 600/28 800/39
Sent from my MB525 using XDA App

Running eclair 2.1 blur version 2.21 & my settings are:
300/18
700/32
1100/56
Could probably get the 300 & 700 lower (1100 is at the lowest stable I could set) but I'm happy with what they are.
Up_threshold set to 75%.
Very snappy & good battery life - only uses 4% battery when sleeping over night for 8 hours.

My threshold iz on 99% and i get 3days owt of mine
Sent from my MB525 using XDA App

I have used this for the first time tonight and I'm running the following without any issue
300 / 18
600 / 32
1100 / 56

Mine is 1000/50. I did some testings and it is stable.

sp8y said:
Running eclair 2.1 blur version 2.21 & my settings are:
300/18
700/32
1100/56
Could probably get the 300 & 700 lower (1100 is at the lowest stable I could set) but I'm happy with what they are.
Up_threshold set to 75%.
Very snappy & good battery life - only uses 4% battery when sleeping over night for 8 hours.
Click to expand...
Click to collapse
Now running the leaked UK 2.2 froyo 3.4.2-117 & I've kept my vsel the same but now have the up_threshold set to 70%.

if i set the lowest vsel, will my battery live longer?

albertocalle said:
if i set the lowest vsel, will my battery live longer?
Click to expand...
Click to collapse
Less voltage consumption = more use time without needing to charge.
Less charges = Increased lifespan of battery (ussually batteries are rated at 1000 charge cicles)
Less voltage also means less temperature, which may increase lifespan in the long term too.
In climates of 32ºC+ for stores who sell it, its very recommended to store them in refrigerators not in the coolest compartment but next to the drinks.
One battery stored at 10º vs 30º for a few months could mean a lot.
btw my battery lasts at least 12/24 hours more per charge, thanks to setvsel
My settings are
19 300 30 600 40 800
Aply at boot + Limit to vsel1 while screen is off.

In my case:
300/24
600/34
1000/50
At the above voltages, the stability test can run at least 30 minutes with interruptions, like pulling the status menu, showing the instructions etc, from time to time.

[APP] Keep your Phone cool with CPU-Tuner

At the moment i'm on cm10 Alpha 4 with Stock kernel. My phone was often very hot (>55°C) even if i wasnt playing games. I found CPU-Tuner on the Store and now my phone is on Deep Sleep down to 26,5°C cool and while playing "Dead Trigger" over 25min only 46,3°C.
I made some CPU-Settings and Underclocked the QuadCore a little bit. With 51mhz min and 1300mhz max settings on my "Full Battery" Profile, "Dead Trigger" is running without any lag. App Pushed to "system/app" () I also got better Battery Stats trough that App!
https://play.google.com/store/apps/details?id=ch.amana.android.cputuner
http://forum.xda-developers.com/showthread.php?t=1786696
https://play.google.com/store/apps/details?id=com.madfingergames.deadtrigger&hl=de
Pics are Attached, the Battery stats pic is old a new one will be uploaded soon.
New Battery Stats with PIC with 7h 9m 52s
I used the Setup from the old Pics (thats why its not in the Update Post!)
Explanation:
Screen Brigthness all day long 50%
Screen-on-time: 2h 34m 5s
Dead Trigger: CPU: 40m 24s
CPU Foreground: 40m 15s
Mediaserver: CPU: 23m 13s
Active: 1h 42m 44s
Deep Sleep: 4h 27min 13s
Apollo (Music): Active 32m 17s
Tomorrow i'll post a pic for my new setup in updates post...

updates
My new setup is a little more drastic but i want to see what abilitys the App offers:
Leistung:
On @ <=100% Battery
interactive
51mhz to 1000MHz
4 Cores
Normal:
On @ <=50% Battery
interactive
51mhz to 1000MHz
2 Cores
Screen OFF:
On @ Screen OFF
interactive
51mhz to 880MHz
2 Cores
Battery Saving:
On @ <=15% Battery
interactive
51MHz to 640MHz
2 Cores
ANY TIPS ???

Omg the Celsius is from the battery,not from CPU.... Can you read ?
Sent from my HTC One X

I've never said that its the temp of the CPU and does that really matter? The Battery is also very hot while gaming and gets cooler with my setup. Do you know a good APP for monitoring CPU temperature ?
Sent from my HTC One X using xda app-developers app

Dead Trigger doesn't lag when two cores are active.
EDIT: I play all games with two cores, only for battery saving. But now, I set CPU tuner profile to battery saver (740 mhz) and it work smoothly on two cores.

Deleted.

VaderSKN said:
Dead Trigger doesn't lag when two cores are active.
EDIT: I play all games with two cores, only for battery saving. But now, I set CPU tuner profile to battery saver (740 mhz) and it work smoothly on two cores.
Click to expand...
Click to collapse
Wow i never thought that this would work. Did you try that with GTA3 and other games ? Is there any lag in Multitasking operations ? ROM?
Sent from my HTC One X using xda app-developers app

Works great on FIFA!

buy quadcore phone installs app to use only two . sad

@ONE! Where's the Widget Extension? I click on install and then accept and nothing else happens and they aren't in your play store, could please upload and provide them to me. Thanks

Aggressive Unbounce Wakelock/Alarm Blocking Settings

Started off with this document https://docs.google.com/spreadsheets/d/19S0tKF-kfozACgnGIX0gYFBe1K8_R3NBloP4Q1FgpIU great resource, but not quite enough ^_^
Thought I'd share my Unbounce setup, getting amazing battery life, as little as 0.4%/hr drain overnight.
Unbounced ALARMS
com.android.internal.telephony.data-stall = 600
android.content.syncmanager.SYNC_ALARM = 600
com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR = 3600
com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION = 3600
android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED = 900
com.google.android.intent.action.SEND_IDLE = 3600
com.google.android.gms.nlp.ALARM_WAKEUP_SENSOR_UPLOADER = 2400
com.google.android.gms.nlp.ALARM_IN_OUT_DOOR_COLLECTOR = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_S_COLLECTOR = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTOR = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_BURST_COLLECTION_TRIGGER = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_CALIBRATION_COLLECTOR = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_CACHE_UPDATER = 2400
com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR = 2400
Click to expand...
Click to collapse
Unbounced WAKELOCKS
GCoreFlp = 2400
*net_scheduler* = 2400
RILJ = 1600
Wakeful StateMachine: GeofencerStateMachine = 2400
NfcService:mRoutingWakeLock = 2400
NetworkStats = 2400
NlpWakeLock = 3600
LocationmanagerService = 2400
Icing = 900
UlrDispatchingService = 240
GpsLocationProvider = 600
NlpCollectorWakeLock = 1800
wake:com.google.android.gms/..config.ConfigFetchService = 1800
Event Log Service = 7200
Checkin Service = 3600
Event Log handoff = 2400
Checkin Handoff = 3600
SystemUpdateService = 3600
DownloadManager = 240
wake:com.google.android.gms/.auth.be.proximity.authorization.userpresence.UserPresenceService = 99999
Click to expand...
Click to collapse
Haven't noticed any negative side effects so far, all calls still coming, still getting GCM PUSH from my apps, accounts still syncing.
!!! google for raping our devices with 982938432 alarms & wakelocks for your own data collection purposes.
Also see this post http://forum.xda-developers.com/showpost.php?p=55874584&postcount=1941 if you don't care about the stupid Smartwatch, Fitness, Chromecast, Drive.
Impact on battery life is HUGE.

Gee wiz ! So you spend an extra 5 min on the charger, get a grip on yourself man.

PanchoPlanet said:
Gee wiz ! So you spend an extra 5 min on the charger, get a grip on yourself man.
Click to expand...
Click to collapse
If only 5mins gave a full charge

Thanks Camry, it's helpful to hear what others have bounced and what effects it has had on their phone.
0.4% drain overnight is pretty amazing, I'm burning around 10% but would be happy if i can even get that down to 5.

Oehane said:
Thanks Camry, it's helpful to hear what others have bounced and what effects it has had on their phone.
0.4% drain overnight is pretty amazing, I'm burning around 10% but would be happy if i can even get that down to 5.
Click to expand...
Click to collapse
10% overnight is a huge amount :crying:
These are my stats for the past 24hrs, used my phone quite a bit today, still averaging 2.4% / hr... & still a good amount left over

camry89 said:
Started off with this document https://docs.google.com/spreadsheets/d/19S0tKF-kfozACgnGIX0gYFBe1K8_R3NBloP4Q1FgpIU great resource, but not quite enough ^_^
Thought I'd share my Unbounce setup, getting amazing battery life, as little as 0.4%/hr drain overnight.
Unbounced ALARMS
Unbounced WAKELOCKS
Haven't noticed any negative side effects so far, all calls still coming, still getting GCM PUSH from my apps, accounts still syncing.
!!! google for raping our devices with 982938432 alarms & wakelocks for your own data collection purposes.
Also see this post http://forum.xda-developers.com/showpost.php?p=55874584&postcount=1941 if you don't care about the stupid Smartwatch, Fitness, Chromecast, Drive.
Impact on battery life is HUGE.
Click to expand...
Click to collapse
Hi, according to Google drive document, I am a little confused... Usually there are settings around 240s, you have 10times lower, is that right?
Thanks

Be carefull when you apply those settings (even partly) I found that the native WiFi Hibernate with my S5 wasnt working properly / randomly and using Tasker with WiFI Near State would generate a really high and constant load over 9% when used (even when Scan Timeouts were set high - over 600s).
Switched to Cell Near and made Profiles for Screen On/Off and now it's down so 1-2% again.
Wakelocks seem fine now thought I'll post if I encounter more strange bugs. E.g. I'm not sure if only that high load was causing the massive Battery drain when the screen is on (over 6%).
Edit:
Well as I was writing this another 2% are gone so maybe something else is going into panic mode. This definately didn't happen yesterday (still not sure if it's related to those settings)

Overheating protection, battery error?

I'm sorry for my english I write through Google Translate.
Please help as I could not find an answer to existing topics.
I have a problem: my LG G4 H818P off, overheat protection.
When I bought a smartphone, it was installed Android 6.0 official, without root. During the test smartphone does not showed no errors, it worked perfectly. The problems started later, when I came home.
In the smartphone is not working battery temperature sensor.
When I charged the battery is 100% phone is on, and everything worked good.
Temperature sensors were all normal.
But when I started to install software, listen to music.
Battery temperature instantly increased to 28 ° C (82 ° F) to 65 ° C (149 ° F) and triggered overheating protection. I waited 30 minutes, and turn on the device.
After that, my phone displays such indicators:
CPU - 31°C [87°F]
GPU - 31°C [87° F]
Battery - 49°C [120°F] ????
But the battery is cold, not even warm. Because of the false testimony of the sensor temperutry battery, it is impossible to Use phone. Because any load on the CPU, the phone is switched off.
What should I do?
It is possible to disable the thermal protection?
Bought a new battery, it did not help. Can I install custom firmware and disable thermal protection?
Model: LG G4 H818P
Android: android 5.1 (downgrade to 6.1)
Root: Yes.
Installed Kernel Adiutor and CPU-Z.
We are now on the street is cool, -44 ° C, I pulled the phone that he had cooled down. I turn it on after 5 minutes.
BMS - 32°C [89°F]
Battery - 32°C [89°F]
tsens_tz_sensor (all) ~16°C [60°F]
pm8994_tz - 143 °C [289°F] !!!!!?????