Posts by chewitt

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 ..

Look for the BT audio addon in our repo. It does exactly that.

If you stream media to the same playback device the output should be identical. If you are comparing output from the NAS 'PC' vs the HTPC 'PC' they have different hardware (different GPUs) so you get different output from different drivers etc.

Test with a current milhouse release because then you're testing a codebase that is being actively developed (unlike LE 7.x-8.x which are not going to see any more releases, or OE which hasn't been touched in 12-months). If the problem is resolved, great. If not, report the issue via Kodi forums to their developers.

Allwinner VPU support in mainline Linux status update (week 23) - Bootlin's blog

^ things are making progress, but there's still a ton of development before we start releasing public images

Storing media on a NAS device and using a separate (smaller, usually cheaper) is the way to go, but the moment you throw HDR into the equation you end up recommendations limbo:

Intel = only the latest devices support 4k/60 and HDR support in their drivers is still work in progress (but is progressing). AMD = similar to Intel as it uses the same VAAPI driver framework which is similarly waiting for upstream development. nVidia = forget it, stuck on 8-bit no HEVC. Amlogic on 3.14 kernel has 4k/60 support but horrible HDR code (on S905X/D) that needs major development to resolve (and nobody is volunteering) and S912 will be stuck on 3.14 indefinitely. Amlogic on mainline kernel is progressing but drivers are currently missing 4k/HDR support. Rockchip devices are only just starting to get HDR support.

So today Amlogic S905S/D is the least-worst option, but some of the HDR stuff is fudged in the current Amlogic 3.14 kernel and won't be resolved until we make the switch to mainline and finish implementing the HDR featureset. Latest NUC devices will get support, but it's months not weeks before things will be complete. Maybe not resolved in LE 9.0, but a 9.2 release.