(2017-02-19, 18:51)bacsom Wrote: There is a fix for the KODI 17 bug. Linux systems identify T3 as a joystick.

For the fix you have to install the program here:
https://github.com/denilsonsa/udev-joystick-blacklist

Probably you also have to add your own remote to the end of the list here: /etc/udev/rules.d/ .

(2017-01-20, 00:25)julianmclean Wrote: Ok, bit of an update that may possibly help to contribute to getting the unrecognised keys on the T3 remote recognised in Linux.

Firstly, so far this has all been on my Openelec RPi2...

From reading on t'internet, I found I could use a tool called evtest to find out the scancodes for the buttons, but couldn't get this working on Openelec, so I migrated over to Libreelec and installed their system tools addon, which gave me evtest, and found me some more info on the buttons:

Code:

4 rectangles:
Event: time 1484862141.061309, type 4 (EV_MSC), code 4 (MSC_SCAN), value 7008a
Event: time 1484862141.061309, type 1 (EV_KEY), code 92 (KEY_HENKAN), value 1
Internet Explorer
Event: time 1484862204.261669, type 4 (EV_MSC), code 4 (MSC_SCAN), value c008a
Event: time 1484862204.261669, type 1 (EV_KEY), code 150 (KEY_WWW), value 1
Zoom in:
Event: time 1484862205.813901, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022d
Event: time 1484862205.813901, type 1 (EV_KEY), code 418 (KEY_ZOOMIN), value 1
Zoom out:
Event: time 1484862206.245953, type 4 (EV_MSC), code 4 (MSC_SCAN), value c022e
Event: time 1484862206.245953, type 1 (EV_KEY), code 419 (KEY_ZOOMOUT), value 1
Recent/2 rectangles:
Event: time 1484862247.603470, type 4 (EV_MSC), code 4 (MSC_SCAN), value 700bb
Event: time 1484862247.603470, type 1 (EV_KEY), code 240 (KEY_UNKNOWN), value 1

A bit more reading suggested I could drop a customer hwdb file so after finding (I think) the usb kernel modalias for the remote using:

Code:

udevadm info /dev/input/event0

..I created a hwdb file called "99-t3remote.hwdb" in ~/.config/hwdb.d/ directory:

Code:

# T3 Remote
keyboard:usb:v25A7p2402*
KEYBOARD_KEY_07008a=f8                                  # 4 Rectangles
KEYBOARD_KEY_0c008a=f9                                  # Internet Explorer
KEYBOARD_KEY_0c022d=f10                                 # Zoom In
KEYBOARD_KEY_0c022e=f11                                 # Zoom Out
KEYBOARD_KEY_0700bb=f12                                 # Recent

...which was an attempt to map the keys to something that I hoped Kodi would see - i.e. the F8 to F12 keys.

Unfortunately this doesn't seem to have worked and Kodi log still reports the same thing:

Code:

DEBUG: CLinuxInputDevice::KeyEvent: TranslateKey returned XBMCK_UNKNOWN from code(92)

Anyone got any more experience/knowledge in this area and can say if I'm getting close?

(2017-03-11, 21:31)badkarmaboy Wrote: The command "lsusb" might yield better results See third result line:

Code:

Libreelec:~ # lsusb
Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 1d57:ad03 Xenta
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

which part of this will show my remote

(2017-03-11, 22:48)badkarmaboy Wrote: Bus 001 Device 009: ID 25a7:2402

(2017-03-12, 00:03)badkarmaboy Wrote: You will have to replace idVendor and idProduct with your values:

Code:

Code:
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}=""