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

If it is the Jabra streamer then they are still keeping “in house” :frowning:
I have reverted to my Kirkland9.0 and just use a bluetooth two device transmitter. I am holding on for an android update to samsung/jabra this fall. At least until my 6 months is up

In reply to @Member376

HomeSpot BA210 Broadcaster v2 has this problem solved. The problem is mainly about the limited buffering of GN and an issue with Samsung OUI 6.x. Press and hold the MFB button at the back of the Broadcaster for 3 seconds to switch between Open SQ mode and Encrypted HQ mode. SQ mode has better compatibility with HAs. HQ mode provides 48K high quality audio for consumer headphones. It has been tested with Jabra EP20 and ES500.

Send a message to cs@homespotdigital.com and tell them you want to have your Broadcaster replaced with a v2.

Now that the Rexton Reach has released their bluetooth LE firmware update, (latest Connexx 9.12 update) does anyone know if there is a dongle / broadcaster that supports it, so that I could broadcast the sound from say my PC to the aid?
Do we know which chip / technology (eg Qualcomm or ?) /codex the Reach uses? I have ordered a couple of le dongles, but judging by the discussion on this dive, it will not be that easy, and for example I may have to direct the aid to which channel to pick, and hope the codex is similar etc.
I have an iphone currently which I am using with the Reach .

In reply to @Deenovan

Do you need to get the:
HomeSpot JM320 Wireless Headphones x 1 (SKU: HS-JM320-BUN210)
To get the 210 broadcaster?

I do not see the:
HomeSpot BA210 Broadcaster v2
Listed on their website.

Can you just get the broadcaster with the required cables?

Great to hear and many thanks for your notice. Jabra doesn’t seem to want to publish their current versions on their website and previously you had to go into Costco and request that they verify you had the most recent version. It would be an improvement if the update mechanism actually worked as intended. I just sent my back for repair and expect a replacement set next week. The revision (9.35.1.0) along with the new Samsung OS (UI 6.1.1), while curing several of the most egregious problems was still far from satisfactory. I am hopeful that the newer version you mention will correct my remaining problems (e.g. others can barely hear my voice) and also allow for compatibility with the S24 series. I also have a suspicion that my , being one of the earlier pro 20 series may have experienced some manufacturing or component defects that have since been resolved. I have suggested to several friends to hold off on purchasing these HAs until these problems have been resolved by Jabra and Samsung engineers. I still am optimistic for their technology.

@Frank_G said:

I am hopeful that the newer version you mention will correct my remaining problems (e.g. others can barely hear my voice) and also allow for compatibility with the S24 series

My partner has the S24 and Jabra and we can hear each other well with protocol. She had not reported any problems with others hearing her voice as long as the volume on her phone was up. Actually I am remembering, she does have to toggle Bluetooth occasionally while I have not been doing that. She is still at the original firmware however but as should be apparent she too is at One UI 6.1.1.

Good luck with yours @Frank_G!

I am pleased to report that I just picked up the new replacement Jabra Enhanced Pro 20 under warranty, and so far, all is well, and I am very pleased. Based on the dramatically improved performance of this new set, I now believe that the original and replacement were both defective on arrival.

Just a quick fyi the FlooGoo FMA 120 (avail at Amazon) now also works with Rexton Reach

Hi All;

I am not sure so I’ll ask. Most of these hearing aids use the Qualcomm Chip set. More specifically Rexton, Widex and Signia.

I would presume that all manufacturers must use the same chipset/API or they would not connect with a public broadcast.

Related discussions