Posts by Da Flex

Looks like a problem of interlaced video modes. Has your TV the ability to display 1080p?

OK. Because we haven't found any cause in the LE log yet, I guess your receiver stops HDMI connection, and LE can't deal with it.

The reason for this could be too much HDMI data coming from LE. If you can change the cabling to avoid the receiver, give it a try.

On RPi you can use the tvservice command to change the video mode on-the-fly.

The implementation of the Python script depends on the button behavior you wish to have.

You could use one button to switch among video modes, or one button for each video mode.

Quote from MrMister76

Wild guess: I am using pass through audio, maybe that's an issue?

Good idea. Reducing HDMI data rate in general should be the next test. You could reduce the resolution and refresh rate, too.

What happens when you plug off / in the HDMI cable, after an HDMI crash appeared?

Thanks for checking temperature.

Next I would try to run LE without NFS. In case of an NFS error, different LE hardware wouldn't help.

PS. Both logs have this error at the end:

ERROR: Got MSGQ_ABORT or MSGO_IS_ERROR return true (-1)

I can't decrypt that error code.

Calling a script by RC goes like this at /storage/.kodi/userdata/keymaps/remote.xml:

<keymap>
  <global>
    <remote>
      <red>RunScript(/full/path/to/python/script)</red>
      <green>RunScript(/full/path/to/python/script)</green>
      <yellow>RunScript(/full/path/to/python/script)</yellow>
      <blue>RunScript(/full/path/to/python/script)</blue>
    </remote>
  </global>
</keymap>

To give advice about script content we need to know your LE hardware.

I haven't found a reason for a broken HDMI signal on your log.

Maybe the RPi gets too hot after some time, and you need better cooling.

Login by SSH and watch the output of vcgencmd get_throttled from time to time until HDMI crashes.

Sorry, I forgot to tell you the final tweak about "Raspberry Pi Tools".

Import the GPIO lib like this at your Python script:

import sys
sys.path.append('/storage/.kodi/addons/virtual.rpi-tools/lib')
import RPi.GPIO as GPIO

Quote from MrMister76

What to do with that?

Upload the log to Pastebin and post the link.

If it's not related to your current issue, open a new thread.

@admins:

Please move this thread to the "Showcase" sub-forum. That will make it easier to find for reference. It's rare and advanced stuff.

PS: Hey, I'm an admin now. I can do that!

Maybe LE runs out of memory when buffering such high resolution.

I would try to reduce the refresh rate.

In case you are puzzling how to program the GPIO pins in Python: The add-on "Raspberry Pi Tools" is needed to get that lib.

Hi grhhm!

I don't know your complete setup, but I think you're on the right track.

To call a TV RC power button script, you could wite something like that at /storage/.kodi/userdata/keymaps/remote.xml:

<keymap>
  <global>
    <remote>
      <power>RunScript(/full/path/to/your/python/script)</power>
    </remote>
  </global>
</keymap>

Test this mapping by scripting a simple task, like creating a file.

If your TV backlight RC power button acts the same way like the TV RC power button, then you probably don't need a variable for the on/off status. Acting the same way means, both devices only have one RC button for turning on and off.

Maybe the LIRC solution of Hias is better, but it's good to have extra options.

Connect an IR sending LED with the RPi and send the fitting IR code to the TV backlight.

Installation instructions about IR sending LED on RPi GPIO are available on the net.

This sending process will be triggered when the RPi receives the "TV Power" button press over CEC.

You can use LE's key mapping to start your script by "TV Power" button press.

The RPi "knows" whether "TV Power" on/off means TV backlight on or off by using a variable at your script.

Cheapest and easiest solution: Install a power button instead of using RC.

If you really want to turn it on by RC, then you definitely need additional electronic parts. There is no way to use an attached USB IR receiver after the RPi 4B has been turned off.

You could use an Arduino (or other micro controller) with an attached IR receiver, which:

• is permanently listening for the right IR code
• triggers RPi's GPIO 03 when it receives the right IR code to turn the RPi on

Problem: This micro controller has to be an always-on device. It just consumes less power then an RPi while it's on.

Quote from MrMister76

Code

config_hdmi_boos=7

According to the official config.txt documentation this option will be ignored on RPi 4B.

To increase HDMI signal strength, you could try a new cable. HDMI 2.0 and HDMI 2.1 standard cables are made for 4K. Get one of those.

Quote from milan0

This forum is not so important that it gets spamped. Too small community.

Well, it seems to be very important for Chinese spammers. Guess why...

I've seen many pages of pure spam here. Drastic protection is necessary.

Yes, the community is small, but high quality.

Quote from clarkss12

I have this low powered minipC and tried to install LibreELEC but no luck......... Any clues on what I need??

Beelink Content of the article

New thread please. This is only a buyers guide, not about precise installation instructions.