Posts by chewitt

ISTR the reason we "nuke and pave" the existing second partition is primarily about speed/performance as parted resize is a slower operation than remove and create new with the correct geometry and it's more prone to issues with the underlying boot media. Embedding files in the SYSTEM file and copying them out to /storage is the least invasive (requires least changes) approach to pre-configuring things on storage; it's also tried and tested. If you want to do something different and resize the existing partition it's not an invalid/wrong approach, but we're not going to be able to provide lots more guidance as it's simply not how we do things today.

The better fix would be to mount using SMB2 or higher from Volumio, instead of dropping the Samba server back to SMB1

custom_edid [LibreELEC]

^ that page describes how to fiddle with the resolutions available in Kodi.

No, we do not support your torrent based content streaming stealing engine.

Our master branch (future LE 9.0) includes support for 32-bit devices using GRUB as testing with 32-bit syslinux gave patchy results.

see: added EFI 32bit support via GRUB2 by maideii · Pull Request #2061 · LibreELEC/LibreELEC.tv · GitHub

Our 3.10 kernel has been hacked enough to make HDMI and S/PDIF work properly but analogue audio was not a priority. There are no plans to go back and fix that among any of the staff devs. Community contributions are welcome.

That will be why you see error messages about the RTC not initialising then.

The folders in the filesystem cannot be removed (they will be recreated on reboot) so just ignore them. If you have Samba enabled you can rename the sample samba.conf in /storage/.config and edit the file in nano to remove the entries.

Binary add-ons compiled for aarch64 will not run on an arm build. You need to remove and reinstall pvr.hts.

Does your C2 have an RTC shield fitted?

"echo 3 > /sys/class/mpgpu/scale_mode" > /storage/.config/autostart.sh

Just run ^ that command from the SSH console and then reboot.

Someone provided a pre-built version of the Linux (not Android) kernel module which can be embedded to make things function. However this is a workaround not a proper solution. The root issue remains the same; the manufacturer refuses to release the driver sources.

The GUI allows you to change the backup destination to something other than /storage/backup so if you mount a remote filesystem on the host or connect a USB drive those 'off box' locations can be used.

Milhouse builds have been running for months, but video code is still being actively written so no guarantees of speedy support; Kodi is still several months from an official Alpha release.

From a comment I saw earlier this evening Amlogic devices that support HDR are doing it via an 8-bit internal conversion process; so not 10-bit and it's probably necessary to keep the processing bandwidth to a management level. The TV still recognises it as HDR though, so the general masses who obsess over the 'pass-through' lights on their AVR blinking appropriately will be happy.

Current LE 8.x/Kodi v17 cannot play HDR on anything - even the claimed HDR support on Amlogic devices is fake. Future LE 9.0/Kodi v18 should have real HDR support, but that codebase is still under development.

No idea, unless you can tell us the chipset inside the box.

Users like to dream of add-ons to cure their specific issue. Challenge is, someone still needs to create and maintain the add-on.

First step is to go figure out 'a' solution to the issue.

Fcuked up cache settings are a frequent source of problems. There are few legitimate reasons to ever touch them. And even in those few corner cases the correct 'solution' is fixing the broken network, not fiddling with the cache.