After the latest Samsung firmware update, my Galaxy only discovers 24 kHz 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 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.
You’re ignoring this member’s posts.