Annnounce: System Monitor Plugin for OS2008
 

Hi,

This is a quick recompile of Daniele Maio & Mauro Foti's SMP plugin for Chinook from Bora. Compiling was a one line change and it seems to work fine on my N800.

Enjoy.

EDIT: I'll see if I can figure out how to add internal mmc to list too.

http://i220.photobucket.com/albums/d...reenshot04.png
http://i220.photobucket.com/albums/d...reenshot05.png
http://i220.photobucket.com/albums/d...reenshot06.png

Re: Annnounce: System Monitor Plugin for OS2008
 

1.2 never worked on my N810. Will this new recompile work on it? Thanks for the update!

Re: Annnounce: System Monitor Plugin for OS2008
 

This is 1.3 and if it works on my N800 with OS2008, it should be fine on a N810 :)

The only thing I need to figure out is how to add a new mmc thing to the list. It is only showing my external card.

Re: Annnounce: System Monitor Plugin for OS2008
 

Awesome, this trumps Khertan's homexxx applets that I'm using now!

Re: Annnounce: System Monitor Plugin for OS2008
 

Can it run commands?

Re: Annnounce: System Monitor Plugin for OS2008
 

No. I don't think it's meant for that. osso-statusbar is the only applet I've seen that can do that.

Re: Annnounce: System Monitor Plugin for OS2008
 

Installed fine and works great. Thanks!

Re: Annnounce: System Monitor Plugin for OS2008
 

Sys Stat shows CPU usage consistently above 40%, sometimes much higher, even with all apps (including the browser) closed down. All the CPU usage is attributed to maemo-launcher. Is this normal?

That other status-bar CPU meter (name? the one that includes screenshot utility) doesn't even include maemo-launcher.

Re: Annnounce: System Monitor Plugin for OS2008
 

The CPU usage might be compromised by DVFS: the system is ideally always either in clock stop or close to using all the horsepower provided by the operating point currently selected. The view should be extended to show the current cpu frequency.

Re: Annnounce: System Monitor Plugin for OS2008
 

I'd like two gauges, one for clock frequency, and one for % cycles used. I'd happily give up both disk gauges, and the proposed internal one as well, for that, but some people obviously use those, so it's getting a bit crammed.

It might be more helpful to show %cycles * frequency; thus giving a single measurement from 0 (at idle, though I'm not sure how that would actually work out) to 400 (full load at 400 MHz) of actual CPU usage.