Posts by chewitt

Please run "lsmod | paste" and share the URL; let's see if there is more than one GPU detected. If there is and the BIOS doesn't provide options for disabling one of the cards we can blacklist modules to prevent them loading and confusing Xorg.

Pi Zero is kind of "minimal spec" for running Kodi and is not ideal for a Kodi workhorse. There are some caching improvements that should improve the GUI navigation in large lists (e.g. library views) due in LE 8.0.1 (with Kodi 17.1). From personal experience an RPi3 with a faster clock speed and more RAM is very daily-useable; although in comparison a 3.5 year old Intel/nVidia box I have is still miles better (was 4x the price of a typical RPi3 kit at the time I acquired it though). Yatse is nothing to do with LE, if that doesn't work it's not our problem

The 3.10 kernel used by the WP1 does not support many of the internal functions needed for docker support. We managed to backport missing things to enable support in the 3.14 kernel used by WP2/Hub but it wasn't simple and 3.10 would be a huge amount more work (and after the 3.14 effort nobody is volunteering). There are no plans from Amlogic (or LE staff) to bump the kernel used by MX chipset devices to anything newer, which means there are no plans to bring docker support to WP1.

It looks like everything is up and working .. run "/usr/lib/kodi/kodi-xrandr | paste" so we can see the Xorg modes available. You can also switch modes by running "xrandr --output HDMI-1 --mode 0x1be" (where 0x1be is a valid mode shortcode). You might need to see if other modes are within range of what the monitor will handle?

Code for the update back end is not public and for several reasons there are no current plans to change that. If you'd like to explain your interest in more detail we may be able to answer questions.

It's pretty unusual for devices to truly brick, but it's not impossible, and I can totally see some of the less scrupulous manufacturers using lower grade eMMC or NAND chips in their devices to save a few cents in the rush to make the cheapest box.

If installing on another machine results in something that boots .. do CTL+ALT+F3 on the "hung" screen and you should see a local console (because it hasn't hung, it's just not showing output). At the console run "cat /var/log/Xorg.0.log | paste" and "journalctl -b 0 --no-pager | paste" and share the URL's generated. You should also be able to do "ifconfig" and see the IP address and then SSH in to the box.

Pastebin a debug log so we can see the format of the media coming in .. although it sounds like it's software decoding.

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.

"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.

Feb 25 19:27:26 Lemini systemd[1]: Started ATV client remote support.

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/

Quote from kszabo

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.