Closed Hubro closed 2 years ago
pfps
commented
2 years ago This appears to be unavoidable. When a device is sleeps it forgets the changes that have been made to it such as diversions. When a key is pressed in the sleeping state this wakes the device up but there is no chance to apply the changes before the key press is processed by the device.
As a workaround, you could try pressing some benign key first, like shift, and then waiting for a bit for Solaar to apply the diversion.
Hubro
commented
2 years ago As a workaround, you could try pressing some benign key first, like shift, and then waiting for a bit for Solaar to apply the diversion.
That's what I'm doing, but it's easy to forget since the keyboard falls asleep relatively quickly.
Does this behavior also happen on Windows with G-Suite? Seems strange that it should be impossible to avoid. :confused:
As a sidenote, I often use my keyboard plugged in, just so I don't have to remember to charge them. I primarily bought a wireless keyboard to make it easier to clean the desk, as I can just unplug the keyboard and move it away. It's also a bonus that I only need to plug the keyboard into a charger, not necessarily the computer.
As a result, it feels pretty pointless for the keyboard to fall asleep so quickly. Is there any way to extend or disable the sleep timer on the wireless keyboards?
pfps
commented
2 years ago Agreed. I am not aware of any way to extend the time before the keyboard sleeps.
It may be that the M keys are always "diverted" (even though the Solaar documentation hints otherwise). Try creating a rule for an M key and see whether this is triggered when the key is pressed while the keyboard is asleep.
pfps
commented
2 years ago It appears that the M keys are diverted by the G-key diversion and thus will also "misbehave" when the device is sleeping.
Information
uname -srmo):Linux 5.16.10-arch1-1 x86_64 GNU/Linuxsolaar show:Describe the bug
I have enabled "Divert G Keys" and set up a rule on G5 to toggle mute on Microsoft Teams on key-down and key-up, giving me a push-to-talk key. By default, the G5 key just maps to F5.
The rule on G5 works perfectly as a push to talk key, but what keeps happening is that when I've been silent for a while and I press G5 to talk, my Microsoft Teams window reloads, kicking me out of the call.
After this happened a few times I realized it's because the keyboard falls asleep (i.e. the backlights turned off and the keyboard entry in the Solaar GUI turns grey). If I press any of the G keys at this point, their default mapping is executed instead of my custom rules. After the keyboard turns on and appears as connected in the Solaar GUI, my custom rules now work as intended.
To Reproduce Steps to reproduce the behavior:
Screenshots
Additional context I am using the "G915 KEYBOARD".