Posts by chewitt

The canupdate file must be at /usr/share/bootloader/canupdate.sh within the SYSTEM file either by embedding it directly into the filesystem or being picked from a "bootloader" folder at project or device level. If you put it anywhere else it will not be seen or used.

[ "$1" = "iMX6.arm" ] && exit 0 || exit 1

Your current script passes imx6.arm as $1 (the $PROJECT.$ARCH of the current image) to the script which evaluates true (exit 0) so the upgrade continues. In the PR I've changed it to ^ this which will evaluate false (exit 1) and fail .. but as you point out, if the older image doesn't support zstd it will also fail.

Test images are on Index of / .. there will be no "official" alpha images for LE10 because too many people don't read release notes and will blindly update and then whinge when it's not a) exactly the same, or b) perfect. Better to field user Q's about why there is no official image (which didn't break anything) than deal with proper support issues.

Kodi > Settings > Services > SMB Client

HEVC has been working for months (H264 is/was the hold-up). 4K is working now (not 4K60, but that's will be along eventually). HDR is complicated but will come. Upstreaming will take time.. but getting it all working comes first. We aren't going to do a formal Pi release for LE10 out of an abundance of caution (we have hundreds of thousands of Pi users) but things are moving along nicely..

Ahh.. I was forgetting about the zstd change. That's good detective work and useful info

Quote from Stereodude

Thanks! I didn't realize the setting had moved to elsewhere in the menu.

It's hasn't moved .. it's always been there

WP2 has eMMC not NAND storage (despite what the WeTek boot splash says). I'm still working on mainline u-boot support for WP2 (and WH). It is not currently possible to truly boot the box from internal emmc as MBR structures and boot firmware conflict with each other (both need to reside in the first sector of emmc). The vendor u-boot has hacks to coexist things but we don't want to replicate this as it would never be accepted upstream. However it should be posssible to have mainline u-boot on an SD card and LE files on emmc storage.

Setttings > Playback > Adjust refresh .. set to start/stop

LE does not support the nVidia shield at all, but it's the main reference device for Kodi Android support and works well under Android. WP2 support is coming along but still a few quirks to figure out.

Most of my DTS audio disks are raw .wav files combined with a .cue file for Kodi to scrape into the audio library.

SMBv1 needs you to set the version min/max to SMB v1. If you set min v1 and max v3 it will continue to connect at v2 (default) and fail.

I have fuzzy memory (git history will confirm) but I think we added canupdate.sh for LE v8.0. I know it was not part of the OpenELEC codebase that we forked from or the initial LE v7.0 release. The update process is controlled by the older image (not the newer) so this means there is no check against canupdate.sh when updating from older OE or LE v7.0 images. It is also not an upgrade script or place to effect complex changes. It is a deliberately simple check to see whether the update should proceed or not. The calling update script simply passes $PROJECT.$ARCH so crossgrades between arm and aarch64 of the same $PROJECT can be allowed and wrong $ARCH or wrong $PROJECT updates prevented. If the canupdate.sh script exits with "exit 0" update proceeds and if it exits with "exit1" update is blocked.

In the current PR that I submitted I'm simply checking "if [ "$1" = "iMX6.arm" ]; then" because all "legacy" images are "imx6.arm" (not iMX6.arm) so we can fail the update. I've included an "echo" message but In hindsight (thinking about it now) I think the on-screen failure message comes solely from the update script that calls canupdate.sh and I think there is no way to pass a nice message back or display on-screen info from canupdate.sh .. the only thing passed back is the exit code.

There are ~380 active installs for imx6 images (and approx. the same number of OE installs). Legacy LE images stopped at v8.2 and OE ended at v8.0 (which was a mess so most users remained on v7.0). Those installs are now old and we see greater problems (mostly from add-ons) when updating older installs to current. I appreciate the desire/intent to support a nice upgrade experience, but IMHO the simplest and best option is to force a clean install and not attempt to handle upgrades and migration from legacy images.

IPv6 support in ConnMan is currently quite broken. It works enough to get a connection for normal network, but WireGuard will not work over IPv6. It has been reported to the ConnMan developers but fixing it requires quite an effort so I am not expecting it to be fixed anytime soon.

Quote from Biomecanoid

.. so I that I may download higher bitrate movies.

We just lost interest in your problem.

Stick to answers in the Kodi forums kodi-pvr / pvr.wmc client 6.0.0-Matrix testing, stuck at loading timers

LibreELEC-AMLGX.arm-9.80.9-box.img.gz is an experimental mainline kernel image that includes support for the WP2 *but* there is currently no upstream support for the DVB card in the box and no HEVC so it might not be the solution you're looking for. Recent CE images will be more feature complete, but I have the impression CE are becomming more focussed on newer devices (and newer vendor kernels) as their latest kernel reportedly drops support for S905 (because the vendor BSP dropped support) .. so there's some renewed interest in the direction LE is taking.

Quote from chevy54

i have a Blu-ray audio DVD that i have archived to a .thd file . But Libreelec will not recognize or even display the files so that they can be played. any ideas on how to solve this would be greatly appreciated

Ripping it to a format/container or ISO format that Kodi supports instead of one that it doesn't would be a good start.

"docker ps" will show you that the installed containers are already running (probably) .. and "docker start|stop" will work too.