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:
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.
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:
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.
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.
Have anyone seen this before?
No. If you did a clean shutdown after your last session, then maybe your 24 hour test created an overload of temporary data.
Read here about Allo Boss DAC on RPi.
...although the usb controller does support USB3...
Unfortunately you need the xhci_hcd driver to make the controller work (source).
All disks use usb-storage driver, but the root_hub uses xhci which might be the problem?
If the root hub is USB3 then you can't do anything. If it's USB2 then blacklist the xhci_hcd driver.
Login by SSH, and open the settings file by nano /storage/.kodi/userdata/guisettings.xml.
My "audiooutput" part looks like this:
<setting id="audiooutput.ac3passthrough" default="true">true</setting>
<setting id="audiooutput.ac3transcode" default="true">false</setting>
<setting id="audiooutput.atempothreshold" default="true">2</setting>
<setting id="audiooutput.audiodevice">PI:Both</setting>
<setting id="audiooutput.channels" default="true">1</setting>
<setting id="audiooutput.config" default="true">2</setting>
<setting id="audiooutput.dtshdpassthrough" default="true">false</setting>
<setting id="audiooutput.dtspassthrough" default="true">false</setting>
<setting id="audiooutput.eac3passthrough" default="true">false</setting>
<setting id="audiooutput.guisoundmode" default="true">1</setting>
<setting id="audiooutput.maintainoriginalvolume" default="true">true</setting>
<setting id="audiooutput.passthrough" default="true">false</setting>
<setting id="audiooutput.passthroughdevice">PI:HDMI</setting>
<setting id="audiooutput.plladjust" default="true">0</setting>
<setting id="audiooutput.processquality" default="true">30</setting>
<setting id="audiooutput.samplerate" default="true">48000</setting>
<setting id="audiooutput.stereoupmix" default="true">false</setting>
<setting id="audiooutput.streamnoise" default="true">true</setting>
<setting id="audiooutput.streamsilence" default="true">1</setting>
<setting id="audiooutput.truehdpassthrough" default="true">false</setting>
<setting id="audiooutput.volumesteps" default="true">20</setting>Then go to the bottom of the file content and check that audio is not muted and has a noticeable volume:
<audio>
<mute>false</mute>
<fvolumelevel>0.900000</fvolumelevel>
</audio>Does it affect all audio formats, even mp3?
Do you have all other audio settings on default values (especially amount of channels should be 2)?
Set audio output to HDMI and analogue. Then plugin headphones on your RPi to check whether you hear audio.
A second test is to disable audio pass-through at Settings -> System -> Audio.
Maybe new drivers increase efficiency, but don't solve the real problem. Your kodi.old.log has a couple of errors, which maybe affects playback indirectly.
You have a lot of add-ons, so I would try a fresh LE installation. Don't install add-ons, and disable audio pass-through at System -> Audio settings. If this vanilla installation runs without playback errors, add add-ons step-by-step to identify trouble makers.
I noticed that HiassofT was reading here, so I'm optimistic that things start rolling.
At similar issues people often blacklist a Linux driver, but that's just another dirty fix.
Finally to make this stick i'll finish off with adding it to autostart.sh:
echo "xrandr --output eDP1 --off && xrandr --output HDMI1 --mode 1920x1080 --rate 60.00" >> /storage/.config/autostart.sh
Selecting this HDMI mode at the LE video settings doesn't work?
