Posts by HiassofT

The fix is included in LibreELEC since mid December and I just tested with the final 9.0.0 release on RPi3B+ and it worked fine:

USB HDD with ext4 FS with root dir set to mode 2775, plugged into LE, mode still showed up at 2775, unmounted in LE, plugged into notebook, mounted and mode still was 2775.

Please retest and if you got different results tell us what exactly you did.

so long,

Hias

Just configure the Harmony to use the Microsoft Media Center (MCE) profile, this will work out of the box.

If you want to / need to keep the Zotac profile see this thread IR Remote malfunction after upgrade to LE 9.0

so long,

Hias

Thanks a lot for the detailed report!

I've prepared a fix for that (linux: add patch to fix Zotac IR remotes by HiassofT · Pull Request #3289 · LibreELEC/LibreELEC.tv · GitHub) which should be included in tonight's Milhouse builds (0203)LibreELEC Testbuilds for x86_64 (Kodi 18.0)

Could you please test if the issue is fixed with these builds?

With the fix you should see 80340xxx scancodes and an additional "toggle" indicator flipping on/off on repeated button presses instead of alternating 80340xxx/80348xxx scancodes.

so long,

Hias

It looks like we are getting odd mouse events from this remote. Can you try disabling mouse and touchscreen support in Kodi's input settings?

so long,

Hias

Also make sure you have `dtoverlay=gpio-ir` in your config.txt - the old lirc-rpi dtoverlay will no longer work - and that you disabled in-kernel decoding by creating an empty .config/rc_maps.cfg file if you want to use lirc (see the wiki page Infrared Remotes [LibreELEC.wiki] for details).

If that doesn't work please use the log file upload function in LibreELEC settings and post the URL.

In general it's recommended to re-do your IR remote config and switch to the new ir-keytable configuration scheme, it's easier and most of the time performs better than using lirc.

so long,

Hias

Configure the Harmony to use the Microsoft Media Center (MCE) profile, this will work with LibreELEC out of the box.

We dropped a bunch of remote configurations in LibreELEC 9.0 that were buggy and/or caused issues (the Zotac config is one of them).

so long,

Hias

Infrared Remotes [LibreELEC.wiki]

Quote

The option to enable / disable Lirc in LibreELEC settings has been removed as well, lircd will now be started automatically if the

/storage/.config/lircd.conf file is present.

Unless you've got a really oddball remote you don't need to use lirc at all - in-kernel decoding with ir-kleytable configuration handles most common IR protocols and is a lot simpler than creating lircd.conf files.

so long,

Hias

Netflix is software decoded so it's quite CPU intensive and in general you need to install a heatsink to prevent overheating (the thermometer icon means the CPU is getting too hot).

When using a soundcard/HAT you can use a GPIO stacking header to get more space between the RPi and the HAT so you have room for a heatsink. There are available eg from Pimoroni but I haven't tested these myself yet.

I'm using the BGA-STD-065 heatsinks from ABL (about 28x28mm, 11mm height) here on my RPi3B+s with a Cirrus Logic audio card on top - that card has a larger GPIO header so it works without a stacking header.

Netflix plays fine here in 720p without heat issues (I also have temp_soft_limit=70 in config.txt to keep the 3B+ running at 1400MHz at a bit higher temps - default is 60°C).

so long,

Hias

I recently tested that on my RPi3B+, running current LibreELEC 8.95 beta, and it worked just fine using an LG USB DVD drive.

Insert DVD, wait until Kodi recognized the disc, then select "Play DVD" to bring up the DVD menu.

I used original DVDs, so libdvdcss was very certainly in play as well.

so long,

Hias

According to the IQaudio guide Raspberry Pi Audio - IQaudIO Limited you have to add the unmute_amp or auto_mute_amp options to the dtoverlay line (see page 5)

dtoverlay=iqaudio-dacplus,unmute_amp
or
dtoverlay=iqaudio-dacplus,auto_mute_amp

so long,

Hias

You have to remove the dtoverlay=gpio-ir line from your config.txt, keep only the second one which has gpio_pin=25. Actually it'd be better to remove gpio_pull as well (that'll activate a pull-down which works against the pull-up in the IR receiver) so you only have that gpio-ir line in config.txt

dtoverlay=gpio-ir,gpio_pin=25

With the two gpio-ir dtoverlays in config.txt you'll get 2 IR receiver devices and the one without gpio_pin defaults to GPIO 18 which is needed for I2S. Depending on the order in which modules are loaded (which is rather random) either the I2S driver or the gpio-ir reciever gets the pin and the other one fails. In your log gpio-ir "won" so the I2S driver "lost" and you got no soundcard.

Jun 22 16:41:51 LibreELEC kernel: pinctrl-bcm2835 3f200000.gpio: pin gpio18 already requested by ir-receiver@12; cannot claim for 3f203000.i2s

so long,

Hias

Please use the "Upload latest Kodi log" function in the LibreELEC settings addon and post the URL. See here for details Provide Log File [LibreELEC.wiki]

It would also help if you could test with the previous LibreELEC beta releases and post which ones work. You can download them directly from one of the mirrors Mirrors [LibreELEC.wiki] - just download the LibreELEC-RPi2.arm-8.95.XXX.tar, copy it to the Update samba share and reboot.

so long,

Hias

Use pin5 - it has an external pull-up on the board so it's guaranteed to be high as soon as power is applied.

You can also use the gpio-shutdown overlay with other GPIO pins to get a shutdown button if you don't want to use pin 5 for that.

Powerup from shutdown by shorting pin 5 to GND is independent of overlays, that's a feature of the RPi (GPU) firmware which will always work.

so long,

Hias

Without external hardware you can't turn off the RPi completely. You can use eg the gpio-poweroff overlay to signal shutdown to an external circuit which then cuts power to the RPi.

so long,

Hias

Have a look at the gpio-shutdown dtoverlay https://github.com/raspberrypi/linux/blob/rpi-4.19.y/arch/arm/boot/dts/overlays/readme#l692-l721

By shorting pin5 and pin6 on the GPIO header you can shutdown LibreELEC and if you then press the button again it'll power up again.

so long,

Hias

A faulty SD card might cause those issues but most of the time it's the power supply. Amp rating on USB chargers usually doesn't mean much and/or the USB cable might not be up to the job and cause a voltage drop. The RPis, especially 3B and 3B+ are very picky about that.

You can easily check that, use the RPi running LibreELEC for a while then ssh in and run

vcgencmd get_throttled

If you get anything else than throttled=0x0 you have a problem.

so long,

Hias

I'm not 100% about the audio issues. Analog audio out of the RPi isn't great so almost no one uses it. Some time ago audio quality was improved via a firmware update (see this thread here Analogue audio testing - Raspberry Pi Forums) but this seems to have caused higher GPU load and people reported issues with HEVC playback or deinterlacing.

Going the HDMI route isn't easy, if you use HDMI then the analog video output will be disabled.

Probably the easiest and cheapest method will be to use one of the plenty RPi soundcards. Hifiberry, Iqaudio, Justboom, Pimoroni pHAT DAC and several others work out of the box (some need a dtoverlay line added to config.txt) or if you want it cheap get some RPi soundcard with a PCM5122 or PCM5102 from Asia - they should work fine as well and provide a lot better audio quality than the on-board output.

so long,

Hias

If you add overscan settings in config.txt you also have to set overscan_scale=1, otherwise the settings don't apply to kodi (they only affect the framebuffer that's shown during boot). While that removes the borders you'll still get a stretched display on 16:9 screens in anamorphic mode which you'll need to compensate for in kodi screen calibration.

So, it's better to use only kodi's screen calibration to set both the corners and the aspect ratio, that's easier to do and also avoids having 2 scaling steps (one from kodi and one from the firmware).

so long,

Hias