You could always create/build something yourself cherry-picking commits from 8.0 branch, but I won't be creating anything official for Pi Zero W on our 7.0 branch as it is officially closed to further development.
Posts by chewitt
-
-
"probably" .. but I'd suggest you have a search in the code of add-ons in the Kodi add-on repo. Finding prior art from other add-on creators is usually more instructive than asking Q's to the wrong audience. In the LE forum you'll find people with expertise in the OS that runs the app, but we're not experts in the plugins that run in the app.
-
I'd like to see "journalctl -b 0 --no-pager | paste" from first boot (or after hard reset to clear all config) to see what that connect error is about. Share the sprunge.us URL generated.
-
Test an provide information from LE 8.0.0 because nobody is going to fix an issue on 7.0.3 now.
-
journal shows the atvclient driver being started, but lsmod doesn't show the module loaded. If you type 'atvclient' from the console do you then see any output from button keypresses? - btw, atvclient doesn't tie into the normal ir-keytable stuff. At some point it should be replaced by a more standard lirc arrangement. -
LE stores the SSH daemon configuration in /storage/.cache/services/sshd.conf but I have no idea if Lakka does the same. You should really ask Lakka questions in their forum.
-
Please see if this works: Index of /pizero/
-
Please see how this works: Index of /pizero/
-
which is not a bug as this is deactivated on purpose in libreELEC).
it is not deactivated on purpose in LE, it is not part of the VideoPlayer design in Kodi. We are not to blame for anything. We simply consume upstream code. -
Windscribe are probably using a certificate with a validity date beyond 2038 which hits a known issue in LibreSSL on 32-bit platforms that will not be fixed (not seen as a bug according to LibreSSL devs). If my guess is correct, your options are a) picking another VPN provider, or b) asking Windscribe to issue a cert with shorter validity period.
-
Soli, If you disable CHD and software decode Jarvis works fine (within the usual limits on what's software playable) but when you enable CHD the box behaviour wasn't anywhere near as polished as the OE 6.0.1 build and overall differences in the OS between 6.0/7.0 are not large. I struggle to see the point in spending hours and hours trying to discover a new winning formula when an S905 box can be had for $30 - the performance difference is night and day..
-
I build official images on Ubuntu 16.04. In theory it should work on other versions/distros, but as long as it works on 16.04 myself and others on staff never look any further at compatibility.
-
LE can run the binary apps you found in our add-on repo and anything you can find in a CPU arch compatible docker container, but there is (by design) no apt-get so if things like TeamViewer are essential you're stuck. Perhaps look at OSMC which is debian based and apt-get is possible.
-
Generic S812 devices are not officially supported but there are community builds available. RockChip devices are not currently supported, hence no builds available. If you are generally "a bit of a noob" with these boxes it's probably best to stick with Android.
-
Set a small and badly named "wait for network" boot delay in the LE settings add-on. It sounds [sic] like Kodi is starting before the audio drivers have finished loading in the kernel, and if not loaded Kodi won't auto-detect the audio hardware.
-
It means the version of inputstream.rtmp in the Kodinerds repo was compiled against an older (now out of date and incompatible) Kodi API version.
Install the officially supported (and compatible) one from the LE repo - or post in Kodinerds forums.
-
Scope: No, probably because we have no support for PPTP/L2TP and no plans to add them.
-
If you have issues with 2TB+ drives the problem will be SATA chipset firmware not the Linux drivers. It's quite common to find older drive caddy's from the era before 2TB drives that have bad firmware. Anything recent should be fine.