Users have been asking us about RK3568 and RK3588 support since boards launched (3-years ago now) and there is some work in progress here: https://github.com/LibreELEC/LibreELEC.tv/pull/7864
However HDMI output support has only recently arrived and media codec drivers are still in the early stages of being written, and until those are done there's not a huge amount of point in us releasing images; hence the slow pace of progress.
Ohh.. that's ancient (2006 ish) and the worst era for EFI boot support over USB in Apple firmware. I had a similar era/vintage mini some time ago and it was a complete pig to get Linux installed onto. USB boot was so flakey that I have fuzzy recall of needing to remove the drive and install Linux from a more modern system, then reinstall the drive, then faff about with rEFInd.
NB: Appreciate you have this device in-front of you, but a cheap RPi3B+ board will give a better overall playback experience.
You cannot use device-tree files for vendor kernel images on AMLGX which uses an upstream kernel. They are very different.
Start with an LE13 nightly, use an older/smaller SD card if needed. Once booted you can install the image direct to internal eMMC.
The settings moved to the GUI so advancedsettings.xml isn't required.
Also note that unless your network is broken, changes to the caching defaults are not (or are only rarely) required. If your network is broken enough to need more than 1GB of cache to support playback, the correct solution is fixing the network, not forcing Kodi to use some ridiculous cache value that will add more problems than it solves.
The log and screenshots show that you forced the desktop to 4K@30 and there is a single whitelist entry for 4K@30 .. which means you're attempting to force all media to play at 4K@30 resolution with Kodi upscaling everything itself. It's a recent i7 CPU with 16x cores so it has some grunt, but media apps aren't as multi-threaded as you might assume, so regardless of the specs that might not work, and processing e.g. [email protected] media (most movies) to 4K@30 requires a lot of compute. The log doesn't show any playback, so hard to comment on what goes wrong, but..
I'd recommend setting the desktop to 1080p and then whitelisting 4K@30/29.97/25/24/23.976 and 1080@60/59.94/50/24/23.976 and allowing mode doubling (hence 1080@25/29.97 are not required). That should allow Kodi to switch 1080/4K to native resolutions as needed, and the only stuff that won't be handled is 4K@60/59.94/50 which requires HDMI 2.0a capabilities in the AVR/Projector.
All suggestions long documented in here: https://wiki.libreelec.tv/configuration/4k-hdr
mglae Could ConnMan be patched to log failed attempts too? .. might be useful?
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.
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
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.
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.
