LE 8.1.x defaults to SMB2+ connections and most Kodi versions are only capable of SMB1 connections. Until other Kodi releases catch-up with SMB2+ support you will need to go into LE settings and set the Samba version to use min SMB1 protocol.
^ all of this is in the release notes that nobody bothers to read.
SSH is all you need. You need to map ports on the firewall of your router (the internal iptables firewall in LE is active but has no rules) and organise dynamic DNS to make the box easy to find. You should also install SSH keys and disable password authentication as our default password is well known. That said, we do not recommend or endorse exposing LE boxes to the internet and the general rule is; if you need to ask how to do it you shouldn't be doing it..
LibreELEC on Windows ..
^ I wonder how that works? 
Kodi can be configured with sources that are on a remote server, and if they are not available the connection attempt simply times out after 30 seconds. It is not possible to add/remove sources in Kodi without stopping and restarting Kodi with a manually or script modified sources.xml. You can also set Kodi to use local sources and handle mount/unmount via a watcher script that runs as a cron task and tests for availability of the remote share, but again the Kodi GUI will always show the source as available as Kodi has no concept of things being ad-hoc added/removed. As Kodi gracefully handles timeouts on share access IMHO it's not worth bothering trying to use local mounts; just configure the remote shares in Kodi.
There's no reason it should fail, but RPi(1) isn't going to be a great device for Docker due to slower CPU speed and only 512MB RAM.
You'd need to share a Kodi debug log so we can see if something is reported during add-on install.
LE settings > Services > Enable BT
You cannot, but mods/admins can. What would you like it to be?
On normal (not RPi) installs it will be extlinux.conf or syslinux.conf (I forget which) not cmdline.txt and the active file is either in /flash or /flash/EFI depending on whether the device is/is-not EFI booting.
No plans to start Leia alpha builds until Kodi does, and the earliest we (Team Kodi) talk about that is late October. Don't hold your breath.
You may think it's silly, but we care about the security of our users: Stop using SMB1 | Storage at Microsoft
home > add-ons > program add-ons > is an alternative route to home > settings > libreelec which only exists in the default skin
If hardware fails to auto-detect port speeds correctly the solution is normally changing cables, hub/switch/router ports or something physical not tweaking software. If you ever need to force a port speed, force it on the switch not the ethernet adapter.
It's also possible to disable the CD mount behaviour with a udev rule, see: LibreELEC.tv/40-modeswitch.rules at master · LibreELEC/LibreELEC.tv · GitHub which ejects the CD to force the mode change for a USB wireless stick that does similar things.
You probably need to set the embedded Samba server to allow SMB1 protocol support. Further information resides in the release notes.
"0x80070035 Samba" throws up a lot of Google results but always where the client fails to connect and not where file transfers fail at a specific filesize. The only thing I can suggest is checking the HKLM\CurrentControlSet\Services\LanmanServer\Parameters and ensuring SMB2/3 support is enabled how-to-enable-and-disable-smbv1-smbv2-and-smbv3-in-windows-and-windows
There is lots of hardware in the world. Unless you ask about support for a specific device we cannot give a specific answer.
HiFiBerry cards have been supported for aeons. The only known problem is PEBKAC.
Your box has a Realtek RTD1295 chip inside. This is not supported and we have no plans to support it.
