nrf connect mobile app LE Audio

[RakeLund]

I have been using the nrf connect mobile app (on android) to assist in debugging and testing of BLE applications before. Now I am working on a peripheral that has some custom services and also can operate as a broadcast sink. I was successfully able to connect and discover services and write and read from the characteristics when the peripheral was just advertising as a peripheral and then scanning for and syncing to a broadcast stream. But when I add the necessary configs for BAP (CONFIG_BT_BAP_BROADCAST_SINK and it's dependencies) the mobile app is stuck in discovering the services and characteristics.

I am still able to discover and write to the peripheral with a modified version of the nrf5340 audio gateway application, so I am wondering what might be missing to make it work with the mobile app? Should it be possible, or is there some missing support here?  I have tested with a phone with Android 14 which supposedly has support for LE Audio. (Google Pixel 7 pro)

To be clear I am not expecting to actually test and debug LE Audio with the mobile app, I just want to be able to interact with my custom services.

[Amanda Hsieh]

Hi, 

What NCS version are you using? 

Could you try to enable CONFIG_BT_BAP_BROADCAST_SINK_LOG_LEVEL_DBG and provide the log?

Regards,
Amanda H.

[RakeLund]

I'm using NCS v2.6.0
Log from my application:

[DEBUG] (WEST_TOPDIR/application/src/bluetooth/bt_mgmt.cpp:211) Initializing Bluetooth

[DEBUG] (WEST_TOPDIR/application/src/bluetooth/bt_mgmt.cpp:139) Bluetooth initialized

[INFO] (WEST_TOPDIR/application/src/bluetooth/bt_mgmt.cpp:160) Local identity addr: D5:85:EA:BF:B2:34 (random)
[INFO] (WEST_TOPDIR/application/src/le_audio_rx.cpp:76) LE Audio initialized

[DEBUG] (WEST_TOPDIR/application/src/bluetooth/broadcast_sink.cpp:469) Broadcast sink initialized
[INFO] (WEST_TOPDIR/application/src/bluetooth/bt_mgmt.cpp:112) Connection established!
Connected to: 4E:AC:F7:05:F9:E9 (random)
Role: 1
Connection interval: 36
Slave latency: 0
Connection supervisory timeout: 500

[INFO] (WEST_TOPDIR/application/src/bluetooth/bt_mgmt.cpp:90) Connection parameters updated (interval: 36, latency: 0, timeout: 42)

The config didn't give any extra log messages.

nrf Connect mobile app when auto discover is on:

Auto discover off, not able to read characteristics:

I also have tested with this sample https://github.com/rick1082/sdk-nrf/tree/nus_on_bis_headset/applications/nrf5340_audio which sets up a NUS server on the headset (just modified to use v2.6.0 instead of 2.3.0) and it has the same behaviour. Log:

*** Booting nRF Connect SDK v3.5.99-ncs1 ***
HL [00:00:00.270,935] <inf> board_version: Compatible board/HW version found: 1.0.0
HL [00:00:00.323,364] <inf> fw_info:
nRF5340 Audio nRF5340 Audio DK cpuapp
NCS base version: 2.6.0
Cmake run : Tue May 07 10:05:35 2024
HL [00:00:00.323,394] <inf> fw_info: ------- DEBUG BUILD -------
HL [00:00:00.323,394] <inf> fw_info: HEADSET left device
HL [00:00:00.336,090] <inf> bt_mgmt_ctlr_cfg: Controller: SoftDevice: Version 5.4 (0x0d), Revision 8591
HL [00:00:00.336,303] <inf> bt_mgmt: Local identity addr: C7:B4:5C:E6:56:29 (random)
HL [00:00:00.337,860] <inf> main: Created adv: 0x20003348
HL [00:00:00.338,867] <inf> main: Advertiser 0x20003348 set started
HL [00:00:00.340,087] <inf> bt_mgmt_scan: Local addr: C7:B4:5C:E6:56:29 (random). May time out. Updates not printed
HL [00:00:00.340,087] <inf> bt_mgmt_scan: Scanning successfully started
HL [00:00:12.896,453] <inf> bt_mgmt: Connected: 4A:5A:1E:C9:C8:18 (random)
HL [00:00:12.896,484] <wrn> main: Unexpected/unhandled bt_mgmt event: 2
HL [00:00:12.896,484] <inf> main: Connected
HL [00:00:18.238,464] <wrn> main: Connection parameter updated
HL [00:00:18.238,464] <wrn> main: CI = 0x24, latency = 0, timeout = 42

[Amanda Hsieh]

Thanks for the information. We are checking with the app team. I will be back when I collect enough information. 

[Amanda Hsieh]

Hi, 

The new version v4.28.1 should fix this issue. Our APP expert pushed the latest version to the Play Store which will be available soon. 

-Amanda H.

[RakeLund]

Cool, thank you! I will test as soon as I receive the update :)