echo "options cfg80211 ieee80211_regdom=DE" > /storage/.config/modprobe.d/cfg80211.confRPi3 defaults to a safe "global" wireless regulatory domain, but this only sees channels 1-11 and may not be fully compatible with the radio properties of some access points that are using a local-country regdomain. The above 
sets the regdomain for Germany (DE) and other locations generally follow the normal ISO country codes; GB, RU, CN, US, etc.
Have a look at MusicBrainz 'Pickard' .. it's much (much) more than a tag editor, but if you want to cure a whole bunch of other tagging related things that you're probably unaware of in your library and ensure your media scrapes correctly it's the best option.
It's something we already do in Generic/x86_64 with Chromium. The main use-case we've seen is access to services like Netflix or Amazon which also need flash or widevine support. It's probably not too hard to create/package netsurf as an add-on, but would it support those services?
In Kodi Jarvis favourites is a buried item with a star shortcut on the Kodi home screen. In Krypton favourites has been promoted to a top-level item on the home screen (if you have it exposed in skin settings) so there is no need for the star shortcut. In other skins the decision to show anything is up to the skin author.
add "dtoverlay=pi3-disable-wifi" to /flash/config.txt and reboot
Time to add SHA256 checksums in our build system. Who will start on that (I have free time)?
I think it's time we did this. Let's chat.
Did you migrate/restore anything (i.e. config) from the WP1 install? .. I'm using a WP2 with the stock remote as my current 'daily driver' and there's no repeat issues in the default image.
At this stage it's too early to say what the future holds for 32-bit Amlogic devices. Kodi needs to clean-up Linux support similar to how the Krypton move to "mediacodec" simplified Android support. In the long term Kodi wants a V4L2 based Linux video architecture, and that almost certainly requires Linux platforms like Amlogic (and Raspberry Pi) to be running a current/mainline Linux kernel with V4L2 video drivers. Older 32-bit S802/805/S812 devices are stuck on an ancient 3.10 kernel that falls wildly short of that requirement. If code clean-up progresses quickly it is quite possible that a 64-bit Amlogic device will be required for Kodi v18 support on Linux.
It depends on the Kodi v18 schedule. If Kodi decide to do a shorter sprint for v18 that results in an autumn-ish release then your 4.11+ fix will arrive in the next series of alpha/beta builds as we move towards that release. If it looks like v18 will run longer (end of year-ish) then we'll organise a mid-year 8.2 release with a newer kernel/mesa to pick up improved Intel hardware support, and we'll probably throw in a switch back to openssl for some bonus credit. So nothing firm yet, but we have Kodi DevCon over the next few days and that might firm ideas.
That can probably be solved by tweaking openvpn configurations to set appropriate routes. Or you go shop and get a proper router, because the hotspot feature in LE is not and never will be a proper wireless router.
OE's update process has no protection against "wrong image" updates (unlike LE which does) so it's blindly applied the RPi2 .tar file to the boot partition and this has overwritten the SYSTEM file. The box still half-boots because RPi devices use a kernel.img file not 'KERNEL' so the original KERNEL file is still present and being used. Half-booting doesn't help though 
If you took a backup (and moved it off-box) before updating the fastest option is to create a new installer USB using our USB/SD creator app and then clean install LE on the box. Once it's up/running you can restore the backup.
If you did not take a backup you need to boot the box from an LE install USB or Ubuntu "Live" USB; both can be run in Live mode. LE boots/runs and can give SSH console access to run some terminal commands. Ubuntu gives you a full desktop environment. Basically you need to mount the first partition on the internal HDD and overwrite the KERNEL and SYSTEM files there with new ones extracted from the LE 8.0.1 update .tar file, then reboot and you should be running LE.
NB: On the download page there is a drop list (above the pi logo) and if you click this, you'll see an option for Generic x86_64 hardware. Click that and the page links change to show the Generic image update files. If you don't click it.. you're looking at RPi2 links.
Ideally this is fixed by setting the TV to "just scan" or it's equivalent. Plan B, use calibration in Kodi. Zoom is wrong.
[Linux] Generic drm/kms implementation by lrusak · Pull Request #11955 · xbmc/xbmc · GitHub
this is also supporting current efforts with the Rockchip based TinkerBoard and Amlogic aarch64 devices on a 4.11 kernel, and sometime in the next week or so an Exynos based DragonBoard should end up in the hands of the same developer. There are no plans for LE to "support" DragonBoards but it has the best (or most-complete) V4L2 stack of any ARM device so it has development uses as we figure out fun stuff like atomic modesetting. Things are moving in the right direction and it's not a unicorn, but there's a HUGE amount of unwritten code between where we are today and the next release of Kodi using Wayland etc.
So best support is and probably always will be Raspberry Pi, but after that there's no clear winner. Right now I'd give Amlogic a minor edge but that's only due to knowing more about the fugly state of their current kernels and the efforts Baylibre are doing to correct them. Rockchip has more code in the mainline kernel, but we know less about them.
NB: S802 is 32-bit and none of the current mainline effort targets Amlogic 32-bit devices. There is a fair amount of IP common with aarch64 platforms but there are differences and nobody is being actively paid to code for them.
chmod 700 /storage/.cache/ssh
chmod 600 /storage/.cache/ssh/*
chmod 644 /storage/.cache/ssh/*.pub I believe that should restore things back to defaults
Some Amlogic devices suffer from installation quirks/niggles (unique device trees etc.) and some have shitty firmware so there is always a slight gamble to be made, but 64-bit devices from reputable vendors have a lot of promise and we are working very closely with the developers Amlogic contracted to rewrite and upstream 64-bit platform support into the mainline Linux kernel. That effort should be more or less complete around Linux 4.13, although graphics fettling and tuning will take longer - but we already have private test builds working on 4.11 and the video architecture changes needed in Kodi v18 are in process too. So the future is a little way off.. but very visible. Amlogic is not at pi levels of community focus but it's move a long way from the hideous codebase it was 1.5 years ago. I have zero expectations of S912 fbdev drivers so the 'libhybris' wrapper will continue as the only option for S912 devices like the one you mentioned. That hack seems to be holding up, but it's still a gamble.
I would expect all serious development on 32-bit Amlogic platforms using ye ancient 3.10 kernel to dry-up once mainline support for S905/905X arrives around Linux 4.13, and there is currently zero support for Exynos chips in current Kodi although DRM/V4L2 we're doing might open the door to that changing before v18 ships. Those factoids might narrow your selection criteria.
The sucky answer is "build on Ubuntu 16.04" .. we know that works.
Just create a release thread in the main support area. If it ends up growing legs and runs with lots of posts and activity we'll move it somewhere more permanent, although I suspect we've caught up on support in the near-ish future as 4.11 released yesterday.
I'd ask for your changes to be in your GitHub repo, and for a URL to the repo in the first post of the thread. Keep the first post up-to-date with the latest build details and comments.