Posts by chewitt

It doesn't work because the release manager repeatedly forgets to enable it .. CvH

The best solution is to experiment and see which works best for your eyeballs and media collection.

Kodi does not support output to multiple devices and there is no no support for it in LE (unless handled in hardware, e.g. old laptops). If you want to explore this in any way you'll need to stick with Raspbian.

Quote from galagonya

hy please help. Whats download x96a905x3 max + 4gb/64gb.

Index of /

Wat tar.gz file? Thx

The AMLG12 "box" image, the X96max dtb will probably work.

You can either add "debugging" to kernel boot params in config.txt and then reboot and connman will be running in debug mode which means the systemd journal (and the entire system) will be very verbose .. or you can stop connmand from running (systemctl stop connmand) and manually restart it with -d to run in debug mode.

Read: Configuring WireGuard in LibreELEC (v9.2.1 and newer) [LibreELEC.wiki]

I have to get someone who does code to review the changes before merging. On one hand we don't particularly care much as all official images are now running Lima not libmali. On the other it's bad form to merge something that causes problems.

Allwinner support is still in a pre-alpha experimental state, albeit progressing nicely. If you go back in time more than a few months you'll end up with a non-functional device .. so there are no "old" images to use.

Read this and follow the screenshots: Personal API Keys · jdf76/plugin.video.youtube Wiki · GitHub

If you add the keys manually via the SSH console make sure to remove ".apps.googleusercontent.com" from the ClientID else it won't work.

Looking at the original sources.xml shared in post #5 I notice the shares have spaces in their names and the paths are not quoted or escaped. I'm not sure how Kodi handles this, but it might be something to look into.

e.g. Escaping:

        <source>
            <name>TV Shows</name>
            <path pathversion="1">smb://192.168.1.111/Media\ Library/TV\ Shows/</path>
            <allowsharing>true</allowsharing>
        </source>

or Quoting:

        <source>
            <name>TV Shows</name>
            <path pathversion="1">"smb://192.168.1.111/Media Library/TV Shows/"</path>
            <allowsharing>true</allowsharing>
        </source>

or (best) remove spaces:

        <source>
            <name>TV Shows</name>
            <path pathversion="1">smb://192.168.1.111/Media/TV_Shows/</path>
            <allowsharing>true</allowsharing>
        </source>

No idea if that's the issue but simple enough to test.

It sounds like a communal garden "flakey connection" .. the soluions are:

a) Run an Ethernet cable

b) Use an external WiFi device with a better antenna

c) Use an Ethernet bridge (combines both)

d) Run and Ethernet cable <= always the best

RPi4 has better wireless than previous Pi devices that I've used, but it's not the best WiFi device.

Configure the Harmony as an MCE remote and it should mostly work as-is.

Nope, but you can always install the Jarvis-era "Confluence" skin from the Kodi repo. AFAIK this is still being maintained.

I'd guess that you only calibrated the 60Hz "desktop" refresh rate, and then Kodi switches to 50Hz (PAL) or 23.976Hz (DVD) for media playback. Kodi requires you to calibrate each refresh rate independently (which is annoying and dumb, but is how it works) so you need to switch the desktop to those modes and repeat the calibration process. See if you can change the TV to "Just Scan" or similar.. modern TVs shouldn't need calibration.

It normally requires changes in the low-level firmware. I'm not familiar with RK firmware, but most ARM devices are dependent on closed-source pre-compiled blobs, which will rule out making any changes.

Have a look at /storage/.kodi/userdata/sources.xml

Our normal approach is to encourage a couple of capable users to create some unofficial community images that are published/shared here in the forums. Set "BUILDER_NAME=stpf99" when you build images and this is embedded and we can see exact stats on the number of users the images attract. If things ever get popular we can move to "adopt" the changes. If not, we don't have to add complexity for a niche audience.

If it's anything like the nVidia equivalent, it will require continuous package bumping to match with continuously evolving card drivers and thus will be completely un-maintainable over time. I'm not aware of anyone doing this or working on it.