When we dropped support from OE (about 3.5 years ago) there were approx. 1,500 total i386 users in 400k+ active installations. The decision to drop was about saving time/effort during x86 development and was never about whether 32-bit things could be built. There are numerous other platforms that remain 32-bit which ensures a level of compatibility if you patch support back in.
GitHub - maideii/LibreELEC.tv-Intel-i386: Just enough OS for KODI might be worth a look if you self-build.
I wouldn't make it more complicated than exposing a list of supported actions and allowing users to set an alternative /path/to/pattern.png
The chip is S812-H in my box (H i think stands for hardware acceleration or something like that)
The -H designation means additional licensing fees have been paid, e.g. Dolby DTS, Widevine and PlayReady. This enhances playback capabilities for things like Netflix under Android but has no impact on Linux where there are no native DRM capabilities. It normally indicates a more reputable box as the far-east manufacturers racing for the "cheapest box" title aren't going to pay for something that's not essential.
You shouldn't need to create things twice (as Iridium describes) but not "ejecting" the SD card before removing will result in an unclean filesystem and Linux frequently refuses to boot from unclean filesystems.
If you want support provide a Kodi debug log that shows a clean system.
Samba 3.6.5 in LE 8.0.2 only speaks SMB1 and Win10 after the creators update only speaks SMB2+ so nothing can be reconfigured to work. Your options are a) updating to a current Milhouse (which is Kodi Leia) or self-build version of the forthcoming LE beta based on our 8.2 (still Krypton) branch, or you wait patiently for the 8.2 beta/release. Those contain Samba 4.6 which supports SMB2+ out of the box.
Hyperion is in our add-on repo (and Hypercon to match is on the wiki) and should work fine as-is today with most of the frame-grabber based Ambilight kits. Normal "pi" kits that use the GPIO pins won't be compatible as those interfaces aren't on the rear of a Slice box. In theory it's should be possible to drive something from one of the USB ports but that needs some tinkering and (based on previous conversations with Gordon) possibly driver support. I am slowly acquiring the physical parts to investigate and post-vacation I have a working Slice (CM3) box again, but I don't code so wouldn't be able to complete the task unaided, and for various reasons it's currently super-low on my personal priority list.
I was reading Arch Linux on The Surface Pro 4 | John Ramsden and you probably need to disable "secure boot" in the BIOS in addition to changing the boot order, but that's a random guess.
"Select" or "Save here" would be more accurate; you are selecting the folder/location to download into.
Thread moved.
Set the Skin to Confluence before updating, then update. The skin will switch to Estuary on update, but it won't throw errors. Now you can install the updated (Krypton compatible) version of Aeon Nox from the Kodi repo (if it doesn't update automatically) and switch back.
You will need to share specific model and hardware details about the card i.e. the PCI or USB device ID's before anyone can comment on how it might be supported or what is missing.
Possible issues:
a) If you have any pre/release version of the fall/autumn creators update installed this removes SMB1 server support for your Win10 shares and Kodi currently only speaks SMB1. A beta testing release of LE 8.2 with SMB2/3 support in Kodi should be out in the next couple of weeks.
b) If the server now speaks SMB2+ (no SMB1) even with the LE 8.2 version there will be no network browsing as this requires the network master browser to speak SMB1 protocol. You will have to add sources manually using the full server/share path.
c) MS is actively discouraging guest/anon access in their security patches and setting a user/pass is becoming mandatory. If you set user/pass it needs to be a local machine user account and not an MS hotmail/outlook ID account (e.g. desktop login ID) as the authentication schemes are completely different and the latter is known to cause some challenges.
Delete /storage/.kodi/userdata/guisettings.xml and any machine specific stuff will be gone. You loose all Kodi settings but Library DB's, thumbs and add-ons etc. will still be there which is the main content people are looking to retain.
I'll ask the ls.io folks can add it to their LE add-on repo
The internal WIFI on the RPi3 is not renowned for being fast and reliable. Use an external USB dongle and things should improve.
The http 401 refusal is probably due to an outdated version of the TVDB scraper add-on; the API keys used by Kodi in the add-on were revoked recently due to widespread copying/abuse from pirate add-ons. You need to update the scraper so it uses an updated/valid key.
If the box is not showing add-ons at all try add-on a 10-second "wait for network" boot delay in LibreELEC settings or context click on the Kodi repo and run 'check for updates' to see what it finds.
We operate to our rules not Swiss rules. You will receive no support in this forum with banned add-ons installed.
