Posts by chewitt

If running on an x86_64 or 32-bit ARM SoC device the Docker binaries are going to update once the new addon repo is accessible and this might throw up some minor config issues related to dockerfiles; sometimes Docker conventions change and there's probably a large enough jump from whatever (older) version is used with LE 9.2.6 for that to occur.

If running on a 64-bit ARM SoC device, LE12 changed images from "arm" (32-bit) userspace to "aarch64" (64-bit) and this forces you to remove all "arm" containers before updating and redeploy them using "arm64" versions once the update has completed. If you leave arm containers installed they will crash post-update due to wrong CPU arch.

kodi-send --action="UpdateLibrary(video)"

If you mean updating the library after adding files, "kodi-send" commands can be used.

See https://kodi.wiki/view/List_of_built-in_functions

Does the C2 exhibit the same behaviour when only GND and TX are connected (leave RX disconnected)?

Does the C2 exhibit the same behaviour when only GND and RX are connected (leave TX disconnected)?

Just wondering if this has something to do with RX pull-up..

READ: https://wiki.libreelec.tv/hardware/amlogic (then use the correct image; hint, it's not the WP2 image).

No idea what devices you are using, but no issues here using Spotify on iOS 17.6.1 to LibreSpot running on a current LE13 dev image.

No idea what chipset is in the device (and you provide no logs) .. but as a first blind guess, have you configured the correct wireless regulatory domain (country)?

Start with reading: https://wiki.libreelec.tv/hardware/amlogic .. then stop trying to boot a 2023 upstream Linux kernel with the dtb file from a 2015 vendor kernel. Note that Realtek (RTL8189ES/FS) WiFi is not supported in official LE images.

Follow the settings advice here (ignore the 4K/HDR stuff, the rest is relevant): https://wiki.libreelec.tv/configuration/4k-hdr

Quote from subvert

Thought my best chances would be to ask reddit

Sounds like a good idea. Our expertise is in supporting our own Kodi oriented distro, not helping people flash old Android boxes to make a Plex server.

It doesn't explain it because in LE the NTP request comes from ConnMan not "ntpd" and there is no issue with the boot date/time starting in May and then being corrected to current time; unless the configured NTP server(s) fail to respond. Unless you explicitly define servers for a ConnMan service, it will use ntp.org servers. Some ISPs and network routers block requests to ntp.org (no idea why, but it does happen) and some routers will set themselves as the time source via DHCP. If you look at the systemd journal it will show requests being made, where they were made, and what the outcome was.

It's not possible for users to install modules, they need to be baked into the image. We might need to package them into the core image to support the required script being run.

heitbaum  HiassofT thoughts?

Quote from spigui

Does this version work with S805?

No, AMLGX is for S905 and up. The AMLMX image supports S805 .. although that's rather unfinished and I didn't find the enthusiasm to do any work on it in about two years now. There's a couple of older test images in my webshare but they are not supported (as I can't remember much about them at this point) and they're now rather dated.

I replied here: https://github.com/dave-p/TVHadmi…ment-2357927072

Do cold boot not warm boot?

ifconfig bond0 192.168.1.1 netmask 255.255.255.0 up
ip link set eth0 master bond0
ip link set eth1 master bond0

Something like that ^ might work? .. I've no ideas how ConnMan will react to a bonded interface, or whether it will be persistent, or whether it kicks you from SSH at the same time (likely). LE will support the "iproute2" command-set (see https://www.kernel.org/doc/Documentat…ing/bonding.txt) but we're not really designed for fancy network configurations. Our goal is less about having the fastest connection (although that's nice) but to ensure it's "fast enough" to play what you need without issues.

If there were general issues with SD card boot on RPi5 boards we'd be flooded with reports, and we're not, so it's likely to be something local. I'd start with updating to the latest board firmware, and experimenting with another SD card.

READ: https://wiki.libreelec.tv/hardware/amlogic (then use the correct image; hint, it's not the WP2 image).

mount -o remount,rw /flash
fdtput -t i /flash/rk3288-tinker-s.dtb i2c@ff140000 status okay

It's probably easier to use "fdtput" to make the modification. I think that's ^ correct.