Posts by chewitt

Kodi add-on repo > Look and Feel > Languages > German

That's more of a Kodi feature request than LE (i.e. wrong forum) but IMHO (and having spent quite a bit of time doing IT things in Africa - so I understand the issue) the better solution would be a small UPS.

systemctl stop kodi
rm -rf /storage/.kodi/temp
rm -rf /storage/.kodi/addons/packages/*
systemctl start kodi

I view 4GB as a bare-minimal size for LE. The distro itself is tiny but with a large media library Kodi will cache lots of thumbnails. It's also common to see pirate add-ons where content lists rotate all the time cache lots of thumbs. The commands above ^ normally clear a bunch of space, but some add-ons also have their own caches and log files - so it's hard to make specific recommendations.

No Xorg = No Chromium. The browser add-on work from AlwinEsch is progressing and once he declares it ready for testing and preferably puts it in the Kodi binary add-on repo we'll start building it.

No idea. Make sure all the fancy compression options are disabled in WinRAR and just use zip as a container format.

Sure it's possible. There is nothing to stop any of our users contributing an oscam update (or new package) to the add-on repo, and we welcome community engagement in the maintenance of niche-use add-ons.

Most laptop DVD drives use custom connectors between the drive and main board so it's probably not worth trying to recycle parts as the special cable will cost more than a new USB external "laptop" DVD drive on Amazon ($15). Kodi needs the drive to be connected before you start the box (it doesn't support hot-plugging after start) but otherwise it should just work.

The DB being "full" is not an error that I recall seeing before and it makes no real sense as there is no size limit on the DB itself. Check for free space on the SD card. Kodi caches thumbnails and if there have been other issues log files and cruft can accumulate in /storage/.kodi/temp (it can all be deleted to free space) - and if it's a smaller 4-8GB card it's not impossible to run out of space.

You might need to call binaries using explicit paths, e.g. 'tee' is /usr/bin/tee and 'nc' is /usr/bin/nc

from the release notes:

"Connection failures to anonymous and guest shares are normally solved by creating a local machine user account and password credential for Kodi to use, then setting read or read-write permissions for that credential to the shares Kodi will access."

QED

Under-voltage warnings - Raspberry Pi Forums

^ First result returned from typing "pi disable voltage indicator" in Google. Took me ~10 seconds.

There are patches for VP9 support for Amlogic in Kodi but we don't have confidence in the underlying kernel code, it needs some work before the developer who's looking at it wants to submit upstream or consider including them in public releases. It will happen, but it will take time.

"SMB2 will use too much resources" wins this months "most bogus comment" award .. aside from the fact that SMB2 is both more secure and gives better throughput performance, the comment is, just, wrong.

In that case you'll need to make a custom build with either different build options or cherry-picking the required binaries from the Samba build folder to somewhere appropriate in the squashfs SYSTEM file image.

Or you find another solution. The only thing that jumps to mind is a webserver on a Windows box that hosts a CGI script to perform the shutdown command, and then you only have to call a URL from the LE side to invoke the script.

Or Google .. i'm sure there's another easier way. Controlling Windows boxen isn't our area of expertise though.

The system log doesn't show anything useful but it looks like Xorg might not be running.. hence Kodi cannot detect the GPU device and aborts. I've no idea why Xorg might die. However, make a backup and update to 8.1.2 (best) or 8.0.2 (okay) ..because even if somehow an issue is diagnosed on the 7.x release you're running it will never be fixed - all development stopped 12+ months ago. Start over with a current release and post again if the problem is still present.

VDR server is in the LE add-on repo. VDR client is in the Kodi add-on repo. Add-ons for LE are installed only through the GUI not apt-get (which does not work on LE). Server and Client do not talk to each other via SSH.

openvpn --config /path/to/file.ovpn

^ something like that. There are LOTS of tutorials online about using OpenVPN .. we are not known for our love of spoon-feeding lazy readers.

I don't think this error is related to SMB protocol version. I have a hunch it has something to do with authentication and/or anonymous access to the shares on the Win10 box. I'm interested to know if you are using anonymous access, a dedicated kodi user/pass, or the Win10 logon user account, and if it's the logon account whether it's normal user/pass or what's known as a Microsoft ID, e.g. [email protected] or similar MS domain?