You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the Defy is looking for a bluetooth connection as soon as it receives power - even if the wireless function is set to off by the switches on the undersides (🛜=🟥). This leads to a unwanted user experience when trying to enter the BIOS settings on boot up, as the keyboard will not send any key press to the pc.
I understand this shortcoming when the keyboard is paired over bluetooth (and maybe RF), but when connected per USB the keyboard should act like any other wired keyboard.
Steps to reproduce the behavior:
Shutdown the pc.
Put the switches for the wireless function to the off position.
Connect the keyboard to the pc per the neuron and the USB cables.
Power on the pc.
Try to enter the BIOS settings and feel miserable for failing.
Expected behavior
When connected per USB the keyboard should act like any other wired keyboard.
Desktop (please complete the following information):
OS: Arch Linux (kernel 6.8.9.arch1-1)
Bazecor Version: 1.4.0-rc.3
Additional context
Still quite happy with my purchase!
The text was updated successfully, but these errors were encountered:
Currently the Defy is looking for a bluetooth connection as soon as it receives power - even if the wireless function is set to off by the switches on the undersides (🛜=🟥). This leads to a unwanted user experience when trying to enter the BIOS settings on boot up, as the keyboard will not send any key press to the pc.
I understand this shortcoming when the keyboard is paired over bluetooth (and maybe RF), but when connected per USB the keyboard should act like any other wired keyboard.
Steps to reproduce the behavior:
Expected behavior
When connected per USB the keyboard should act like any other wired keyboard.
Desktop (please complete the following information):
Additional context
Still quite happy with my purchase!
The text was updated successfully, but these errors were encountered: