Ticket #1159 (accepted defect)
bluetoothd no longer started on bluetooth activation
|Reported by:||mazikeen||Owned by:||mrmoku|
|Component:||Frameworkd / FSO||Version:||SHR-unstable|
bluez4 uses a udev rule to start bluetoothd when a bluetooth device is detected. shr-full-eglibc-ipk--20100721-om-gta02.rootfs.tar.gz does not include udev, or anything else to act on these rules. As a result bluetoothd is not started when the bluetooth resource is requested, so bluetooth is unavailable to applications despite the hardware being powered.
bluez4 also uses udev rules to handle bluetooth HIDs.