Hello,
I am using OpenSUSE Tumbleweed with KDE Plasma (Wayland) on a PC connected to my TV as a kind of HTPC solution.
I recently bought a G20BTS. It is basically a BTLE remote control with some of the typical media buttons (play, pause, mute, etc) and an integrated Gyro mouse that can be toggled with an extra button.
The pairing was no problem and the gyro mouse is working just fine out of the box. But I’m having trouble getting the media key to work. Strange thing is that every keypress is correctly recognized when I check with evtest:
user@htpc:~> sudo evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
[...]
/dev/input/event27: G20BTS Keyboard
/dev/input/event28: G20BTS Mouse
/dev/input/event29: G20BTS
[...]
Select the device event number [0-29]: 27
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x1d5a product 0xc081 version 0x0
Input device name: "G20BTS Keyboard"
Supported events:
[...]
Event code 113 (KEY_MUTE)
[...]
Testing ... (interrupt to exit)
Event: time 1764839720.952000, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e2
Event: time 1764839720.952000, type 1 (EV_KEY), code 113 (KEY_MUTE), value 1
Event: time 1764839720.952000, -------------- SYN_REPORT ------------
Event: time 1764839721.144087, type 4 (EV_MSC), code 4 (MSC_SCAN), value c00e2
Event: time 1764839721.144087, type 1 (EV_KEY), code 113 (KEY_MUTE), value 0
Event: time 1764839721.144087, -------------- SYN_REPORT ------------
However, nothing happens after pressing the mute key as shown above. When I watch my normal keyboard with evtest and press the same key, I also get the same keycode 113 (KEY_MUTE) and the system is muted / unmuted.
What seems a bit strange to me is that the remote is
what seems strange to me is that the “keyboard-part” of the device is listed with “tablet-pad” capability only by libinput:
user@htpc:~> sudo libinput list-devices
[...]
Device: G20BTS Keyboard
Kernel: /dev/input/event27
Id: bluetooth:1d5a:c081
Group: 15
Seat: seat0, default
Capabilities: tablet-pad
Tap-to-click: n/a
Tap-and-drag: n/a
Tap button map: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: n/a
Middle emulation: n/a
Calibration: n/a
Scroll methods: none
Scroll button: n/a
Scroll button lock: n/a
Click methods: none
Clickfinger button map: n/a
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: n/a
Rotation: n/a
Area rectangle: n/a
Pad:
Rings: 0
Strips: 0
Dials: 0
Buttons: 10
Mode groups: 1
Group 0:
Modes: 1
Buttons: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9
Device: G20BTS Mouse
Kernel: /dev/input/event28
Id: bluetooth:1d5a:c081
Group: 15
Seat: seat0, default
Capabilities: pointer
Tap-to-click: n/a
Tap-and-drag: n/a
Tap button map: n/a
Tap drag lock: n/a
Left-handed: disabled
Nat.scrolling: disabled
Middle emulation: disabled
Calibration: n/a
Scroll methods: button
Scroll button: BTN_MIDDLE
Scroll button lock: disabled
Click methods: none
Clickfinger button map: n/a
Disable-w-typing: n/a
Disable-w-trackpointing: n/a
Accel profiles: flat *adaptive custom
Rotation: 0.0
Area rectangle: n/a
[...]
Also the button count (10) seems to be too low, as the device has in fact 17 buttons that are all reported correctly with a matching keycode to evtest as shown in the first example with the mute button.
If I do a debug with libinput and press some of the buttons, I get simply nothing. enabling the gyro mouse instantly reports POINTER_MOTION events, but again: the gyro mouse is working fine ad is not part of this problem.
user@htpc:~> sudo libinput debug-events
[...]
-event27 DEVICE_ADDED G20BTS Keyboard seat0 default group15 cap:P left buttons:10 strips:0 rings:0 mode groups:1
-event28 DEVICE_ADDED G20BTS Mouse seat0 default group15 cap:p left scroll-nat scroll-button
event28 POINTER_MOTION +10.542s 0.00/ -0.30 ( +0.00/ -1.00)
event28 POINTER_MOTION 2 +10.553s 0.00/ -0.73 ( +0.00/ -1.00)
Is there anything I can do to make this thing work? to me it seems like it can’t be that hard, since the keycodes are already reported correctly. I just don’t get it why they don’t trigger the usual action as they do on my normal keyboard. Any help would by appreciated, if further logs are required just let me know.
regards,
cnrd
