Look ma, no tracker!
Yes, it has involved removing mediaplyer. I use symfonie and smplayer instead. If only I could persuade them to register such that they lanch automagically by tapping on the file in filebox.

Question: has anyone managed/failed removing filemanager? it seems easy but don't apps use it in their file open dialogs?

Interesting. I have also removed tracker from one of my N900s. But I didn't notice any issue with the file manager because, well, because I never use it. Long live midnight commander!

I'll see if I can remove it and see what happens. AFAIK the file-open dialog is part of the hildon framework (but perhaps provided by the file manager, I don't know).

Thanks for pushing this effort still further!

Sorry if I confused the issue. I don't have a problem with file manager. I just want to get rid of it because it comes with 20 language packages and I can't get rid of them selectively

I do have an issue with mplayer integration but that's off-topic in this thread. Stock media player launched automatically by tapping a movie file in file manager. With stock media player gone, nothing launches when I tap the file. I need to open it from mplayer.

2nd link google gave me when I searched for dbus switchboard, which I thought could help you:
http://talk.maemo.org/showthread.php?t=17757

Thanks. I was going to do a search (even though I wouldn't know the magic word was 'dbus' - I was going to go for 'integration' and/or 'association' as in that thread you've linked) as soon as I get home (at work now). I posted it at 00:48 and mentioned the missing integration just by the way, admitting it was off-topic

What exactly do packages sysinfod and wappushd do?
Nothing depends on them, at least on my phone.

Please note I ask 'exactly'. I can guess from their names what they might be doing.

I'm also interested in to hear. Seems "/usr/sbin/sysinfod --system" is running all the time as default. Relevant packages are: sysinfo-common sysinfod sysinfo-tool libsysinfo0


This is far from exact answer but: "This package contains daemon for handling WAP push messages" Which might lead to the: https://en.wikipedia.org/wiki/Wirele...tocol#WAP_Push

That sounds like I can live without wappushd. Well, I removed them both, leaving the other packages with sysninfo in the name untouched. Now, I am not sure if this is related or not, but I've lost Bluetooth. Reboot or even power off with battery out does not solve it. Which doesn't bother me that much except that FMTX went with it. Currently on the hunt for the cause and the cure.

There are one more closed source package with sysinfo on it's name: http://wiki.maemo.org/Fremantle_clos...etooth-sysinfo Do you still have it installed?

I have four "sysinfo" packages installed: bluetooth-sysinfo, libsysinfo0, sysinfo-common and sysinfo-tool.

There is bluetooth-sysinfo script in /etc/event.d that is triggered by bluetoothd and testserver. I removed testserver months ago and bluetoothd is running. I've tried following all scripts in event.d and init.d that look relevant to bluetooth and fmtx but I have to multitask with the job I actually get paid for so the progress is a bit slow.

Edit:
Reading the bluetooth-sysinfo script, it calls sysinfo-tool -g /certs/npc/esn/bt_id to get the BT address and then dumps it to /sys/devices/platform/hci_h4p/bdaddr (typing this by hand, no ssh at the moment). When I call sysinfo-tool -g /certs/npc/esn/bt_id in xterm I get, "The name com.nokia.SystemInfo was not provided by any .service files (2)".

Edit2:
/sys/devices/platform/hci_h4p/driver and /sys/bus/platform/drivers/hci_h4p circularly link to each other. As do other components under /sys/devices/platform and /sys/bus/platform/drivers. It it supposed to be like that? I wonder if that might be the effect of flashing.