Description
Usage Timelines is a CPU and process monitor with graphical load history. It shows you when & which app overloads your phones cpu so you can stop it.
A trial version is available at http://www.refined-apps.com/trials/UsageTimelinesPro-release.apk
For questions, remarks, suggestions or feedback mail us at support@refined-apps.com
A trial version is available at http://www.refined-apps.com/trials/UsageTimelinesPro-release.apk
For questions, remarks, suggestions or feedback mail us at support@refined-apps.com
—- Features ————
✓ Extended cpu load history as notification in the notification bar (like xload/windows task manager)
✓ Process listing
✓ Cpu and memory usage of processes (similar to “top” or windows task manager)
✓ Processes can be terminated and uninstalled
✓ Works without rooting
✓ Very low power usage
✓ Start/stop widget
✓ Supports English and German
✓ No ads
✓ Extended cpu load history as notification in the notification bar (like xload/windows task manager)
✓ Process listing
✓ Cpu and memory usage of processes (similar to “top” or windows task manager)
✓ Processes can be terminated and uninstalled
✓ Works without rooting
✓ Very low power usage
✓ Start/stop widget
✓ Supports English and German
✓ No ads
—- Power Consumption ————
Some remarks about power consumption and performance (percent values are for an HTC Desire).
✓ tl;dr
Set your update intervals as high as acceptable for you. Power consumption should be fine then.
Shorter update intervals lead to higher power consumption since the values are updated more often.
You may also use it just when you experience problems and turn off the notification otherwise.
✓ Usage Timelines has been highly optimized (e.g. the history notification uses 0%-1% of the cpu power with an update interval of 2 seconds if the screen is on).
✓ If everything is fine, Usage Timelines should be the app in the app list that uses most cpu since all other apps should be paused by android. That’s normal and expected behavior.
✓ Displaying the process list needs some additional power, especially if you are working with the app (e.g. scrolling). Without scrolling etc. thisis about 1-2% for an 5 seconds update interval. If the process list is not shown (e.g. while you are using another app), the process list does not use any cpu power.
✓ If the screen is off, only the values for the notification history are acquired to be able to properly update the usage history as soon as the screen is switched on again. Neither the notification history nor the process list are updated if the screen is off since you could not see the update anyway, saving cpu power and lowering power consumption.
Some remarks about power consumption and performance (percent values are for an HTC Desire).
✓ tl;dr
Set your update intervals as high as acceptable for you. Power consumption should be fine then.
Shorter update intervals lead to higher power consumption since the values are updated more often.
You may also use it just when you experience problems and turn off the notification otherwise.
✓ Usage Timelines has been highly optimized (e.g. the history notification uses 0%-1% of the cpu power with an update interval of 2 seconds if the screen is on).
✓ If everything is fine, Usage Timelines should be the app in the app list that uses most cpu since all other apps should be paused by android. That’s normal and expected behavior.
✓ Displaying the process list needs some additional power, especially if you are working with the app (e.g. scrolling). Without scrolling etc. thisis about 1-2% for an 5 seconds update interval. If the process list is not shown (e.g. while you are using another app), the process list does not use any cpu power.
✓ If the screen is off, only the values for the notification history are acquired to be able to properly update the usage history as soon as the screen is switched on again. Neither the notification history nor the process list are updated if the screen is off since you could not see the update anyway, saving cpu power and lowering power consumption.