[APP 2.1+] System Tuner

[3c]

How it impact battery life?

@ you and @ Dev

How does this affect batterylife?

Hello,

I'd rather let users answer this question, but here are few points about what I found-out so far:

Widget consumption
- During screen-off widget is sleeping too and uses no CPU at all.
- Rest of the time, one widget takes an average of 20ms CPU to update (on HTC HD2)

So everything will depend on how often you set the widget to refresh!


Recorder consumption
On the other hand, using the recorder (which I often do) uses around 10ms for each sample, the default rate being every minute, it results in a 0.12% CPU usage

Tested in plane mode, screen-off, CPU at ~245MHz! Measured mA consumed was always at 2mA. Will put screen-shots of that later.

Recording rate can be lowered to 5 minutes (for example) which will consume 5 times less and will still bring accurate CPU usage readings.

I'm trying to measure the total % consumed on a 6 hours span, with and without recorder in plane mode to have everything else even, otherwise I can't see much of a difference... Will report findings soon.

Task Manager consumption
This is the most power angry component, as it reads much more data. It's set to refresh every 10 seconds by default (I personally use a 5 seconds refresh rate).
Each run consumes between 70 and 250ms depending on amount of apps running and what's being displayed (all or non-excluded apps only).

I just did some comparison with System Panel, running the UI looking at apps list without touching anything:
CPU load was at 3-10% while running PMW
and 3-15% while running System Panel
note that system panel refreshes CPU more often so it "seemed" at first to consume less. Both apps were showing all 27 apps running at the time.

I hope some users will report their findings too It will be less biaised

 

[3c]

Analyzing both battery and cpu together

Any thoughts about combining your battery monitor widget functions and tying the battery consumption to the process? Maybe I'm over(under)thinking it, but being able to see graphically process history vs battery consumption per process would be very helpful to narrowing down inefficient apps.

Cheers

Yes, I've been looking into this, but haven't found an elegant solution that does not consume anything... but now that you ask... just got some ideas

Though to have a clear picture it actually requires measuring or estimating how much various components are consuming (screen, wifi, gps, bluetooth, etc...).
Or knowing how much the CPU is actually consuming based on load and frequency. But each CPU is different...

 

[DirkStorck]

I have installed the free version but I don't see any widgets in my widget list. Besides that it looks like a great app to find out which apps are using most cpu

 

[Vinsane]

Very nice app.

The only issue I have is all.the info inside the widget is "crushed" together.

It looks like it could use some more room to be able to see all the info clearer.

I tried it set as the following:

cpu freq
Icon
Process

I cant even see the process info on the bottom.

Can you make it to where there is an option for only 2 info spots instead of 3? Thst way...it doesn't use as much space inside the widget.

Keep up the great work!

Sent from my HTC Glacier using XDA App

 

[britoso]

Whoa, very nice!

 

[3c]

I have installed the free version but I don't see any widgets in my widget list. Besides that it looks like a great app to find out which apps are using most cpu

Thanks for posting the issue here so I have an opportunity to help/reply.

That's quite odd and might be related to installation... Do you have an app that forces install on SD card by any chance?

Or do you use app2ext or app2sd+ and removed the SD card at some point?

Android up-to 2.2.1 (not sure about 2.3 yet) have issues moving widget app to SD card, such widgets will completely vanish until the home screen is restarted, which often mean reboot, but then depending on the boot sequence it will not appear again.

Maybe that's what's going on here?

 

[DirkStorck]

Thanks for posting the issue here so I have an opportunity to help/reply after seeing comment on Android market

That's quite odd and might be related to installation... Do you have an app that forces install on SD card by any chance?

Or do you use app2ext or app2sd+ and removed the SD card at some point?

Android up-to 2.2.1 (not sure about 2.3 yet) have issues moving widget app to SD card, such widgets will completely vanish until the home screen is restarted, which often mean reboot, but then depending on the boot sequence it will not appear again.

Maybe that's what's going on here?

Hi I am using LeeDroid 2.3d with normal app2sd and I dont use an app to force install location.

I have deinstalled and installed it again....and tada....the widget is here

 

[imakul8]

I've replaced System Panel with this. It's just easier for me to understand and SP seem to use alot of power itself. One question about the auto-kill feature when display turns off...How can I be sure that it's killing tasks. Every time I quickly enter into the PWM(with the screen having been off) to see if apps are restarting, they seem to have never stopped. I can't imagine all would be up and running so fast. I understand that some apps will restart themselves.

 

[3c]

I've replaced System Panel with this. It's just easier for me to understand and SP seem to use alot of power itself. One question about the auto-kill feature when display turns off...How can I be sure that it's killing tasks. Every time I quickly enter into the PWM(with the screen having been off) to see if apps are restarting, they seem to have never stopped. I can't imagine all would be up and running so fast. I understand that some apps will restart themselves.

Well, actually the auto-kill is done when widget is refreshed, thus only when screen is on! I'm working on a new auto-kill that will be scheduled independently for the next update.

Stay tuned

I was very reluctant to implement such feature as it will consume just to kill unwanted processes, which will be restarted sooner or later.

But it's requested many times so it will be in next update!

 

[imakul8]

Well, actually the auto-kill is done when widget is refreshed, thus only when screen is on! I'm working on a new auto-kill that will be scheduled independently for the next update.

Stay tuned

I was very reluctant to implement such feature as it will consume just to kill unwanted processes, which will be restarted sooner or later.

But it's requested many times so it will be in next update!

Yeah, I know some will restart, but it will still kill the one's that don't restart. I only want it to kill once when the screen goes off, not over-and-over at intervals while the screen is off. That way, it won't have to keep consuming energy to kill restarted apps. I won't use the auto-kill during refresh. I would just use kill all whenever I need it. Anyway, look forward to the improvements.

 

[schnowdapowda]

Just wanted to say.. great job with this. Exactly what I've been looking for.

cd's or tapes?

 

[zeppelinrox]

@ you and @ Dev

How does this affect batterylife?

Well, I'm too lazy to quantify it, but I'm having a look with Super Task Manager and the Dialer, news and weather (genie) widget and android keyboard (which are all doing nothing lol) are using more juice than process monitor widget - which I have set to refresh every 30 seconds...

Battery monitor widget uses a bit less than process monitor widget but what's interesting is that Battery Diviner, which I recently installed, uses up more juice than either of them.

So I'd say it's a pretty small footprint, especially when you consider all the data that it's watching...

Did you ever click the Logs button? It's crazy... cool I mean

Hey I just noticed today that it has a built in terminal...

 

[zman519]

HI ccounotte

I really like this app its some thing android really needed. I do have one small thing to ask.

When you tap on one of the Bar grapfs Memory, Internal and go into the part that shows you the pie chart the "Memory" (RAM) and the "internal" have identical texts/wording So theirs noway of telling what data your really viewing.

Could you add "RAM" like this "CHIP_icon Memory RAM Details" that way its ez to see what you viewing. And or Maybe ad it to the line right above it "Process Monitor - Memory-RAM"

Just an idea i think that will help a lot of people To me if i have the pie chart open and look back at it quickly i find myself adding the two numbers in the bar graph to see if the sum = the ram in my phone or the internal flash.

 

[3c]

I really like this app its some thing android really needed. I do have one small thing to ask.

Could you add "RAM" like this "CHIP_icon Memory RAM Details" that way its ez to see what you viewing. And or Maybe ad it to the line right above it "Process Monitor - Memory-RAM"

Thanks for being supportive

EDIT: Please note that currently both screens are actually displaying 'live' memory, not internal memory usage. This last one requires root access, but the screen will be available in a future release, showing which app is using what.

For now I'm working on various improvements: new CPU % sorting, CPU settings (governor+frequencies), better auto-kill options.

The internal memory screen will come after those.

 

[MKairys]

This is fun!

I was curious about the relative cost of running Process Monitor's GUI. All the dynamically sorting process lists I have seen require a good chunk of the CPU themselves just for the GUI. I'm also curious about comparisons with SystemPanel, which I have used for a long time. Here's what I did:

10-minute interval with PM open and display on, SP in background (CPU%)

PM 1.7
SP 24.0

10-minute interval with SP open and display on, PM in background (CPU%)

PM 18.0
SP 0.5

12-hour interval, overnight display off

PM 4.0
SP 1.6

So I would say PM's GUI is much more efficient (the SP list can't even be sorted dynamically) but SP is more efficient at collecting data in the background.

SP also has a more polished interface to historical data, with a time range selector for the graphs, but it doesn't have the "start/stop recorder" feature which is so valuable when wanting to test a particular condition. I think that's a fair tradeoff for maybe a little more CPU when collecting.

And since the raw data is readily available, how about reports? Spreadsheet generation? Cross-sample comparisons?

The other enhancement I would like to see is a scheduler service to run samples at repeated intervals, and give them names. This could be the best system app ever!

 

[3c]

So I would say PM's GUI is much more efficient (the SP list can't even be sorted dynamically) but SP is more efficient at collecting data in the background.

Well, it's time I look into saving more CPU collecting data in the background
By the way, did you also record the CPU frequency in your tests?

SP also has a more polished interface to historical data, with a time range selector for the graphs,

And since the raw data is readily available, how about reports? Spreadsheet generation? Cross-sample comparisons?

The other enhancement I would like to see is a scheduler service to run samples at repeated intervals, and give them names. This could be the best system app ever!

That makes a few features/improvements to work on for future updates thanks a lot for the tips!

Did you use the 2-finger zoom on the graphs and then long-press to actually crop the data to what's visible?

 

[zeppelinrox]

10-minute interval with PM open and display on, SP in background (CPU%)

PM 1.7
SP 24.0

10-minute interval with SP open and display on, PM in background (CPU%)

PM 18.0
SP 0.5

12-hour interval, overnight display off

PM 4.0
SP 1.6

Were they both monitoring at the same rate in these tests... say 1 minute apart for example?
Also, that 18% doesn't look right at all... PM has a very small footprint.
PM is at 18% cpu for 10 minutes but down to 4% for 12 hours... it does not compute...

Anyway, it's probably just me but SP makes my eyes bleed lol

 

[3c]

Were they both monitoring at the same rate in these tests... say 1 minute apart for example?
Also, that 18% doesn't look right at all... PM has a very small footprint.
PM is at 18% cpu for 10 minutes but down to 4% for 12 hours... it does not compute...

Anyway, it's probably just me but SP makes my eyes bleed lol

I took a recording the other day, and it showed PM was using less than 0.65% of CPU with a CPU frequency stuck at 245MHz (46.37% of 1.39%)! Will be lower with higher frequencies!

Attached is a screen-shot of the recording. You can see it uses less than 0.6 seconds of CPU in each sample taken every 60 seconds

With default frequency of 998MHz it was less then 0.2 seconds every minute.

EDIT: Tested cpu usage while using the UI (with the upcoming version) and it's more around 6% than 18% indeed while refreshing every 3 seconds! Added screenshot of the UI. But surely % depends on the CPU so I should test again System Panel, unfortunately SP doesn't show CPU% on the main screen, and doesn't allow changing refresh rates (seems every 10 seconds?).

 

[3c]

That would be nice....

Any thoughts about combining your battery monitor widget functions and tying the battery consumption to the process? Maybe I'm over(under)thinking it, but being able to see graphically process history vs battery consumption per process would be very helpful to narrowing down inefficient apps.

Cheers

Very nice app.

Can you make it to where there is an option for only 2 info spots instead of 3? Thst way...it doesn't use as much space inside the widget.

Keep up the great work!

Sent from my HTC Glacier using XDA App

Thanks,

Added the following to the TODO list:
- 'no icon' option.
- load BMW logs and display mA graphs along CPU consumption in analyzer

I only want it to kill once when the screen goes off, not over-and-over at intervals while the screen is off.
Anyway, look forward to the improvements.

New auto-kill options have been added in the last update, replacing old settings (NB: old auto-kill settings are lost during update).

 

[Testingchip]

Cool little app. Also replaced system panel with this. Very functional and ready to set up. Thank you.

Sent from my ADR6300 using Tapatalk