Posts by HiassofT

Unfortunately the parameters which are responsible for the bad response to repeated button presses are not configurable via config files or standard commands.

One of them, the timeout value, can be set on some IR receivers with "ir-ctl -t ...", but the xbox dvd driver has that set to the default 125ms and doesn't allow changing it. The other parameter, the IR repeat period, is set by the IR core - and as the xbox dvd driver specifies RC_PROTO_UNKNOWN it's 125ms too. The repeat period probably isn't too far off, rc-5, rc-6 and NEC have a period of about 110-115ms, but the timeout is probably far too high.

In combination this means pressing a button quicker than about 4 times a second (250ms) isn't recognized as separate button presses but interpreted as a button held down, so the normal key repeat will kick in after half a second. The key repeat settings are configurable (using ir-keytable -D ... -P ...) but that won't help you much with the case of quickly repeated button presses.

so long,

Hias

As suspected the BIOS has broken ACPI tables.

On non-broken BIOSes you should see a PNP device with ITE in it's name in dmesg, like this

[    0.998539] pnp 00:01: Plug and Play ACPI device, IDs ITE8708 (active)

Back then I tried using different acpi_os_name settings (add it to the cmdline in syslinux.cfg), as suggested eg here https://wiki.archlinux.org/index.php/dsdt but that didn't help. You could try this, too, but don't expect too much - probably not much we can do about it.

so long,

Hias

Sluggish response to multiple presses seems to be a known issue with the current driver, see the discussion here: linux: restore Xbox DVD Movie Playback Kit support by benpicco · Pull Request #3015 · LibreELEC/LibreELEC.tv · GitHub

The correct parameters (repeat period and timeout) haven't been measured and configured in the driver yet - see explanation here Re: [RFC] [PATCH] media: rc: Improve responsiveness of Xbox DVD Remote

There's not much we can do about it until someone does that, there are no "knobs to turn".

so long,

Hias

The ITE CIR receiver should be supported by Linux kernels out of the box and you should get an entry in /proc/bus/input/devices and a "rc0: ... " line in dmesg.

Check if it's enabled in BIOS settings, usually there's some entry with "CIR", on some BIOSes it's disabled by default.

A BIOS update could also help, sometimes the BIOSes have messed up ACPI tables and Linux won't detect all devices - I have an ancient P4 board here with a connector for an IR receiver and IR settings in BIOS but the ACPI tables don't list it so it's not usable in Linux (manually patching ACPI tables is a possibility, but that's a really deep rabbit hole).

If you can't get it working please post a full dmesg (dmesg | paste), maybe there are some hints in there.

so long,

Hias

Make sure you have dtoverlay=gpio-ir in your config.txt, as described in the wiki Infrared Remotes [LibreELEC.wiki] and your Harmony is configured to use the Microsoft Media Center Remote (MCE) profile, then everything should work out of the box.

so long,

Hias

If you are using LE on RPi or x86 just delete the lircd.conf file - kernel 4.19 ships with a driver for the old Xbox DVD remote/dongle so it should work fine out of the box.

so long,

Hias

You can only use one of the few defined kodi button names in Lircmap.xml - see eg the default Lircmap.xml lircmap.xml or the button translater source code irtranslator.cpp for a list of valid names.

So for radio you could use the "liveradio" button <liveradio>KEY_A</liveradio>.

For the DVD button it's probably best to map it to "eject", this will open/close the tray.

so long,

Hias

Thanks a lot for the info! This particular remote and IR receiver indeed generate very odd key codes. LibreELEC ships with a translation layer (via eventlircd) to translate some of these codes into usable ones. The 4 colour buttons seem untranslated though.

You should be able to remap the colour buttons with a Lircmap.xml file (in /storage/.kodi/userdata). eg this should get you the standard red/green/blue/yellow kodi button codes, which you can then assign via the keymap editor

<lircmap>
  <remote device="devinput">
    <red>KEY_TUNER</red>
    <yellow>KEY_AUDIO</yellow>
    <blue>KEY_GREEN</blue>
    <green>KEY_SUBTITLE</green>
  </remote>
</lircmap>

If you prefer you can also map the red button directly to kodi's video button via <myvideo>KEY_TUNER</myvideo>

To change the behaviour of the power button (which fortunately seems to use the standard KEY_POWER keycode) it's best to create a remote.xml file in /storage/.kodi/userdata/keymaps eg like this to change the power button to suspend

<keymap>
  <global>
    <remote>
      <power>Suspend</power>
    </remote>
  </global>
</keymap>

My personal preference is to get the shutdown menu displayed which you can get with <power>ActivateWindow(ShutdownMenu)</power>

so long,

Hias

Which IR receiver are you using, is it the same Belkin one as mentioned in the Kodi wiki page?

Please post the full journal output, this should give some more hints

journalctl -a | pastebinit

so long,

Hias

This is due to a bugfix in Kodi's keymap. The "EPG" / "Guide" button is meant to bring up the EPG (for live TV), as that's what most people expect. Not quite sure why it had been mapped to "context menu" before.

so long,

Hias

Create a .kodi/userdata/keymaps/remote.xml file with the following contents:

<keymap>
  <global>
    <remote>
      <power>ActivateWindow(ShutdownMenu)</power>
    </remote>
  </global>
</keymap>

so long,

Hias

At some point you configured you harmony remote, right?

That seems to have resulted in your Harmony remote sending MCE codes for up/down/left/right/play/stop/... and a Zotac code for power.

Until LE 8.2.5 Zotac codes were supported by default, in addition to MCE and a bunch of other remote codes.

In LE9.0 we cleaned that up and now only MCE and Xbox remotes are supported out-of-the-box, other remotes have to configured by users as described in the wiki Infrared Remotes [LibreELEC.wiki]

The easiest solution for you is to configure your Harmony remote to only send MCE remote codes. The alternative is to create a custom remote configuration (keytable and rc_maps.cfg) - but just switching your Harmony remote to the MCE profile is a lot easier to do.

so long,

Hias

It looks like you configured the navigation keys to send Microsoft MCE codes, but the power button to send a Zotac remote power code.

The easiest solution is to configure the power button to send a Microsoft MCE code as well, or just use the Microsoft MCE remote profile in the Harmony software.

so long,

Hias

The lightning bolt indeed means undervoltage. This can be due to an improper power supply or USB cable.

I'd recomment using the official RPi3B+ power supply, this is known to be working fine.

As undervoltage can cause all sorts of odd issues it's best to fix this one first - the CEC issue could be a consequence of undervoltage situations.

BTW: you can also check with `vcgencmd get_throttled` if any undervoltage (or overtemperature situation) occurred since bootup - you should get `0x0` printed there,

so long,

Hias

The log file only shows a "Stop" and a "Video" button press, no sign of a power button press. Hmmm.

Which remote profile are you using on your Harmony remote? Did you create any IR configuration files (lircd.conf, rc_maps.cfg) in LibreELEC?

Could you please grab the latest logfile ZIP from the Logfiles SMB share and upload it?

Then, without the IR dongle plugged in, please run the following commands:

First stop kodi and eventlircd

systemctl stop kodi
systemctl stop eventlircd

Then run

ir-keytable

and post the output.

Then run

ir-keytable -t

press the Stop button and then the Power button and post the output, too.

so long,

Hias

Can you please post a kodi debug log where you pressed the off button?

so long,

Hias

9.0.1 includes a fix so that the IR signals of Zotac remotes can be decoded properly.

What kind of remote are you using?

I'm a bit puzzled about that external IR sensor, I thought the Zotac boxes had already a builtin IR receiver.

Does your remote work at all without the external sensor? What happens if you press the power button on your remote in that case?

so long,

Hias

Das ist sehr seltsam. Hab' gerade mit meiner HifiBerry Digi Pro auf einem RPi3B+ unter LibreELEC 9.0.1 getestet und da hat alles einwandfrei funktioniert.

Die einzigen Einstellungen die ich in den Audio settings geändert hatte waren das Audio output device auf "ALSA: snd_rpi_hifiberry_digi, S/PDIF" zu setzen und Limit sampling rate auf 96kHz (mehr schafft mein DAC nicht).

Die "Output configuration" sollte auf "Optimized" stehen (das ist default), dann wird automatisch die richtige Samplerate (bis zum eingestellten Maximum) verwendet.

Hast Du bei Dir irgendwellche Einstellungen geändert? Probier's am besten mal mit den default Settings (im Zweifelsfall einfach "Reset above settings to default" in den Einstellungen auswählen), in der config.txt muss für die Karte auch nichts eingetragen werden (die hat ein EEPROM drauf und wird damit automatisch erkannt/eingebunden).

so long,

Hias