Posts by chewitt

MacOS would ignore the ext4 partition and mount the two FAT32 ones, but as Windows doesn't understand multiple partitions on USB/SD media there isn't much point. Request denied

S912 is disqualified for having no proper Linux drivers (forcing use of Android drivers in a compatibility fudge). S905X is technically the best chipset, but all boxes are crippled with 100-BaseT Ethernet. S905 is thus the best real-world option as it has 95% of S905X features and 1000-BaseT Ethernet on most (not all, but most) boxes. If you purchase a $cheap box from various far-east websites expect a more complex install process, zero support from the vendors, lower quality internal chip choices, and frequently shitty firmware and manufacturing practices. Caveat emptor..

No tapatalk support unless someone writes a plugin for tapatalk. Stats show there are typically 35-40 active users of tapatalk (max) in a week so it's something we'll continue to track but it's not a high priority.

We have to balance the importance of the security update against the ignorance of our userbase. The breakage issues with 17.2 that result in 17.3 mostly don't concern us so we could ship something quickly, but then there are tens of thousands of users who will whine and moan like crazy if we give them 17.2 once 17.3 is available. So for the sake of waiting 12h while Kodi fix the 17.2 issues, we'll wait. Meanwhile it's 4.40am here and I'll get back to building test releases so we can move quickly once things are merged upstream so that "but you're not treating it seriously" whiny folk can get off our case and go back to polishing their tin foil hats.

Fixes will be done against master branch (Leia) but backports to Krypton will be considered if the fix doesn't touch too much code.

Not for community builds unless the developers create a custom channel.

Check Kodi github for PR's that fix the issue, and if none are found report the issue via Kodi forums, which will be triaged and will eventually end up with a bug report in Kodi trac. If you don't report it, the long-term likelihood of it being fixed is low.

We don't provide support to users of piracy add-ons.

I put the incorrect githash in the original 17.2 update PR, but this has now been corrected. However Kodi has found some issues with add-ons that will result in a 17.3 release soon-ish, so our 8.0.2 release will be delayed until upstream has things sorted.

Kodi depends on smbclient which is obtained from the version of Samba installed in the OS. LE is currently using Samba 3.6.x and the first version which supports SMB2/3 connections is Samba 4.1 (current release 4.6) so unless you create your own custom image Kodi will only support NT1 (SMB1) connections. We've been investigating what's required to move up to a newer Samba version in Kodi but since SMB is full of implementation quirks we've discovered as many problems as benefits. There is no plan to bump Samba in LE 8.0 but there are tentative thoughts for a mid-year 8.2 release that bumps a small number of major packages and it might happen then.

You're the first user that I ever encountered in all my OE/LE days who plays video's via omxplayer commands. It's not required for our user audience and thus we are not planning to re-engineer Kodi audio support to accommodate alsa in the OS. Kodi development has also been focussed on MMAL for some time now - OMXPlayer is in sustaining/maintenance mode only to continue basic Kodi support for the dwindling number of first generation devices and even smaller group of people who want to run Kodi on a pi zero. Sorry.. but no.

The only thing you need to do is enable "disable password auth" in LE settings. You need to deploy keys and create authorized_keys but there's no need to edit other files.

Quote from televisi

Error received: Permission denied (publickey,keyboard-interactive).

Does it mean my remote machine (OSX) does not recognise the public key?

It means you are attempting to authenticate with a password, which is not a valid authentication method. If you allowed passwords the methods available would be "publickey,password,keyboard-interactive".

Quote from Demetris

Can wait to test these changes in
Lakka. Do you know if S912 will be supported too?

The Kernel work Baylibre are doing will fully support S912 hardware but Amlogic have no plans that I'm aware of to license fbdev drivers for Linux so you're stuck with the libhybris Android driver hack to make S912 work.

You can, if you self-build from sources, and right now it would probably cause you a load of problems due to recent upstream content merges that are still being fixed upstream (and on our side). Also consider that 64-bit Amlogic devices will hopefully jump from Linux 3.14 > 4.13 kernel and will end up with a completely new graphics architecture in Leia if things go to plan. I run a WP2 as the family daily driver and I won't be entertaining the idea of Leia code on it for 2-3 months yet. Leia is roughly targeting a year-end release.

First observation is that you're building from the master branch not 8.0 (see LibreELEC-RPi2.arm-9.0 visible in paths) and due to upstream doing some major merges in the last week you'll probably find things a little broken at the moment. We're deliberately waiting for things to stabilise before we fix up our master branch. If you want to build 8.0 run "git checkout libreelec-8.0" before building.

LE works with QEMU and for 8.0 there's a dedicated image for vmware (Virtual) but I'm not sure anyone has tested KVM. If it works, great. If it doesn't work, it's up to you to fix it

Check cables. Use different HDMI ports.