Develop Bugs

Battery temperature

Hello.
The battery reading is constant 36.8°C, im used to that. Anyway, yesterday i was observing the terminal while charging the battery to see whats going on with adjusting mAh and units, and noticed that aux0 value from ds2746 is getting lower as the battery gets warmer.
so i stuffed the digital thermometer probe under the battery and made a few notes while heating ans cooling the phone:
aux0....temp
268.....27,8
343.....20,2
365.....18,3
390.....15,5
then i played with the numbers a bit and got this:
546 - aux0 *0,1 = temp (close value)
it was a crappy cheap thermometer so the values could be wrong. should repeat the measurment with more acurate thermometer and make more than 4 notes....
Could the kernel be moded so the temperature reading would be from the upper formula?
Edit:
it's 596 - aux0 * 0,1, that should show the same as in WM

Thanks for the research! I've been meaning to do this for quite a while, but haven't. Out of curiosity, I have two questions:
a) What battery do you have?
b) What is aux1 reading for you?

aux1 jumps arround from 61 to 67 right after boot. After that its quite stable. 64 when charging, 62 when not charging.
Batteries are one 1350mAh and one dissassembled, using the controller with random battey packs, currently 750mAh

I'll update the kernel to use your data:
Temp C = (596 - aux0)/10.
I'll make the 596 a new kernel parameter: temp_calibration = 596.
If you come up with a better equation, please let me know.
The kernel will do integer math, not floating point, and it reports tenths of degrees, so with your equation it's simply C*10 = 596 - aux0, which is nice.
I wonder if perhaps the value HTC intended was 600?

It's a small difference, 596 just came from measuring, an the thermometer isn't pin point acurate. 600 should make less than 0.5C difference.

Okay, I just pushed the kernel change.
New kernel parameter, temp_calibration = 600.
Temp (C) * 10 = temp_calibration - aux0.
Coming soon to a kernel near you.
Thank you again V3rt!g(o) for the data.

[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.

[Q] battery issue?

Hi, i have an lg g3 (32 gb) stock purchased yesterday.
after 10h and 30 min i have 20% of battery and those are my stats:
CPU = CPU time
AT = active time
MA = maintain active
screen on time :
- AT = 2h 41m
android system:
- CPU = 1h 22m
- MA = 34m
android OS:
- CPU = 36m
- MA = 4h 53m
gogle services
- CPU = 12m
- MA = 1h 16m
- GPS = 8m
systemui
- CPU = 15m
tasker
- CPU = 3m
- MA = 8m
... and others few things
i played even at two games but for not more than ~45min ( at MOST)
do i have a battery issue?

raff0z said:
Hi, i have an lg g3 (32 gb) stock purchased yesterday.
after 10h and 30 min i have 20% of battery and those are my stats:
CPU = CPU time
AT = active time
MA = maintain active
screen on time :
- AT = 2h 41m
android system:
- CPU = 1h 22m
- MA = 34m
android OS:
- CPU = 36m
- MA = 4h 53m
gogle services
- CPU = 12m
- MA = 1h 16m
- GPS = 8m
systemui
- CPU = 15m
tasker
- CPU = 3m
- MA = 8m
... and others few things
i played even at two games but for not more than ~45min ( at MOST)
do i have a battery issue?
Click to expand...
Click to collapse
Yes that looks well below normal - can you take a screenshot of battery rather than using your "key"
Are you rooted?

Vivasanti said:
Yes that looks well below normal - can you take a screenshot of battery rather than using your "key"
Are you rooted?
Click to expand...
Click to collapse
no i'm not rooted and if is possible i want to remain stock,
for now i let the battery discharge out for a first calibration after a full charge in the night (because of i've purchased the phone yesterday) and installed greenify (using non root functions) and qualcomm battery saver.
theese screenshots are enough?

if you say that the battery life will improve (a lot) with root i'll think on that

Whats your screen on time (SOT)
What are you doing in the middle with such a big drop?
Gaming?

Vivasanti said:
Whats your screen on time (SOT)
What are you doing in the middle with such a big drop?
Gaming?
Click to expand...
Click to collapse
SOT at 5% was ~4hr 30m + (i didn't checked)
i've checked facebook, google+, gmail then did some web browsing and ~15min of gaming

Occasional Poor Battery Life (Stats reveal nothing)

Some days by the evening, my battery is still at 70% other days it's flat. My usage patterns are very consistent. On a bad day, I captured this from the logs, and it looks unusual to me. Only 1hr of screen time, and nothing obvious from the other stats.
Anyone else seen this? (Rooted N5X with otherwise stock 6.01)

CrazyPeter said:
Some days by the evening, my battery is still at 70% other days it's flat. My usage patterns are very consistent. On a bad day, I captured this from the logs, and it looks unusual to me. Only 1hr of screen time, and nothing obvious from the other stats.
Anyone else seen this? (Rooted N5X with otherwise stock 6.01)
Click to expand...
Click to collapse
It's your terrible signal for a large chunk of the day

CrazyPeter said:
Some days by the evening, my battery is still at 70% other days it's flat. My usage patterns are very consistent. On a bad day, I captured this from the logs, and it looks unusual to me. Only 1hr of screen time, and nothing obvious from the other stats.
Anyone else seen this? (Rooted N5X with otherwise stock 6.01)
Click to expand...
Click to collapse
Look at all the time your phone is awake but your screen is off. I would say your wakelocks are causing your battery drain and that your battery stats reveal quite a lot. Try using Better Battery Stats to find out what your wakelocks are.

I have purchased better battery stats, but I can't see anything that looks like a culpret. Can someone who is experienced take a look?
Thanks.

CrazyPeter said:
I have purchased better battery stats, but I can't see anything that looks like a culpret. Can someone who is experienced take a look?
Thanks.
Click to expand...
Click to collapse
There is a better battery stats app thread on xda
It looks like Google hogging it again, your phone is having trouble sleeping
Since 6 h 41 m 48 s Awake
(Screen Off) (): 1 h 8 m 49 s 17.1%
Level lost [%]: Bat.: -56%(100% to 44%) [8.4%/h]
com.google.android.gms (): Wakeups: 693 (1.7 / min)
*net_scheduler* (Google Services): 1 m 3 s Count:9224 0.3%
WearableSyncService (com.google.android.apps.fitness.Fit): 58 s Count:353 0.2%
NlpWakeLock (Google Services): 53 s Count:7094 0.2%
Etc etc
my phone does not doze properly, compared to my nexus 5, I think Google services are to blame.
I had to remove alot of Google apps from system and install from app store and stop syncs to have proper idle drain, and its better now.
Eg on my phone today, YouTube *net_scheduler* over 300 counts and 24mins awake, It started itself, nor am I subscribed to any users, it shouldn't of been running in the background and I'm having trouble deleting the app

Did a backup and a factory reset of my phone, and battery life is back to normal. At the same time I did upload SuperSU to 2.66 (I was on 2.61), and I noticed in the changelog some mention of fixes that fixed devices not sleeping.
It might be worth a shot to see if it helps others. Please report back if it does. I only noticed it after I had reset my phone (for the 3rd time, to fix battery life problems).