New Noahlink Wireless 2 from AliExpress - Using old HIMSA driver instead of new Windows driver
- Thread starter pvc
- Start date
pvc
Well-Known Member
- Joined
- Apr 12, 2023
- Messages
- 3,584
- Reaction score
- 855
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?
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?
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?
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
Last edited:
pvc
Well-Known Member
- Joined
- Apr 12, 2023
- Messages
- 3,584
- Reaction score
- 855
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;
And another driver under Universal Serial Bus Devices as "Noahlink Wireless 2";
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;
This seems to be a Windows Driver issue. There are two drivers, one under HIMSA;
And another driver under Universal Serial Bus Devices as "Noahlink Wireless 2";
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
There is something you should know about noahlink wireless. All of the noahlink wireless devices are now manufactured in China. The first series of noahlink wireless 2 did not have the label ( made in china ) but later series has made in china printed on the device, so dont worry about them. they are all original and you have to mention that the counterfeit or copy models will not be upgraded using firmware upgrader. I am an audiologist and I order bulk from the manufacturere in China.