My RF remote has stopped working after a fresh install debian-stretch Kodi v17.6 clean installation on rpi2

Help and Support Raspberry Pi
1

My c120 Air mouse has stopped working when a fresh install OSMC images based on Debian Stretch “Kodi v17.6”. the issue is that the all keybord key and the up /down /home/R-Mouse/Back button no longer work, except the gyroscope move of mouse cursor are getting valid signals.

2

To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.

Thanks for your understanding. We hope that we can help you get up and running again shortly.

3

this my log after first boot for a fresh install https://paste.osmc.tv/yovuqavawu

Appreciate any help!

4

Any suggestions? any help plz

5 
07:28:38.766 T:1925827072 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 10
07:28:38.766 T:1925827072 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 11
07:28:38.766 T:1925827072 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 12
07:28:38.766 T:1925827072 WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 13

Check this thread seems to be similar error message in there

6

I tried but it did not work

7

So you have the blacklist configured. Have you checked journalctl if they are applied?

8

I don’t understand you can explain sorry

9

Did you read through the thread I linked (which also was started by you). In there the solution seemed a blacklist that avoids it being recognised as joystick

10

I tried this method GitHub - denilsonsa/udev-joystick-blacklist: Fix for keyboard/mouse/tablet being detected as joystick in Linux but nothing

11

here is what I did
I unplug the USB dongle for my RF remote & Plug it in and run

dmesg | paste-log

New USB device found, idVendor=1d57, idProduct=ad03

I created new udev rule /etc/udev/rules.d/51-not-a-joystick.rules
sudo curl -o /etc/udev/rules.d/51-these-are-not-joysticks.rules
http://paste.osmc.io/raw/agimemukal

> # /etc/udev/rules.d/51-these-are-not-joysticks-rm.rules
> # https://github.com/denilsonsa/udev-joystick-blacklist
> # /etc/udev/rules.d/51-these-are-not-joysticks.rules
> #  Using information from https://github.com/denilsonsa/udev-joystick-blacklist
> 
> SUBSYSTEM=="input", ATTRS{idVendor}=="1d57", ATTRS{idProduct}=="ad03", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
> SUBSYSTEM=="input", ATTRS{idVendor}=="1d57", ATTRS{idProduct}=="ad03", KERNEL=="js[0-9]*", MODE="0000", ENV{ID_INPUT_JOYSTICK}=""

but still having the same problem . its only working as a mouse.

12

Any suggestions? any help plz

13

I have the same problem with the Kodi 18 LEIA Build version 17.8-158, 10 Jan 2018 and with LibreELEC (Krypton) 8.2.2 MR.
I dnot know if the problem is due to Debian stretch or Kodi version

14

We already include the ‘not joystick’ rules in OSMC by default, and I updated them recently.
Can you try reinstall OSMC and check if your adapter is blacklisted already in OSMC?

Sam

15

I will try this night and I will let you know.

16

i did a clean install 2017.12-1 release “OSMC_TGT_rbp2_2018010”
I still have the same issue

17

Please see previous suggestion

18

please explain to me how do I check if my adapter is blacklisted.

19

grep for the hardware id in udev directory or search there in the not a joystick file that is already present.

20

my hardware id

idVendor=1d57, idProduct=ad03

and I find them in /etc/udev/rules.d/999-not-a-joystick.rules
line 66 and line 67

SUBSYSTEM=="input", ATTRS{idVendor}=="1d57", ATTRS{idProduct}=="ad03", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="1d57", ATTRS{idProduct}=="ad03", KERNEL=="js[0-9]*", MODE="0000", ENV{ID_INPUT_JOYSTICK}=""