Posts by Da Flex

On my RPi 3B+ the kodi.bin is at about 10 - 15% when idle. I think your 18% are still normal.

Currently LE has no idle timer, just a screen saver. Try the CEC Adapter settings at Settings -> System -> Input -> Peripherals.

donbrew did some additional changes at his config.txt to make an older TV work. Read here.

System.log says:

[    1.808835] usb 2-5: new high-speed USB device number 3 using ehci-pci
[    1.830343] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    1.955525] usb 2-5: device descriptor read/64, error -71

Those read errors appear several times. Check your SDA2 device.

Quote from Kacha

Reach a certain amount of posts?

Yes, it's necessary spam protection. I think your primary partner to solve the issue is AMD now. They get payed for providing solutions.

PS: Try plugging the HDMI cable off and on after a bad boot.

This part is interesting:

Quote from bobacisko

This works only if UEFI boot type is set to Win7 on Zotac. UEFI and Legacy options do not display anything (TV shows no signal).

So it could be a timing issue, and the box misses the transmission of HDMI modes coming from the TV. Maybe switching HDMI off / on (after booting and running LE invisible) will enforce a complete transmission of HDMI modes. You could script HDMI off / on by using LE's autostart.sh.

Complete log file please.

PS: Take into account that ATI / AMD drivers probably have the same errors on Windows and Linux. I'm sure the Linux iGPU driver is proprietary, so they copy-and-paste errors among OS'es, and you get trouble on LE, too.

Google for "atidxx64.dll" errors. "Final Fantasy" players have crashes with that library, too.

It's possible that your new TV transmits available HDMI modes at higher speed, and your box is unable to receive the modes correctly. If you are lucky, you just have to replace your HDMI cable (use "HDMI high speed" standard).

Quote from Rembrandt

Would the changes the original poster mentioned have any noticable effects, and where would these be most obvious?

Iridium already said it: Heat is your number one point to take care of. Overclock gently step-by-step with a good cooling strategy.

Devs don't like it, because overclock systems are not comparable to normal ones, and people often forget to mention it on bug reports.

Wrong conception. Always search for compatible LE touchscreens first, before you buy. Yours isn't one of them, as your link says:

Quote

You can enable the touch in two ways: Method 1. install driver to your Raspbian/Ubuntu Mate OS. Method 2. use the Ready-to-use image file of which LCD driver was pre-installed.

We have many threads about RPi 4 framerate issues. Please use the search function (keywords like "pi4 stutter" or "video stutter").

The overclocking options are independent of LE. You can use them, but it's not suggested by LE developers.

Quote from Kacha

With LE I'm happy if I can just watch a 45 minute episode without a crash and with Windows 10 it's a crash every 10 episodes or so.

If you did a complete RAM test, then it's probably not a caching issue. On LE you could play around with different audio output settings. Have you already tried to disable audio pass-through, as I mentioned above?

PS:

Quote

Although, I have to say that I don't use the latest BIOS anymore, because I read the combi BIOS causes some GPU issues. I will likely try it again though.

That might be critical. The most recent GPU driver usually depends on the most recent BIOS.

Quote from Kacha

Windows 10 is significantly more stable with Kodi, but even there Kodi crashes from time to time. By the way, on Windows, when I try to change sound from Directsound to Wasapi it immediately crashes.

Sounds like an issue, which is independent of Kodi and LE. I would buy an eGPU and disable the iGPU.

If disabling CEC wake-up already does it for you, then you can mark this thread as "solved".

The Pimoroni SHIM should be compatible to the C2, if you also want to keep that device off.

chewitt :

Something like an idle power-off timer would be a nice feature for LE. So after a power cut the device would power-off automatically again. Currently we have an idle-independent power-off timer, but that's not suitable for a power cut situation. I know I could do it with an autostart script, but having it as a GUI function would be easier.

That's the same behavior like on RPi's. To my knowledge there is no software solution to solve this.

I only did a short research, but maybe the Pimoroni On / Off SHIM hardware will avoid automatic power-on for the C2.