[Desire General] th3:
It appears in my case only on the OD ROM and correctly so as Contact/Calendar sync is very persistent and buggy on this.

Does PT show this app under just CPU or other hardware components too?

How much time/energy is it showing?

PT can log each processes/applications internal Unix usr-time, CPU, WiFi and screen time as well as that periods power split between components pretty accurately. I'd be surprised if it was wrong when it can track the UID/PIDs and when they are spawned by what. You can cross-check with OSMonitor/System apps if it is mis-identifying certain app CPU/net usage though when they do spawn activity.

The screen you're talking of is the one labeled 'Energy usage over all time', right?

Is the energy shown for the Maps app increasing while it is idle?

This screen will show the time it has been running but not the CPU-time the app is requiring at that moment. Just how long it has been running.

The energy listed will be, for say, if the app has used CPU power for a certain period of time, its total energy requirement will be listed there only for the duration when it required, even if the app is not using any energy at the moment when idling in the background. If it is using power at that moment, the total energy shown for the app will be increasing and if you tap the app name in the list, the next screen will show you just that processes sole power usage.

IME the Maps app doesn't take CPU time/power when idling in the background. It shouldn't.

Can you share with me which screen is showing this?

The apps listed under the 'Energy usage over all time ' screen will have required usage at some period for some interval. However, they may not have taken any component power but still be listed there if the app had screen time, i.e. listed under OLED. That isn't really the power draw of the app, just the energy usage total for the OLED screen when you were using that app. You probably know that you can uncheck 'OLED' energy usage by tapping on it, and similarly the rest.

In the 'Energy usage over all time' press Menu>Sort By>Current Power if you want to see which app is taking the CPU power/time at that instance.

I've already mentioned about PTs' lack of thorough documentation so this is very understandable. They're still working on that.

The PT app currently has some bug where individual pixel power draw isn't being added into the final OLED calculations. It only occurs in some cases, like when you've decreased RGB subpixel luminance through calibration. Typically, when I'm indoors after evening, I turn down the OLED RGB luminance to 600/550/524 from 1000/950/924 which should drastically cut the OLED power. While the pixel power values are picked up fine, the power figure isn't changing which isn't correct. I'm still querying on this...

BTW, I am quite certain that a large part of why the OD ROM is very smooth, consistent and fast for typical usage is because its memory management is very different to with the HTC release. I'm always at 100-170MB free after hours of use with it whilst the HTC ROM starts at ~105MB free and after a few hours stays hovering at the 50-65MB available mark. After some test observations, I'm inclined to think the extra memory burden is by Sense and HTC installed apps.

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

- Sent via my HTC Desire -