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
My laptop (Surface Go 2) has built in volume up/down keys like a Smartphone or Tablet usually has. I also have a little Bluetooth camera remote that in effect is just a input device sending volumedown/volumeup events.
However, while the events of both show up in showkeys, neither of these devices are found by keyd. They neither show up in keyd monitor, nor does this:
Intel HID 5 button array is the media keys. UBeesize is the Bluetooth remote. It appears they are both detected to have no "capabilities" and therefore are ignored by keyd (?)
Question 1: Is it possible to just disable this check for capabilities? I assume it is only there for optimization, as not to listen to devices that are deemed not to send relevant input events.
Question 2: Would something similar to this PR be possible to resolve this issue? Yes, see PR #832.
The text was updated successfully, but these errors were encountered:
Garbaz
changed the title
Remapping Volume Up/Down Keys
Remapping (built-in) volume up/down buttons
Sep 9, 2024
Garbaz
changed the title
Remapping (built-in) volume up/down buttons
(built-in) volume up/down buttons ignored by keyd
Sep 9, 2024
Hi,
My laptop (Surface Go 2) has built in volume up/down keys like a Smartphone or Tablet usually has. I also have a little Bluetooth camera remote that in effect is just a input device sending
volumedown
/volumeup
events.However, while the events of both show up in
showkeys
, neither of these devices are found bykeyd
. They neither show up inkeyd monitor
, nor does this:in the
/etc/keyd/default.conf
change their behavior (while the volume up/down keys on my regular keyboard do change behavior, so the config is fine).Running
KEYD_DEBUG=2 keyd monitor
as the person in this issue does, I do get:Intel HID 5 button array is the media keys. UBeesize is the Bluetooth remote. It appears they are both detected to have no "capabilities" and therefore are ignored by
keyd
(?)Question 1: Is it possible to just disable this check for capabilities? I assume it is only there for optimization, as not to listen to devices that are deemed not to send relevant input events.
Question 2: Would something similar to this PR be possible to resolve this issue?Yes, see PR #832.The text was updated successfully, but these errors were encountered: