New Noahlink Wireless 2 from AliExpress - Using old HIMSA driver instead of new Windows driver

I have updated the DIY School Hearing Aids (v2.2) PDF File named (Noahlink Wireless 2 - DIY User Guide) to compensate for this Sh... Stuff.
 
Question about this blurb saying → Noahlink Wireless 2 now released?

The question is, how can Noahlink Wireless 2 reap the benefits of Bluetooth BLE 5.3 protocol if the default driver is the same driver used for the previous/older Noahlink Wireless device which does not support the Bluetooth BLE 5.3 protocol? :rolleyes:
c1.png
 
Ripped device.

Main Chip marked:
N5340
QKAAD0
2233B0
(Nordic Semiconductor designed, The nRF5340 is a wireless Bluetooth 5.2 System-on-Chip (SoC) with two Arm® CortexM33 processors, supporting Bluetooth® Low Energy, Bluetooth mesh, Thread and Zigbee wireless protocols.)

RF chip:
66403-1
3778863
2218MX
with SKY logotype

Any ideas?
 

Attachments

  • IMG_20250322_104418.jpg
    IMG_20250322_104418.jpg
    768.7 KB · Views: 8
  • IMG_20250322_104616.jpg
    IMG_20250322_104616.jpg
    375.8 KB · Views: 7
Last edited:
Thanks @JaoMing for the great pictures of Noahlink Wireless 2!!

This seems to be a Windows Driver issue. There are two drivers, one under HIMSA;
c1-png.1073

And another driver under Universal Serial Bus Devices as "Noahlink Wireless 2";
device-manager-jpg.1059


It seems to me that a new Noahlink Wireless 2 device should use the new/Signed/Windows driver under Universal Serial Bus Devices as "Noahlink Wireless 2" and not the old "not-signed" driver under HIMSA for Noahlink Wireless. But that is not what happens. Which driver gets assigned for your Noahlink Wireless 2 device is left up to chance and dependant upon which event happens first;
  • install the fitting software first
  • or plug in the Noahlink Wireless 2 device into a USB-port on your computer first
 
Back
Top