Skip to content
HearingTracker
Log in

Compatible 3rd party LE Audio and Auracast devices - a technical deep dive

134 replies16.8k viewsLast reply

Jump
Link to this topic
Reply
Edited
@user490 said:

Each of the potential LE audio transmitters will need a different app just to connect?

No, to run , you either need an assistant built into the phone which should allow you to find any broadcast that is available to listen too, or you will need an assistant built in to an app for that particular device which should bypass the phone and allow an Auracast broadcast to go directly to the device.

For example, let’s say you have Resound hearing aids and are using the assistant in their app. You can find any broadcast to listen too, but you can only listen wearing your Resound hearing aids.

However, the Resound app assistant will not allow you to listen to an Auracast wearing a pair of Google Pixel ear buds. To do that, you will either need a built in assistant in your phone, or a dedicated Google app with an assistant built in.

@user490 said:

Aside from potential hassle are there privacy issues?

You can make your broadcast public or require a code to be entered to listen to your Auracast broadcast.

Edited

Well then don’t use it. Any software can be compromised, just through user error. I’m sure someone will find a bug somewhere.

If one is worried about security, then don’t use an old phone that hasn’t been updated with latest security update.

In reply to @user490

What we have seen so far is that, manufacturers have implemented some kind of security to prevent connections from untrusted Broadcast Assistant BA. The most popular mechanism is to allow only BAs residing on the same mobile device it has already been bonded or paired with.

In reply to @dant220

Not really. At chipset level, vendors have done their job well in terms of compatibility, thanks to SIG’s coordination. For example, Qualcomm based products should be able to connect to Nordic’s TV streamer or transmitters running on MTK/Airoha without an issue. The current problem is mainly from product manufacturers on how they do their implementation, or configure their product firmware, or how they develop/upgrade their apps. However, I believe, as time goes by, compatibility problem will go away.

Well, if Apple had built in BA function into iOS as many was expecting, such problem would never exist anyway. As if iPhone 3G became the common benchmark device in 2008 and kicked off the Bluetooth audio bonanza.

In reply to @Crbha

@Crbha said:

I just got the ba210 v2 and it works perfectly with my resound nexias and Samsung 23. Simple, easy and affordable.

I bought the ba210 v2 but it would not work with my Pixel 4a and my Rexton Reaches; nor with my Pixel 9 with just replaced my Pixel 4a; however my Rextons, which kept cutting in and out of Hearing Aid and dropping into Speaker on phone calls on the 4a, now are rock solid with my Rextons on phone calls on my Pixel 9 and what I assume is std Bluetooth and not . I’m not complaining but it makes me curious for an explanation.

Edited

I just received the FMA120 from FlooGoo.
I tested the work as a transmitter from 2 computers in Broadcast Public mode.
So far with Resound Nexia.
The control (as an assistant) worked with iPhone (Smart3D Resound), Sony Xperia 1 V (Smart 3D Resound and Xperia setup), Samsung Galaxy S25 (Smart 3D Resound and also directly in the Galaxy setup). Android V15.

I am very pleased.
I will test further.

In reply to @flashb1024

@flashb1024 said:

I believe Auracast is slated to be enabled on android 16, so your P9 should have full implementation

You don’t have to wait for Android 16 to experience Audio Sharing (). You can preview it now with the March stable update of Android 15 - you need to turn on the knob (mentioned in the reddit post below) in Settings/System/Developer option.

https://www.reddit.com/r/GooglePixel/comments/1j6reh6/psa_you_can_enable_audio_share_auracast_on_march/19

@Nate, I suspect the recent firmware update of Rexton Reaches doesn’t support Auracast but only LE (unicast) audio. You can try out Audio Sharing in your P9P. If your Reaches can support Auracast, you should see “Find an audio stream” as in the pic below.

IMG_6173

is a collection of Bluetooth Low Energy () profiles that support either or both unicast audio (1-to-1, equivalent to Bluetooth Classic) and broadcast audio (1-to-many, known as ). Generally, people refer to LE Audio as unicast audio and Auracast as broadcast audio.

Manufacturers determine which profiles their products will include, thereby deciding whether LE Audio, Auracast, or both will be supported. For example, Oticon Intent / Philips 9050 currently supports LE Audio (unicast) but does not support Auracast (broadcast), while ReSound Nexia and Starkey Edge support both.

Oticon doesn’t support capability? I thought they did, if not that’s nuts! it’s one of the main reasons is implemented in , well Signia (Rexton) and obviously ReSound (Jabra) are, Starkey as well.

Edited

One of the talking points around the release of the Oticon LR Audio adapter was that it would require a firmware update in the Intents and an update to the fitting software, presumably to add capability. So hopefully soon.

In reply to @tenkan

As @d_Wooluf mentioned, they said will be available through a firmware update. So, soon.

The only I know that can support Auracast “now” are

  • GN’s Resound (Nexia/Vivia/Savia), Jabra (EP20/Select500), and Beltone (Serene/Commence/Envision)
  • Starkey (Edge).

I don’t know whether Signia/Rexton can support Auracast now. Can somebody confirm?

In reply to @Mingdee

@Mingdee said:

@Nate, I suspect the recent firmware update of Rexton Reaches doesn’t support Auracast but only LE (unicast) audio. You can try out Audio Sharing in your P9P. If your Reaches can support Auracast, you should see “Find an audio stream” as in the pic below.

I don’t see that, Mingdee but Thank you very much for this tip. I followed your instructions and I believe it () is working on my Rexton Reach hearing aids, although frankly I can’t be 100% sure because there was already such a huge improvement in using my phone with the Rextons immediately upon upgrading from my Pixel 4a to my new Pixel 9 just a couple days ago. With my 4a, my connection would not stay locked on Hearing Aids but kept annoyingly flipping me to the phone’s Speaker whereas right after setting up my Pixel 9 and Android System 15 upgrade, my Rextons stay locked on Hearing Aids. Either way, viva la difference!

In reply to @Mingdee

@Mingdee said:

You don’t have to wait for Android 16 to experience Audio Sharing (Auracast). You can preview it now with the March stable update of Android 15

Thanks for that.
Unfortunately for me I’ve got a Pixel 6a which the genius’s at google decided was not getting LEA.
I’ll prolly wait for the Oticon Easy LE Adapter.

Related discussions