Posts by chewitt

The log referred to in the add-on has nothing to do with the Kodi activity/event log that you've looked at. Enable debug logging, reboot, demonstrate the problem, then SSH in and "cat /storage/.kodi/temp/kodi.log | paste" and share the URL so we can see the debug log.

I reposted the request in team chat, but nobody leapt at the opportunity last time so better if you crack on with it yourselves.

LE 7.0 uses the older nVidia 304.xx driver whereas LE 8.0 moved up to the 340.xx driver. This change effectively drops support for GeForce 7xxx cards (8xxx is the minimum supported) hence the correct/expected message about your GPU not being supported.

You have three options:

a) Get a newer card (one with VDPAU or VAAPI support would be better).

b) Self-compile an LE image that reverts the nvidia-legacy driver package to 304.latest, which is still possible to build/use as nVidia still maintains the older legacy driver against current mesa/xorg.

c) Stick with LE 7.0.3.

http://kodi.wiki/view/Official:Forum_rules/Banned_add-ons
Post a debug log from a system that doesn't have banned repositories installed. Then we will reconsider providing support.

Please post a full debug log.

Kodi does not support hardware decode of 10-bit HEVC yet, it is still being developed and should appear in v18 in the future. Until then it is being software decoded by ffmpeg hence the CPU usage you're seeing.

You can find the "Inadyn" add-on in the LE repo.

jrssd. Sending emails to further complain about our refusal to provide support is a bit pointless (guess who reads that mailbox). You may be personally offended by the refusal and think me arrogant, but the support policy of this forum is VERY clear and the staff here are equally and personally offended by your decision to use our product to run multiple add-ons that encourage the piracy and theft of copyrighted media.

Regards the "Why I will never contribute money or time to LibreELEC" title of your email. I think we'll survive. We're okay with your decision.

Again, open a new thread providing a debug log that shows a clean system and we will reconsider support.

Krypton builds have been available on our downloads page for months. LE 7.95.2 with 17.0 final code will be out tonight or tomorrow morning.

Comment from one of our Pi Foundations contacts is "Yes, not expected to work. In theory I could fix the part of display being cut off but performance would be awful (we have to render to off-screen buffer and transpose that then display it) .. and on a Pi0"

I guess that's not what you'd want to hear, but at least you have an authoritative answer.

There is a directory caching behaviour that was removed after Jarvis and should (maybe) be reinstated for 17.0 final

Make a backup in OE before you start, as it's possible to "update" back to OE but you're likely to have minor issues with newer LE add-ons now being installed in /storage/.kodi/addons. The backup ensures you can update back to OE and then restore the backup.

Create a USB and the LE install files are in the boot partition of the USB, or grab the update .tar file and unpack it, they're in the target folder. I'm not aware of anyone writing up exact instructions for this scenario, but "install grub linux" returns 500k+ results in Google and the rest requires "gparted" and some copy/paste in Ubuntu so I guess there's some instructions around. Just have a go, you can't break anything..

Do a manual installation and use GRUB or whatever bootloader appears to work on Ubuntu. Installation is an over-rated word because all we're doing is creating two partitions, formatting them as ext4, installing syslinux to the disk, then copying the KERNEL/SYSTEM files and extlinux.conf to the boot partition. There's no reason why you can't use other bootloaders.

If you want support to continue post a new thread showing a debug log that demonstrates you don't have a ton of piracy add-ons installed. Sending PM does not excuse you from the support policy in this (or Kodi) forum. I have deleted the PM message without reading it.

That's not a debug log, and worse it's not a compete debug log. Enable debug logging, clean reboot, demonstrate the problem, then use "cat /storage/.kodi/temp/kodi.log | paste" to pastebin the log and share the URL generated here.

If those are the tools available .. sounds good.

Official:Forum rules/Banned add-ons - Official Kodi Wiki

No further support will be provided.