Not able to connect nRF5340 LE Audio to Android

[Paveletu]

Hi support team! I hope you're well.

I'm trying to connect nRF5340 Audio DK (gateway) to my Pixel 6a. The problem is there's no `NRF5340_AUDIO` detected via Bluetooth when I flash the sample in CIS mode and in BIS mode it's detected but cannot be connect (please find a screenshot from nRF Connect application attached).

Is there any way to make nRF5340 connectable to a phone?

Also, does my phone require to have a "LE Audio" supported chipset (like the once listed here: www.qualcomm.com/.../bluetooth-le-audio) on it to even be connected? Will Bluetooth 5.2 and OS support (Android 13 has support for LE Audio profile) not be enough?

As a side note my question is very similar to this one: https://devzone.nordicsemi.com/f/nordic-q-a/91856/nrf5340-audio-dk-connection-to-phone

Many thanks,
Warm Regards,
Pavel

[dejans]

Hi Pavel,

Can you check if the same happens with NCS v2.1.0-rc2 and with current main?

Best regards,
Dejan

[Paveletu]

Hi Dejan, thank you for your prompt response,

I've just built the app (both, old version with SBC codec and a new version from v2.1.0 samples) using NCS v2.1.0 and the behaviour is still the same. I've built the sample for both, app and net cores, using command: python3 buildprog.py -c both -b debug -d gateway -p

I can see programmed status is done in configuration table overview and the board lights up green. Is there some sort of a protection in nRF5340 Audio which prohibits any device other than nRF5340 being connected? And why the device is not visible at all in CIS mode?

Actually I've just discovered that there's no support for LE Audio in Pixel 6a according to nRF Connect app. I assume that would be the reason, right? I'd still think there should be Advertising being sent in CIS mode if I'm not mistaken.

Many thanks, 
Warm Regards,
Pavel
     

[OVJA]

Hi Pavel, Dejan,

I can confirm that i am seeing the same as this issue. when the gate way is programmed to NCS v2.1.0-rc2 using the python build script, The gateway is not visible, however I assume this is because it is scanning for the headset and not advertising.

I have also tried the headset, and this is visible, and I can see all the services with the latest Build. but as soon as I pair via the android OS everything disappears and the device is not able to be connected on the phone again until it is reprogrammed and cannot be used as a headset.

I have the same issue in the NRF app suggesting I don’t have LE Audio capabilities, Mobile is a Oneplus 10 Pro processor:  Snapdragon 8 Gen 1 – which has a Bluetooth 5.3 stack and Android 13 which is LE audio compatible to my knowledge.

Regards

Jack

[dejans]

Hi,

This might be related to the fact that your phone does not support LE Audio.

Best regards,
Dejan

[dejans]

Hi,

Could you please check the behavior with NCS v2.1.0?

Best regards,
Dejan