Elysium sample is playing fine here as well.
Might be worth testing with a different, 18Gbps certified HDMI cable, and without the JoyIT case (which seems to have a HDMI adapter board which could be problematic).
BTW: RPi4 doesn't support 4k H264 playback, stick to H265 material.
so long,
Hias
Downloads from the 4ksamples.com site don't work, downloads.4ksamples.com doesn't resolve to an IP address. Please provide a link to a working sample file.
so long,
Hias
The temperatures look OK, basically stable at 60°C - which is fine.
If playback crashed you should have something in journal or kodi log - reproduce the issue again, then run "pastekodi" and post the URL with the log here.
so long,
Hias
If you are having issues with EDID test without the case, and also a known good (or new) 18Gbps certified, fully wired HDMI cable - those two things solve about 95% of "display not working correctly" issues.
Don't touch config.txt, gpu_mem=1024 can never work and even if it would it would only reduce usable memory without any benefit. 96 instead of 76 may help in very odd corner cases when dealing with out-of-spec H264 files but that's it.
So in short: best use stock HW and SW setup - only adjust Kodi settings as outlined eg here https://wiki.libreelec.tv/configuration/4k-hdr
Concerning hyperion: don't hold your breath for a solution soon, better thing about alternatives (external HDMI grabber or TV with ambilight built in).
so long,
Hias
ssh in and run "bcmstat.sh" - this will show current clock frequencies and temperature
so long,
Hias
Linux can't deal with windows storage spaces.
so long,
Hias
Yes, that's expected and mentioned in the RPi2/3 section of the release notes
https://libreelec.tv/2022/10/17/libreelec-matrix-10-0-3/
Note that GPU accelerated H265 decoding is no longer available in LE 10 and future versions. If this is important to you stay at LE 9.2.so long,
Hias
You can use the internal script "dump-active-edids" (it's used by "getedid" on RPi) to write the edids of all connected displays to /storage/.config/firmware/edid
It'll tell you which HDMI/DisplayPort/... connections it detected, for each one it created a edid-<NAME_OF_CONNECTOR>.bin file - which you can then simply decode with edid-decode.
eg here on RPi4 with one display connected to the first HDMI port (edid-decode cut down for brevity):
xbmc:~ # dump-active-edids
found active connector(s) HDMI-A-1
xbmc:~ # edid-decode /storage/.config/firmware/edid/edid-HDMI-A-1.bin
edid-decode (hex):
...
Block 0, Base EDID:
EDID Structure Version & Revision: 1.3
Vendor & Product Identification:
Manufacturer: GSM
Model: 1
Serial Number: 16843009
Made in: week 1 of 2018
...You could also check through all the connectors in /sys/class/drm/, verify if the status reports "connected" and then use the edid file from there (eg /sys/class/drm/card0-HDMI-A-1/edid) - this is basically what that script does - but as card, and connector names may change it's probably easier to let the script deal with that 
BTW: so far we only tested the script on RPi, it should work on all other devices though, so if you have issue or notice something odd please tell us about it so we can fix/improve it.
so long,
Hias
so long,
Hias
Thanks, this is interesting and useful information - this thread has become a bit convoluted, but most issues seemed to affect older (Samsung) models.
Could you please test with the latest LE11 nightly build from here https://test.libreelec.tv/11.0/RPi/RPi4/…/11.0/RPi/RPi4/ ´(currently 20221215, scroll down to the end of the page) and if doesn't work test if the workaround of setting a different mode in config.txt works?
Add the following to the end of config.txt
hdmi_group=1
hdmi_mode=20Also test (without those config.txt changes) if unplugging and replugging the HDMI cable gives you working video output, if yes set the display resolution in kodi to something different than standard (eg 1920x1080 at 50 Hz instead of 1920x1080 at 60 Hz) and report back if that works, too.
Anyways, we'd need logs (with debugging enabled in kodi) of all working and non-working cases.
so long,
Hias
What I meant is that the issue is specific to a couple of older TV models, not RPi models - which makes shipping even more problematic
so long,
Hias
AFAIK no developer has been able to reproduce the issue - it seems to be limited to a few specific older models - and without being able to reproduce the issue it's next to impossible to fix it.
Personally I tested with my LG 55C8 OLED and my parents' old LG 32LH7000 TV - and both work just fine.
so long,
Hias
Test with a different HDMI cable and if you are using a case also without the case.
Argon cases have a long history of causing HDMI issues because of low manufacturing quality of their internal adapter PCB, but as I just experienced myself even cases without internal adapter boards can cause HDMI issues as they often won't let you fully plug in the HDMI connector - even half a millimeter or a millimeter can make a huge difference.
And it gets even worse if the HDMI cable is a bit worn out and starts to fall out easily.
I just had that issue here with a "full armor case" and both a new and an older HDMI cable, and also with a USB3 cable - have to say I absolutely hate the HDMI and USB connector crap, it's as bad as SCART was in the old days, non-interlocking connectors just cry for problems. Display port did it right, same goes for ethernet, VGA, DVI etc but the consumer connector crap is starting to really annoy me...
so long,
Hias
Hard to tell as you didn't post a full pastekodi log but I'd also suspect your fritzbox is acting up or you have some kind of other wifi issue (like neighors using same wifi channels etc).
Check with WiFiAnalyzer https://f-droid.org/en/packages/com.vrem.wifianalyzer/ or some similar apps on your tablet/phone if you have channel clashes, or contact AVM for support with your fritzbox.
so long,
Hias
What kind of splitter / audio extractor are you using?
The splitter needs to mix the EDIDs of both the AVR and and projector, LibreELEC heavily relies on that being accurate and it is quite likely Windows was more relaxed about it.
My HDFury Vrroom has very extensive settings how it'll mix (or patch up) the edids and also allows you to download the edid directly via the web interface.
You can also grab the edid presented to your chromebox from /sys/class/drm/cardX-HDMI-A-Y/edid (A, X, and Y may vary on your system) and decode it with edid-decode. eg
edid-decode /sys/class/drm/card0-HDMI-A-1/edidif you have multiple cards or connectors (A-1, A-2 etc) try all of them and post the output (the unconnected HDMI ports will show "empty" - just ignore them).
so long,
Hias
Yes. The TV is Philips 4K Android TV and with Kodi installed on it the same file plays just fine. Only the Rpi4 has problem.
Please provide a debug log, the output of modetest | pastebinit while playing a HDR file and mediainfo output of the file (mediainfo is available in the multimedia tools addon).
so long,
Hias
Today I found out that my Rpi4 can play 4k hdr10 file, but with washed-out colors... while my Huavei laptop, Ryzen 5 3500u, running Kubuntu, can play the same file just perfect (with vlc and Kodi), with HW acceleration and very nice colors? Why is that? why Rpi4 can not do it?
Does your TV support HDR and BT.2020?
If not that's expected as the RPi can't tonemap HDR videos to SDR which vlc on your laptop probably does.
so long,
Hias
The post from Dec 12 on the plex thread you linked to https://forums.plex.tv/t/testers-need…lity/481208/251 mentions the same thing is happening with official kodi 20rc1 on Android.
So I'm pretty sure, too, that it's a Python 3.11 issue as mglae wrote - and it's not specific to LibreELEC and it's up to the plex folks to fix their addon.
so long,
Hias
Standard pastekodi log (with kodi debug logging enabled) would do fine for the next step. Edid and sound device info look like it should work (from driver and kodi side).
so long,
Hias
