I tested on RPi3 and I can confirm that reverting commit 4cd13c21b207e80ddb1144c576500098f2d5f882 completely fixed the issue.
^ to be pedantic, it works around the issue, it does not fix the issue. Adding patches is only a short term solution and we don't want to add patches all the time as it impacts long-term sustaining of the distro. At least we now understand where the issue lies.
There has been contact between developers on the AMD side of things and their work on VAAPI should (no guarantees, but should) fall into line with the future Kodi linux graphics architecture we're driving. No timescales though.
Unless you've seen a particularly cheap AMD card to acquire I'd stick with the nVidia card for a while until the way forwards is more visible.
There is not much interest in developing for the 8726-MX chipset in those boxes when something 10x better can be acquired for $30 these days. It can probably be done, but there is probably not nicely written guide or pre-pacakged release.
You can keep asking, but no friendly guide for hardware porting exists, and there are no plans to create one. There is an extensive library of "prior art" in our GitHub repo. If you have the skills for the task, or the aptitude to learn them, everything you need is there.
Intel drivers in the Linux kernel do not currently support HDR, but development is ongoing. Kodi Krypton also has no formal support for HDR, but this is expected to become part of the Leia release. If HDR is a big requirement you will have to suffer Windows for a while longer.
Old routers may require SMB1 and the legacy security option to be forced. It's a simple change in Kodi SMB client settings.
In future please ask for a thread to be moved instead of posting the same thing twice. The previous thread has been deleted.
Last I heard Xtreamer went bust, hence the lack of website. One less GPL violator in the world 
There are a couple of community efforts for S812, but it uses the older 3.10 kernel which doesn't see much activity or focus. Look for S812 threads.
It's not an add-on, it's a compilation dependency for the Chromium add-on, hence in the addon-depends subtree
The add-on is in the LE add-on repo.
The entire ecosystem of Kodi depends on Python 2 today so it's not something worth chasing just yet. Kodi will effect a hard transition to Python 3 (dropping Python 2) with v19 and there are posts and a dedicated developer transition-help area on the Kodi forums to support this. We already did some prep work for this change, but more will be required once the actual transition starts.
It probably requires the older 304.xx driver instead of the current 340.xx driver. There is usually a thread with someone sharing a build with the older driver in these forums.
You will also need to restart Kodi first.
try /storage/.kodi/media/Fonts .. F not f
Nothing to do with malware, only unreliable hacking of the Kodi codebase. Just because something works, does not guarantee it works well.
For official dev purposes vmware does what we need, and we don't formally support it. If the community wants Hyper-V support, the community needs to band together and create/maintain a community release that provides it. If we see strong demand we can always later adopt the changes, but from experience virtual things are very niche. In its heydey the 'Virtual' image saw a maximum of 38 users. That would currently be 0.0001% of our userbase.
There are some "dual audio" LE builds in circulation on the internet. Not available from these forums, and not endorsed as a great idea (as the code is hacked up) but might suit your purposes. Google has details.
WebHome < U-Boot < DENX <= anything capable of using Android and LE will be using u-boot.
