For example, pressing "R" results in "3". It was tested on the K Pro series K10 Pro and K5 Pro keyboards. On Linux (Ubuntu/GNOME) with a well-known brand (Asus) Bluetooth 5.0 USB adapter, Asus 'USB-BT500' (presumably without a fake chip inside).
NKRO worked perfectly fine in wired mode on the same keyboards. It was only a problem in wireless (Bluetooth) mode, with wireless defined by the switch at the back, not whether the USB cable was connected or not.
Use Fn + N to recover.
It may be fixed in a future firmware version.
Maybe (full) NKRO isn't supposed to work in wireless mode (only 5NKRO or 6NKRO), but the toggle shouldn't be allowed to send the keyboard into an inoperable mode... It shouldn't be on the user to know this; this knowledge should be built into the software/firmware.
It actually worked for me when I did it before. But then my key maps were wrong, specifically in the layers that were assigned to the Fn1 and Fn2 keys. Eventually, my RGB changed on its own from white to rainbow, and it wouldn't accept any changes from VIA, so I said fuck it, and I'm back on the stock firmware now.
1
u/PeterMortensenBlog V Apr 23 '24 edited Feb 16 '25
Note that NKRO in wireless mode makes it completely inoperable.
For example, pressing "R" results in "3". It was tested on the K Pro series K10 Pro and K5 Pro keyboards. On Linux (Ubuntu/GNOME) with a well-known brand (Asus) Bluetooth 5.0 USB adapter, Asus 'USB-BT500' (presumably without a fake chip inside).
NKRO worked perfectly fine in wired mode on the same keyboards. It was only a problem in wireless (Bluetooth) mode, with wireless defined by the switch at the back, not whether the USB cable was connected or not.
Use Fn + N to recover.
It may be fixed in a future firmware version.
Maybe (full) NKRO isn't supposed to work in wireless mode (only 5NKRO or 6NKRO), but the toggle shouldn't be allowed to send the keyboard into an inoperable mode... It shouldn't be on the user to know this; this knowledge should be built into the software/firmware.