Posts by ghtester

Another solution could be to use irexec and map a script to some IR remote control key. The configuration is very simple and it works great.

Post

RE: Remote Control

For running scripts / commands by IR remote I would recommend go this way, it's reliable and easy to (re)configure, especially if you can map buttons unused by Kodi (use search to find some more examples here):



echo /usr/bin/irexec -d /storage/.config/lircrc >> /storage/.config/autostart.sh

And some example of lircrc config file:

/storage/.config/lircrc :

begin

prog = irexec

button = KEY_A

config = kodi-send --button=a

end

begin

prog = irexec

button = KEY_TITLE

config = /storage/signalshow/sigshow.sh

end

…

ghtester

January 13, 2021 at 6:20 PM

Hopefully you won't brick your RPi 4B (even though you install a bad bootloader and your RPi 4B does not boot, it's possible to create a recovery micro SD card which can fix it) but I think it won't help you.

Please note the firmware (which is located on LE filesystem) must support the RPi 4B hardware release. As RPi 4B v. 1.4 is newer than LE 9.2.6 build (and there are significant HW differencies between old and new RPi 4B revisions), it probably won't work with new RPi 4B as the firmware in LE 9.2.6 is simply too old. So you may try to replace the firmware files on LE 9.2.6 filesystem but who knows if it ever helps...

Instead I would upgrade the bootloader to latest stable (pieeprom-2021-12-02.bin) and run LE >= 10.

I wouldn't do it but it's up to you... Try this:

cd /tmp
wget -O pieeprom.bin -c https://github.com/raspberrypi/rpi-eeprom/raw/master/firmware/stable/pieeprom-2020-09-03.bin
rpi-eeprom-config pieeprom.bin > bootconfDefault.txt
# default config
cat bootconfDefault.txt
vcgencmd bootloader_config > bootconf.txt
# current config
cat bootconf.txt
rpi-eeprom-config /tmp/pieeprom.bin --config /tmp/bootconf.txt --out /tmp/pieeprom
rpi-eeprom-update -d -f /tmp/pieeprom
reboot
#

Please note you may need to change the bootloader config as there're some changes in recent bootloader revisions.

Some IR remote controls generate two different scan codes for the same key (when you repeat pushing it). Check with ir-keytable -t command if that's your case. Then you need to add both scan codes for the appropriate command to keymap file (so it should contain two lines for each command).

I am not using it but perhaps you could try to search and read something about Audio Profiles:

libreelec audio profiles - Google Suche

The same issue on LE 11 Nightly 20220106.

It's very annoying when the Audio is lost and can't be restored without losing Timeshift data.

You need to enable the appropriate Kodi settings:

Services - Control - Allow remote control via HTTP option

On recent LE 11 nightly builds (from about 20211224) I am experiencing the USB resets which are fatal due to DVB-T2 USB & USB/SATA adapters connected.

It looks an old bug already fixed couple months ago is back in the 5.15.10 kernel, at least on RPi 4B with TVheadend 4.2 / 4.3 & Tvheadend HTSP Client.

Usually the USB reset happens after DVB-T2 channel switch to another one. It happens randomly but quite often.

RPi 4B/2GB, bootloader 2021-07-06 - running from HDD with USB/SATA adapter, Tvheadend 4.3, LE nightly 20211231

[ 9807.686787] rpivid feb10000.codec: PPS changed

[ 9807.738452] rpivid feb10000.codec: PPS changed

[ 9807.850504] rpivid feb10000.codec: rpivid_h265_stop

[ 9809.614406] rpivid feb10000.codec: rpivid_h265_start: (1024x544)

[ 9809.618317] rpivid feb10000.codec: SPS changed

[ 9809.618341] rpivid feb10000.codec: PPS changed

[ 9809.618374] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[11768.812800] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[11770.511944] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[11815.566272] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[11818.211815] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[11818.211848] rpivid feb10000.codec: Missing DPB ent for col

[11818.213154] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[11818.214488] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[11818.215856] rpivid feb10000.codec: Missing DPB ent 1, timestamp=0, index=-1

[13062.011359] rpivid feb10000.codec: Missing DPB ent 0, timestamp=0, index=-1

[14552.768050] rpivid feb10000.codec: rpivid_h265_stop

[14555.261658] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[14555.268395] usb 1-1.2.2: dvb_usb_v2: rc.query() failed=-71

[14555.338220] usb 1-1.3: device descriptor read/64, error -71

[14555.461968] usb 1-1.2: USB disconnect, device number 3

[14555.461999] usb 1-1.2.1: USB disconnect, device number 6

[14555.521486] usb 1-1.3: device descriptor read/64, error -71

[14555.701488] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[14555.729626] usb 1-1.2.2: USB disconnect, device number 7

[14555.774851] usb 1-1.3: device descriptor read/64, error -71

[14555.954846] usb 1-1.3: device descriptor read/64, error -71

[14556.135180] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[14556.135383] usb 1-1.3: Device not responding to setup address.

[14556.341314] r820t 23-003a: r820t_write: i2c wr failed=-19 reg=0c len=1: f1

[14556.341510] usb 1-1.3: Device not responding to setup address.

[14556.547955] usb 1-1.3: device not accepting address 4, error -71

[14556.621294] usb 1-1.3: reset high-speed USB device number 4 using xhci_hcd

[14556.621518] usb 1-1.3: Device not responding to setup address.

Also observed on

RPi 4B/4GB, bootloader 2021-12-02 - running from SD card, Tvheadend 4.2, LE nightly 20211231

Of course I am using the hand made fork cable so the HDD is powered from 5V PSU, not from the USB port at all. The USB reset was not an issue with earlier LE builds, it looks that updated kernel may have some bugs.

The occasional crashes / kernel panic encountered on LE Nightly 20211224 & RPi 4B.

Some crashes were due to unexpected USB reset (I am running LE from HDD connected through USB/SATA adapter so the USB disconnect leads to total crash). The current LE Nightly build is less stable than before.

The same issue on LE 11 Nightly 20211215.

Sometimes the Audio stream is not detected (Audio stream = None in Audio settings) after LE start (Play TV on startup is configured in Interface menu) or after a channel switch and the sound is silent (it does not matter if the Allow passthrough option is enabled or disabled in Audio settings).

Regarding to possible HDD sleep, look at this thread - maybe you can play with the hdparm a bit to disable that feature etc.

Thread

HDD not spinning down/idle/sleep

Hi everyone,

Bit of a beginner with LE

I have installed LE on SD card on an amlogic 905X box. Works perfectly, with the exception that the box no longer lets my external HDD go to sleep/idle/spin down (not sure exactly which term to use but it is still making noise and sounds like the hdd is active even when LE is shutdown).

Before LE was installed on the SD, i was using KODI on android, and my external hdd would idle/sleep/spin down after a period of time, i also noticed it also does this when…

DMG

April 4, 2017 at 12:16 PM

You may also try the latest LE 11 Nightly build to see if the issue persists...

Index of /

Yeah I know, thank you but I believe I should be able to do it without opening the box (a non-standard, hand-made so the SD card slot is inside )

Thanks for the confirmation.

Yes I am booting from HDD connected to USB/SATA adapter. The problem is the config is part of the bootloader so now it's locked forever... :-]

I'll try to look at the script...

Unfortunately it still does not work on my RPi 4B / 2GB & LE 11 Nightly 20211203 (even if performed manually by rpi-eeprom-update -f /tmp/pieeprom)

LE:~ # FIRMWARE_RELEASE_STATUS=stable rpi-eeprom-update -a

*** INSTALLING EEPROM UPDATES ***

BOOTLOADER: update available

CURRENT: Tue Jul 6 10:44:53 UTC 2021 (1625568293)

LATEST: Mon Nov 22 11:23:32 UTC 2021 (1637580212)

RELEASE: stable (/usr/lib/kernel-overlays/base/lib/firmware/raspberrypi/bootloader/stable)

Use raspi-config to change the release.

VL805_FW: Dedicated VL805 EEPROM

VL805: up to date

CURRENT: 000138a1

LATEST: 000138a1

CURRENT: Tue Jul 6 10:44:53 UTC 2021 (1625568293)

UPDATE: Mon Nov 22 11:23:32 UTC 2021 (1637580212)

BOOTFS: /flash

EEPROM updates pending. Please reboot to apply the update.

To cancel a pending update run "sudo rpi-eeprom-update -r".

LE:~ #

LE:~ # reboot

LE:~ #

login as: root

root@le's password:

##############################################

# LibreELEC #

# https://libreelec.tv #

##############################################

LibreELEC (community): nightly-20211203-53a5e7f (RPi4.arm)

LE:~ # rpi-eeprom-update

BOOTLOADER: up to date

CURRENT: Tue Jul 6 10:44:53 UTC 2021 (1625568293)

LATEST: Thu Apr 29 16:11:25 UTC 2021 (1619712685)

RELEASE: default (/usr/lib/kernel-overlays/base/lib/firmware/raspberrypi/bootloader/default)

Use raspi-config to change the release.

VL805_FW: Dedicated VL805 EEPROM

VL805: up to date

CURRENT: 000138a1

LATEST: 000138a1

I'll have to try with another OS.

Not sure if this could be due to ENABLE_SELF_UPDATE=0 option present n my current bootloader config but in past there was no issue with the bootloader manual upgrade & this setting.

At least there's a mess with LATEST bootloader versions as outlined above (the bootloader dated Thu Apr 29 16:11:25 UTC 2021 is not the latest for sure, maybe it is latest tested but there're some more stable versions already released and the real LATEST stable dated Mon Nov 22 11:23:32 UTC 2021 is present in the latest LE 11 Nightly image yet).

Kodi menu - Settings - Media - General

The same issue on LE 11 Nightly 20211202.