Skip to content
HearingTracker
Log in

Bring Auracast to Any Hearing Aids with the FlooGoo FMA120

95 replies5.3k viewsLast reply

Jump
Link to this topic
Reply
@pkonrad1996 said:

MED-EL Sonnet 2 AudioStream processors

Maybe it’s clearer to answer your questions in reverse order.

At the museum, you have two options:

  1. You can wear the provided headphones (though you’d likely need to place them over your hearing aids, which might not be very comfortable).

  2. Alternatively, you can use an FMA120 with your iPhone, allowing the audio stream to reach your hearing aids via .

image

For your home setup, the concept is the same. You would still use your phone and the FMA120 as the receiver, while each audio source you’d like to listen to would have its own FMA120 (or an FMA121 for your TV, since most TVs don’t support USB audio output). This way, each source functions like the museum’s broadcast system. As shown in the demonstration image, switching between sources is simple and can be done directly in the app.

Just make sure to load the correct firmware versions for the transmitter and receiver roles on the FMA120/121. You can refer to the two user guides for each respective role.

FMA120 User Guide (PDF)8 : See the section “Using FMA120 as an Auracast Transmitter.”

User Guide: Auracast Receiver (PDF)5

@Ranson said:
  1. You can wear the provided Auracast headphones (though you’d likely need to place them over your hearing aids, which might not be very comfortable).

If someone has a cochlear implant, it means that without the sound processor, the person cannot hear anything at all. The only headphones that are suitable are large over-ear headphones, and to find the right ones, you have to search and test, because with some headphones, pain around the ear can appear after a while due to pressure. In-ear headphones are not an option, as the person will not hear anything even at maximum volume.

@Ranson said:

For your home setup, the concept is the same. You would still use your phone and the FMA120 as the receiver, while each audio source you’d like to listen to would have its own FMA120 (or an FMA121 for your TV, since most TVs don’t support USB audio output). This way, each source functions like the museum’s broadcast system. As shown in the demonstration image, switching between sources is simple and can be done directly in the app.

Just make sure to load the correct firmware versions for the transmitter and receiver roles on the FMA120/121. You can refer to the two user guides for each respective role.

Regarding this response, I really like the system. But in this situation, I have a few questions:

  1. Let’s assume I am in a museum with my iPhone connected to an FMA121, and the iPhone is paired with the sound processor. If I am touring museums that offer headphones using technology, but I am unable to use the headphones, can I connect to the Auracast audio system in the museum and listen through my sound processors via the iPhone?

  2. Would it be possible for you to test-implement a direct audio streaming function as follows: MacBook Pro M1, 3.5mm minijack or USB-C → FMA121 → Med-El Sonnet 2 sound processor with the AudioStream module? This would bypass the iPhone intermediary due to concerns about audio latency. AudioStream works via Bluetooth Low Energy; in Android systems, the mode is used with the G.722 codec or similar, but on iOS it probably uses when connecting to the Med-El Sonnet 2 processor with the AudioStream module. I would be happy to test and provide feedback, and with your assistance, I could even generate logs or remotely control it.

Yes, the FMA120 (or FMA121) connected to your iPhone receives the broadcast and forwards the audio to your Cochlear implants through the sound processor.

The latency introduced by the iPhone is very small—typically around 10 ms. Compared with the latency of Auracast itself (about 40–90 ms, depending on configuration) or that of / streaming, it’s minimal and not a concern in practice.

The FlooGoo dongle doesn’t need to connect directly to the sound processor—there’s no need to reinvent the wheel, since Apple and Cochlear have already perfected that part of the integration. This setup also allows the phone to handle incoming calls while streaming Auracast audio, which I think is an essential advantage.

Many users have confirmed that this setup works well with a range of legacy hearing aids, including some Oticon Intent users who are using iPhones while waiting for the official Auracast firmware update. For hearing aids that won’t receive such an update, we’re proud to be the first company to design a low-cost and effective solution that allows them to access Auracast.

Indeed, such a small delay is unlikely to be an issue — even for Med-El processors. However, I do see two minor drawbacks:

  1. The charging port on an iPhone or an Android smartphone without a mini-jack will be occupied, which means it won’t be possible to charge the device unless one uses wireless charging — which, however, has significant energy losses and generates a lot of heat. The solution would be for the FMA121 dongle to include an additional, third USB-C port for charging the smartphone.

  2. In the case of smartphones, the downside could be the overall size — unless a very slim version is made, possibly with a magnetic ring, similar to some cases designed for wireless charging.

Other than that, I see no downsides, and I’d gladly buy the FMA121 even now, outside the official sales channel — in fact, I’d get two units :sweat_smile:

In reply to @pkonrad1996

There are some USB-C hubs designed specifically for phones that might be useful. The Satechi USB-C Hub Mobile, for example, explicitly mentions support for audio I/O — though we haven’t tested it yet.

image

Since Apple still doesn’t support or , hearing aid brands have had to take matters into their own hands by putting broadcast scanning inside the hearing aids. The results show up in their apps — ReSound already did it, and Oticon just released a similar update. It’s not really a technical improvement — more like a workaround. The hearing aids now have to do the scanning themselves, which eats up their tiny batteries instead of letting the phone handle it like it’s supposed to. Using a battery pack for your phone is easy enough, but charging hearing aids in the middle of a trip or event isn’t exactly practical.

Another nice advantage is scanning speed — you can clearly see how much faster the FlooGoo scans compared to the hearing aid apps. FlooGoo picks up broadcasts almost instantly, and with a battery pack connected, your phone can keep doing those fast scans all day without any problem.

We’ll have some FMA121 samples in Australia this week. If you don’t want to wait, you can reach out to us via our support email channel.

In reply to @Gerhard_R

The overall audio quality depends largely on the QoS (Quality of Service) settings used for both unicast () and broadcast () modes.

In the FlooCast app, you can switch between High Quality and Gaming modes to prioritise either sound fidelity or low latency for LE Audio connections.

Bluetooth dongle with Auracast support - FlooGoo FMA120
The Starkey Edge AI has received a new firmware update (version 10.2.0), which now enables ultra-low latency — around 35.5 ms in Gaming Mode when used with the FMA120. [image]

In Broadcast mode, the app also offers different latency options — higher latency allows for more packet retransmissions in case of data loss, resulting in improved audio stability and quality.

In reply to @Ranson

I hadn’t thought about using a HUB with a phone, although it’s worth noting that it might not work — that was the case with the Pico- shermp project when I connected the Pi Pico 2W with a HUB to a computer. Still, I’d be happy to test it.

It’s true that Apple doesn’t support . is reportedly implemented in some models, but it still doesn’t allow using LE Audio with hearing aids even when they technically support it. Fortunately, this doesn’t affect me directly, since my AudioStream sound processors don’t support LE Audio or Auracast anyway — and it’s unlikely they will for at least the next five years, maybe longer, until the Sonnet 4 is released. It’s also uncertain whether the Med-El Sonnet 3 will ever receive Auracast or LE Audio support, which seems rather improbable.

That’s why your project is the only real solution that would allow me to continue using my MacBook with the M1 processor for as long as possible. I’m satisfied with the devices I have, and I’d hate to spend a large amount of money just because of the lack of connectivity between my sound processors and the MacBook — not to mention Windows. I want to keep using my current MacBook until The Witcher 4 comes out, and then I’ll buy a newer one :wink: Besides, the M1 MacBook is still very powerful for me, and even when it loses official support, it already runs a stable version of Asahi Linux.

Scanning for sound processors through the app takes quite a while and doesn’t always succeed, so it’s great that you’ve managed to work around that issue.

I’d love to buy and test the FMA121 right away without waiting — I just don’t know if you’d be willing to ship the FMA121 to Poland. If so, should I contact you via email at info@flairmesh.com?

Thank you for sharing the listing here. We did experience some delays, so we’re glad it became available before Christmas.

We’ve redesigned our website so it no longer looks like a development log. The new layout presents the different working modes more clearly, while still reflecting our ongoing work on and and making support materials—such as user manuals—easier to access. This is especially important since we’ve packed so many functions into a single device, yet still want to reassure everyday users that it remains easy to use.

Edited

No, users will need an optical-to-3.5 mm converter if their TVs only provide an optical audio output.

However, many TVs that only offer optical output also support Bluetooth headphones. If that’s the case, can be enabled completely wirelessly using the FMA120.

Use FlooGoo FMA120 to Add Auracast to Any Bluetooth-Enabled TV
Many TVs that only provide an optical output also support Bluetooth headphones. In that case, you can simply load the relay-mode firmware onto an FMA120 and pair it with the TV just like a Bluetooth headset. The FMA120 will then broadcast the audio wirelessly via Auracast. After pairing, there’s no need to plug the FMA120 into a PC or the TV—just power it with any USB charger, and it will begin broadcasting automatically whenever the TV connects to it over Bluetooth. Here’s an example using re…

The USB and 3.5 mm inputs are switchable in the FlooCast app.

We haven’t had the opportunity to test the adapter on a TV that supports USB audio output. However, it exposes a standard USB audio interface that has been confirmed to work with PCs/laptops and gaming consoles such as the PS4/PS5, Nintendo Switch, Legion Go, Ally X, and MSI Claw. If the TV supports USB DAC audio devices, it should work as well.

Also, as mentioned in the previous post, most TVs released in the past 5–7 years already support Bluetooth. For those models, there’s no need to use USB or 3.5 mm cables with the FMA120/121. This provides the cleanest and simplest way to add to a TV.

image

Bluetooth will add some delay and another device contributing to wireless communication noise. Wired and forget it tends to be better if not much more trouble. It’s good to have the Bluetooth option.

Edited

Regarding latency: since all PCs and TVs already compensate for the delay of classic Bluetooth audio to maintain lip-sync (the player delays the video so it matches the Bluetooth audio), the relay-mode solution will offer the same—or even better—latency compared to wired connections. This is because PCs and TVs do not compensate for any additional delay introduced when converting a wired audio signal into .

Relay mode is also a “pair-once and forget” solution. The classic Bluetooth connection is very stable, whereas wired connections can sometimes become loose or disconnected for various reasons. Best of all, you don’t have to reach behind the TV or search for connectors and plugs.

@d_Wooluf said:

My memory with the FMA121 and a TCL TV is that it worked intermittently. I don’t think my TV quite supplies the current the device needs.

If you are using the TV’s USB port to power the adapter, try a different USB port or cable to see if it improves stability. The adapter draws very little current—approximately 10 mA in mode and 18 mA in mode.

For comparison, a typical USB flash drive consumes:

  • Idle: 20–60 mA

  • Read/Write: 80–200 mA

  • Peak: ~250 mA (rare)

@Ranson said:

The adapter draws very little current—approximately 10 mA in LE Audio mode and 18 mA in Auracast mode.

If that’s how much it draws in USB-audio mode, my theory is obviously wrong. The TV can take a USB flash drive without any problems.

Related discussions