from the release notes:
"Connection failures to anonymous and guest shares are normally solved by creating a local machine user account and password credential for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access."
QED
Under-voltage warnings - Raspberry Pi Forums
^ First result returned from typing "pi disable voltage indicator" in Google. Took me ~10 seconds.
There are patches for VP9 support for Amlogic in Kodi but we don't have confidence in the underlying kernel code, it needs some work before the developer who's looking at it wants to submit upstream or consider including them in public releases. It will happen, but it will take time.
"SMB2 will use too much resources" wins this months "most bogus comment" award 
.. aside from the fact that SMB2 is both more secure and gives better throughput performance, the comment is, just, wrong.
In that case you'll need to make a custom build with either different build options or cherry-picking the required binaries from the Samba build folder to somewhere appropriate in the squashfs SYSTEM file image.
Or you find another solution. The only thing that jumps to mind is a webserver on a Windows box that hosts a CGI script to perform the shutdown command, and then you only have to call a URL from the LE side to invoke the script.
Or Google .. i'm sure there's another easier way. Controlling Windows boxen isn't our area of expertise though.
The system log doesn't show anything useful but it looks like Xorg might not be running.. hence Kodi cannot detect the GPU device and aborts. I've no idea why Xorg might die. However, make a backup and update to 8.1.2 (best) or 8.0.2 (okay) ..because even if somehow an issue is diagnosed on the 7.x release you're running it will never be fixed - all development stopped 12+ months ago. Start over with a current release and post again if the problem is still present.
VDR server is in the LE add-on repo. VDR client is in the Kodi add-on repo. Add-ons for LE are installed only through the GUI not apt-get (which does not work on LE). Server and Client do not talk to each other via SSH.
openvpn --config /path/to/file.ovpn^ something like that. There are LOTS of tutorials online about using OpenVPN .. we are not known for our love of spoon-feeding lazy readers.
I don't think this error is related to SMB protocol version. I have a hunch it has something to do with authentication and/or anonymous access to the shares on the Win10 box. I'm interested to know if you are using anonymous access, a dedicated kodi user/pass, or the Win10 logon user account, and if it's the logon account whether it's normal user/pass or what's known as a Microsoft ID, e.g. [email protected] or similar MS domain?
It indicates the Raspberry Pi wants more current than the PSU can provide. Shorter/better cables or a PSU with a higher Amp rating will make it go away. I think these days 2.5A or 3A is the recommendation.
Before debating drive support check that the disc you are attempting to play has keys in the KEYDB.cfg file. You can also tail the Kodi log and if you see errors about encrypted content .. it's because no key exists to decrypt it.
Kodi must have permission to access the shared content on Win10, which is done by setting access controls on the content. Do you share content using a local machine user/password or what's called a "microsoft ID" account, e.g. [email protected] ?
zip the firmware instead of tgz
Well no.. but you didn't share that nugget before. Is this an LE vs Android comparison or .. ??
"touch /storage/.config/debug_connman" and reboot, then "journalctl -f" to see the live log output of connman while you attempt to enable the tethered hotspot. I forget what the actual error message is but connman output is readable (if very extensive/verbose) and it's a fairly clear message about driver support .. but generally it either works, or the driver doesn't support it.
shut-down-your-windows-pc-remotely-from-linux
^ That might work. We have the samba stuff although we don't compile with all possible options enabled which restricts some functionality. No harm in trying though.
Connman "polls" for new networks and periodically updates the list of visible SSID's in the connections screen. It also has a hard-coded behaviour of preferring Ethernet over Wireless so if you have a wireless connection active and connect Ethernet the latter becomes the primary connection. The wireless connection will remain active but it will lose the ability to route data off-subnet.
Tethering requires a wireless driver that supports AP modes. Not all drivers support it and it is not possible to reliably pre-detect whether a driver supports it so the option shows in the GUI even if the driver doesn't. If it doesn't work, 99.99% the driver doesn't support it.