Posts by chewitt

Sounds like something broken on the Kodi (or mirrror) side. Nothing you can do locally. If it's still and issue (hasn't resolved itself) you need to flag it in the Kodi forums and include the full debug log - not just snippets.

If you see the same problem on multiple OS it's likely to be a hardware problem, either something physical in your setup or a faulty board (rare but not unheard of). HDMI should be connected to the port nearest the USB C power connector .. and you need to share a Kodi debug log.

RPi4 supports H264 in hardware to 1080p (same capability as the RPi3) and above that will be software decoded though this is way beyond the CPU capabilities of the hardware. H265 is supported in hardware to 4K (new capability for RPi4). Some people see the lack of 4K support for H264 on the RPi4 as an issue, but as no broadcast formats use that combination (only test files and deliberately encoded media) it's not a real-world problem.

Most of the whiny threads about RPi4 video issues in the LE forum are caused by people not understanding how to use the whitelist and/or forcing deinterlaced media (which needs 50/59.94 modes) to run at 25/29.97 refresh rates, often at 4K resolution, which is never going to be good. I've never been a big Pi user as I always had other toys around, but I've been using RPi4 as the daily driver for a while now and I don't see any major issues. I don't care about 3D support and other niche things RPi3 excells at though. Firmware updates continue to address minor nits in RPi4 behaviour (e.g. heat) but software support has generally come a long way in the 6-months since launch. HDR and higher-bitrate audio support are still missing but they don't exist on older hardware either and neither are simple additions. There are other higher-priority items for the RPi Foundation to work but they are being worked on in the background.

Hard to tell as the software support link on the page fails and the more detailed product specific pages are blank on details. I'd guess the device-tree overlays (or revised device-tree files) are required to make these devices work on the mainline kernel; which not a huge thing to do but something that would need to be done - and Radxa are the people to do it, not us.

Nope, it still has a completely unsupported SoC.

It already works .. so what more answer do you need?

"it's similar" or "it's a cut down version of" means "it's different" and thus images are not likely to work without explicit changes for that chipset, and now that we dropped support for the Rockchip 4.4 kernel and moved Rockchip support to mainline Linux 5.4/5.5 kernels device tree files for the 4.4 kernel are even less likely to get an output/result than before.

Kodi debug log output (full log) will tell us more technical detail about your setup and media than your text description.

echo "options cfg80211 ieee80211_regdom=AU” > /storage/.config/modprobe.d/cfg80211.conf

^ I'm 99% sure this will fix things assuming you're using the onboard pi wireless. If the regulatory domain is not set, it defaults to 00 which is a global safe default that will be missing a variety of channels and other radio properties depending on where in the world you are.

Kodi only references the EDID data necessary for audio/video config once at startup, so if the HDMI monitor isn't on/connected before Kodi starts it sees nothing after you turn it on. You can dump the edid data to a local .bin file and then configure xorg.conf to always use the .bin file. This makes the nvidia driver (and Xorg) behave as if it's connected to the monitor, even when it isn't connected. This behaviour has been the same since early OE days so you probably did this once on the OE install and then forgot about it. See Custom EDID [LibreELEC.wiki]

Software deinterlaced media will play terribly if forced to 25/29.97/30 modes as Kodi currently renders each half-frame as a whole frame, so you need the "double" refresh rate to get all the frames rendered. If you force 25Hz content to play on a (4k)30Hz mode you're probably missing 50% of the half-frames in the video stream. I have Kodi set to 1080p60 and I whitelisted the 4K resolutions and 1080p 23.976/24/50/59.79/60 modes. The GUI plane is rendered at 1080p by default so you won't see any real-world difference from having the resolution at 4k but the GUI takes less effort to render so navigation is a little snappier and Kodi will still switch to 4k modes if you play 4k media. If you mostly watch deinterlaced 1080p PAL media 1080p50 may be a better default as this avoids the 60>50 mode change.

rm /storage/.kodi/userdata/profiles.xml

It's a known Kodi bug/issue. Delete the file to resolve.

SoC vendors typically only upstream the stuff they need for a project, and the scope is frequently limited to current chips because that's what their projects are using and because it reduces exposure to future maintenance work. Sometimes contributions are structured (and named) with future expansion to other devices in-mind, and sometimes not. In this case .. appears not.

Kodi does not follow symlinks so it may work from a desktop OS with another player app, but it will not work with Kodi. So your choices are:

a) Change your symlink scheme to a more conventional arrangement with movies in folders (can be subfolders of a single 'movies' share)

b) Use a different OS with different player app that can follow your scheme

c) Submit code to Kodi so that it gains the ability to follow symlinks

On which OS are you running the tool?

Software deinterlaced 1080i content is no drama as long as you do not whitelist the 25/29.97/30 Hz refresh rates in video settings which allows Kodi to run at 50/59.94/60 instead.

Some work has been done, but no public news at this time.

root/libreelec are the default credentials but the first-run wizard will prompt you to change them. Make sure you didn't enable "disable password auth" in LE settings as this will require you to use SSH key authentication to login. If this is enabled you'll still receive a password prompt but no password will be accepted.