Guardian

CPU et Wakelock surveillance

Sophisticated device monitoring tool that, not only alerts about rough applications, but is also able to do something about it.

Features

• Live Overview of Process Activity. This includes CPU Usage, Wakelock time and additional details about owning processes etc.
• Option to terminate individual processes, although this should not be used unless a rough app needs to be put down
• Choose between a Persistent or Scheduled Service to monitor processes in the background and have the app alert you of both extensive CPU and Wakelock usage
• Option to automatically handle rough applications, like terminate it or release it's wakelocks
• Plenty of configurable options to make the above features fit your needs

Do note that Wakelock Monitoring will need Xposed Framework or Cydia Substrate. Android has no support for applications getting Wakelock information. This information is hidden deep inside the Android framework. Also note that some of the additional options will only work with the In-App Premium addition.

Any issues, feature request or help should be done via email. Save the comments for just comments.

About

Unlike similar tools, Guardian is build to analyze a problems before handling it. Just because an application seams to be running rough does not mean that this is the case. For an example if you are playing a game. This game will of cause be using a lot of processing time, but that does not mean that your game is running rough. If however you quit this game and it is continuing to be using a lot of processing time, then this application is running rough. A monitoring tool should only have an interest in this rough application in the last scenario. It should not interfere in the first.

Guardian has also been build to give applications a chance to calm down themself. If Guardian detects an application that is using to much processing time, but it seams as if this application is about to calm itself down, Guardian will give the application some time to do so before interacting. In other words Guardian will only interact and report if there truly is a reason to, unlike similar tools that constantly interrupts users with false alerts.

Guardian can be configured for two states. One configuration for when the device is interactive (when you are using the device) and one configuration for when the device is not interactive (when it should be sleeping). It can also be configured to handle rough application automatically. Alerting a user is fine but there might be circumstances where you might not be able to respond to an alert and handle it manually, for an example if you are sleeping. This way you can avoid waking up to a burning device or one which battery has just been completely drained.