View Single Post
pichlo's Avatar
Posts: 6,453 | Thanked: 20,983 times | Joined on Sep 2012 @ UK
#60
Originally Posted by AapoRantalainen View Post
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.

Last edited by pichlo; 2013-05-22 at 12:32.
 

The Following 2 Users Say Thank You to pichlo For This Useful Post: