Posts by HiassofT

First of all I'd recommend updating to LE 9.2 - 8.2.5 is quite old.

To change the protocol simply use ir-keytable -p ... (leaving out the -d device) or specify the rcX device with -s rcX.

Your IR receiver is a bit limited as it contains a hardware decoder that only supports a few protocols. It should work fine with the remote that came with it but it- could well be the remotes you tried use a protocol that this receiver can't understand.

For further info also check the Wiki: Infrared Remotes [LibreELEC.wiki]

so long,

Hias

Odd, haven't seen a hang on reboot here yet. The hangs reported in the linked thread were caused by early versions of the USB firmware updater (which updated the firmware while the system was running), LibreELEC ships with a later version where updates are performed by the bootloader (recovery.bin to be more specific).

In LibreELEC settings you can't reflash the firmware if they are up to date, but you can do it manually via ssh if you like. LibreELEC includes the rpi-eeprom-update tool (same tool as on Rasbian) and you can also use it to install beta firmwares (do that at your own risk though).

To re-flash the USB firmware use the "-u" option of rpi-eeprom-update

rpi-eeprom-update -u /lib/firmware/raspberrypi/bootloader/critical/vl805-000137ab.bin

so long,

Hias

You seem to have put a lircd.conf file into /storage/.config so lirc is used - make sure the file matches the remote you are using.

You can also try running ir-keytable -p all -t, if that outputs lirc scancodes when you press buttons it means the IR protocol is supported by the kernel (the output will show you which protocol that is) and you can drop the lircd.conf file and use ir-keytable / rc_maps.cfg configuration instead (which is a lot less error-prone than using irrecord to create a lircd.conf file).

so long,

Hias

Double-check you've properly added dtoverlay=gpio-ir to /flash/config.txt - if in doubt post your config.txt

so long,

Hias

The RPi4 bootloader and the VL805 USB firmwares are both stored in EEPROMs so they will "stick" and you need to only apply them once.

The traditional RPi firmware files (start.elf, fixup.dat) are stored on SD card and loaded on boot.

so long,

Hias

Yes, it's recommended to apply these updates.

The official LibreELEC 9.2 builds only ship with the "critical" firmware updates (which are applied automatically on Raspbian) and in general it's safe to install them.

Milhouse builds and other development/test builds may contain beta firmware versions, so be careful in this case.

The VL805 update should reduce temperature quite a bit (3-5°C IIRC).

LibreELEC 9.2.1 will ship with a newer RPi firmware and kernel which will reduce (idle) temperature further. I've been testing these here the last months, all initial bugs and rough edges seem to have been ironed out and it's working fine here.

so long,

Hias

Can you test if the time is correct in current Milhouse builds? Looks like the 9.2 version ships with a bit older timezone info (early 2019), master is using latest (Sep 2019) timezone data.

so long,

Hias

This is to be expected, H264 hardware decoding is only supported up to HD resolution. 4k videos should be in HEVC/H265 format, like it's the standard for UHD BluRay.

so long,

Hias

/lib/firmware is a volatile directory in a ramdisk and re-created on every boot.

If you want to permanently add firmware files create a /storage/.config/firmware/ directory and put the files there, then reboot.

so long,

Hias

Quote from wymand

It is a pity that so many out dated and totally wrong instructions exist.

This is true, but a general problem of stuff you find on the internet - the majority is either outdated or completely wrong. Better don't google for third-party info on the net but always refer to the official documentation.

Therefore we have a wiki page with the current info - and it was linked in the first post of this thread:

Infrared Remotes [LibreELEC.wiki]

so long,

Hias

If you plan to only use it on the RPi I'd recommend the RPi TV Hat Buy a Raspberry Pi TV HAT – Raspberry Pi - it works out of the box.

so long,

Hias

The addon update PR [le92] kodi-binary-addons: update to latest Leia versions by HiassofT · Pull Request #4069 · LibreELEC/LibreELEC.tv · GitHub has just been merged, updates should be available in the repo soon.

so long,

Hias

Check the scancodes with ir-keytable -p all -t - on LE 9.2 this'll also print the protocol.

There's no real standard how the scancodes are formatted (eg lirc uses a completely different scheme than ir-keytable) and it could well be that AnalysIR uses a different one.

Also see the wiki for details Infrared Remotes [LibreELEC.wiki]

so long,

Hias

Yes.

so long,

Hias

Thanks for the hint!

I've opened a PR with a bunch of addon updates (including pvr.teleboy 18.1.8), if testing goes fine the updates should be in the LibreELEC addon repo within about a week or so.

[le92] kodi-binary-addons: update to latest Leia versions by HiassofT · Pull Request #4069 · LibreELEC/LibreELEC.tv · GitHub

so long,

Hias

Could you try to install Raspbian Desktop on a separate SD card and check if switching resolution / refresh rate with the display configuration utility causes the same issue?

This would help us to narrow down if it's an issue with LibreELEC/Kodi or the RPi firmware.

If the issue also occurs with Raspbian it's best to open a bug report here Issues · raspberrypi/firmware · GitHub

so long,

Hias

Pulling the plug while the RPi4 was running may have resulted in the settings not being saved.

Better connect the RPi4 to the TV, change the resolution to 1080p60 and then shut it down cleanly. Then pull the plugs and connect RPi4 to the AVR.

so long,

Hias

Thanks for reporting back!

Updating the AVR firmware would be worth a try, often the release note / changes are incomplete.

Can yoiu also try configuring the RPi to 1080p60 and then powering off both RPi and the AVR?

It's interesting that the initial 1080p60 mode from RPi seems to work and most issue reports I've seen so far involved resolution and/or refresh rate changes, so there's some change that using the same mode as on powerup could result in a working display.

so long,

Hias