Posts by chewitt

    LE releases do not currently overwrite the factory u-boot installed on your device, so if your hardware is wired to support power-on events from the RCU waking the device this will remain working when you install LE. If the hardware does not support RCU wake events no amount of fiddling with u-boot will make it work. If you erased a working factory u-boot for some reason, the easiest solution is restoring the Android ROM/image, then reinstalling LE.

    It's not possible for a user to self-delete their account. Various actions can be done by staff .. depending on what reason you have for wanting to delete the account?

    1GB is too small as you only have 512MB for /storage which is where the update file (.tar) and decompressed update files + Kodi data need to coexist at some point for the update to work. 4GB is a sensible minimum, 8GB or 16GB are better sizes to use. 1GB cards will be older and dog slow to use too.

    If you want to fiddle with the contents of /etc/fstab you're trying to locally mount remote NFS shares. Look at the sample systemd .mount scripts in /storage/.config/system.d for the correct way to handle mounts in LE.

    It all depends on how the UPS signals the Pi to shut-down. If it's toggling GPIO pins or communicating via the network there's a dozen ways to do things and LE has all the Python libs that you'd likely want to use packaged into an addon.

    The ssh boot param still works. If set you cannot disable/enable the SSH service in LE settings. Note that if you want to use USB for /storage the USB needs to be correctly partitioned with EXT4 or another supported *Linux* filesystem. If it's FAT or NTFS the filesystem doesn't support unix permissions and contents of /storage default to 777 which means the SSH private key in /storage/.ssh isn't secured (it's world readable) and the SSH daemon will preventatively refuse to start.

    AMD dropped VDPAU (because it doesn't support 10-bit or HEVC and nVidia no longer maintains it) and switched to VAAPI which already has DRM/KMS and GBM support from work done by Intel for their own GPUs (which means VAAPI is no longer a proprietary single-vendor thing so it's saved from execution in k19). I'm not aware of all the details but it would be reasonable to assume the newer driver supports the majority (but probably not 100%) of the current devices.


    NB: It should still be possible for nVidia users to switch to another distro that supports X11 or Wayland which can hook into NVDEC support in FFMpeg. It just won't be possible to continue with 'official' LE once we remove X11 as the DRM/KMS architecture needs GBM (which nVidia does not support) or someone has to go implement EGL Streams; which is entirely possible but unlikely to come from current LE/Kodi developers who are rather fed-up with proprietary nVidia stuff. If someone wants to implement it, they need to have a thick skin to deal with comments on the submission and they need to be committed to long-term supporting the code. If there's a hint of expecting Kodi developers to maintain it there will be impolite responses from Kodi's lead architects :)

    Nothing changed. Kodi (still) defaults to anonymous/guest auth unless a credential is used. If the Windows end supports anonymous auth things will work. If it doesn't (which is increasingly the case) the user needs to use a credential. As it's impossible for us to guess Windows configuration from the typically illiterate descriptions we receive we advise everyone to use a credential; which is also the best advice for security.

    Hi! I'm new in the forum, but I thought giving my 5 cents about this LE image was worth the subscription :)


    I've checked it with an orange pi pc plus (wifi, 8GB EMMC), with a 16 GB, chinese class 10 SD card, for some minutes


    I had quite a lot of artifacts decoding some h264 files, not too much with some h265, only installed **PIRACY** addon (worked OK), good ethernet speed. Right now it's not totally usable if you get artifacts/glitches in all h264 videos, but it's really good.

    The addon you installed is a piracy addon. Go read the forum rules.

    Create a script that checks at 1 second intervals for the drive being mounted or until a suitably large timeout value is reached, and then create a systemd service required by the Kodi service to run the script. The combination should see Kodi 'delayed' until the drive has mounted.