[Desire General] th3:
Yes it does, everys second. FYI, this was my last logged reading with the app (for the last second). I've added some notes to help decipher:

begin 1634
total-power 697 (mW)
LCD 312 (mW)
LCD-brightness 10
LCD-screen-on true
LCD-10106 312 (mW used by this app UID)
CPU 346 (mW)
CPU-sys 41 (% of total CPU power)
CPU-usr 0 (as above)
CPU-freq 998.4
CPU-0 3
CPU-1000 28 (mW used by each UID)
CPU-1001 0
CPU-1002 0
CPU-1008 0
CPU-1010 0
CPU-1013 0
CPU-1014 0
CPU-1017 0
CPU-10000 14
CPU-10002 0
CPU-10011 0
CPU-10018 0
CPU-10019 0
CPU-10042 0
CPU-10067 0
CPU-10072 0
CPU-10076 0
CPU-10079 0
CPU-10083 0
CPU-10086 0
CPU-10088 0
CPU-10095 0
CPU-10097 0
CPU-10106 153
CPU-10110 0
CPU-10117 0
CPU-10118 0
CPU-10119 0
CPU-10126 0
CPU-10127 0
CPU-10128 0
CPU-10139 0
CPU-10143 0
CPU-10146 0
CPU-10167 125
CPU-10190 0
Wifi 39 (mW)
Wifi-on true
Wifi-packets 0
Wifi-uplink 0
Wifi-speed 36
Wifi-state LOW
3G 0
3G-on false
GPS 0
GPS-state-times 1.0 0.0 0.0
GPS-sattelites 0
Audio 0
Audio-on false

If that's what it is showing, then that would be correct. I would suggest you wait for the updated version before taking its absolute figures seriously though as there is more work going on for our device. The Google N1 official figures do vaguely suggest contrary however:

Which means a good, stable WiFi connection should be quite a bit lower in power as these values are based on standard controlled lab tests. To break it down, what the above figures mean is:-

WiFi net rated power: 1400*3.7/6.5 = 797mW

3G net rated power: 1036mW

Video playback: 740mW

2G standby: 17.9mW

3G standby: 20.7mW

2G talk: 518mW

3G talk: 740mW

Audio playback: 259mW

However, we don't know what load those internet figures are taken under. And also, could the Desire internals be very different to the Nexus One?

AFAIK, the problem why official phone stats for 3G are usually lower is because it required higher CPU power draw than WiFi which dropped its runtime in comparison. I get approx. the same figures as you for the individual component but when I run YouTube at all settings on max, PowerTutor shows idle at 960mW, and load for the total device at ~1516mW for WiFi and ~2069mW for HSPDA. Under minimum settings for everything running the same vid it gave me 830mW for WiFi and 1230mW for HSPDA. What do you get?

Research studies carried out on this found similar observations suggesting that WiFi/3G power draw and efficiency depends on the workload and for smaller workloads, some 3G implementations may be more efficient than WiFi (as in energy required for the task in joules). I mean research papers like Y. Agarwal, R. Chandra, A. Wolman, P. Bahl, K. Chin, and R. Gupta. Wireless wakeups revisited: energy management for voip over wi-fi smartphones. In ACM MobiSys, volume 7, 2007.

If you see this study, although they didn't test video/audio streaming through both technologies, they found these values for simple web use on the Nexus One:

As for the audio; the engineers power modeling showed only a few power draw bands for the audio subsystem irrespective of anything except if the audio signal is being put out. That it stayed relatively fixed. I have only seen two values so far. Around 345mW and around 400mW. I haven't checked exactly what causes the difference yet. I did ask because I too found it peculiar.

I've been searching and querying high and low to get some power figures for the Desire type AMOLED implementations but found nothing. All the reserach studies and papers are pre-2008 when this tech wasn't even working at these specs and no where as good. I mean older papers like this and this show a 4" AMOLED in 2003 at 670mW max and a 2.4" AMOLED at 738mW max, whereas later studies show things like:

So I couldn't be sure what power characteristics our display had.

However, the PowerTutor dev has kindly notified me that their study measurements found approx. 100mA draw by the OLED screen in idle, on a black background, which is about 365mW. So the estimation of some of you that the screen-off to screen-on roughly 100mA jump was primarily the display, seems correct. Can we take confirmed N1 figures as completely respresentitive for our phone?

The second thing he kindly did is provide more details on Android UIDs which we on this forum we're confused about. Remember complaints about readings like process 1008, CPU usage 10%? I'm not sure if you knew but I was unaware of some of these. They are fixed: http://www.netmite.com/android/mydroid/system/core/include/private/android_filesystem_config.h

Now to how long the battery should theoretically last. PowerTutor shows around 950mW under idle but with everything on at max. Add some consistent usage and it shows about 1030mW. That would mean you get 5hrs runtime max on a full charge... which if you look earlier, is exactly what I obtained under this usage :)