Posts by tabensvktefxebyk

    LibreELEC solution requires the libinput misclassification fix first regardless of whether you use uinput, JSON-RPC or LIRC
    Libreelec deoesn't have in itself a c++ compiler, as far as I'm aware. But Debian does. But the issue still seems to stem from the misclassing of the remote as a touchpad

    I think the misclassification is also the issue in debian.

    The code provided creates a NEW generic usb keyboard device which IS NOT misclassified and Kodi will respond to.

    The keycodes Kodi is responding to from that device are just captured from the Zidoo device and re-sent (forwarded).

    Libre doesn't need to compile the code, compile the code elsewhere and copy the binary to Libre

    gcc uinput-forwarder.c -static -o uinput-forwarder


    or cross compile to aarch64

    aarch64-linux-gnu-gcc uinput-forwarder.c -static -o uinput-forwarder

    or cross compile to arm32 (the print_event function needs rework for arm32 but it's only for debugging so can be remove)

    arm-linux-gnueabihf-gcc uinput-forwarder.c -static -o uinput-forwarder


    3 Solutions to the same problem, each with merit

    Here I got AI to write it.


    Tested working on debian with Zidoo V12.

    Run as root with the Zidoo V12 Keyboard device as arg 1: sudo ./uinput-forwarder /dev/input/eventX

    I had to chmod /dev/uinput

    sudo chmod +0666 /dev/uinput

    since libre is running as root already drop the sudo for libre


    I have the same issue with the same remote when paired to Debian.

    The hwdb provided by chewitt on post #5 will change what events evtest sees.

    Under no circumstances does Kodi see any input from this remote, debug log never triggers "HandleKey".

    At the same time Kodi only ever sees the device "Zidoo-V12 Remote Mouse" and not the Keyboard.

    A FireTV remote will pair and work normally though so at least I know in general that bluetooth and bluetooth remotes work.


    The only place I can get this remote to work is under CoreELEC and I don't know why.


    I suspect there is a classification problem in the device type or there is some permission issue.

    All I have are suspicions though as I haven't been able to fix it.


    I posted about this on the Kodi forum 21 days ago to be met with the usual silence or vague declarations of what to use instead.


    Slightly off topic as this has to do with this remote when used with linux but not necessarily LibreELEC.