Posts by chewitt

The backup function in LE settings is just creating a standard .tar archive. To avoid all the unnecessary time and space issues of imaging the SD card just make a tar backup that includes the folders you need to backup. It's, really, not, hard.

K18 is still in an early alpha state so the whitelist function probably isn't fully developed. Perfection rarely comes at the first attempt

ping lrusak

Looks like the package is expecting to cross-compile for arm64 and you're trying to build for arm. It probably has hardcoded references to the arm64 toolchain which need to be revised.

Look in /storage/.ssh .. it appears we moved it since the last time I looked (about 5-years ago)

LE has two partitions; boot files (visible in /flash) and persistent storage (visible in /storage) and you need to make a 'dd' image of the entire card to capture both. However, it is significantly quicker to use the backup/restore functions in the LE settings addon as this only saves the 1-2GB of data in /storage/.cache /storage/.config and /storage/.kodi vs the 8/16GB on a typical SD card. Users frequently obsess over making an 'identical' clone but this really is not important or essential. SSH config lives in /storage/.cache/.ssh.

Update to a newer LE (and Kodi) version that works with the remote app, or complain to the app developer that he broke support for Kodi v16.

If you have a VPN tunnel active this will not work because the connection manager that controls the hotspot has no knowledge of the tunnel interface and thus won't NAT/route traffic to it.

Kodi allows you to change font/size/style/colour and position, but there is no option to have a 'box' around the font.

Provide a Kodi debug log that demonstrates the problem.

Assuming an SBC board with a dedicated image you just write the image to the SD card (or eMMC via SD adapter) and off you go. If you go the box route expect more hassle.

You probably need to map the USB device to the container in the run command.

The connection manager (connman) uses 0-3.pool.ntp.org servers; so unless you have a reason to use a local network time source or your ISP blocks them there is no reason to change the defaults. There are some improvements for NTP retry in LE 9.0 pre-release images. The best cure for recurring Pi NTP issues is spending $3-5 on an RTC chip.

Several Kodi scrapers have had their API keys revoked a few times recently which requires devs to update the keys and push an updated add-on while users sit tight and wait for the update to propagate. Make sure you have the latest version installed and things should be okay.

No Krypton images exist. RK hardware shows a lot of promise but LE support is still "work in progress" and under active development.

It is not an LE problem and the difference to OE probably means something got fixed and something else now needs to be adjusted. Report the Kodi problem to Kodi developers.

Unless you have "adjust refresh rate" enabled so the TV is switched to the same fps rate as the media, the media is being resampled to match what the TV is statically set to and resampling is a lossy process. That's the only explanation I can think of for a sonic difference.

The connmanctl app can be used to configure connections. Connecting to a wireless network requires a two-step process so you'll need to write a script that watches for the input prompt and provide the passphrase.

Amlogic has cult status in the absence of any serious price/performance competition in the last ~2 years. That will change as other SoC types get supported this year. Right now (today) an S905X or (better) S905D device with GB ethernet is probably the best thing available. If you want an easier install and run experience choose an SBC device from LibreComputer or Khadas. Android box devices are cheaper but require you to jump through more hoops with device trees and bootloaders to make the hardware work. I would strongly avoid S912 devices because those are stuck forever on the shitty 3.14 kernel due to an ARM licensing issue.

excessive signature removed ..