LE9.0 remote configs ir-keytable Amlogic devices

    Could someone please tell me the relation between remote.conf file and actions in kodi?


    I'm using a harmony one plus remote, configured as "minix u9" and a matching remote.conf (I guess).


    I'm using kszaq's latest stable build - 8.2.2.3


    Some buttons bring up some actions within Kodi, but not always the actions they are supposed to.


    How or where can I reassign the buttons?


    Some hints on where to start would be appreciated.

    Hey guys, i recently tried the 8.90.5 build. I did a fresh install over the previous 8.2 build. What i instantly noticed is that the IR remote is very sluggish and double/triple repeats sometimes. I did not have this issue in the 8.2 stable build, where my IR remote was working flawless and responsive.


    Device: Tanix TX3 Mini

    Quote from kostaman

    Read the opening page 1.

    I already tried "ir-keytable -D 375 -P 100" and "ir-ctl -t 50000" if that's what you mean. It made no difference, except now it repeats even more on every key input, and still very sluggish and unresponsive.


    EDIT: The sluggish and delayed key inputs seem to affect only the up/down/left/right keys. The ok/home/back/menu buttons are still snappy and responsive.

    Edited once, last by Orman ().

    Quote from Orman

    I already tried "ir-keytable -D 375 -P 100" and "ir-ctl -t 50000" if that's what you mean.

    Quote from HiassofT

    Another knob you can turn to improve remote response is the idle timeout. By default it's set to 200ms on Amlogic / meson-ir, which is quite long - other IR receiver drivers use 125ms.

    kostaman I've already tried nearly every combination of keytable delay/period and idle timeout. It's still impossible to get it as smooth as the 8.2 build :(

    Edited once, last by Orman ().

    So I upgraded to 8.90.6 alpha on my Mecool m8s pro+ box (used LibreELEC-S905.arm-8.90.6.img.gz file) onto external microSD card. And the remote does not work. Updated the dtb.img tree to the latest from the update directory (gxl_p212_2g.dtb). Also renamed that file to dtb.img. But the remote still does not work. So maybe it is not baked in as per previous version. I then tried to create the keymap and rc_map.cfg file.


    SSH into Libreelec and stopped kodi and LIRC in SSH successfully.


    Ran "ir-keytable -t" command and got the following message -

    "/sys/class/rc/: No such file or directory

    No devices found"



    Checked using Winscp and true enough there is no /sys/class/rc directory. Obviously I also cannot create that directory manually. Any help or suggestions?

    Edited once, last by sirzur ().

    The mecool remote configuration is still integrated into the image

    No devices found means you are not using the correct DTB

    I'm guessing you have LE installed on internal?

    Adamg - thanks for your builds and keep up the good work


    Sorry - I edited the post later to say that I have it installed on microSD card. I dont know which other DTB to use. The Mecool m8S Pro+ that I have is definitely S905X chip and it is also definitely 2GB RAM - I checked in previous versions of your alpha build. The other DTBs are for kvim, lepotato, nand, slowemmc - none of which describes my player.


    Any suggestions. Does the error message also suggest incorrect DTB? Also of note is that the CEC still works, so I can still control using the TV remote

    sirzur use the DTB from here

    Just double check you are overwriting your existing one because that error message definitely indicates you are using an older DTB

    Thanks.


    An update


    Yes I downloaded the DTB from that directory. I also downloaded all the 2GB DTB and the generic 1GB and 3GB DTB and unsuccessfully tried them all. On some of the DTB, it would not even boot up pass the Mecool screen, so I can assume that the DTB is being overridden


    So I finally re-wrote the 8.90.6 image to a new microSD card and the remote worked straight away. Looks like the update process from 8.90.5 to 8.90.6 (via placing the newest in the update directory) must have messed something up. I re-did the update 3 times, each time unsuccessfully.


    One message that I got during the update process - "Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit". Maybe that affected the update process.


    TL:DR - If having a problem (whether remote or TVheadend) after updating to latest, best to start from scratch

    Quote from sirzur

    One message that I got during the update process - "Dirty bit is set. Fs was not properly unmounted and some data may be corrupt. Automatically removing dirty bit". Maybe that affected the update process.

    Possibly, I have seen that error message myself before.

    I'm happy to hear you got it sorted anyway.

    As much as I would like upgrading to work seamlessly, it is not always possible, especially with the Alpha releases there has been too many changes recently.

    Sky+ HD Remote

    skyremote.zip


    it needs the timing adjusting otherwise you get double clicks,this is achieved with
    # ir-ctl -t 50000

    the post below lists how to make it survive restarts

    Quote from HiassofT

    autostart.sh should work, but it' be better to create a udev rule for that. Copy /usr/lib/udev/rules.d/70-input-repeat.rules to /storage/.config/udev.rules.d, and then add this line at the end (all in a single line, after the LABEL="end" line):


    Code
    ACTION=="add|change", KERNEL=="lirc*[0-9]", DRIVERS=="meson-ir", RUN+="/usr/bin/ir-ctl -d $devnode -t 50000"


    so long,


    Hias

    Edited 2 times, last by deanochips ().