Is the wifi chip supported at all?
The upstream device-trees for Amlogic reference boards describe a Broadcom WiFi module and your box probably has something else inside. QCA9377 would be my guess for an S912 box, but others are possible.
The "box" image here: https://chewitt.libreelec.tv/testing/ includes a patch that removes the Broadcom specifics to allow other WiFi modules to probe and work. If that's the case, please report back and share the log URL from "dmesg | paste" - You can wget the image to /storage/.update and reboot to udpate.
If that image doesn't work you'll need to share a log from the original Android kernel or other working Linux distro or share photo's of the board so we can understand what chip/module is inside.
For context, here's the patch (sent to kernel mailing lists this morning by random coincidence): https://patchwork.kernel.org/project/linux-…[email protected]/
The HomeAssistant "add-on" seems to be running things in a Docker container, see https://github.com/sunfounder/hom…man5/Dockerfile - which might be a simple (albeit heavy) way to run things. The Dockerfile needs minor tweaks to replace variables with content to be used on LE.
From a quick glance at https://github.com/sunfounder/pironman5 it's probably not that hard to make a simple Python script to poke the GPIO bits required to change fan speeds. Elsewhere in this forum you'll find an add-on for the Argon40 case which also comes with a fan and will be doing essentially the same things, though possibly with different GPIO pins being toggled.
Sunfounder seem to be maintaining the integrations for other OS, so might be worth asking them to look at LE too.
Was this a clean install? Because based on the amount of installed addons, I wouldn't guess that.
Due to those add-ons being installed, support ends here too.
We have been using the same syslinux bootloader for aeons (unless EFI booting, but that's similar) so the drive should be movable between devices. You might need to reset the audio config afterwards as device names might/will change, but that's probably all.
No issues connecting to the repo from here (and the repo is not mirrored) 
The Nexbox A95 device-tree file in the upstream kernel defines no SDIO WiFi module, which normally means the module will not be probed and detected. It's possible the module is connected via USB instead; it's nnot unheard of but unusual in Amlogic boxes of that era. Ampak modules are normally using Broadcom chipsets, but which one? Logs from the Android/vendor kernel are needed else there are more questions than answers.
Some discussion/info on USB WiFi devices supported upstream: https://github.com/morrownr/USB-WiFi
RPi boards are best with cases that provide passive cooling, then there's no fan noise. The Flirc cases are great. No preferences on fans .. they're all much the same and what's available locally for you will be different for me and others.
I notice, with the latest bump of Kodi in both the nightlies and chewitt's experimental builds, the GUI no longer renders on my Odroid C2
I've pushed an update to the images in my share with that patch added.
This is a forum for solving LibreELEC issues, not reviving dead Android boxes. You're better off asking in an Android focussed forum that might have an archive of Android ROM(s) .. this is not one.
It's on by default and accessible with libreelec/libreelec credentials. You can change that in the LE settings add-on. If you want to fiddle with deeper samba features you can rename /storage/.config/samba.conf.sample to samba.conf, make edits, then reboot and your conf will be used instead of the embedded one.
Can I do this with libreelec?
LE runs a Samba server in the background, so shouldn't be an issue.
Have you tried a different USB flash drive?
would really appreciate if LE or the ConnMan developers consider to give LE such a basic functionality back.
We have not 'removed' anything that broke proxy support. Proxying in Kodi works. Proxying in the OS works too, but proxy config methods are application specific (not OS-wide/catch-all) so you will need to follow whatever conventions the apps require.
TrinitronX /storage/.profile can be created and used with LE for interactive shell config. If you want to export the variables to the system environment on boot this should be achievable from /storage/.config/autostart.sh.
Thanks for the confirmation, good to know it works 
darktigrous I've pushed updated images to my webshare that should contain the dtb files again. I'm interested to know whether this is working or not as I've rather forgotten status of things recetly (work/life is rather busy).
Probably best to report/flag to the devs working on inputstream.adaptive in the Kodi forums. It looks (to my very-ignorant on the topic eyeballs) to be something unsupported in the stream manifest which results in a stall, and then a recovery.
This PR will add support eventually add support: https://github.com/LibreELEC/LibreELEC.tv/pull/7864 - note that the RK3588 device does not have HDMI support currently (will come in a future kernel bump) and the PR is already 18-months old, so unlikely to be merged soon.
