Page History

...

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 User 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).

...

If you are initiating the connection from the tablet, you must first start an agent.  The agent allows accepting of connections from remote devices.  You can do this using option 31. After invoking option 31, connect to the settop from your tablet.

...

Optionally, before attempting to connect, you can run option 34 to install an authentication callback.  This allows the settop to accept or refuse the connection from the tablet. If you run option 34, then attempt a first time connection from a tablet, you will be prompted to enter option 32 to accept, or 33 to deny the request.

...

The current btrMgrStreamOutCoreTest is shown below:having following option in RDK

• 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
• 24. Send WAV to BT Headset/Speakers - btrMgrStreamOutTest
• 25. Send Live Audio to BT Headset/Speakers
• 26. Send audio data from device to settop with BT
• 88. debug test
• 99. Exit

Once you connect bluetooth connected with your tablet, start the player on your tablet, then do option 21 (this gets needed parameters for playback.  Note, this functionality is automatically invoked in the btrCore utility, but has not, as of this time, been implemented in the btrMgr utility). 

...