[SOLVED] My RF remote has stopped working after migration to Kodi v17

Thanks. I was thinking of buying a different remote but that won’t help the community either (and its not guaranteed that it won’t have the same problem).

Makes sense.

It depends on needs. The OSMC Remote is most popular, and will always be supported, but doesn’t meet everyone’s requirements. It does seem to meet WAF and children’s requirements though.

We plan to fix it soon, but it’s always hard without hardware in our hands. One user has actually purchased a remote for me off Amazon to test.

3 Likes

I am a Libreelec user myself, but we have the same problem with T3 and Krypton. The remote produces the same symptoms on Raspbian (Piplware repo) as well, but NOT on Windows.

I hope this gets fixed soon, I have the same air mouse as OP and navigating using just the gyroscope is a nightmare

1 Like

Hello,

I just bought my raspberry pi and installed kodi v17 on it last week, i bought my remote yesterday (this one) and I am getting the same problem. The air remote works but the keyboard and the buttons do not.

My logs contain the same text as Ori’s does:

WARNING: CLinuxInputDevice::RelEvent: Unknown rel event code: 13

I could provide more information if anyone has any clue how to resolve this?

I had the same problem running kodi 17.0-2 on Arch Linux (4.4.49-1-ARCH) on a raspberry pi 2.

I discovered that the kernel was misidentifying the keyboard part of the remote as a joystick.

Using information from https://github.com/denilsonsa/udev-joystick-blacklist I created the udev rule /etc/udev/rules.d/51-not-a-joystick.rules

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]*", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""

I think kodi may be only looking for specific types of input devices, that is, not joysticks.

4 Likes

Nice find @eubuleus

There have been changes to Kodi handles input, particularly with the support for games controllers now in Kodi v17.

Can anyone confirm if this also works for them?

I’ll ping Garbear who may have some ideas, as creating a number of udev rules for each affected remote to address this problem is not necessarily practical.

Sam

1 Like

Thanks @eubuleus

I can confirm that this fix works for me.

Jose

2 Likes

May be you could hold a list of list of ‘idVender:idProduct’ pairs and generate a tailored udev.rules for any that are found.

1 Like

Yes – I think that’s what we are going to need to do. We already have udev handling for some remotes and peripherals as it is.

I wasn’t aware of the GitHub project which had a list of recommend udev rules. I may consider pulling those in, although we need to be careful and make sure we don’t see any regressions.

Thanks

Sam

1 Like

Thanks @eubuleus

I can confirm that this fix works for me too

Using information from https://github.com/denilsonsa/udev-joystick-blacklist I created the 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/fazuposufu


# /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}=""
1 Like

Another thanks for @eubuleus :slight_smile:
Works fine with T3 remote now.

Thanks @eubuleus, it works fine now

I have the same issue, but with a different remote.

This is the remote I have.

I tried the udev fix. But it did not work. I’m guessing it is because the id it is referring to is different. How do I find out what the id of my remote is?

I am new to all this and trying to work it out as I go. Feel free to talk to me like a 5 year old. :slight_smile:

anyone tried with a Minix A2 light? I get it and want to upgrade but…yeah you get it :slight_smile:

From a 6 year old in this matters (I’m new to this too so, just followed github instructions) :slight_smile:

To find out “idVendor” and “idProduct” just do this (as per github page)
Unplug and plug your USB device while monitoring for kernel and udev events: “udevadm monitor -p”

You will then find neccessary IDs there, and from there just edit the file you already made :
sudo nano /etc/udev/rules.d/51-these-are-not-joysticks.rules

Again, as I’m as much new to this as you, there might be some easier procedure, but this is the way I did it to get my T3 working.

1 Like

I unplug the USB dongle & Plug it in after booting and run
dmesg | paste-log
find out your “idVendor” and our “idProduct”

Thanks you guys. That worked. All fixed now. If anyone else has the August PCR500 the idVendor =24a7 and the idProduct=2402. Thanks again :smile:

Thanks to @eubuleus and @schetz, both of which passed on critical info. After ssh into the box, monitoring the udev output by unplugging and replugging the 2.4 GHz dongle created lots of chatter, but the IDproduct and VendorID were right there. That is a solid way to discover the ID numbers you need.

I have a Lynec T5 remote, ProductID=2404 VendorID=25a7, and this worked like a champ.

For the record, I elected to create the file 51-these-are-not-joysticks-rm.rules (the ‘second’ method referred to in the github reference) manually. Autogenerating it created lots of entries I really didn’t need. After discovering the correct product and vendor ID’s, I navigated to the correct directory

cd /etc/udev/rules.d

and created the file I needed with

touch 51-these-are-not-joysticks-rm.rules

edit the file however you like (I installed vim) and added this text

# /etc/udev/rules.d/51-these-are-not-joysticks-rm.rules
#
# This file is auto-generated. For more information:
# https://github.com/denilsonsa/udev-joystick-blacklist

SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="25a7", ATTRS{idProduct}=="2402", KERNEL=="js[0-9]*", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}=""

and saved the file. I rebooted from the interface and everything worked.

Thanks to everyone. This was a slick fix.

3 Likes

Here. Use this so you don’t have to bother with nano

sudo curl -o /etc/udev/rules.d/51-these-are-not-joysticks.rules \http://paste.osmc.io/mayoqozayo.vala