I don’t know, but I’ll take a stab at it. Through the scanner in the receiver, the phone could likely detect Auracast broadcasts and I would think be able to choose one. However, BT sound between phone and hearing aids would have to be BT Classic. So, from Auracast source to Auracast hearing aids or earbuds would be LE Audio, but streaming from phone would not.
@MDB @d_Wooluf Basically, if I have a smartphone that is Auracast capable, then technically I could get the Auracast stream straight to my Marvel HA via my smartphone!!!, Once the link is established between my HA and the Auracast stream, potentially, I will not need my smartphone!
(That’s my understanding watching numerous youtube videos and reading few articles and comments)
Is that correct?
@d_Wooluf Post is about a legacy smartphone and Auracast capable receiver (earbud, HA,…), so not exactly the same as my post above. 
My only quibble would be using the words “via the smartphone” To best of my knowledge, the smartphone is just choosing the broadcast and has no other role in the transmission.
1 Like
I think that refers to streaming from the phone, not an Auracast source.
1 Like
The gist of it is that if you have a ‘legacy’ phone, the phone and receiver can still co-ordinate. The difference is that the scanning is done by the receiver. The receiver sends the results of the scan to an app on the phone, the app presents the list of broadcasts to the user, and tells the receiver which broadcast has been selected. The receiver takes the broadcast. The downside is that there is a hit on battery life for the receiver. The upside is that almost any phone is a potential Auracast Assistant.
5 Likes
@Baltazard. No, you’d need Auracast capability in the hearing aids. This is a prospective solution for those with this capability but who don’t want to upgrade their phones. They’ll be able to use their phones to assist their aids in receiving broadcasts from Auracast transmitters. They won’t be able to use their phones to stream to their aids.
3 Likes
I concur this but i do think this is an optional implementation though
Looks like we’re not the only ones frustrated. Here’s a Reddit thread.
This seems to be the gist of it:
I’ve read from a Japanese site that had a search for LE Audio support on different OS. The conclusion is, although new network chips for Windows is claiming they all have LE Audio feature, there’s no commercially available device that has proper audio driver on Windows to actually use it, including Intel, Mediatek and Realtek and Qualcomm.
Here’s a link to the entire thread:https://www.reddit.com/r/Windows11/comments/1atdur2/is_there_anyone_got_bluetooth_le_audio_working/
2 Likes
Trying to get more informed on this. Are these the potential benefits of an LE Audio standard:
-
Bluetooth hearing aid standard where, for every hearing aid that implements it, ability to connect to any bluetooth LE Audio device, but not legacy Bluetooth devices. (Thinking phones, tablets, Laptops, generic LE Audio transmitters)
-
Transmission to multiple hearing aids from bluetooth transmitters and tv transmitters (thinking households with multiple hearing aid wearers)
-
Broadcast of LE Audio (thinking commercial setting like group broadcast in a movie theater)
1 Like
All valid I think. For ‘hearing aid’ you can substitute ‘any LE Audio-equipped audio sink’. That widens the market by a huge amount, leading (we’ve been hoping for years) to a faster and wider takeup. There’s also audio sharing.
You can also include the lower-level technical advantages- low latency, low power consumption, robust connection, multiple synchronised but independent streams.
2 Likes
Updated my Samsung S23 to the latest updates which has OneUI 6.1, and now the phone supports audiocast
10 Likes
I just updated my S23 to OneUI 6.1 also. NRF Connect says it now supports LE Audio Broadcast Source which is new. I still don’t see any indication LC3 Codec is supported. It’s not even a greyed out option.
4 Likes
Took a look in my Pixel 7a.
In the Developer under codec there are about 8 choices to select. My phone is in auto but there is a selection for LC3. It and the others are not greyed out which means they are available.
Need to correct something here.
The code selections are greyed out.
Sorry for the confusion.
2 Likes
That’s where I’m looking in my phone too, but LC3 Codec is not there.
1 Like
Try this
3 Likes
If this is directed at me, it’s not my issue. I don’t have any devices (headphones or HA) that are LC3 compatible. Still, it is my understanding that LC3 Codec ought to show up in Developer options as greyed out. It does not show up at all.
That’s funny, in my Pixel 7a all the options except Use System Selection are grayed out.