just got
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
Silicon-based (m1 / m2/ m3) Mac DIY HA Programming Guide w Noahlink Wireless (Tested for Oticon Genie 2024.2)
- Thread starter mobbdeepq
- Start date
A big thank you to everyone for all the software, driver and testing contributions!
This is possibly interesting:
I just switched to the dark side, a Macbook Air M4, and I tried setting things up today for my Phonak i90 using Windows on Parallels Desktop with a Noahlink Wireless 2.
My plan was to try gluchykuj2's trick .ini file. But, after setting up the Windows virtual machine and connecting my Noahlink Wireless 2, I looked in Device Manager and found that the Noahlink was already associated with the winusb.sys driver.
I installed Target after that, and I was able to discover the Noahlink and update the firmware in Trial & Tools --> Firmware update.
I haven't tried a fitting yet, but currently the Noahlink Wireless passes the "Check" function in Setup --> Fitting Device, and it's showing the model, FW version and serial number info. I'll update later once I've done a fitting.
I don't know what might have changed, but it appears to simplify things for ARM Windows 11.
Windows version on the VM is 24H2, OS build is 26100.4349. Parallels Desktop version 1.20.4.
This is possibly interesting:
I just switched to the dark side, a Macbook Air M4, and I tried setting things up today for my Phonak i90 using Windows on Parallels Desktop with a Noahlink Wireless 2.
My plan was to try gluchykuj2's trick .ini file. But, after setting up the Windows virtual machine and connecting my Noahlink Wireless 2, I looked in Device Manager and found that the Noahlink was already associated with the winusb.sys driver.
I installed Target after that, and I was able to discover the Noahlink and update the firmware in Trial & Tools --> Firmware update.
I haven't tried a fitting yet, but currently the Noahlink Wireless passes the "Check" function in Setup --> Fitting Device, and it's showing the model, FW version and serial number info. I'll update later once I've done a fitting.
I don't know what might have changed, but it appears to simplify things for ARM Windows 11.
Windows version on the VM is 24H2, OS build is 26100.4349. Parallels Desktop version 1.20.4.
Last edited:
My plan was to try gluchykuj2's trick .ini file. But, after setting up the Windows virtual machine and connecting my Noahlink Wireless 2, I looked in Device Manager and found that the Noahlink was already associated with the winusb.sys driver.
Windows version on the VM is 24H2, OS build is 26100.4349. Parallels Desktop version 1.20.4.
I've just setup a fresh VM using exactly the same software versions as you (Win11 24H2, Parallels 20.4), but unfortunately couldn't reproduce this. My Noahlink wasn't detected and remained as a driverless device. I think it might be hardware version 1 though (Model CPD-1 is on the bottom) so maybe it's just the newer one that works out of the box.
But mostly just posting to give a huge thanks to @gluchykuj2 - the hacked inf worked a treat and I'm up and running.
I have a MacBook M4 Air with a Windows 11 ARM VM installed using VMWare Fusion. I was able to use the modified Noahlink.inf file to get Windows to see the Noahlink Wireless device. I then installed the Signia Connexx software (9.11), which then updated to 9.14 using Update Manager. However, when I run Connexx, it is forcing me to add a new client before I can make any configuration changes. So, I added myself to get around this. I was then able to use the Noahlink wireless to connect my Signia Active Pro IX hearing aids and load the programming from the hearing aids into the Connexx application. However, shortly after getting everything loaded, the Connexx software pops up an error message saying something went wrong, and it must shut down. After shutting down, I restarted the Connexx software. I can connect to my hearing aids, but then shortly after they are connected, I get the same pop-up message and the Connexx software shuts down again. Does anyone have any ideas about why this is happening and how I might be able to fix it? I tried asking the Grok AI assistant, but everything it has suggested has not worked. I would really like to get this to work so I can use my MacBook for everything. Right now, programming my Signia Active Pro IX hearing aids is the only reason I still have an Intel Windows 11 machine.
I sent an email to HIMSA asking when they were going to have a Noahlink driver that would work on an ARM-based MacBook or Windows 11 machine, and they responded that there were no current plans to implement that.
FYI...I did try to create a Windows 11 x86-x64 VM using UTM, but it was much, much, much too slow to be usable.
I sent an email to HIMSA asking when they were going to have a Noahlink driver that would work on an ARM-based MacBook or Windows 11 machine, and they responded that there were no current plans to implement that.
FYI...I did try to create a Windows 11 x86-x64 VM using UTM, but it was much, much, much too slow to be usable.
I was able to create a Windows 11 ARM VM using UTM on my MacBook M4 Air, install the Signia Connexx software, and the modified unsigned Noahlink.inf driver. This allowed me to use the Connexx app and Noahlink Wireless v1 to view and modify the progamming of my Signia Active Pro IX hearing aids. When I connected my Active Pro IX hearing aids, the Connexx software informed me there was a new firmware version available for my hearing aids. I was able to update the firmware using Connexx/Noahlink Wireless through the Windows 11 ARM VM running on my MacBook M4 Air. This was the last reason for me to keep my Intel-based Windows 11 machine. I "should" now be able to do everything I need to using my MacBook M4 Air! I am going to try to document everything I did to help others who would like to do the same thing.