Posts by chewitt

user changes should go into /storage/.kodi/.smb/user.conf so that GUI driven changes don't remove them.

It's not really been discussed. Largely because most decisions depend on the next 3-4 months of Kodi Leia development.

Back-up the old config and clean install the box. I'm never surprised when spring cleaning all the old cruft out of an install solves problems.

Raspberry Pi 3 is always a safe bet.

There are no specific plans at this moment. Kwiboo (and others) started Rockchip work on the Tinkerboard, but that only has HDMI 1.4 and broken CEC so they picked-up a better spec no-name device and then moved on again recently to poke sticks at the ROCK64. The main objective is RK3328 support in the OS (which leads to good Kodi/mpv support) and not specifically creating LE images for the ROCK64 or any other device. There are fun decisions to make about RK3328 and Amlogic in the mid-term future

You can run Chrome in a Docker container, but that's the only option. It won't run natively because Chrome is released in pre-compiled binary packages that are not compatible with our OS; hence we compile our Chromium add-on from sources.

No, because it has a Rockchip 3229 chipset.

In LE 8.0.2 - enter LE settings - set update to manual - set update channel to libreelec-8.0 - check for updates - select 8.1.0 - let it update. This will give you 8.1.0 which will automatically update to 8.1.1 sometime in the next 48h (prob) and eventually to 8.2.0 when released.

LE before 7.0.3 or any OE devices need to do it the old way copying .tar files around.

I'd like to drop support for anything that uses the Amlogic 3.10 kernel as soon as we have a viable Amlogic mainline kernel that we can focus all of our development energies upon. That means dropping the Core which has a tiny userbase (so it's an easy decision) and the Play1 which has a load more users but an even older chipset.

Current indications are that we won't have an Amlogic mainline kernel for LE 9.0 (Kodi v18) so your Core box probably survives another release. No promises though.

The 8.2.0 release with have zero changes from 8.1.0 (and shortly 8.1.1) so you'd best read #6 again.

The OS configuration of LE on v8.2 will be the same as v9.0 - no plans to do major changes and the roster of binary add-ons we provide should be exactly the same. Kodi changes are unknown this far out, but as long as you don't go overboard with customised skins etc. things normally update okay. The kids box in our house has a deliberately "sensible" config and it's updated all the way from OE 3.0 to its current LE 8.2 config without any real-world issues. TL/DR; install 8.2 or experience a long wait

Kodi Leia release content will be discussed at a DevCon event in Prague in mid-October. Part of that discussion will be when to start formal Alpha releases. LE has no plan to do it's own 9.0 Alpha releases until after Kodi starts shipping theirs and we can assess the state of them on the current range of hardware we support. Right now I'd guess things are 3-4 months from Alpha and 6-months from release.

Milhouse images for Generic/RPi are available for those who like to be on the bleeding edge of LE development. These images are fairly stable from a core OS perspective but there is still major plumbing to change on the Kodi side.

There are no obvious errors in the logs .. apart from one message which shows the box accepting an SSH connection/login.

Not possible. The config is hard-coded and (same as a hotspot function on a mobile phone) is not designed to be user-configurable.

Removing the add-ons lines from the Logfile before sharing isn't the same as removing the add-ons.

You might need to force the SMB client in Kodi (in Kodi settings) to use a maximum of SMB1 for compatibility with an older Samba version in the router. Kodi settings > services > smb client

<6>[  307.216521@0] usb-storage 1-1.1:1.0: USB Mass Storage device detected
<6>[  307.217677@0] usb-storage 1-1.1:1.0: Quirks match for vid 152d pid 2329: 8020

^ random guess - make sure the USB quirks for the SATA adapter exist in our kernel

It appears some firmware went missing among the firmware repo cleanup's we've done. However, nobody has PR'd a change to re-add that firmware to the 8.2 and master branches on github yet, so the issue is not solved.