Posts by HiassofT

  • Libreelec registers multiple key presses for each button on my IR remote (8.2.1 & 8.2.2)

    Lexridge the question in this thread was about an MCE remote on x64, where in-kernel decoding is used, and having Lirc enabled in addition to that will often cause double keypresses.

    You, however, seem to be using a GPIO remote on RPi using the lirc-rpi dtoverlay, which is something completely different.

    I'm not exactly sure what problem you are experiencing. There were no changes between 8.2.1 and 8.2.2 in that area and the dmesg lines you posted should be there both with 8.2.1 and 8.2.2 if you have the "dtoverlay=lirc-rpi" line in config.txt.

    Anyways, if you are using lirc-rpi it's best to switch to gpio-ir and disable Lirc in LE settings. lirc-rpi will be dropped in LE9, gpio-ir is the more modern successor (which doesn't need lircd to work, decoding is performed in the kernel). Read the wiki for details: infrared_remotes [LibreELEC]

    so long,

    Hias

  • DVB issue since LE switched to kernel 4.9.x

    jahutchi could you test if the issue also occurs on your Revo with other Linux distributions running a current kernel like Ubuntu? And if reverting the same commit fixes it there?

    Next step then would be to check if the issue also occurs if the DVB device is accessed directly (eg using VLC, Kaffeine or some other DVB player) or if tvheadend plays some part in it.

    Then that needs to be discussed with upstream (dvb driver / tvheadend / kernel maintainers).

    so long,

    Hias

  • Fernbedienung richtig anlernen.Brauche eure Hife!!!

    A step-by-step guide is available in the wiki: infrared_remotes [LibreELEC]

    If your remote is compatible to the Microsoft Media Center (MCE) remote, you just need to add the following line to config.txt:

    Code
    dtoverlay=gpio-ir

    Note that the use of lirc_rpi is deprecated and will be removed in LE9. If needed gpio-ir can still be used with lirc, you have to put your lircd.conf file into /storage/.config/ and enable Lirc in LE Settings -> Services.

    so long,

    Hias

  • Kodi won‘t react to IR Remote after a while/some sleep cycles (since LE 8.2)

    Please don't cut down logs, always upload full logs to a paste site (eg using the "paste" command in LE).

    There are quite a lot of USB errors in the snippet you posted, but without having the full log it's impossible to know if they are related to your USB IR receiver or not.

    If irw is showing button presses after resume but you don't get them in kodi you could also try disabling the kodi-lirc-suspend systemd service and see if this helps:

    Code
    systemctl mask kodi-lirc-suspend.service

    If it didn't help or made things worse use "unmask" instead of "mask" in the above command to re-enable it again.

    so long,

    Hias

  • IR Remote Keypress Problems

    AFAICT the issue you are seeing is caused by a bug / missing feature in the meson-ir driver. The in-kernel protocol decoders need to receive a trailing space (or "timeout") to know when the IR transmission is finished, and meson-ir doesn't seem to generate that.

    So what's happening is that when you press a new button meson-ir sends a rather long space to the decoder which finishes decoding of the last received IR signal (the "old button") and then goes on decoding the new signals - IOW every last button is leaking into the next button.

    Until this bug is fixed it's better to use userspace lirc instead, it does it's own timeout/decode-end handling and should work fine.

    so long,

    Hias

  • LE optimal samba conf

    With older kernels you have to add vers=2.1 to the options - the default is 1.0 (aka SMB1) and thus you get the error(95) not supported.

    eg.

    Code
    mount -t cifs -o vers=2.1,username=xxx,password=xxx //xbmc.lan/MyBookHias/ /mnt/temp/

    so long,

    Hias

  • 100% cpu lircd after installing 8.2.1

    In most cases you don't need lirc, the majority of remotes are supported directly by the linux kernel.

    It's main purpose is to support rather odd remotes that aren't supported by the kernel and to use standard remotes with older IR receiver drivers (like lirc_rpi on the Raspberry Pi) that don't offer in-kernel decoding of remote signals - therefore lirc currently ships with a default config that is similar to the kernel default IR config.

    In LE9 support for those older lirc-only IR drivers will be dropped and the plan is to use Lirc only for those "odd remotes" and only if the user installed a custom lirc configuration file.

    so long,

    Hias

  • Raspberry Pi 3 Ethernet connection keeps dropping requiring reboot

    First thing to check is to make sure you are using an adequate power supply. The official 5.1V 2.5A one is known to work fine.

    Even small voltage dips can cause the USB network chip to "fall off the bus" or lock up.

    When this has happened you could try to enable wifi in LE settings, this should allow you to get access to the RPi again and provide logfiles. Use the LE Settings addon or Samba method as described in the wiki how_to:provide_logfile [LibreELEC] - these methods include the system logs which are important to diagnose your issue (a kodi log alone won't be enough).

    so long,

    Hias

  • Classic Xbox remote control phantom clics

    You could try to alter the default lircd.conf file, there are some comments in it regarding repeats. First copy it over to /storage/.config

    Code
    cp /etc/lirc/lircd.conf.d/xbox-dvd.conf /storage/.config/lircd.conf

    Please keep in mind that the lirc_xbox driver which you are currently using for the xbox IR receiver won't be supported in LE9 - we removed it from our current development tree because it never made it upstream and started to make troubles. So you might be better off switching to a different remote or using another IR receiver (on the RPi a simple GPIO IR receiver should do fine).

    so long,

    Hias

  • remote double button press

    ati_remote is the driver responsible for handling your RF receiver. rc_core is the base remote driver and rc_medion_x10 the keymap for your remote.

    I'm not really familiar with the ati_remote driver, one thing that's a bit puzzling is that it has a repeat_delay option - usually that's handled by the input layer (you can configure delay and period eg via ir-keytable). Not sure at all what the repeat_filter option is for.

    I still suspect the core issue is bad RF reception. Mounting a receiver inside a case isn't ideal - I even had problems with a Logitech unifying receiver if it was plugged into the back of a PC (and the whole metal case shielding off quite some of the RF signals from my K400 keyboard)., Plugging it into a front USB port made a huge difference.

    so long,

    Hias