Fix for Xiaomi bluetooth remote with nonworking button.

patric · November 9, 2022 at 11:28 PM

Hi,

Wanted to report a incorrect configuration for a Xiaomi remote and a fix for it. Documenting this fairly detailed to assist anyone else that may have a similar issue.

This is a guide on how to remap this invalid keycode. See "70-local-keyboard.hwdb" part for what should be added to libreelec's defaults.

# cat /proc/bus/input/devices

I: Bus=0005 Vendor=2717 Product=32b9 Version=4a4c

N: Name="Xiaomi RC Consumer Control"

P: Phys= ......................

S: Sysfs=/devices/virtual/misc/uhid/0005:2717:32B9.0003/input/input8

U: Uniq= ......................

H: Handlers=kbd event1

B: PROP=0

B: EV=13

B: KEY=50 0 0 0 0 0 38200 2 0 0 0 0 0 3000 d8011001 1c1680 0 0 0

B: MSC=10

I: Bus=0005 Vendor=2717 Product=32b9 Version=4a4c

N: Name="Xiaomi RC Keyboard"

P: Phys= ......................

S: Sysfs=/devices/virtual/misc/uhid/0005:2717:32B9.0003/input/input10

U: Uniq= ......................

H: Handlers=sysrq kbd leds event2

B: PROP=0

B: EV=120013

B: KEY=10000 7 ff9f207a c14057ff febeffdf ffefffff fff80f80 3c00f002

B: MSC=10

B: LED=1f

Default mapping of the button.

# systemctl stop kodi

# /storage/.kodi/addons/virtual.system-tools/bin/evtest

....

Event: time 1668034708.559812, -------------- SYN_REPORT ------------

Event: time 1668034708.717304, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041

Event: time 1668034708.717304, type 1 (EV_KEY), code 28 (KEY_SELECT), value 0

Event: time 1668034708.717304, -------------- SYN_REPORT ------------

But to work with kodi this needs to be mapped to KEY_ENTER and it defaults to KEY_SELECT.

# udevadm test /devices/virtual/misc/uhid/0005:2717:32B9.0003/input/input8 2>&1 | grep ^MODALIAS

MODALIAS=input:b0005v2717p32B9e4A4C-e0,1,4,k72,73,74,80,8C,90,9B,9C,9E,9F,AC,AD,161,189,18F,190,191,244,246,ram4,lsfw

Create, or update, the file /storage/.config/hwdb.d/70-local-keyboard.hwdb with the following entry. Device-identifier (red) you get from udevadm and the keycode (green) comes from evtest.

evdev:input:b0005v2717p32B9e4A4C*

KEYBOARD_KEY_c0041=enter

Reload udev rules, or just reboot.

# udevadm hwdb --update
# udevadm trigger -s input

and now i got a working Xiaomi remote.

**chewitt** · November 13, 2022 at 5:06 AM

https://github.com/LibreELEC/LibreELEC.tv/pull/7122 <= if this gets merged it should be in LE11 nightlies and future releases

Glennza · December 2, 2022 at 12:34 AM

Thanks for solving this problem. I used your instructions to do the same for my G20BTS remote. However; "70-local-keyboard.hwdb" didn't work for me so I added the lines to the existing "99-osmcrf.hwdb". The README file in that folder states that "

your files must be named 99-xxxxx.hwdb", so I don't know if that's why it didn't like it? I am on 11 nightly (Dec1).

It's this one, if anyone else need to do the same

G20BTS

evdev:input:b0005v2B54p1600e0000*

KEYBOARD_KEY_c0041=enter

patric · December 5, 2022 at 7:03 PM

Just did this for a BT remote from a "Nvidia Shield TV" (from around ~2015) and it works as expected with latest LibreELEC.

chewitt

It seems like multiple Android-box remotes use KEY_SELECT for the "ok" button while Kodi expects "Enter" for selecting things.

Maybe LibreELEC should add a default config for BT remotes so c0041 gets mapped "enter"?

Code

LibreELEC:~ # cat /storage/.config/hwdb.d/70-local-keyboard.hwdb
evdev:input:b0005v0955p7213e0002*
 KEYBOARD_KEY_c0041=enter

Code

I: Bus=0005 Vendor=0955 Product=7213 Version=0002
N: Name="SHIELD Remote"
P: Phys=**************
S: Sysfs=/devices/virtual/misc/uhid/0005:0955:7213.0002/input/input1
U: Uniq=**************
H: Handlers=kbd event0 
B: PROP=0
B: EV=13
B: KEY=600 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 2000000 1010 40000000 c1680 0 0 0
B: MSC=10

# /storage/.kodi/addons/virtual.system-tools/bin/evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:    SHIELD Remote
Select the device event number [0-0]: 0
Input driver version is 1.0.1
Input device ID: bus 0x5 vendor 0x955 product 0x7213 version 0x2
Input device name: "SHIELD Remote"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 103 (KEY_UP)
    Event code 105 (KEY_LEFT)
    Event code 106 (KEY_RIGHT)
    Event code 108 (KEY_DOWN)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 158 (KEY_BACK)
    Event code 164 (KEY_PLAYPAUSE)
    Event code 172 (KEY_HOMEPAGE)
    Event code 217 (KEY_SEARCH)
    Event code 353 (KEY_SELECT)
    Event code 713 (BTN_TRIGGER_HAPPY10)
    Event code 714 (BTN_TRIGGER_HAPPY11)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)
Event: time 1670266030.397679, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041
Event: time 1670266030.397679, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1

Display More

**chewitt** · December 6, 2022 at 9:10 AM Best Answer

Quote from patric

Maybe LibreELEC should add a default config for BT remotes so c0041 gets mapped "enter"?

It's not possible (and wrong) to assume all devices have the same mapping. That said, I'll have a scout on the interwebs for other distro's lists of BT remotes and see if we can increase coverage in our default/embedded list.

Juiceycow · December 30, 2022 at 2:01 AM

Thanks for the thread guys, the same issue has been driving me nuts ever since buying a G20.

Quote from Glennza

Thanks for solving this problem. I used your instructions to do the same for my G20BTS remote. However; "70-local-keyboard.hwdb" didn't work for me so I added the lines to the existing "99-osmcrf.hwdb". The README file in that folder states that "
your files must be named 99-xxxxx.hwdb", so I don't know if that's why it didn't like it? I am on 11 nightly (Dec1).
It's this one, if anyone else need to do the same
G20BTS
evdev:input:b0005v2B54p1600e0000*
KEYBOARD_KEY_c0041=enter

Display More

I picked up a similar WeChip G20.

Couldn't get evtest working, but got enough information from running cat /proc/bus/input/devices

Created the 70-local-keyboard.hwdb file with the code below and it worked OK

Code

evdev:input:b0003v4842p0001*
 KEYBOARD_KEY_c0041=enter

ElGato · January 11, 2023 at 11:55 AM

OK, so where does this file need to be on Pi4, struggling to find location. Just bought a new G20 and have this issue, strange thing is I have an existing G20 I've had for a couple years and it's OK

hagaygo · February 9, 2023 at 5:51 AM

Hi,

I recently got a sofabaton u1 universal remote, it works kinda o.k with IR mode with my libreelec 10.0.4 and a MCE IR receiver.

It also supports Bluetooth , so i paired it with the RPI 4 Bluetooth and partially working.

Navigation , volume and few more buttons works great, but as mentioned here OK button does not work.

I followed the instruction here and added the following lines to the hwdb files :

evdev:input:b0005v00C0p0000e0000*

KEYBOARD_KEY_c0041=enter

And it still did not work.

I think that the remote does not send c0041 , evtest shows nothing when i press OK (it shows for other working buttons like navigation or volume).

Does it mean the remote indeed sends nothing for those buttons ? or evtest shows only registered mapping and i need to use something else to show raw commands ? (like IRW for IR commands)

Thanks in advance.

hagaygo · February 9, 2023 at 8:00 PM

Just an update.

Did more digging and found out that the sofabaton app can remap every button on the remote to a keyboard button so i just mapped the OK button as enter button (and the other remote keys) and so far it is working great.

Norrin-Radd · October 12, 2023 at 2:40 PM

Hi,
i've connected an air mouse (G10 Pro) via Bluetooth to my Chromebook running Kodi 20 (installed from google play).
The air mouse works great without any configuration, EXCEPT that the OK button doesn't work.
Same behaviour as mentioned above for the G20BTS

i couldn't find any .hwdb file under Android.

i was wondering if anybody can help me to get the mapping done under ChromeOS (Android)

THX

**chewitt** · October 13, 2023 at 7:02 AM

There aren't many Android users in this forum (for obvious reasons). Better to ask in the Kodi forum or an Android forum.

m1s3rys1gn4l · June 8, 2024 at 9:46 PM

Quote from Glennza

Thanks for solving this problem. I used your instructions to do the same for my G20BTS remote. However; "70-local-keyboard.hwdb" didn't work for me so I added the lines to the existing "99-osmcrf.hwdb". The README file in that folder states that "
your files must be named 99-xxxxx.hwdb", so I don't know if that's why it didn't like it? I am on 11 nightly (Dec1).
It's this one, if anyone else need to do the same
G20BTS
evdev:input:b0005v2B54p1600e0000*
KEYBOARD_KEY_c0041=enter

Display More

can you tell me where is this file located 99-osmcrf ?

**chewitt** · June 9, 2024 at 4:59 AM

It was located in /storage/.config/hwdb.d but I did some searching on the internet among other distros and consolidated all the ok button hwdb entries I could find into a single file; including the OSMC remote changes. Once that was merged the 99-osmcef.hwdb file wasn't needed anymore. You can still create your own files there.