Posts by chewitt

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.

Write the 8GB card image to the 16GB card using our SD/USB writer app or any other writer app. Then put the 16GB card in a computer running any standard-ish Linux distro and use gparted to resize the storage partition on the card. Our app can write the image, but it cannot expand it.

rhubarbe if ruuks screen reader add-on works on Isengaard it will work on the 6.0.1 build, but my recommendation would be to drop ATV1 and make something around a Raspberry Pi v3; perhaps using the flirc case that comes with integrated IR receiver. The stability of pi hardware is 250% of anything we could ever achieve on ATV.

Quote from Exp245

Kszaq is there any chance you could put acestream in LibreELEC ?, such as Alex put in AlexELEC

The chances of that happening are rather small. Like somewhere between sub-zero and absolute zero. If you want to discuss content theft please go do it in another forum, or preferably don't do it all.

Thanks for the offers, but for security reasons we need to have exclusive admin control over any servers we use or store data upon.

HOW TO:Provide Logfile - LibreELEC

I'd guess that something is hanging on http requests, but a debug log is the starting point for any investigation. Also include the system journal log as that may show issues with the SD card, if there are any.

There's been progress in the sense that we narrowed the memleak issue down to an area of kernel code and changes we've been testing have a positive overall effect, but it is not resolved. Our aarch64 devices will not move up to beta until things are resolved or considerably improved.

As a general request .. do NOT invent release numbers that don't exist yet. Your 7.95.2 release contains what exactly?

Jester Current investigation shows it's unlikely to be an app level leak, more like something related to memory management in the kernel.

The community build is from escalade; best to post in his support thread to see if there's a driver bump available.

mount -o remount,rw /flash
touch /flash/oemsplash.png
mount -o remount,ro /flash
reboot

I'm not entirely sure whether a zero bytes png causes any graphical issues at boot, but I suspect it just results on no LE boot logo. Worst case you can create a proper all-black png image and deploy that. It will still be squashed up, but you won't see it.

systemctl stop kodi.service
rm /storage/.kodi/userdata/guisettings.xml
systemctl start kodi.service

SSH in and run the above commands. It will drop Kodi back to defaults (skin, language, etc.) and that normally clears things back to a point where Kodi will start, download a load of updated add-ons, which normally resolves the issue with something being out of date and causing Kodi to crash.