We’ve updated the Android app (v1.0.2) to improve the user experience: a spinner now indicates when a broadcast is syncing, and the array icon—previously mistaken for a button—has been replaced with a music note to show streaming status. Please give it a try and let us know if it feels more intuitive.
Regarding your mention of the FMB120, I have the following idea:
Developing the next-generation FMA121 may involve high costs and uncertain return on investment. Therefore, you might consider building upon the current FMB120 by adding a 3.5mm microphone jack.
In other words, by simply adding a 3.5mm microphone port to the existing FMA121 version, PHONAK users can choose based on their environment:
Use a hearing aid microphone
2.Use a phone microphone
3.Use a hands-free 3.5mm wired microphone
The cost would certainly be much much lower than developing a brand-new FMA121, significantly reducing development risk for your company. The expected profit margin should be quite good.
Also, I’d like to take this opportunity to speak to all fellow users of PHONAK hearing aids:
If the FLOOGOO FMA120 version comes with a 3.5mm wired microphone jack, I highly recommend getting one — it’s something you’ll definitely find useful.
The FMA121 is built on the FMB120 module, which also powers the FMA120. It features USB-C and 3.5mm line-in inputs, making it suitable for TVs or phones with USB-C. To keep things simple, it shares the same firmware as the FMA120. We’ll consider Phonak-specific requirements in the future—likely using the same ID design with a new PCB, still based on the FMB120.
I will provide this information about broadcast for square dancing when we get it figured out on his system.
I have had a couple people tell me that I would not get this to work receiving with the Samsung FE 23. It does work. I had one person indicate it would not work with my Rexton BiCore BTE aids. It works. Windows PC Laptop with FMA120 broadcasting to the Galaxy S 23 FE receiving with a USB A to USB C adapter to a different FMA 120 and the Floocast Android APP.
JUST because the BiCores may not have LE capability (have not checked this today) does NOT prevent this. The connection between the two FMA120 Transceivers IS LE. The 23FE with the new UI upgrade receives LE and internally shuffles it through the Rexton aid APP to the aids via bluetooth, hence to the wearer’s ears. This is a good thing. It costs $50 US to receive an Auracast broadcast signal. No new hearing aids. No new phone. It may not work with all brands of aids that have no app. YMMV.
As I wrote earlier, you must limit your phone to no more than two bluetooth connections, THE FMA120 and your hearing aids. I have a watch with a Bluetooth connection. It has to be turned off or this won’t work. Similarly, automobiles, Fitness bands, etc.
Good luck.
As my Indian friend Suresh says, “I may be telling you more than I know.” But I believe Ranson has said that they have an Apple iPhone App now. He watches this forum and will likely respond soon. In the meantime, check his posts and the Flairmesh website. This tech and the Flairmesh firm are doing more for us than our hearing aid providers.
Cordially,
KP75
No, this setup will work with your iPhone and Rexton Reach hearing aids, as they use the MFi protocol, which isn’t affected by the A2DP limitation.
Simply load the receiver-mode firmware, download the FlooCast app from the App Store, and try it with your Rexton.
For context: Apple does not allow audio from a USB microphone to be routed to Bluetooth devices using the A2DP profile. I assume this may be because Apple believes users typically don’t need microphone input while streaming music via A2DP. (I might be wrong about that, but I hope it helps explain the limitation.)
Since MFi hearing aids don’t rely on A2DP for audio streaming, they are already compatible with Auracast.
Currently, the only unsupported scenario is Phonak hearing aids using classic HFP/A2DP with iOS. If the user is on an Android device, Phonak hearing aids are also Auracast-compatible, as Android does not impose the same limitation.
We also received confirmation from a user in Italy that the FMA120, in receiver mode, successfully receives the Auracast stream transmitted by Listen Technologies’ Auri transmitter.
I agree that a FM120 plugged into an iPhone will receive Auracast broadcast. This is something I don’t need yet as I have yet to come across a place that transmits Auracast. I am hoping for an auracast assistant in my iphone to work with my Rexton aids without adding adapters and dongles to my phone. I am happy to use my FM120 to transmit from my pc to my aids.
New user here. I’ve recently purchased a set of ReSound Vivia 9’s which are supposed to be the same as Nexia’s but with the AI noise reduction model and the FMA120 from Amazon.
Here’s the specs: FMA120, Vivia 9 firmware 10.21.2.1;Windows 11 FlooCast version 1.1.4 with 1.1.2 firmware.
The FMA120 is recognized by both my Surface Pro 7+ Windows 11 tablet and my Dell desktop computer as an audio output device (QCC3086 USB dongle). The FMA120 is recognized on my Pixel 7 phone in the ReSound Smart 3D app and streams to my HA’s when I activate it.
BUT, I can’t get the FlooCast app to recognize or pair to my HA’s. I’ve tried everything mentioned in the thread to no avail (i.e., turn off every Bluetooth device in the universe, start and restart the HA’s manually and through the charger, plug and unplug the dongle, restart the computers, etc.) Nothing works.
Have you tested the Vivia’s versus the Nexia’s to see if there’s any difference in firmware that would cause this? Are you aware of any customer that has successfully paired Vivia’s?
Please feel free to email us (the address is in the FAQ section of our online manual), and we’ll send you a debug firmware version with log output so we can take a closer look at the issue.
Since many new hearing aids are expensive and only available by prescription, we’re not able to test every model ourselves. That’s why we really appreciate the help from customers and volunteers who can share logs when something doesn’t work as expected.
Please note that version numbers with four digits indicate testing or hotfix releases for specific issues. Other users don’t need to upgrade to these versions; improvements will be merged into the next main release (1.1.3), which always uses a three-digit version number.
Just recently started demoing Oticon Intent 1’s and noticed that one of the hearing aids would cut out while streaming a YouTube video. I didn’t have this kind of issue when I was demoing Phonak Audeo Infinio l90, Widex Allure 440, or Starkey Edge AI 24. When I would unpair and repair in a few minutes it would do it again.
NOTE: This issue happens when I am paired to the FMA120 on a laptop. Not a phone.
Please check whether a USB 3.0 device (such as an external HDD or SSD) is connected to an adjacent port. USB 3.0 devices are known to generate interference in the 2.4 GHz band, which can negatively impact Bluetooth performance.
The transmission power of hearing aids can vary between brands. For instance, if a Starkey device has higher output power, it may achieve a better signal-to-interference-plus-noise ratio (SINR) when received by the FMA120, resulting in a more stable connection.
To determine if interference is the cause, try temporarily disconnecting the USB 3.0 device and see if the issue improves. USB 3.0 interference with Bluetooth is a well-known and documented issue.
For more information and possible solutions, please refer to the support page below: