What I’d really like is for some highly knowledgeable people to conduct a very detailed analysis of the DV Master output, there are likely a few small things that could use some tweaking.
noggin are you around? .. that ^ sounds like something you'd be good for 
Thanks for the confirmation. Can I ask you to share some Kodi debug logs of an assortment of different media types and refresh rates. Just to see what's going on underneath.
I’m using the Aeon Nox Slivo skin.
What do you think?
Nox and its many derivatives have been causing performance issues for aeons [sic]
aka "self inflicted problem"
Switch to another HDMI port then. Your TV mishandling the native RGB output from an Intel/AMD/nVidia GPU is not a problem we are going to solve with software dumbfcukery.
Change the configuration of the HDMI port on the TV then.
I pushed everything to LE master in the last week so there's currently no difference between my images and nightlies.
Nice to hear it's working well for people 
MikhailR Could you rebuild and retest using the rockchip-upstream branch; this is subtly different with a cleaner set of changes and the current Linux 7.3-rc7 kernel.
You won't be allowed to submit the add-on with bundled pre-built binaries but it could be submitted as a binary add-on that needs to be compiled with the rar packages as a build-from-source dependency to get unrar that way. Or ask Claude to author a Python3 script that functionally does the same thing as the unrar binaries (no idea if that's possible, but I suspect it is).
Update to this LE13 test image: https://chewitt.libreelec.tv/testing/LibreE…_64-12.95.1.tar
It has the ath11k PCI driver enabled so the card should be detected, but will not work due to missing firmware. The system log will normally complain about the missing firmware files and you can add them yourself to get the card working:
If you confirm the card works and what specific firmware files are required I'll submit changes to add them for LE13.
Have you considered submitting it to the Kodi addon repo?
Tvheadend is a lightweight app. I have an instance running on an old RPi3B (1GB) without any issues at all.
Until you update to a current image and start sharing logs, I have no clue at all.
Are you using the default Estuary skin?
Samba generates filesystem/IO activity on the device and stops it going into power saving mode; would be my guess.
Do you have the Kodi GUI in standard, advanced, or expert mode?
I'm always in Expert mode due to testing. I see uninstall options 
Plan B, use SSH to access the device and the add-ons are in /storage/.kodi/addons - delete the add-on folder there and it is gone.
Our website has nothing to do with AI, it was hand-rolled by staff. Feel free to whinge about AI somewhere else.
You can append ?mirrorlist to the end of any .tar/.img.gz download URL to see the sha256 hash, e.g.
Mirrorlist /LibreELEC-RPi5.aarch64-12.2.1.img.gz
The exception is nightly images which are served from our own infrastructure. You run those at your own peril anyway.
