It is correct, but it doesn't help. Your TV is "HD ready" standard.
According to this it's very difficult to deal with interlaced video modes. So I think Kodi has good reasons not to support interlaced modes.
Maybe you had real interlaced modes on other RPi OS'es, but on LE (and other multimedia OS'es) your chance is very low to make it work.
Why do you need ad blocking on LE? I don't see any ads at my LE.
Yes, you're probably right, HDMI disconnection shouldn't do any bad.
I have noticed that the crash happens nearly every day around 5am.
That's interesting. To my knowledge, Kodi doesn't have a stand-by mode (as well as RPi itself), but CRON jobs will run occasionally. I just had a look at my /etc/cron.d folder. The only service I found is e2scrub_all, which checks all EXT file systems. Maybe that check runs daily, and crashes Kodi in case of errors. So you could check all your (network-) connected EXT devices for errors manually.
Thanks for testing. My math was that half of the progressive rate would be interpreted as interlaced rate. Unfortunately that doesn't work.
I'm running out of ideas now. As chewitt mentioned, you maybe never used an interlaced mode on your other RPi.
Remove the line hdmi_ignore_cec=1 from config.txt.
Then faking an interlaced mode might work (1080p at 30Hz):
hdmi_group=1
hdmi_mode=34I there a way to use tvservice to show the exact mode currently used?
tvservice -s
Then you probably have an older TV, right? User donbrew made an older TV work with this config.txt. Give it a try.
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.
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 GPIOWhat 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! 