Ticket #1159 (accepted defect)

Opened 3 years ago

Last modified 18 months ago

bluetoothd no longer started on bluetooth activation

Reported by: mazikeen Owned by: mrmoku
Priority: major Milestone:
Component: Frameworkd / FSO Version: SHR-unstable
Keywords: bluetooth Cc:

Description

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.

Change History

comment:1 Changed 3 years ago by mrmoku

  • Keywords bluetooth added
  • Owner changed from ainulindale to mrmoku
  • Status changed from new to accepted
  • Component changed from SHR Image to Frameworkd / FSO
  • Milestone set to MS1

I talked with mickey about that... He will integrate starting of bluetoothd to fsodeviced when the Bluetooth resource is requested.

comment:2 Changed 18 months ago by morphis

  • Milestone MS1 deleted

Milestone MS1 deleted

Note: See TracTickets for help on using tickets.