We haven’t received any feedback about the Oticon Xceed yet.
For the Xceed you may need the Oticon Connect Clip to connect to your laptop as I don’t think the Oticon Xceed supports Bluetooth LE audio. I’m not sure if in the future you would be able to use a FlooGoo FMA120 plugged into your iPhone with the iPhone Camera Adapter to connect your Windows 11 laptop. Ranson might have more details. There is a different thread for that.
The upcoming AS1.0.7 update will add support for using the Auracast receiver mode with iOS devices. As you mentioned, for an iPhone with a Lightning interface, a camera adapter can be used to connect the FMA120 to an iPhone 13. For newer iPhones with USB-C, a simple USB-C to USB-A adapter can be used instead. Then, using the FlooCast app, the FMA120 can receive the Auracast stream and forward it to the Xceed—via the ConnectClip if that’s the original connectivity method.
I am using a Samsung S24 and the Phonak Lumitys. 1.1.2.1 firmware works but I’m not sure how to tell which microphone the phone is using.
Thank you for the confirmation — I believe this answers the question @jack2 raised.
As long as you can pick up a call, hear clearly through your Phonak hearing aids, and the other person can hear you well, it indicates that the phone’s built-in microphone is being used — because the FMA120 running firmware 1.1.2.1 does not have a microphone interface.
The main point we wanted to confirm was whether the phone supports using different physical devices for input and output during a call. Based on your experience, it appears that it does.
Xceed BTE is able to connect with the Iphone 13 for Direct audio streaming & Two-way communication with ConnectClip (CC). I have to talk directly into the Iphone microphone in order for the caller to hear me.
To connect Xceed with Windows 11 laptop for Zoom , I have to use CC.
So, having a FlooGoo 120 and iPhone Camera adaptor, I don’t need a CC. This FlooGoo 120 is basically a universal connector to any devices that have new generation BT - Auracast i.e sound send out from the Auracast ecosystem & pickup by Floogoo120 then transfer to any HA’s.
A customer recently shared a detailed review on Amazon about using the FMA120 with the Oticon Intent. I hope the review provides a helpful reference or guide for other users with the Intent or similar hearing aids.
############
I can confirm that this works with Oticon Intent.
Prerequisites: Oticon Intent must have the latest firmware (1.2.1 as of now—the launch firmware will not work).
You can use their app, FlooCast, to fine-tune the settings. Be patient during the first pairing; it may take a few minutes. If pairing fails repeatedly, turn off AptX and ensure only LC3 is enabled. Don’t use broadcast mode. (Make sure “Prefer LE Audio” and “Public Broadcast” are checked, and leave all other options off except LED.)
All other Bluetooth devices paired to your hearing aids must be turned off during pairing. Turn off your phone’s Bluetooth. If you have paired your hearing aids to iPad/Mac, don’t forget them. If you have a ConnectClip or TV Adapter, turn them off as well (they likely won’t interfere, but it’s better to be safe).
Once paired, you don’t need to turn off the ConnectClip or TV Adapter to use this transmitter. It’s treated as a “phone” by the hearing aids, and Oticon Intent supports multiple Bluetooth connections. You can only have one device streaming audio at a time, but multiple devices can remain connected simultaneously.
However, if your iPhone is paired to the hearing aids, you must turn its Bluetooth off in order to connect the FMA120 to your hearing aids. This is because the Made for iPhone (MFi) protocol assumes exclusive use of the hearing aids (you can still use a TV Adapter concurrently, but not a second phone connection).
If you connect the FMA120 first, your iPhone won’t be able to stream audio to the hearing aids. If you connect the iPhone first, the FMA120 won’t stream. This is not like the TV Adapter and iPhone combination—those can both stay connected, and the second device can stream as long as the first isn’t actively streaming. With the FMA120 and iPhone, even if the first device is idle, the second cannot stream. So you do need to switch them manually.
To switch between them, simply disable Bluetooth on one of the devices. For the FMA120, unplug it. For the iPhone, use Control Center. No need to unpair, don’t try it.
The signal strength is just slightly better than an iPhone, perhaps because the exposed USB pins are more vulnerable to interference. Any USB 3.0 device—such as an external HDD or SSD—will interfere with it if connected to the same USB hub. This is a known limitation of Bluetooth audio streaming.
Solution for Poor Microphone Audio During Calls with PHONAK Hearing Aids
Hello everyone,
If you or someone you know is using PHONAK hearing aids with an Android smartphone and experiencing poor microphone audio during phone calls, I’d like to share a solution that has worked best for me after trying many methods.
- Purchase the FlooGoo FMA120 from Amazon.
- Update the firmware to version 1.1.2.1.
- Pair your PHONAK hearing aids with the FlooGoo FMA120.
- When making calls in noisy environments, plug the FMA120 into your phone (you’ll need a USB-A to USB-C adapter for this to work properly).
- This setup allows your phone’s built-in microphone to be used stably during calls.
Special thanks to Ranson from FlooGoo customer service—without his help, solving this issue would have been very difficult.
(Also, Ranson, may I ask if it’s possible to use a 3.5mm wired microphone for hands-free calling with this setup?)
Since I don’t use an iPhone, I’m not sure whether this solution works on iOS devices, but friends are welcome to test it out and share their experiences.
I hope this method provides a stable solution for those who have struggled for years with poor call audio using PHONAK hearing aids.
Thanks again to Ranson from FlooGoo.
—Jack
https://forum.hearingtracker.com/t/phonak-marvel-hands-free-the-achilles-heel-of-this-ha/44306
Glad to know it’s working for you. As for using a 3.5mm microphone, it really depends on the specific phone. There’s also a chance the system may switch audio output to the 3.5mm jack instead of keeping it on USB.
It’s technically possible for us to create a separate hardware version of the upcoming FMA121 that supports this setup, since it includes both USB-C and 3.5mm inputs. However, we might not do it if only a few people need it, as producing a separate version probably wouldn’t make business sense.
Meanwhile, we already have an important task in our queue to enable Auracast for Phonak users on iPhone, as mentioned in the link below.
Thank you, Ranson,
for incorporating a potential hardware version of the FMA121 that supports a 3.5mm microphone.
Personally, I believe that if this version becomes available,
all PHONAK users should consider choosing it,
as it significantly improves call quality stability with minimal cost.
Your solution (which uses USB-C, is compact, and doesn’t require an adapter) ensures that every call can be reliably conducted with clear communication on both ends.
thanks for Ranson great help!
Jack
Really appreciate you pointing this out — we’ll look into what we can do.
Could you make one version where the 3.5mm jack could have a switch to enable it to work as mic / audio in / combo ? This might offer more options for using the aids for conference calls but not having to use the aid mics.
Thanks for the suggestion! If we make such a device, an in-app switch is likely—fewer physical parts usually mean better durability. We chose USB-A for the FMA120 for the same reason: it tends to last longer than smaller connectors like USB-C. Personally, I’ve had to replace Lightning cables often because they break easily. Also, the FMA120’s exposed connector is big and easy to clean, which helps with long-term reliability. We want users to count on it for years.
How do the contacts hold up? It’s a non-standard design and it seems there could be extra play and extra wear especially because it needs to be removed each time one needs to restart it.
Hello everyone,
- I agree with Ranson’s explanation that the reason FMA120 uses USB-A is to ensure better reliability and longer lifespan. However, nowadays, most users tend to prioritize compactness over longevity. From a manufacturer’s point of view, using USB-C—even if it may have a shorter lifespan—could actually increase sales volume.
- The FMA120 has no physical switch design, which I think is excellent—it avoids accidental touches and ensures stability. By the way, the FMA120 can only be paired with one device, which makes its reconnection stability exceptional. Even during a call, if you discovered that the hearing aid’s microphone isn’t picking up sound well, simply plugging in the FMA120 can re-establish a stable connection to the hearing aids within just a few seconds. As long as Bluetooth on the phone is turned off, audio will be routed to the FMA120 within seconds, and the system will automatically route the microphone input to the phone’s built-in mic.
- My personal suggestion for the FMA121 design is that it could continue the idea of having no physical switches. As for how to determine audio routing, the following logic could be applied:
(1) If the FMA121 is not plugged in, follow the phone’s original settings.
(2) If only the FMA121 is plugged in, route the audio to the hearing aid while using the phone’s built-in microphone for input.
(3) If both the FMA121 and a 3.5mm microphone are plugged in, switch the input from the built-in microphone to the 3.5mm mic.
If this concept is feasible, it could avoid the complications and costs associated with physical switches, align with user habits, and eliminate the need to learn new software settings or operations.
I previously tried DIYing a similar idea based on this product:
But due to its large size and poor stability (connection quality was bad, and volume fluctuated), I eventually gave up.
(I also tried building a large setup using the PHONAK TV CONNECTOR—it was bulky and ugly, but very effective when stable phone calls were needed.)
In my opinion, if the FMA121 could be designed and brought to market with USB-C and the benefit of microphone routing, and if it’s compatible with both Android and iPhone, then every user of Phonak hearing aids would must buy it.
Thanks to Ranson and also to Floogoo for your efforts on this issue.
— Jack
Thanks for all the suggestions.
Another option is to design your own product using our FMB120 module—the core of the FMA120/121. Some customers are already doing this for LE Audio and Auracast. Samples are available on request, and our FlooCast app is open source if you’d like to customize it.
Thank you, Ranson,
for mentioning the possibility of using the FMB120 module to build it ourselves. I really wish I had the ability to operate it, but due to the challenges in hardware connections, form factor, and software configuration, I find myself lacking the necessary skills.
So I’d like to ask you to evaluate whether it is commercially feasible to develop this product. I would be very happy to see FLOOGOO make a lot of money from it.
Thank you, Ranson.
Jack
FMA120, SAMSUNG GALAXY S23 FE and REXTON BiCore BTE Aids work together.
Thanks Ranson for all your work. I purchased two FMA120s so I could test my setup. Using Windows 10 and a Windows 11 laptop, I could successfully transmit via one FMA120 to an additional FMA120 ATTACHED to my 23 FE. I have not yet had success working with my caller’s square dance broadcast setup. But i believe we will be avle to work through this. The Auracast APP which you provide works well. I was a bit too fast fingered trying to connect and hit the white arrow which disconnects it. Once I overcame the user error located between the phone and the seat, it worked extremely well. Thank you again!
If you get Auracast to get working with your square dance caller, let us know how you are set up.
Thank you for bringing this opportunity with Phonak users to our attention — it’s something we wouldn’t have discovered just working in the lab.