Help "Up Time"; "Awake Time" and "Time since Unplugged"

[losl]

The User Manual of HDH dose not mention "Up Time"; "Awake Time" and "Time since Unplugged" in detail. I observed my HDH with Android 2.2.1 and found the following features:

"Time since Unplugged" (xh xm xs since unplugged) is displayed in the top bar of "settings/about phone/battery/battery use". It could be reset to zero after charging the battery and disconnect the USB cable with the phone in "SLEEP" mode. It will not be reset but counts continuously if you charge the battery with the phone in "power off" mode.

"Up Time" could not be reset after either the phone is "power off" or switched to "SLEEP" mode. It reset to zero only after the phone is "RESTART". Furthermore it counts continuously even the phone is "POWER OFF".

"Awake Time" is similar to "Up Time" for reset. But it stops counting in "sleep' mode and 'power off'

It will be highly appreciated if you can check your HDH and confirm these features.

Thank you very much !!

 

[Xyro]

Uptime is the total time the phone has been running since it booted. Unlike most android phones, when you switch the DHD off, you're not really turning it off completely; it uses a little bit of power to keep the memory alive and that's why it turns on so quickly. Its only when you do a restart, or when you pull the battery out/drain the battery completely, that it really turns off. That's why telling it to power off doesn't count as shutting down and uptime keeps counting.

Awake time refers to when the phone is working away at something. When the screen is on, it's awake. When you turn the phone off, the phone should spend most of it's time in sleep mode as it's not doing anything (listening to music and so on will prevent it from sleeping with the screen off, for example). And obviously when you power it off, as I mentioned before, the phone is using as little power as possible and so this also counts as being asleep.

As for the total time since unplugged counter not resetting if you charge with it turned off, that's probably just because it's not active enough to track that kinda thing (doing so would use more power).

Long story short, all of that behaviour seems normal to me