Once changes to add $DEVICE support to our build system are merged I will adjust things to Slice/Slice2 are sub-devices of the RPi/RPi2 projects and then PR support to our main git repo. That should make long-term maintenance of Slice things fairly trivial regardless of who does the image building and publishing part.
For community/official status: There's no current plan, but there's a plan to have a chat about plans which might lead to a plan 
chewitt Is there a wiki for submitting the addons to your repo? I think zap2xml is at the point of being ready for a 1.0 release.
No wiki. You can submit a pull request (PR) to add the add-on to our main git repo, or if you'd prefer to manage your own repo, i.e. rates of change are still higher and you want direct control over changes and publishing, you can PR your repo installer to our repo. If you want to go the 'own repo' route we'd be happy to provide some edit4ever.libreelec.tv webspace to serve files from, or you can abuse free github hosting. Whatever works for you and users works for us
It's good to hear all is okay with the packaging; thanks for testing that. The alpha splash is used in all LE alpha builds. It will change again in beta and then revert to the "clean" one for final release. I still need to adapt Gordon's lirc enable/disable function into the settings app. Subject to me finding the time it will probably appear in the next alpha build.
If you send the requested log output we can tell you facts. If you don't send it we have to make guesses. We suck at guessing.
This is not a forum for Android discussion. For that you want Freaktab etc.
I'd like to stop this thread. If you want a hardware listing it should be in a maintained wiki page not a forum thread that very quickly becomes 20+ pages and hard to follow. I would also ask you to refrain from using the terms "to buy" and "not to buy" as forum rules ask you not to promote commercial products (and we'll extend the same idea to the wiki). I would also prefer if the eventual wiki page had a consistent maintainer who keeps the content up-to-date as LE software and vendor firmware evolves, i.e. not a free for all. Make sense?
belaid38 .. Please stop posting mediafire links to modified Android ROM's, this is a Linux forum.
You are welcome to point users at original WeTek wesbite/wiki/forum pages if they need to download Android ROM files. Otherwise this is not a forum for Android software hacks. Thanks.
It uses the MT7610 chipset. I created an experimental driver package for the MT7610 back in OE days which "worked" in a loose sense. The drivers that are in circulation (can be found) are poorly written and are missing kernel interfaces for a range of wireless features. I've never transported that package over to LE as the radio configuration is ultimately dependent upon a config file which you'd need to edit to set things like region code and we'd need to embed into the read-only kernel image (spot the editing challenge). If that situation ever improves we can add the driver, but I wouldn't hold breath. If you have some dev skills and can custom build LE it should be possible to hack things in using my prior art, but IMHO it's not worth the hassle and you are better off picking up another card. Find something that uses the in-kernel ath9k driver, it's the best written one.
in future please use the embedded paste function; it's easier for you and we don't have to download log files to look at them
I did a full rebuild with the 4.8.1 kernel bump which grabbed the correct/updated files and I now see the file timestamps matching other items which are normally updated as part of an OS update:
Slice2:~ # ls -l /flash/total 133800
-rwxr-xr-x 1 root root 1494 Oct 15 11:35 LICENCE.broadcom
-rwxr-xr-x 1 root root 126730240 Jan 1 1980 SYSTEM
-rwxr-xr-x 1 root root 48 Oct 1 13:07 SYSTEM.md5
-rwxr-xr-x 1 root root 13743 Oct 15 11:35 bcm2709-rpi-2-b.dtb
-rwxr-xr-x 1 root root 14417 Oct 15 11:35 bcm2710-rpi-3-b.dtb
-rwxr-xr-x 1 root root 13717 Oct 15 11:35 bcm2710-rpi-cm3.dtb
-rwxr-xr-x 1 root root 17932 Oct 15 11:35 bootcode.bin
-rwxr-xr-x 1 root root 47 Oct 1 13:07 cmdline.txt
-rwxr-xr-x 1 root root 3365 Oct 14 22:57 config.txt
-rwxr-xr-x 1 root root 1027 Oct 15 11:35 distroconfig.txt
-rwxr-xr-x 1 root root 4451 Oct 15 11:35 dt-blob.bin
-rwxr-xr-x 1 root root 9737 Oct 15 11:35 fixup.dat
-rwxr-xr-x 1 root root 6222256 Jan 1 1980 kernel.img
-rwxr-xr-x 1 root root 48 Oct 1 13:07 kernel.img.md5
drwxr-xr-x 2 root root 8192 Oct 15 11:35 overlays
-rwxr-xr-x 1 root root 3895684 Oct 15 11:35 start.elfimage files on the webserver are still named 7.90.007 but are updated.. would be great if you can do the full update test.
Post the full log else we cannot see system/environment information relevant to understanding the issue.
Plug it into mac OSX and disable journaling on the volume.
that can lead to data loss on the macOS side and is not recommended, exFAT is the best option.
there's nothing that fdisk does that parted cannot do, so no need for fdisk
The issue with Windows browsing (aside from it being designed by morons) is that there is not ONE configuration that works. This is due to different versions of SMB protocol and other OS-unique variations that have evolved in the 20-years since Windows '95. So the only consistent thing you'll find when you look in forums is one group of users (with a certain era of OS) arguing that their defaults are the enlightened best approach, while another group (with another era of OS) argue for a different set. The current configuration in LE is not the best configuration (as that doesn't exist) but more of a "least worst" arrangement that results in fewer support posts. You are encouraged to figure out what works best for your scenario with a custom samba.conf.
Or lets avoid statements which become promotional about vendors in our forum. Thanks.
It's a packaging issue in the image. If you download dt-blob.bin and replace the current file in /flash it should work fine. At least, I have normal stereo output here, a cable needs to be acquired to test the optical output.
Virtual is used daily by developers and is a valid project to use as an example. I added WeTek_Play_2, WeTek_Hub and Odroid_C2 to the page.