nRF5340 stopped scanning after few minutes after Samsung S23 start to broadcast the audio

[JimmyOu]

Hi,

I encountered a stop scanning issue when running the nrf5340_audio application without any configuration changes.

The only modification I made was changing the log level from debug to warnings in Zephyr to observe the issue.

Code: Zephyr Bluetooth Scan Code.

Details:

1. I disabled the Samsung S23 broadcast audio for the first 6 minutes.
2. Then, I enabled the Samsung S23 broadcast audio.
3. After enabling, I observed that no more logs appeared after:
   [2025-02-01 17:36:00] HL [00:12:57.390,686] <wrn> bt_scan: B0:B2:1C:94:8E:52 (public) event 0, len 28, rssi -100 dBm

I checked the WDT_CTLR is enabled in the project. So I guess the controller is still alive.

I also tested with one ADK as the broadcast source and one ADK as the broadcast sink. However, I could not reproduce the same situation in this case.

Question:

I have no idea what's happening in this situation. Is there any way to resolve or avoid this stuck issue?

Attachments:

• Logs from ADK for reference. scan_issue.log

Environment:

• Broadcast source: Samsung S23
• Broadcast sink:
  • Board: nRF5340 Audio DK
  • SDK: nRF Connect SDK v2.9.0
  • Application: nrf/applications/nrf5340_audio (without modifications)

Let me know if any additional information is needed.

Best regards,
Jimmy

[Amanda Hsieh]

Hi, 

We are using S24 for testing, but cannot see any issue when enabling/disabling the broadcaster from S24. The broadcast sink can always sync again.

I would assume the log added by you might trigger the race condition. It's better not to modify the host code.

Regards, 
Amanda H.

[JimmyOu]

Hi Amanda,

Thanks for your suggestion.

I initially encountered this situation without making any changes.

I added that for debugging because I noticed that the device does not connect to other broadcasts.

Additionally, if I only use the nRF5340 Audio DK as the broadcaster, I can see the logs printing continuously for around 12 hours.

Best Regards,

Jimmy

[Amanda Hsieh]

We cannot reproduce the issue with S24. 

[JimmyOu]

Hi Amanda, got it.

Thanks for your feedback.

I will try that with S24.

Thanks again for your help.

[JimmyOu]

Hi Amanda,

I have tested with the S24+ and did not observe the issue; however, when I tested with the S23, I encountered the stuck condition.

Based on my understanding, the scanning process on the nRF5340 should not become stuck, as the S23 is only performing advertising.

Would it be possible for you to reproduce this issue with the S23 on your side? Or, if there is any additional information I can provide to help diagnose the situation further, please let me know.

Thank you very much for your assistance.

Best regards,
Jimmy

[Amanda Hsieh]

The issue seems on Samsung. Unfortunately, we don't have S23 to test. 

Maybe you can analyze their advertising package to find the differences.