I recently setup OSMC on my Raspberry Pi 3 and everything went smooth except that my Justboom remote middle button doesnt work while in keyboard mode. When I switch it over to being a mouse it works just fine. Using the mouse function is just frustrating as hell! I can remember that this also happened last summer/spring after I upgraded my previous Raspberry Pi with OSMC and Kodi.
What I have tried is this #1 Using the keymapper app from the add ons to map the middle button as “Select”. It does pick up that I press the button and create a keymap file, but it does nothing.
#2 Using showkey to figure out if the button pressing is doing anything. It picks this up
keycode 353 press
keycode 353 release
#3 evtest /dev/input/event3 picks up the button while in keyboard mode
Event: time 1583429060.543564, type 4 (EV_MSC), code 4 (MSC_SCAN), value c0041
Event: time 1583429060.543564, type 1 (EV_KEY), code 353 (KEY_SELECT), value 1
Event: time 1583429060.543564, -------------- SYN_REPORT ------------
I am certain that the remote is working, but for some reason it is not being mapped correctly. I am comfortable messing around in the command line through SSH, but I have quite limited knowledge on linux. What can I do to figure this out? Any help is appreciated!
In the mean time, I tried mapping the mute button as Select through the key mapper program and it worked! I dont understand why this is allowed but the middle button not. Is something over riding the gen.xml file or has higher priority?
This is an erroneous result. From what I have been able to gather there is no valid code longer than five digits. This can also happen in Keymap editor if you hold down the button instead of just doing a short press.
I don’t think Kodi can currently pick up a key if this code number is showing more than 255. At least that is how i’m reading this issue…
To fix this I think the key would need to be remapped to “enter” with udev.
Note that there must be exactly one space before the “KEYBOAR…” and the file must not have the execute permission set on it. If your trying to reload it with those update and trigger commands that will probably not work. I had to reboot for it to actually take. You could have probably saved yourself some effort if you replied to the pm I sent you three days ago.
Indeed. This permission would not normally be set if you just used nano and made the file in place. I happened to have copied one of these files from my PC and managed to somehow get that permission set which kept the file from working. I figured it would be prudent to pass along a known failure point.