Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All Keyboards acting strange after using Lock feature #120

Open
Joeviocoe opened this issue Feb 11, 2021 · 1 comment
Open

All Keyboards acting strange after using Lock feature #120

Joeviocoe opened this issue Feb 11, 2021 · 1 comment

Comments

@Joeviocoe
Copy link

Joeviocoe commented Feb 11, 2021

Strange issue after updating the v2.1.0-prodc firmware.
Was previously on v0.2beta8, and used the Lock Button feature without problem.
Running Windows 10

Also, the "?" tooltip popup info incorrectly describes the feature:

Choose a button (1-6) that you can press for 5 seconds to quickly lock your OnlyKey and computer...

But the online manual correctly states the instruction as a single press (which I guess eliminates the use of the slot for that button).
I choose button # 5. I have not set either slot 5a nor 5b.

Holding down the button per this tooltip does NOT lock the OnlyKey or the computer.
Tapping the button does still work to lock the OnlyKey and computer... but that is when something strange happens.

For a few minutes, I am unable to type keypad numbers (such as to unlock the system using a Windows Hello PIN)
I have also noticed (by switching the unlock login screen to login as another user, typing into the non-masked username field) that caplocks are not reporting correctly on my USB keyboard.
I am unable to toggle the Numlock unless I am holding down the shift key.

All of this weirdness seems to subside after about a minute or so. Longer if I had tried holding down the Lock Button on the OnlyKey a few times before finally tapping.

Removing the Onlykey does not fix this. Sysadmin mode is disabled too.

I am not sure what is causing this... but it is very strange behavior.

Perhaps OnlyKey is sending other non-character keystrokes during the Lock operation. Maybe to be cross compatible with MacOS?

@vy-bot
Copy link

vy-bot commented Jun 18, 2021

Seen something that might have the same root cause. After pressing the lock button, one or more of the modifier keys seem to be "stuck" in the pressed position (CTRL for sure). Pressing CTRL fixes the issue.

This is not an issue when creating a custom lock button in admin mode using " \gl ". Unfortunately this doesn't lock the key. Maybe a custom modifier " \L " to lock the key? Would be nice, also could use it for extra security after login in some cases.

Environment: Windows 10, entry speed is set to 10, admin mode enabled.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants