Something has happened recently and two buttons of my standard RF remote (“Info” and “Options (Hamburger menu)”) stopped to be recognized by KODI on my OSMC 4k+ box.
In order to troubleshoot I have plugged in the receiver into my Windows box and started an utility to show keycodes. It shows that “Info” key generates letter “I” (key code 73), and “Settings” button generates letter “C” (key code 67). So, it looks like the remote and receiver are both ok.
When I plug the receiver into OSMC 4K+ box, and start
ir-keytable -t --device=/dev/input/by-path/platform-xhci-hcd.0.auto-usb-0:2:1.0-event-kbd
it also shows the same:
1586706642.490252: event type EV_MSC(0x04): scancode = 0x7000c
1586706642.490252: event type EV_KEY(0x01) key_down: KEY_I(0x0017)
1586706642.490252: event type EV_SYN(0x00).
1586706642.498245: event type EV_MSC(0x04): scancode = 0x7000c
1586706642.498245: event type EV_KEY(0x01) key_up: KEY_I(0x0017)
1586706642.498245: event type EV_SYN(0x00).
1586706643.650287: event type EV_MSC(0x04): scancode = 0x70006
1586706643.650287: event type EV_KEY(0x01) key_down: KEY_C(0x002e)
1586706643.650287: event type EV_SYN(0x00).
1586706643.658266: event type EV_MSC(0x04): scancode = 0x70006
1586706643.658266: event type EV_KEY(0x01) key_up: KEY_C(0x002e)
1586706643.658266: event type EV_SYN(0x00).
But Keymapper plugin in KODI shows both “Info” and “Settings” keys as code 61952.
What can it be?
Can you try rebooting your Vero and see if that fixes the problem? If not please upload full logs.
We have updated these remotes to be seen as a keyboard and to remedy issues with some keyboard languages (specifically i, c, +, and = depending on language) we remap these keys with udev. To enable this remap it sometimes requires one or two full reboots of the operating system. This is invisible to people using English language keyboards (as both old and new keys are mapped the same) but for everyone else the reboots should make the info and menu keys start showing up as parentheses/brackets. You can find out more about this here…
You have a gen.xml in both your master profile as well as the profile you are logged into. This is not the issue though.
Can you give me the output of… ls -l /etc/udev/hwdb.d/*.hwdb && cat /etc/udev/hwdb.d/*.hwdb
The Kodi side of things looks correct but it looks like the system level remap is not loading. If you set settings>system>input>keyboard layouts> to one of the English ones those two buttons should start working in the meantime.
It can be I have those xml files, but I never created them myself.
The output you requested is:
osmc@osmc:~$ ls -l /etc/udev/hwdb.d/.hwdb && cat /etc/udev/hwdb.d/.hwdb
-rw-r–r-- 1 root root 451 Mar 13 14:35 /etc/udev/hwdb.d/osmcrf.hwdb
They were created when you used the keymap editor add-on.
Thanks for that. Everything looks correct other than the keys not remapping as they should. If you change the keyboard layout to one of the English ones those two buttons work, correct? As for why the remap is not working I think I will have to hand this over to @sam_nazarko or someone else who has a more in depth knowledge of Linux.
It is the system level remap that is not working, not the Kodi keymap. As you can see above the proper file is in place and correct, and the log he posted earlier let me see that the system was picking it up with the correct vid/pid, but in the Kodi log I can also see that those two keys are not being picked up as being remapped to parentheses. Kodi is also picking up the remote correctly and loading the custom keymap, but without the system level remap it seems he is hitting the language issue. My issue is that I don’t know how to troubleshoot why that udev remap is not happening like it has for everyone else.
This is strange, on my system the device 1-event-mouse is responsible for the keys info, Hamburger button (like this term), back, play, stop, fast forward, fast backward.
Must be the new OSMC remote with volume buttons at the bottom.
@ilya We think that you managed to exchange the RF receivers of an old remote with the new one which made the current troubles.
Best for the future would be to replace back the receivers to the appropriate remotes and re-pair those. From that point on no special should be required anymore.
