Once kszaq finds time and decides to build an agile build and netflix, prime video,... will work it'll be amazing.
I won't build Kodi 18 until it is in beta stage.
[hr]
Any update on this? I'd also like to rule out this exploit.
As far as I can tell a Samba update is in the works: samba: update to samba-4.6.3 [backport] by MilhouseVH · Pull Request #1628 · LibreELEC/LibreELEC.tv · GitHub
There are ca. 1400 commits from Krypton to Leia. Unless the fix is something trivial it is very unlikely that it can be ported. Have you reported the bug to Kodi bugtracker/forum?
Maybe I will switch back to MM kernel until mainline support is possible.
8.0.1l with MM kernel (freshly rebased on latest LE kernel): Index of /s905/8.0.1l-mm/
Source: GitHub - kszaq/LibreELEC.tv at 8.0.1l-mm
Or are there any dificulties, that stop you from build an image?
I have no free time.
Actually I have already built a version with MM kernel and all kernel updates that came along the way... but I have to test it before uploading.
Pseudo's x265 encodes are a great example of this. If you need samples, a quick Google search should reveal plenty.
This is a very bad joke.
Sent from my Nexus 4 using Tapatalk
I haven't bought K1 Pro.
Sent from my Nexus 4 using Tapatalk
Yes, 8.0.1a is my latest build that uses MM kernel.
Sent from my Nexus 4 using Tapatalk
[hr]
This isn't something that can be forwarded to Amlogic (and I don't know a way how to contact them) as I have imported only some parts of Nougat kernel. When I find time I want to make a build using "full" Nougat kernel to test.
Actually people report something opposite: better colour reproduction and no issues with Live TV thanks to updated decoders.
Sent from my Nexus 4 using Tapatalk
I bet this is not Jarvis/Krypton issue but Marshmallow/Nougat kernel from Amlogic.
Try using 7.0.3.012k and 8.0.1a. You should see the issue with the former and not see it with the latter.
Sent from my Nexus 4 using Tapatalk
Github commit log: Comparing 8.0.1k...8.0.1l · kszaq/LibreELEC.tv · GitHub
I will post user-readable changelog later when I have time.
Maybe it's a good idea to open a new thread for each release, and in the first post list the problems users encounter (brief) accompanied with the solution. This would make the forum much more professional looking and user friendly. Now everyting is "thrown" in one big thread, making it impossible to create any sort of structure and therefore people constantly asking the same questions over and over again.
I used to do this but people mix issues in threads. There is a sticky post with a request to create a new thread for every issue but most people don't care to read and/or apply the request.
For example: it took a VERY long time before the missing framedriver issue with s912 soc's was explained in a decent way . Now it finally got it's own thread. Even when the alpha s912 firmware was release, there still wasnt any explanation and people where thinking the framebuffer driver was found. Only after some time it was added to the first post that this wasnt the case and a brief explanation was added to this first post. Now finally things are clear for most users.
This is not true. From the very first build I put the information about missing fbdev driver for S912 in the first post. Before I published my first build (after LOTS of experimenting and work) there was a thread that explained again and again why there was no build for S912: thread-1653.html
And lots of people have daytime responsibilities and simply dont have the time to go through hunderds of forum pages.
Please remember that developers are also people with daytime jobs and families, they also commit their time to development.
I have to agree that the search engine is not very friendly, let's hope it changes when the forum software is upgraded this weekend.
afl1 If I understand correctly these patches are already uploaded to your report, right? I'd like to use them for my next build. 
Sent from my Nexus 4 using Tapatalk
You really ought to read the sticky thread on reporting bugs first: thread-981.html
You have missed the most important information:
6. Help identify your situation:
- include device type (S805/S905) in thread topic
- write which build you are using
- what device you have
You also missed this:
Known issues:
- 4K support is experimental.
If you're using S905(X) device, try using 7.0.3.012j build (for Jarvis) or 8.0.1a (for Krypton).
Please read the OP and my previous posts carefully. Kernel driver is not an issue here!
Sent from my Nexus 4 using Tapatalk
Integrating the driver should be very simple but we need some good will of chip manufacturer.
Sent from my Nexus 4 using Tapatalk
The driver in archive you provided is in binary format - it is a kernel module and cannot be used. We need the driver source code or at least an object file, e.g. 9082xs.o but in the second case it may still not work.
Sent from my Nexus 4 using Tapatalk
There are no Mali fbdev libs for S912 in the latest buildroot.
Sent from my Nexus 4 using Tapatalk
