yashsingh1/xdaforums huggingface dataset:
[Desire General] prcach:
With 2.1 with medium use it lasted for at least one day, charged it at night and before sleep(2am) it was about 25%.....fine by me

Now....fully charged, mostly in standby, dead in like 6h...i mean wtf, surfing for 10min and battery drops to 80%...got same apps as on 2.1, didnt install any "led" app or something like that. In battery statistic it says that android use 45%+, cell standby about 20%, idle and screen are about 15% each, everything else is 1-3% each...while im typing this battery dropped to 10%, charged 5,5h ago...i cant go everywhere with charger!

Any solution?
[Desire General] BlackBirdf:
Monitoring tool

I think you are still looking for a good batt monitoring tool?

I can recommend this:

Battery snap

by Xhelas

50,000 downloads, 1613 ratings (4.0 avg)

Free

Graph for percentage over time (also has different colors for usb and charger), CSV export (incl. temp+voltage), nearly no battery drain, and some long-term stats...
[Desire General] andycted:
That looks ok, but it's not much different from system panel or the free juice defender. What it's really missing is a real time mAh battery drain monitor.

not sent from an iToilet
[Desire General] BlackBirdf:
I think without additional hardware this won't be possible, because afaik there's no current sensor build in to read out the mA, and without this you can't calculate the mAh.
[Desire General] martintzvetomirov:
GPS off :) But I think it does not matter much because GPS is a piece of hardware that is activated on demand.

I was unable to find an app that shows mAs as well. It's bizarre cuz there were such apps for WinMob. And yeah, voltage kind of matters but I think amperes give more accurate data. To be even more specific the correct thing to use is Watt which is the power of the device and it can be calculated by multiplying the volts with the amps (oops got too carried away :) )

Basically the thing I want to say is that voltage is almost constant and the thing that changes a lot is the current so a reading in amperes should give a more accurate drainage picture. :)
[Desire General] RaptorRVL:
Would be nice to see how many amps a certain program uses. And even more importantly, you can check whether the battery is allright or not. If 100% - 0% only shows up as 1000mah or something, you know something is not right. Either the % is completely wrong or the battery is not good. It should come near 1400, if it's a proper battery even some more (usually batteries are shipped with a slightly higher capacity, to make up for some degrading going on if the device is in storage for a longer period).
[Desire General] th3:
This is true. If you have the GPS on, unlike WiFi, cell or mobile data, it draws next to no power unless and until you open an app or are running an app which uses it. It seems to go into a deep sleep state until called upon on 2.2. Not sure how it was on 2.1.

I'm one of them with the bug of WiFi not switching off after 15mins as set. It just stays on all the time. But I placed the phone in sleep along with myself (in airplane mode with WiFi on) and woke up after 7 hours 23 mins to find battery at 46%. It was 46% when I slept. I was perplexed, so I tried again last night. 32% when sleeping and on awake it read... 32%, resuming lower as usual.

A calibration bug? Maybe. When it died after 16 hours 21 minutes, it read 15% but when I restarted it immediately on AC, it had just reached 1%.

I usually look at battery lifereplies based on some phone details that state:

*BMA150 3-AXIS ACCELEROMETER*

Power: 3.0 mA

*AK8973 3-AXIS MAGNETIC FIELD SENSOR*

Power: 6.7 mA

*AK8973 ORIENTATION SENSOR*

Power: 9.7 mA

*CM3602 PROXIMITY SENSOR*

Power: 0.5 mA

*CM3602 LIGHT SENSOR*

Power: 0.5 mA

-----------------------------------

- Sent via my HTC Desire -
[Desire General] ediflyer:
I'm finding that my phone is now alarming when battery % falls to 14% (as with 2.1) but it is then immediately powering down!! Is anyone else experiencing this sort of behaviour?
[Desire General] andycted:
It did for a while, but not anymore, I think it just need calibration
[Desire General] andycted:
isn't this a sign that there might be a way to read mA ?

Some rough testing for today:

Disconnected from charger at 16:40, battery at 75%

- 1+ hour of browser, 3g, sometimes in very bad reception

- 2 phone calls, 10 minutes each

- 4 sms

- 1.5 hour listening to mp3 with headphones

- worked on 4 albums with mp3 tagger (heavy disk activity)

- 10 minutes google earth

- 15 minutes maps, no gps

- auto brightness on the beach, sunny day

- 15 minutes playing games

- gmail push received 4 emails

- feedr updated about 20 articles and read them

- updated/installed around 6 applications

- layar + gps for 5 minutes

- probably some other stuff can't remember

Phone turned off at 5% battery at 2.30 (almost 10 hours later)
[Desire General] noise79:
froyo battery prb

Basically there are 2 things u have to take care of in order to have your battery lasting longer in FroYo.

U got to use a task killer working under froyo "advenced task killer - rechild" for instance + u have to check your awake time under "settings - about phone - battery". Awake time should freeze while your phone screen is off. If it doesn't, it means that some apps are wasting your battery while the phone should be saving juice during stand by.

By the way, to check your awake time u should have your phone unplugghed as it doesn't "sleep" if connected to the power supply.

After doing that I got normal battery usage on my HTC Desire with FroYo. Now it last 1 day just like with Eclair. Seems like my old task killer app wasn't working with FroYo.

Hope this help, it did for me :-)
[Desire General] meroupow:
high CPU clock

interesting thread, I wish somebody could sum up the findings.

I used standard 2.1 and now standard 2.2, I noticed with system panel (and also with setcpu info) that the clock doesn't go down below 750Mhz whereas before with 2.1 it was a lot more on the 250 Mhz side.

Also I have the feeling that Froyo is much better at maintaining battery in standby mode as already mentioned by others (almost no drain when only using GSM and no data).

But once you turn it on, it gets hot quicker and cpu is always high, maybe they changed the settings of perflock in order to make it feel more responsive.

So to sum up my view, Froyo consumes less in standby and more when turned on hence the mixed users feedback depending on their usage.
[Desire General] andycted:
In my opinion, not a lot has changed from eclair, since you are only upgrading the system and some stuff will always consume the same amount of battery(screen, antenna, etc) but I think that somehow process-intensive applications benefit from the JIT compilation.

I would think of something of a 10% improvement in battery life, which however isn't easy to ascertain, but for sure I won't complain about that battery life reported in my previous post.

Regarding your finding of the Mhz, might it just be that you had a custom kernel installed on eclair ? Anyway, in my experience, the phone seems maybe colder rather than warmer.
[Desire General] Mike's Aria:
I don't know if it has been covered already, but the new Facebook upgrade is a really battery hog. Apparently it runs even when the device is in stand by. Only way to stop it is to log out and kill it.

I noticed an immediate performance increase. Dont know how much it affects battery life yet.
[Desire General] andycted:
I've read somewhere that it sometimes get fixed after a full wipe.
[Desire General] Mike's Aria:
I did that last night. Battery was still down 10% in an hour with no use.
[Desire General] ediflyer:
Just read on Android Central that Facebook have now acknowledged the problem and are working on a fix - I'm holding off installing it until then!

Battery-wise I've found that it's improved with a few charge/discharge cycles (I did a hard reset after the upgrade) and I'm now ending the day with a higher percentage charge left than under 2.1 (with similar usage) - so it looks to me like it has got a bit better in managing standby.
[Desire General] th3:
What I'm trying to get data on is the various silicon used within this device and their power characteristics. Then we can get a rough idea of close to accurate power draw depending on usage and how to optimise for a chosen runtime.

So far I've only be able to gather negligible data; those upper values mentioned and that in standby, this SoC uses close to 200mW.

Every chip off the line is different in power draw than the other. Some better, some worse. When you have more than 2-3 chips on-board running under different environmental conditions, it can create a nice cocktail of variations. So some will definitely attain better battery life than others but the highest power chips are what the MFGs release expected battery runtime data based on.

There will inevitably be users who complain of battery life from 2.1 to 2.2, some correctly for reasons particular to their device/ROM/setup, others not so due to higher expectations, high usage scenarios and/or lack of fair and controlled testing and comparisons. Providing they are not outright lying.

For instance, there are some I've seen since 2.1 angry about only getting 5-7 hours battery life "no matter what they do". Like charging in the morning before work and it being dead by lunch. I have heard this many times. If you want to see it, this is the setup you need to hit as low as 5hrs battery life:

*GPS always on, indoors, poor signal

*WiFi always on, 15-25m away from router

*Screen always on 50%, sleep disabled

*Cell always on with 0-1 bars, auto GSM/WCDMA

*Mobile data always on

*Autorotate on

*Vibrate for everything

*29 widgets sync every 10 mins

*3.75 hours of predominantly white paged internet browser usage including embedded video playback

*GMaps, Earth, GPS Test, HereIAm2 used for 17 mins with location enabled

*20 mins or so synchronizing and reading 23 NewsRoom feeds

*26 SMS sent, 17 in

*2 2MB pic uploads to ImageShack

Start at 100%:

http://bit.ly/92npJi

http://bit.ly/bL9qlN

End at 14%, seconds before it died:

http://bit.ly/9kaOzo

http://bit.ly/9LBzIN

http://bit.ly/b36bnz

That is by no means an average or medium setup and usage and it is completely impossible for me to even get close to after I've left home for work in the morning.

Yes, that battery life is very much like mine. In my typical everyday usage, this is what my last full test managed before shutdown:

http://bit.ly/boK0mF

http://bit.ly/alkNhK

-----------------------------------

- Sent via my HTC Desire -
[Desire General] andycted:
You know when someone says what you think, but with better words ? Hehe, you cracked me up with that example, but then also performed it for real haha !!

The best comments on these battery threads are those "if I have to turn all these things off, I'd better buy an old mono chromatic-lcd nokia". Please do !

I can get several hours of streaming music on 3G, and that's already a miracle in my opinion.

[EDIT] what's that cute battery icon in your notification bar ? Also, I would be interested in seeing the different mAh that those chips/sensors consume, but I'd be probably even more interested in comparing GSM mobile/3G mobile/Wifi/3G data/EDGE data because for years I've heard that being in WCMDA only (like my provider) drains more battery, but I'd like to know how much more. Also what I meant was that there must be somewhere to get mAh in real time and I'm try and going to find it
[Desire General] andycted:
A few more tests

Calling:

- Screen off, 3G data on, perfect signal: 180-201 mA

Misc:

- Floating images, without interaction, low brightness: 274 mA

- Floating images, scrolling photos, low brightness: 300 mA

- Playing "Drop" or any other simple similar game: 280 mA

Streaming music/video:

- Min brightness, 3G data, xiialive on speaker: 271-292 mA

- Min brightness, 3G data, xiialive plugged to tv speakers: 282-305 mA (wrong reading?)

- Min brightness, Wifi data, xiialive on speaker: 223 mA

- Min brightness, WiFi data, youtube video: 269 mA

- Min brightness, 3G data, same youtube video, but probably lower quality: 294-330 mA

I've repeated the WiFi vs 3G music streaming test three times to be sure. While I do have spotty wifi connection and indeed sometimes streaming music gets interrupted, it seems that it drains less battery all the same. This is however different than having wifi idle vs 3G data idle, in that case WiFi is draining a lot more, probably because of the bad connection too.
[Desire General] nicandris:
Do you have render effects in desire? (like the n1)

I think cm6 is available on desire also? I would like to see some results with it enabled
[Desire General] andycted:
Live Wallpapers suck a lot of battery

You get render effect in cyanogen and opendesire (ported from there)

Live Wallpaper vs static:

Dark blue (grass) static wallpaper: 130 mA

Live wallpapers:

Galaxy: 215 mA !!!!

Grass (by night, same as static): 200 mA

Magic smoke default (green): 191 mA

Nexus one: 193 mA

Polar clock (white): 272 mA !!!

Water lilies: 260 mA

Panoplanet + orientation sensor: 214 mA

Starfield 3D: 156 mA (nice !!)

Bezier lines (2 lines): 305 mA !!!! with a black background !
[Desire General] bemymonkey:
I just posted the following in two other threads, but since it fits here pretty well too:

Battery log

Settings & Info:

OpenDesire 3.0.5

Auto Brightness on

WiFi on

3G On

Sync On (Google account & Gmail only)

Sipdroid on & connected via TCP (pbxes.org)

Locale with location-based profiles activated

Launcher Pro

Static WP

Beautiful Widgets Beautiful Home

Dialer Pro

GPS + Location Services on demand

Timeline:

-Unplugged at 11:00 AM (100%)

-Cleaned up SD Card: 5 minutes with device on

-10 minute phone call

-15:00 - 93%

-15:07-15:37 - Read a few forum threads (mainly light grey and white backgrounds) - 86%

-16:35-16:55 - Few more forums... - 81%

-Tested power consumption with Andycted's tip here in this thread, which lost me a few percentage points (idle power consumption with screen on lowest, screen on highest and screen off)

-Another rough half hour of surfing - 73%

So, battery stats at 8 PM (9 hours later):

My current drain figures:

Idle, screen off: 5-15mA

Idle, screen on lowest: 120mA

Idle, screen on lowest, button backlight off: 110mA

Idle, screen on highest: 165-180mA

The screen does seem to use an unfortunate amount of power. I was indoors the whole time the screen was on, in rather dim lighting, so even with auto brightness it was probably on the lowest setting. :(
[Desire General] andycted:
How do you turn buttons backlight off ?
[Desire General] bemymonkey:
http://xdaforums.com/showpost.php?p=7575007&postcount=6293

Basically, use Gscript (or adb or terminal emulator) to send

echo 0 > brightness

in the folder /sys/class/leds/button-backlight

Defaults to on every time the phone's been in standby though. Haven't found a way to launch it on every wake yet...
[Desire General] andycted:
Thanks, I've repeated your test because it seemed a bit too much difference, but indeed it has a 11-12 more with buttons backlight on ! That's huge, it means that if you have the screen on about 1 hour a day, you lose 120 mA for something that you probably don't need. Is my calculation wrong ? That's 8% battery total ?
[Desire General] th3:
I had already written a reply but not proofread it to post saying pretty much that the device has more than 6 chips drawing power so it uses a TI power management IC. In effect that means it can definitely monitor and gather electrical data for the chips used in real-time. Secondly, the battery info provides feedback on the power use of each application/process/hardware which it can't do without being able to monitor and analyze this data. Unless it's making the figures up out of thin air which I somehow doubt :P

Nice find with the app, however, it doesn't work for me so I can't test it. The widget just shows "open error" and I can't access those files any other way either. HTC 2.2 rooted. Some points;

i. That app provides a mAs measurement which fluctuates drastically on chips. Those figures need to be averaged from a number of samples over a runtime greater than 3 minutes in each condition to gain a somewhat accurate moving average. 200-300 mA readings are high, very high. The whole Snapdragon SoC has a Pmax of 350 mW when everything is working at max load. If you really have 200-300 mA draw consistently in a state, you won't get more than 4-7 hours battery life at best.

ii. Current draw fluctuates much with spikes and dips per millisecond. mAh in return is an hourly metric. So this mA reading tells us how many hours we can run at such current draw.

iii. You can already estimate the power draw one way by looking at the percentages and runtime for mAh figures.

When I fired the compass up for 2m47s, it used 11% of the 1400 mAh battery, whilst the WiFi running for 9hr58m9s had used 17%, phone idle 13% for 7hr44m21s and the display 12% in 6hr6m48s. After some lengthy sums you get:

Compass app uses 219.750 mA

Cell standby uses 27.634 mA in auto PRL GSM

Cell standby uses 12.069 mA in GSM only

Display uses 20.061 mA awake at 0% brightness

WiFi running uses 17.428 mA

Phone idle (sleep) uses 17.167 mA

I suppose we can get very rough approximations this way but the accuracy of any software readings depends on the battery percentage reported, the battery usage info and the total mAh the battery delivers all being as suggested.

It's part of this mod: http://xdaforums.com/showthread.php?t=724778

-----------------------------------

- Sent via my HTC Desire -
[Desire General] th3:
I'm assuming you mean 11-12 mA, and if so, that means you'll have 11-12 mA less current draw [per hour] without the backlight. Which equates to 110-120 mA total usage after 10 hours with backlight on.

-----------------------------------

- Sent via my HTC Desire -
[Desire General] andycted:
What you say makes sense, however I've done the tests leaving the device to do something for at least 3-4 minutes, tested 2-3 times and made an average of the results. Also I think those high readings make sense, as you are coupling different things: display, processor, wireless radio, sound, etc. of course you won't get more than 5 hours if you use it like a laptop, always on. But on screen off, 5 mA seemed like a good value.

By the way you probably can't read those values if you are on htc roms, there are other similar values in there with different names
[Desire General] andycted:
Never do your math when you're drunk, that's what my professor always said, and he was right ! So we basically lose 11 mA for every hour of screen on, which probably equates to something in the range of 20 mA per day.

I'm still drunk but I think this time it's correct
[Desire General] th3:
Sure, I don't doubt those values are incorrect but we don't know how accurate they are at all. Do we? ;)

We don't know anything about how those values are measured and the feedback system. We are assuming they are somewhat accurate hence valid.

What I talked about in the beginning kinda has little to do with what you replied though. I'm talking about the TI power management IC being able to gain per second feedback on the hardware current draw in this device. That's its job. Most likely using the Imon pin with a negative feedback system which typically has an accuracy of +/-10% for low-power low-cost implementations. If that chip can acquire such current values, maybe those values can be read by Android ... ? Otherwise, it has no way of knowing how much power of the total power is used by each app/hardware as it shows in the battery info section. I hope you understand me better now.

I'm perfectly aware and didn't state anything otherwise.

And yet again, how do we know this?

Can you post the schematic for the current measurement and feedback system on the Desire? I'd like to see the measurement error and processing.

Yes. The data posted is good.

However, 4-5 hours I've never had and I don't think andycted has either from his posts. 5-8 hours I have only if playing 1.2Mbps 720p vids. 7-9 hours I can agree with you on.

You're assuming too much. You know that leads to misjudgements ;)

Already did all that and the answer is posted above. What I said was correct in mAh. It was worked out as you later stated. I just didn't provide that much depth to the post because it was very lengthy already. I'm using the phone.

As I mentioned clearly, none of these methods are accurate or precise and they can have major flaws. They are only approximations. I have used these approximations in the past when we had no avenue to gauge current draw. The widget is a slightly better method but we are still relying on too many unknowns. Each of which can add large errors to the end values you are being shown.

You're pedantic, very :P

You are right since I worked out the current values per hour it is mAh of power usage but you've just re-said everything else I've said except the hour addition after mA.

Current draw is never fixed in a system. Ever. Nor is silicon subthreshold, gate and junction leakage current which is directly influenced by the operating voltage and temperature. But theoretically if you could fix 11-12 mA current for a full 10 hours that equates to 110-120 mAh drawn from the 1400 mAh battery for that piece of hardware. 10 hours with the backlight on at all times.

-----------------------------------

- Sent via my HTC Desire -
[Desire General] andycted:
Hehe, while my terminology was probably a bit off, all I wanted to say that, buttons on vs buttons off, we lose 11mAh more in an hour usage, meaning that if I burned 120mAh with buttons off, I'd burn 131mAh with buttons on. And that's quite something if you use it a _lot_, say 5 hours with display on per day, you will lose 55-60 mAh in those 5 hours, for something that you probably don't need.

By the way, I really think the sample isn't the average of one minute, but rather the instantaneous value taken each minute.
[Desire General] funkymagicuk:
Are people noting cell strength and hopping etc whilst monitoring their battery usage, as I suspect it'll be quite significant.

For example, a few days ago I went from 100% at 8:30am, down to 30% at 8pm, 11.5 hours later, having taken a few photos, sent a few SMSs and a small amount of web browsing.

Significantly though, 6 of those hours were spent travelling on a train.

YESTERDAY, I let my phone charge to 100% and then put it on my desk at 3pm. I've done a bit of browsing (via WiFi rather than GPRS), downloaded a couple of apps, sent some SMS and taken a few pictures, and as of 10:55am, almost 20 hours later, my battery is still showing 81%. The difference is that I've not moved my phone, and I live in an area where I get a consistent 2 or 3 bars.
[Desire General] andycted:
Actually one of the most interesting findings, that I was trying to interpret, is that not only airplane mode vs mobile on is only a couple of mAh different, but that mobile on vs mobile data (3G) on, at idle, is also only a couple of mAh of difference. In this view, a tool like juice defender, which supposedly saves battery by keeping 3G data off and turning it on periodically, doesn't seem to be able to grant the supposed 2x battery life it says. I guess it could save a little, but it would be compensated by the hassle of having stuff connect to the internet every now and then (some applications don't even work very well this way)...
[Desire General] andycted:
While battery % isn't very reliable in telling the story, you sure have a point, as in fact my spotty wifi drained more than my excellent 3G, on idle. Anyway, my tests were done in (at worst) -80 dBm
[Desire General] bemymonkey:
That's precisely why I don't use Juice Defender ;)

But I (and many other people) could have told you this before: The mobile and WiFi radios power-scale very well according to traffic - if there's little to no traffic coming in or out, they don't really use a lot of power.

If you're syncing hundreds of full RSS feeds with pictures every hour, though, or downloading videos or something in the background... your battery will be dead quickly. :)