17:23:46.186 T:140435866674944 ERROR: CCurlFile::FillBuffer - Failed: HTTP returned error 401
17:23:46.186 T:140435866674944 ERROR: CCurlFile::Open failed with code 401 for http://api.themoviedb.org/3/search/tv?Have you disabled automatic add-on updates in Kodi ? .. ISTR an API key was being abused and was revoked, but an updated version of the add-on was published with a new key to resolve it (or something like that).
Kodi still needs a bunch of rework to work with their new stuff, and right now that development has a much lower priority than all the standardised graphics stuff that won't require so much jumping through hoops.
Make sure you safe eject from Windows else the NTFS volume is 'dirty' and Linux will refuse to mount it to prevent filesystem damage. If that is not the issue run "dmesg | paste" and share the URL (after a clean boot, with the drive connected) so we can see what the kernel thinks.
Our opinion .. it looks like a log file. Next question?
In that case it's a no then. I'll update the 8.2.0 release notes.
The 5.0.10 version shows up here for me, so it's present in the Kodi repo. Perhaps you need to refresh the repo manually.
Kodi can run in SD resolutions on most devices (it depends on what the hardware allows) but the default Estuary skin is designed for 720p minimum, so things will look strange.
changes built/pushed to the repo
not the most simple process, but it can be done
vpeter ^ do we have support in the iMX6 kernel? .. if there's something missing and it can be added, I am working on 8.2.1
It's not platform unique, but it has to be compiled for each specific platform
Yup.. it would be Kodi settings no LE settings
You need to manually unpack the backup tar file and selectively restore items else the "full restore" process is reverting the box to exactly the same state it was in before reinstalling, i.e. nothing changed.
From what we understand those images are a "greatest hits" of hacky patches previously created for OE builds respun as an LE image. They are nothing to do with us. Proper support for some Allwinner chipsets is now being worked on, see recent blog posts on our website.