I've got following Remote Control:
Android TV Box Wireless Remote Control Clavier Air Mouse 2.4ghz pour KODI PC KS | eBay
It works perfect with 8.2.5, but when I use a clean install with 9.02 or 9.1.501 on my PI3 the coursor buttons do not work and the menu flickers after a coursor button is pressed. When I look into kodi.log it looks like events are repeated for 10s although the key was only presssed once on the remote:
2019-10-03 11:29:56.135 T:1937504704 DEBUG: Previous line repeats 2 times.
2019-10-03 11:29:56.135 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.135 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheelup
2019-10-03 11:29:56.136 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.140 T:1927279488 DEBUG: Previous line repeats 2 times.
2019-10-03 11:29:56.141 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.181 T:1937504704 DEBUG: Previous line repeats 3 times.
2019-10-03 11:29:56.182 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.188 T:1927279488 DEBUG: Previous line repeats 3 times.
2019-10-03 11:29:56.189 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.204 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.205 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.205 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.227 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.227 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.228 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.228 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheelup
2019-10-03 11:29:56.228 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.237 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.237 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.238 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheelup
2019-10-03 11:29:56.253 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.259 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.259 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.269 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.269 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.276 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.276 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.285 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.285 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: up, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.285 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.292 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheelup
2019-10-03 11:29:56.293 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.301 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.309 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.309 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.317 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.317 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.326 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.333 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.342 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.349 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
2019-10-03 11:29:56.359 T:1937504704 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.359 T:1937504704 DEBUG: ProcessMouse: trying mouse action wheeldown
2019-10-03 11:29:56.365 T:1927279488 DEBUG: Previous line repeats 1 times.
2019-10-03 11:29:56.365 T:1927279488 DEBUG: CLibInputPointer::ProcessAxis - scroll: down, event.button.x: 0, event.button.y: 0
In the attached file udevadm_monitor.txt please find the events I get with udevadm monitor -p when I unplug and plug the receiver.
I tried to exclude it from udev:
/etc/udev/rules.d/51-these-are-not-joysticks-rm.rules
SUBSYSTEM=="input", ATTRS{idVendor}=="2319", ATTRS{idProduct}=="00B2", ENV{ID_INPUT_JOYSTICK}=="?*", ENV{ID_INPUT_JOYSTICK}=""
SUBSYSTEM=="input", ATTRS{idVendor}=="2319", ATTRS{idProduct}=="00B2", KERNEL=="js[0-9]*", RUN+="/bin/rm %E{DEVNAME}", ENV{ID_INPUT_JOYSTICK}="
But that makes no difference.
Does anyone know how to get it working?
Thx,
Myx