If the problem is only seen with Bello Skin, it's either a bug in the skin or the skin is uncovering a bug in Kodi.
First thing to do is test with LE 8.1.0 and a Milhouse v18 build to see if the issue is already resolved. If nothing is fixed, I'd start with posting the issue to the Bello skin support thread in Kodi forums. The skin author is welcome to contact us for debug assistance if they want.
Quasar is a banned Kodi add-on. No support will be given when using such add-ons.
^ repeating in case the previous post wasn't clear
pastebin a Kodi debug log demonstrating the problem please
I would avoid the Core box; not because there is anything particularly wrong with it, but because it's stuck on the same 3.10 kernel as your current Play1 device which makes it increasingly unattractive for long-term support.
Kodi settings > services > smb client > set max client protocol version to SMB2 .. it will prompt to reboot. This should prevent Kodi attempting (and it looks like failing) to autonegotiate SMB2 connections. Or update the software on the NAS and enable SMB3.
Click on downloads – LibreELEC and download the USB/SD creator app that's linked at the top of the page. Use that to create an RPi2 SD card and then boot from it.
I usually see this PEBKAC error when people visit GitHub and download things using the "save as zip" function; which gives them a zipped copy of the GitHub repo which is not the same thing as the zipped add-on they were hoping for.
For further help you will need to specify the add-ons and state where you obtain the files from.
codesnake there are no objections to posting URL's to the official WeTek Android image here (or linking to the appropriate WeTek forum thread)
It could be a successful crowdfunding project if someone dares to dive in. There is a lot of people being unhappy with closed nature of Mali drivers.
The majority of people who are unhappy have no useful skills for the task. The people with useful skills for the task typically have no knowledge of ARM Mali internals and thus aren't likely to succeed at the task; which makes it an unattractive challenge. The people with useful knowledge of Mali internals are all ARM employees who signed NDA's that result in dismissal for gross misconduct if they share anything. It all sounds like a right negative whinge (and it is) but finding people who are prepared to invest the time/effort in this stuff is hard; hence the lima project ran aground some time ago.
How old is the NAS (and version of Samba it runs)? .. In testing we saw that some old Samba versions don't negotiate SMB3 properly and need to have SMB2 set as the "max client protocol" version. Kodi now allows that to be set - specifically for that reason.
urghh..
edit: been reading more and it seems there is more needed directly from amlogic. could anyone point me to something i can read that shows what exactly is needed, and how the drivers on that link aren't whats needed?
If you have to ask how ARM video licensing works (technically) there is no chance of you making a positive and insightful contribution to the "what's needed" debate. So I will summarise the problem and options (again):
Problem: The open-source drivers require a closed-source blob provided by ARM that is tethered to an unknown combination of hardware identifiers specific to its IP licensee (Amlogic). Options are:
a) Amlogic opens their chequebook and licenses the closed-source libmail.so library from ARM. This is not cheap. In Chinese culture it is impolite to say no, which is probably why the CTO of Amlogic smiled nicely, didn't say no, and also didn't provide any affirmative answers when I explicitly asked about plans to license S912 fbdev drivers in a face-to-face meeting earlier this year.
b) ARM suddenly develops a sense of philanthropy and gives us a free universal libmali.so driver to use; thus breaking the entire ARM licensing business model. I'm an optimist, but I also have a tiny suspicion it's not going to happen.
c) Reverse engineering of libmali.so allows us to defeat the licensing system used by ARM and hack a works-on-all library. It's not theoretically impossible and we already poked sticks at things. Despite being an optimist I suspect the $billion-dollar ARM licensing machine knows more about protecting its IP from reverse engineering than we know about reverse engineering.
d) The fully open-source "lima" driver manages to advance a decade in code maturity and provides a viable alternative driver. Considering the lima project is basically dead for the last two years; this is something I'm not optimistic about.
run "cat /storage/.kodi/temp/kodi.old.log | paste" and share the URL please .. if the video in the skin is playable by Kodi it should play.
Share after a clean boot so we can see the early boot messages. That logs shows nothing.
So how do you enable intro videos?
Formatting won't achieve anything. I'm told we compress the kernel with xz (and overall squashfs with gzip) but we can't think up a scenario where this problem could occur. Milhouse (btw) is the staff member with a Revo3700. He reports no problems with his Leia images.
If you are seeing %H there is a custom samba.conf in use and you need to update it to be based on the new Samba4 template. Basically there is a conflict with Samba 3 configuration and this causes Samba to not start correctly. There is a comment in the release notes that directs people to do this, but as nobody reads release notes I guess most will discover it the hard way.
No official LE images support intro videos, so what image are you running?
There is a wireless hotspot feature that can be enabled in the LE settings add-on if you have a compatible wireless card (drivers need to support AP mode). If that's not what you're looking for you need to explain your definition of ad-hoc network.
