After the latest Samsung firmware update, my Galaxy only discovers 24 kHz Auracast broadcasts. The 48 kHz broadcasts that used to appear no longer show up, even though other receivers still see/join them. Bug, policy change, or setting I’m missing?
Questions for the group
Can anyone confirm on their Samsung (model + One UI/firmware + region/carrier) whether 48 kHz Auracast still shows up?
Is there a setting (e.g., power/compatibility mode) that forces discovery to 24 kHz only?
Did Samsung change the scan filter or codec policy in the latest BT stack? Any developer notes or changelogs?
Any workarounds besides switching transmitters to 24 kHz?
Why I ask
We support both 24 kHz and 48 kHz in deployments; losing 48 kHz discovery on Samsung affects venues that prefer higher bandwidth streams.
A Public Auracast™ transmitter must transmit at least one BIS with a Codec_Specifc_Configuration that represents one of the 16_2_1, 16_2_2, 24_2_1 or 24_2_2 configurations from Table 6.4 of BAP.
Where 16_2_1 / 16_2_2 use 16kHz sampling frequency and 24_2_1 / 24_2_2 use 24kHz sampling frequency.
Also, section 1.2.1.2 High Quality Public Broadcast Audio:
High Quality Public Broadcast Audio streams are broadcast streams which are transmitted using the LC3 codec configurations that are defined in Table 4.2 of PBP. Support for these is not mandated in BAP or PBP, so some Auracast™ receivers will not be able to receive and render these streams. They are included to accommodate devices which wish to use the highest 48kHz sampling rate supported by the LC3 codec. These configurations use 48kHz sampling frequencies with 10ms frames, supporting both low-latency and high-reliability use cases. Within Auracast™ documents, they are referred to as HQ streams.