amlogic: add experimental AMLMX device · chewitt/LibreELEC.tv@1684aaf · GitHub
^ this is the minimum. Odroid C1 needs a bootable image so I'm still experimenting with the least-worst way to combine prehistoric pre-built u-boot and our more mainline u-boot oriented build-system so those bits are not in any of my branches yet.
I'm fuzzy on the details, but ISTR some internal conversation/moaning about the close-source bits of steamlink being compiled with dependencies on pi-specific libs that don't exist on other devices, or something similar..
If you delete /storage/.cache/connman it should remove all traces of previous network config, although I don't see what the issue could be.
Look at your webserver logs and you can see the actual URL being requested. The common mistake is configuring http://your.host/releases.json when all you need to do is configure the hostname, the releases.json will be appended by the settings add-on.
It would have to stop Kodi because there is no way for it to run within Kodi.
As a general rule we're happy to backport useful patches that have been submitted (and merged) upstream, but we prefer to minimise the number of local patches that haven't been submitted. So, it's really a case where if someone made some useful patches, they should submit them to the rockchip mailing list and get them added. Sending stuff upstream is not particularly hard..
LE does not need swap, which is why it's not enabled by default in any of our images.
Odroid C1 is an arm (32-bit) device. Odroid C2 is an arm64 device. You need to do more than simply change the kernel source, i.e. define a device with an arm(32) defconfig and CPU params.
There's basically no difference between the RPi2(3) and RPi4 images. Note that installed paths in LE and OSMC will be different so if you've copied a config file that points to some kind of playlist? (I've never used IPTVSimple so no idea of that's a requirement) the path could need tweaking.
RPi4 is hardware capable of HDR and HBR audio, but neither are implemented in current software. There is active effort to implement HDR on several platforms for Kodi v19, mostt advanced in the quest is recent Intel devices, but that's still in a pre-alpha state and for RPi4 some other essential code plumbing needs to come first.
Cron should be enabled and running by default.
If you mount to the local filesystem all the paths change, so media is seen as new media and will need to be re-scraped. Read the wiki sections on exporting watched status first, so that it can be reimported again.
Pastebin a debug log at the start, and after restarting Kodi, e.g.
cat /storage/.kodi/temp/kodi.log | paste <= share the URL generated
wait 30 secons
systemctl restart kodi
cat /storage/.kodi/temp/kodi.log | paste <= share the URL generated
i'm wondering if it's something to do with drivers/loading.
LE 9.2.2 is here: GitHub - LibreELEC/LibreELEC.tv at 9.2.2
Unless you posted in the Amlogic section deliberately? in which case no 9.2.x version exists and the latest sources are:
LE 9.0.2: GitHub - LibreELEC/LibreELEC.tv at 9.0.2
LE 10 (future, in a pre-Alpha state): GitHub - LibreELEC/LibreELEC.tv: Just enough OS for KODI
This is resolved in master branch (will be LE10) image: add /etc/environment by MilhouseVH · Pull Request #4065 · LibreELEC/LibreELEC.tv · GitHub
"/usr/bin/sh" not "sh" ?
Sorry.. I kind of stopped caring about Realtek chips several years ago and no longer have a clue about what we support or don't support.
