Help systempanel monitoring draining battery and slowing down the phone?

[crackers8199]

has anyone else had issues? i bought the full version of systempanel last night, because i installed setcpu and tasker over the weekend and started overclocking - i wanted to try the monitoring service and try to see if there was a drastic effect on my battery...

well, the battery DEFINITELY seems to be draining faster than it did yesterday, and the phone seemed to be very choppy when switching between home screens. i disabled monitoring and it seems to be more responsive again.

has anyone else seen anything like this?

 

[JuicyJones]

If you're overclocked you're going to use more battery life. Also, task managers in general will hurt ur battery life. Its best to only use them for poorly developed apps, that don't go dormant or inactive after an hour or so of inactivity.

 

[crackers8199]

If you're overclocked you're going to use more battery life. Also, task managers in general will hurt ur battery life. Its best to only use them for poorly developed apps, that don't go dormant or inactive after an hour or so of inactivity.

i said in the initial post that my battery life is worse compared to yesterday, when i was already overclocking. and i said that i paid for systempanel to use the monitoring features, not for task killing.

thanks, though. anyone else?

 

[JSS12]

I have the full version and have used the monitoring function several times over the course of a few days each and have not found any issues.

As a matter of fact it has kept me on top of killing the apps that drain the most battery and as a result my battery life is better than it was - not by much but DEFINITELY NOT WORSE!

I initially thought that monitoring would drain battery but it doesn't seem to have any effect... just my thoughts... hope you rectify your issues.

 

[tliebeck]

I'm the developer of SystemPanel.

The monitoring feature will use less than one minute per day worth of processor cycles. When unplugged, it fires once about every fifteen minutes, and should complete its scan in about 1/4 second. The logging is scheduled as a non-exact repeating task, such that it will avoid waking up the phone in the event that it can run due to another process having woken the device.

It DOES NOT need to continuously record data on CPU usage. The underlying Linux OS records CPU usage by each process automatically, we're just querying that data at intervals to obtain a time-based perspective.