Maybe the people at Libreelec can somehow make it backwards compatible?
Maybe the people producing Argon cases can get their sh!t together and fix their product themselves? .. we (staff) are getting a bit fed up with the number of Argon users showing up here experiencing issues due to lack of software support and fiddly/iffy connectors/cables in ther case causing a range of connectivity problems.
It's best to ask for help in the Armbian forums where they have some experience with that driver. LE no longer uses the 4.4 kernel and that driver does not work on anything newer than ~4.10 due to crypto APi changes in the kernel.
ErikSwan https://github.com/raspberrypi/linux/ <= everything is there. There will be differences between upstream mainline kernel and the downstream Pi kernel, but there's a pleasing-to-see continual upstreaming effort so the differences are not so big. Note that you also need to combine this with Pi firmware and the latest ffmpeg version; not specifically for HDR (which is more of a DRM thing) but to ensure you have the latest playback fixes. FFMpeg changes are still being hoarded downstream; the focus is still on features/fixes before that effort will start in earnest.
If you really want to watch iperf(1) install docker and pull a container with the right version inside. I'll leave you to ponder on whether the need for docker on the host will consume CPU that could otherwise be directed towards maintaining Ethernet performance; e.g. whether or not you are the cause of observer effect 
I'd also comment that you can test by playing a movie. If the movie plays fine your HTPC + NAS + Network combo is "fast enough" to watch movies and you don't need to obsess about whether the NAS is achieving best-in-class or mediocre performance. Watching movies is more fun than watching iperf (any version).
You can edit the docker .service file (somewhere in the add-on dirs) to add the after dependency; don't forget daemon-reload afterwards to update systemd.
I'm also fairly sure you can just dd the LE image to eMMC, I don't think RK doesn't anything too fancy with boot unlike other SoC types.
I'm reaching the point where I read "Argon case" and some combination of audio/video problem and I skip ahead to the next thread.
Get a flirc USB device and use any remote you like. You won't regret it.
"Feedback is welcome via the forum, but please do not expect support"
Thanks for the feedback. No further action required.
Most of the LE filesystem is read-only which would explain the permissions error. You need to use a writeable area like /storage or if using a removable drive, somewhere under /var/media/<drive> where the drive is auto-mounted. I'm not anywhere near an LE device to check but I'm not sure /media is a valid location in the OS.
If you are unable to umount the drives something is using them and this needs to be stopped first. If they are removable drives; disable the samba service which is auto-sharing them .. that's probably the reason.
If you apply Pulse config via /storage/.config/pulse-daemon.conf.d/daemon.conf it will be processed at startup and overrides the embedded config file before Kodi starts. The other alternative is creating a systemd service file in /storage/.config/system.d to run commands or a script with dependencies to set when in the boot sequence the service is run, e.g. after Pulse and before Kodi.
Run "getedid create" from SSH with the Pi connected to the powered-on TV .. it will dump the EDID data from the HDMI connection to a file and change the boot configuration to use the file; then the Pi always sees the TV as connected.
That's a WeTek Play 1 (WeTek OpenELEC) box (8726MX chip) not a WeTek Core (S812). NB: dtech If you do find a Core for sale anywhere that takes PayPal we're happy to fund it.
Kodi supports multiple weather add-ons, depending on where you are in the world, but these are not "apps" that you can do things with from the SSH console. Under the hood the add-ons are just fancy Python scripts that poll online sources for data and populate that data (via APIs) in to the Kodi GUI. I suggest you start over by explaining what you're trying to achieve in more detail.
To better answer the original question .. Yes you can backup/restore using the settings add-on.
Have you experimented with the 4K60 enable options? .. If those are set and the TV supports 4K it will try to use them, and then we often see issues with cheaper cables.
touch /storage/.update/.nocompat
wget https://releases.libreelec.tv/LibreELEC-RPi2.arm-9.2.8.tar -O /storage/.update/
reboot^ I think you should be able to just SSH into the console to download the correct image file and cross-grade to the RPi2 image. You need to disable the compat check with the touch command else it will flag you are using a different image and abort the update.
I've no idea. I've never bothered with skin editing to set defaults because the effort involved will be greater than just setting the view type the first time I navigate into some new part of the Kodi GUI.
Each section of the Library (Movies, TV Shows, Collections, etc.) has its own view type so users are sometimes confused by why changing the default view is not a single global change and they need to set it again in other sections (each section) but once you have changed a section view and leave that section of the GUI it should remain changed. You will not be able to edit the skin xml files directly as they are located in a read-only filesystem.