Skip to content
HearingTracker
Log in

Oticon Intent - Firmware 1.3.0

138 replies6.7k viewsLast reply

Jump
Link to this topic
Reply

In reply to @ROBERT_N1

Could you check if it works when you pair the hearing aids directly with the FlooGoo FMA120 in High Quality mode (without the companion app), and then switch to Broadcast while streaming audio?

The FMA120 has a built-in Assistant, so if your hearing aids support Auracast and are already paired with the dongle, you don’t need a companion app or an Android phone with Auracast support. The dongle automatically sets up the broadcast channel (and passkey if needed) on the hearing aids.

A phone or app is only needed when a second user wants to join the same audio stream and listen together.

In reply to @tenkan

I used NordVPN. I rebooted the computer first, then ran the VPN to ensure the Oticon software was not connected to the US site. But it still told me that no update was available.

In reply to @Luga

The firmware update was available within Genie 2025.2 after I updated the Genie package. The order of progression was connect to the U.K using McAfee VPN, go to Oticon Global Site, download Genie update, install Genie update, disconnect VPN and then run Genie 2025.2. There was a notice in the upper right corner of Genie that new firmware is available for my Intent aids. Then, I updated the aids in Genie 2025.2.

Note: When downloading the Genie update, there were two options. One if you will not have connectivity during the installation (larger file) and a second if you will have connectivity (smaller file). I chose the smaller file. It also asks where you are located and I chose USA.

That’s actually how it’s designed. When there’s audio for only one channel, it can sometimes happen that one of the hearing aids doesn’t stay synced with the broadcast. In a stereo broadcast, both channels work independently, so if one side drops out, the other will keep playing as normal. The sender has no way of knowing what’s happening on the receiver side, so this kind of behavior can occasionally occur.

Putting this out there, in caseit helps someone else doing a Oticon Intent firmware update.

NOAH wireless. Windows 10, USB3 ports.
from 1.2.1 to 1.3.0

I saw repeated failures at approx 1m 42s remaining (of est 4m 2s)

The cure was to put the aids in the charger, while doing the updates. On reflection it may have been a somewhat risky thing to try.

Fully charged from an overnight charge, the batteries were not new (2y?), but still hold a good charge (18-27h use).

Intent should be programmable in the charger. It is an improved feature over Real. Probably helps audiologists avoid problems with not/low charged aids.

I could also mention, that I’m in the USA, and that the newer Android Oticon Companion app (1.6.1) was available last Friday (7-NOV-2025), and the newer Oticon Genie 2025 was available this morning (Tues, 11-NOV-2025).

I had good luck so far, testing with a few dongles. (Pixel 8a/9a). I wish I could find a legimate way to caption the Auracast streams. I wonder if the Pixel 10s might be able to.

There are some kludgy ways to use a Auracast dongle with the Pixel USB-C port, and a mic redirector app, while still having the aids connected via Bluetooth ( presumably).

Google’s Live Captions works in that narrow case. Live Transcribe also works in that setup, but cuts off the audio.

Conversely. if one tries to use the Oticon app to tune the Intents to the (same) Auracast broadcast, it puts up an error message to the effect of “audio already in use"

FYI. Genie 2 updated this afternoon without a VPN connection. Also, upgraded firmware without a problem. Bluetooth did have a little trouble connecting, but after a power cycle, everything is fine.

In reply to @Luga

@Luga said:

Has anyone done the firmware upgrade on Intent 1s as DIY? Any issues?

Thanks in advance…

I’ve done the 1.3.0 upgrade, the only issue since the upgrade is that the option to adjust the volume using the device buttons is no longer available. Has anyone else had this issue or is there some setting somewhere that I’ve missed that would enable the volume button option?

@Philip1 said:

Has anyone else had this issue or is there some setting somewhere that I’ve missed that would enable the volume button option?

You may have disabled that in the software (Genie).

In reply to @Philip1

might have to reanable that in genie2, toggle it, the bineural network.

sometimes my old OPN 1 did that, buttons had no effect, had to restart them, or reconnect them to genie 2 once.

In reply to @e1405

@e1405 said:

You may have disabled that in the software (Genie).

I haven’t disabled that in Genie 2, the volume button option is greyed out since upgrading to v1.3.0 so can’t select that option.

I was hoping someone who had done the upgrade could let me know if they have this issue or not. The trouble may be that the start/stop feature is occupying the button that was previously assigned to volume control. However no options to configure anything.

@Philip1 said:

I was hoping someone who had done the upgrade could let me know if they have this issue or no

Sorry, I should’ve been clearer in my first reply: yes, I updated and I don’t have this issue. Here’s how my coordination is set up. Maybe just double-check that you can tick the red and right checkboxes as shown in the screenshot below?

image

@e1405 said:

Sorry, I should’ve been clearer in my first reply: yes, I updated and I don’t have this issue. Here’s how my binaural coordination is set up. Maybe just double-check that you can tick the red and right checkboxes as shown in the screenshot below?

Hi, thanks for your help, its appreciated. Somehow in the “Fit”…”Automatics” settings, I had “ Broadband” turned off. This is why the “Volume control P1,P2,P3,P4” in “Binaural coordination” was greyed out! All fixed now, thanks again.

As my luck would have it, I finally got Genie to show a firmware update for the Intent 1’s. The right updated successfully but the left one keeps failing at about 1 min 41 seconds to go. I’ve tried charging them fully, restarting Genie and reconnecting the Noahlink wireless and reconnecting the receiver. No luck. Now I am in a situation where the HAs have different firmware versions and wont pair with each other.

Anyone have a similar situation or have any ideas on how to fix?

thanks

That is the reason I don’t do it would be my luck that it would fail and I would be in trouble.

In reply to @Luga

@Luga said:

Anyone have a similar situation or have any ideas on how to fix?

Just a wild guess here, ok… maybe you could try creating a new client profile and simulate someone who needs only one hearing aid (in the “Prepare” tab). Then proceed with the upgrade using this new profile and just your left hearing aid. If you manage to get 1.3.0 on the left one as well, you can go back to your own file afterward and pair both hearing aids, again in the “Prepare” tab.

Related discussions