I have a Bluetooth remote control and I'd like to map its buttons to keys of the keyboard. I actually find the scancodes confusing; they're not the same as what I get on Windows 10 (a single code for each button) and it seems like there is maybe one code for button down and another for button up. Can someone confirm whether button up/down is correct interpretation? I acquired the codes using the command "showkey --scancodes" in a virtual terminal. I've looked up instructions for remapping scancodes in Debian (edit /etc/default/keyboard) but they don't deal with scancodes in the format that I have.
On Windows 10, the shutter button and the volume up button have the same scancode. They're kind of different in antiX but only because the shutter button seems to send two signals for each the volume up would send and the third code of the four contains a unique code. It would be great if antiX could treat them as different buttons.
Shutter button
0xe0 0x30 0xe0 0x30
0xe0 0xbb 0xe0 0xb0
Volume up
0xe0 0x30
0xe0 0xb0
Volume down
0xe0 0x2e
0xe0 0xb0
Back
0xe0 0x10
0xe0 0x90
Forward
0xe0 0x19
0xe0 0x99
Play/pause
0xe0 0x22
0xe0 0xa2
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
Remapping keys using scancodes (in form 0xe0 0x30)
Remapping keys using scancodes (in form 0xe0 0x30)
antiX 16, Wyse V90L thin client with VIA Eden 32-bit 800 MHz CPU and 1 GB 533 MHz DDR2
Raspberry Pi 3 B and 3 B+, both running Raspbian Stretch
We don't inherit the Earth from our parents; we borrow it from our children.
Raspberry Pi 3 B and 3 B+, both running Raspbian Stretch
We don't inherit the Earth from our parents; we borrow it from our children.