Provides an interface to port any Bluetooth application on RDK. Bluetooth Manager (An RDK component) interfaces with BlueZ through the D-Bus API, so there is no direct linking of the BlueZ library with Bluetooth Manager.

In RDK, Bluetooth is comprised of a Core module (BTCore) and a Manager module (BTMgr).  The BTCore module controls basic Bluetooth functionality such as scanning, pairing, and connecting.  The BTMgr module uses the services of the BTCore module for performing audio streaming.  RDK has two utilities for testing.  A btrCoreTest utility tests the BTCore functions.  A btrMgrStreamOutCoreTest utility tests BTMgr functions.  Both utilities share some common functionality.  For example, it is possible to perform a device scan using either utility.

Bluez

In its current implementation, the RDK Bluetooth uses the Bluez stack.  It is possible that another stack (e.g. Broadcom’s BSA) could be used in the future. 

DBUS

The Bluez stack uses DBus to facilitate communication between the user application and the kernel level Bluetooth functions.

gStreamer

BTMgr utilizes gStreamer to process incoming Bluetooth data

Basic Bluetooth Architecture in RDK 

Connecting to a device

In order to connect, the device must first be discovered.  The source device (e.g. tablet or phone) can be put into a discoverable mode.

This can be accomplished with the btrCoreTest utility.  The current options are shown below:

1. Get Current Adapter

2. Scan

3. Show found devices

4. Pair

5. UnPair/Forget a device

6. Show known devices

7. Connect to Headset/Speakers

8. Disconnect to Headset/Speakers

9. Connect as Headset/Speakerst

10. Disconnect as Headset/Speakerst

11. Show all Bluetooth Adapters

12. Enable Bluetooth Adapter

13. Disable Bluetooth Adapter

14. Set Discoverable Timeout

15. Set Discoverable

16. Set friendly name

17. Check for audio sink capability

18. Check for existance of a service

19. Find service details

20. Check if Device Paired

21. Get Connected Dev Data path

22. Release Connected Dev Data path

23. Send SBC data to BT Headset/Speakers

29. BT audio input test

30. install agent for accepting connections NoInputNoOutput

31. install agent for accepting connections DisplayYesNo

32. Accept a connection request

33. Deny a connection request

34. Register connection callback to allow accepting or rejection of connections.

35. Uninstall agent - allows device-initiated pairing

88. debug test

99. Exit

You can use option 2 to start a device scan.  The scan takes about 10 seconds to complete.

You can then use option 3 to see the list of devices that the settop found.  If your device is in the list, you can use option 4 to perform a pairing.  In some cases, you may have to confirm the pairing on the tablet/phone.

Once the device is paired, the next step is to establish an audio connection between the settop and your source device (e.g. tablet).