[maemo-users] Dealing with N900 responsiveness (or lack of thereof)

[From: Eero Tamminen]

Hi,

ext Dawid Lorenz wrote:
> I've had a look at top over ssh connection and seen
> /usr/bin/pulseaudio --system --high-priority constantly
> floating around 1-3% of CPU time. Needless to say, device
> was lying on the desk next to me, doing nothing, not to
> mention anything media-related. I did killall media-player
> but that didn't help and pulseaudio was still working out.
> 
> However I've been listening to music earlier in the morning,
> took couple of calls etx.

Does "killall tonegend" help?

Then it's probably this:
	https://bugs.maemo.org/show_bug.cgi?id=6868


> Then later in the day I've opened
> a camera to take a picture, which threw weird "Another
> application is using audio" message at me few times (while
> no app that I was aware of was running in the background).

To list pulseaudio clients, use "pactl list".


ext Jan Knutar wrote:
 > I guess not even closed NEP was possible as we've heard nothing
 > of it since ;-)

It's a possibility still.  Let's see.

In the meanwhile, there seems to be a 3rd party app that provides
at least some (less accurate & fine-grained) information, see:
	http://talk.maemo.org/showthread.php?t=43748


ext Jan Knutar wrote:
 > On Tuesday 23 February 2010, Dawid Lorenz wrote:
 >> I just get readings from tools like htop or conky.
 >
 > If htop just uses the MemFree field from /proc/meminfo, then it's
 > pretty much supposed to hover at over 90% used all the time. Unused
 > RAM is wasted RAM. What matters is if the system is able to free up
 > RAM when it's needed without excessive I/O traffic slowing things
 > down..

This has some useful tools & scripts for counting memory usage:
   http://wiki.maemo.org/Documentation/devtools/maemo5/sp-memusage

(With some updates hopefully coming to them in next SDK tools update.)


But for tracking _changes_ in _all_ device resources, I recommend this:
   http://wiki.maemo.org/Documentation/devtools/maemo5/sp-endurance


	- Eero