Unicast Client App interacting with non-nordic Headset

RE: Unicast Client App interacting with non-nordic Headset

Maria Gilje — Thu, 19 Sep 2024 11:29:50 GMT

Hi again,

I return with some information gathering points. We do not have any Momentum TW 4 available to test, so we rely on you to get the information for us.

Please make sure that your earbuds are in LE Audio mode. This mode may have to be enabled from a mobile app.
Use nRF Connect for mobile to see which services your phone finds on the earbuds. Please share a screenshot showing the sercice list.

Please include the Kconfig symbols below to enable additional logs

CONFIG_BT_BAP_UNICAST_CLIENT_LOG_LEVEL_DBG=y
CONFIG_BT_BAP_UNICAST_CLIENT_ASE_SNK_COUNT=6
CONFIG_BT_AUDIO_CODEC_CFG_MAX_DATA_SIZE=80
CONFIG_BT_AUDIO_CODEC_CAP_MAX_DATA_SIZE=120
CONFIG_BT_AUDIO_CODEC_CAP_MAX_METADATA_SIZE=120
CONFIG_MAIN_LOG_LEVEL_DBG=y
CONFIG_LOG_BUFFER_SIZE=12000
CONFIG_CODEC_CAP_COUNT_MAX=20

Increase the time from wearing the earbuds from a few seconds to 30 seconds before powering on the unicast client. A few seconds may be too short.

Best regards,

Maria

RE: Unicast Client App interacting with non-nordic Headset

Maria Gilje — Tue, 17 Sep 2024 13:01:37 GMT

Hello,

I am following up while Dejan is out of office.

Here are a few questions to try to close in where the issue originates.

Are you able to share more details about the firmware release notes as well as the firmware version for your Momentum TW 4 earbuds?

Does your earbuds use LE Audio with other (non-Nordic) Gateways?

Best regards,

Maria

RE: Unicast Client App interacting with non-nordic Headset

selim.pousse — Wed, 11 Sep 2024 13:13:32 GMT

the earbuds firmware is up to date with latest firmware. In the release notes of my actual version of firmware is clearly written that it supports LE Audio.
But still same errors and no difference in the logs.

Best Regards.

RE: Unicast Client App interacting with non-nordic Headset

dejans — Thu, 29 Aug 2024 14:21:59 GMT

Hi,

The error from the log "<err> bt_bap_unicast_client: Unable to find ASE Control Point" might indicate some problem with earbuds, such as not having the newest firmware or potentially lacking full support for LE Audio. Can you check if your earbuds have full support for LE Audio and that they are updated with the latest firmware?

Best regards,
Dejan

RE: Unicast Client App interacting with non-nordic Headset

selim.pousse — Thu, 29 Aug 2024 06:17:16 GMT

Hi,

You could also try to power on the earbuds and put into ear first (for a couple of seconds) before starting CIS gateway. Does this make any difference?

=> I doesn't make any difference. here are the logs

*** Using Zephyr OS v3.6.99-8bd088c7c293 ***
GW [00:00:00.269,012] <inf> board_version: Compatible board/HW version found: 1.0.0
GW [00:00:00.293,914] <inf> fw_info: 
         nRF5340 Audio nRF5340 Audio DK cpuapp                      
         NCS base version: 2.7.99                           
         Cmake run : Thu Aug 29 08:10:00 2024
GW [00:00:00.293,914] <inf> fw_info: ------- DEBUG BUILD -------
GW [00:00:00.293,914] <inf> fw_info: Compiled for GATEWAY device
GW [00:00:00.362,854] <inf> bt_keys: SC LTK: 0x684db1200dee505a1155c101ec74ace9
GW [00:00:00.365,142] <inf> bt_mgmt_ctlr_cfg: Controller: SoftDevice: Version 5.4 (0x0d), Revision 8751
GW [00:00:00.365,325] <inf> bt_mgmt: Local identity addr: C6:95:06:0E:89:94 (random)
GW [00:00:00.365,447] <inf> audio_usb: Ready for USB host to send/receive.
GW [00:00:00.369,384] <inf> bt_mgmt_scan: Local addr: 73:0B:BA:72:0A:3F (random). May time out. Updates not printed
GW [00:00:00.369,384] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:03.902,160] <inf> bt_mgmt_scan: Creating connection to device: 80:C3:BA:54:D2:5F (public)
GW [00:00:04.411,407] <inf> bt_mgmt: Connected: 80:C3:BA:54:D2:5F (public)
GW [00:00:04.411,437] <inf> main: Connection event. Num connections: 1
GW [00:00:04.483,581] <inf> main: Security changed
GW [00:00:04.573,577] <wrn> unicast_client: Got err: 0 from conn: 0x20006910
GW [00:00:04.575,286] <inf> bt_mgmt_scan: Local addr: 73:0B:BA:72:0A:3F (random). May time out. Updates not printed
GW [00:00:04.575,286] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:04.913,574] <inf> bt_vol_ctlr: VCS discover finished
GW [00:00:08.813,568] <err> bt_bap_unicast_client: Unable to find ASE Control Point
GW [00:00:08.813,568] <wrn> unicast_client: No sinks found
GW [00:00:08.813,690] <err> unicast_client: Failed to start unicast sink audio: -22
GW [00:00:34.463,562] <inf> bt_mgmt: Disconnected: 80:C3:BA:54:D2:5F (public), reason 0x13 
GW [00:00:34.463,623] <inf> main: Disconnection event. Num connections: 0
GW [00:00:34.465,332] <inf> bt_mgmt_scan: Local addr: 73:0B:BA:72:0A:3F (random). May time out. Updates not printed
GW [00:00:34.465,332] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:34.661,224] <inf> bt_mgmt_scan: Creating connection to device: 80:C3:BA:54:D2:5F (public)
GW [00:00:34.906,982] <inf> bt_mgmt: Connected: 80:C3:BA:54:D2:5F (public)
GW [00:00:34.907,012] <inf> main: Connection event. Num connections: 1
GW [00:00:34.978,240] <inf> main: Security changed
GW [00:00:35.058,654] <wrn> unicast_client: Got err: 0 from conn: 0x20006910
GW [00:00:35.060,058] <inf> bt_mgmt_scan: Local addr: 73:0B:BA:72:0A:3F (random). May time out. Updates not printed
GW [00:00:35.060,089] <inf> bt_mgmt_scan: Scanning successfully started
GW [00:00:35.438,751] <inf> bt_vol_ctlr: VCS discover finished
GW [00:00:39.368,225] <err> bt_bap_unicast_client: Unable to find ASE Control Point
GW [00:00:39.368,225] <wrn> unicast_client: No sinks found
GW [00:00:39.368,347] <err> unicast_client: Failed to start unicast sink audio: -22

RE: Unicast Client App interacting with non-nordic Headset

dejans — Tue, 27 Aug 2024 13:10:44 GMT

Hi,

Could you please enable the settings shown below in your prj.conf and share your log here?

CONFIG_BT_AUDIO_EP_PRINT=y
CONFIG_CODEC_CAP_COUNT_MAX=20
CONFIG_LOG_BUFFER_SIZE=12000
CONFIG_BT_ASCS_LOG_LEVEL_DBG=y

You could also try to power on the earbuds and put into ear first (for a couple of seconds) before starting CIS gateway. Does this make any difference?

Best regards,
Dejan

RE: Unicast Client App interacting with non-nordic Headset compatible Auracast

selim.pousse — Mon, 26 Aug 2024 10:41:21 GMT

Hi,
yes, I'm testing the CIS gateway mode, and the line "CONFIG_TRANSPORT_BIS=y" is already commented with #.
Best Regards.

RE: Unicast Client App interacting with non-nordic Headset compatible Auracast

dejans — Fri, 23 Aug 2024 11:53:29 GMT

Hi,

Unicast Audio client implements CIS gateway mode. Do you see the same error when you remove CONFIG_TRANSPORT_BIS=y from your configuration?

Best regards,
Dejan