Posts by chewitt

Start by pushing your changes and commits into a GitHub repo so that the changes you've made can be seen and inspected.

I was under the impression the script was explicitly executed so didn't require "chmod +x /storage/.config/autostart.sh" to be run, but that might be worth checking too.

Have you added "dtoverlay=allo-digione" to config.txt ?

Some BT devices require you to "pair" them, and some require you to "trust and connect" the device.

I've removed the HOWTO tag because that approach to installing (and all internal emmc installs) should be discouraged. We already see too many issues with people who don't know what they're doing running scripts and shell commands against Android boxes.

Boot the U9 with Android. If it's still 'dark' it's simply the differences between different hardware. If it's great in Android then you probably have a solution because nobody is really working on the 3.14 kernel that S912 devices are stuck with for now.

Just a hunch .. disable MMAL decoding and use OMXplayer instead.

echo "(sleep 10 && /storage/urserver-3.6.0.745/urserver --daemon)&" > /storage/.config/autostart.sh

^ that should work as long as the /full/path/to/urserver is valid. It waits 10 seconds and then executes the command in the background. If you don't background the task the process will be correctly killed on script exit.

DNS caching is disabled by default because it results in the Kodi GUI showing 127.0.0.1 as the DNS server and 9/10 n00b users trying to solve any networking problem wrongly point the finger and report "DNS is broken" as the bug. If we disable it, Kodi reports whatever the DHCP server sets as your DNS servers and all the bug reports stop. The secondary reason is that we found it to be occasionally problematic, and the genuine bug reports also stopped once it was disabled.

Kodi backups are always hardware dependent, but Pi 2B, 3B and 3B+ are hardware compatible (using the same OS image) so whatever the issue is, that's not the problem. The important thing to remember is that restoring data between devices is simply about stopping Kodi (systemctl stop kodi) then moving a small number of key files back to the right places, then starting Kodi again (systemctl start kodi). The tar file can be unpacked and you can move files back manually if required.

ping HiassofT

The onboard wifi on a 3B should support AP mode, although normal wireless performance isn't the best so AP wireless performance is probably similar and you might need an external USB dongle. The challenge there is that not all drivers support AP mode and there's really no way to tell without trying them. If you can find a USB wifi dongle that uses the ath9k driver; it's one of the best/better drivers.

Raspbian will be much the same. It's all about about hardware and drivers and both distro's are broadly equal on those.

LE uses connman which does send the hostname in the DHCP request. However, if the positively ancient Samba support in current ASUS routers is representative of their router codebase it's more likely that the router (even if it's a shiny new model) has some ancient DHCP server binary that only supports older windows-only methods of name registration.

NB: The hostname should be changed via the LE settings app. This writes the file to oe_settings.xml which is read and propagated to the .cache and other locations on startup. You should not modify the file directly.

kodi-send --host=127.0.0.1 -a "UpdateLibrary(video)"

read this for more commands: List of built-in functions - Official Kodi Wiki

LibreELEC has never released official images for Allwinner hardware so we have never published addons for those devices to our repo. The H3 image you've installed probably originates from an Italian community builder who adapted the older OE images by jernej to our codebase. It's his responsibility to provide addons for his images.

NB: In the near future there will be official releases and those will come with official addons. Fun times ahead

No Linux kernel has full 4k HDR support. The current 3.14 kernel predates HDR and has been hacked by Amlogic and various community groups to have some resemblance of HDR support, but the test cases it was coded for are limited and bits are missing. Folks over at CE lack the kernel development skills to architect and solve those problems which is why they've flip-flopped between kszaq, osmc and our older kernel in the hope they find something that works. We (LE) are not wasting our time on that quest because we know none of them work properly, and the 3.14 kernel is not really worth the effort. The situation on mainline kernels is also incomplete as HDR and other HDMI 2.0 elements are still being coded. The good (long-term) thing is that those feature are being actively worked upon, and unlike ye olde 3.14 kernel, the code is written properly.

Start with a current Milhouse development build as this has a much newer Linux kernel and the mmc driver initialisation problem (-110 is just a generic error code, it's not so helpful) may have been resolved in more recent kernels.

There is a VNC server addon for LE allowing you to connect from PC to HTPC, but nothing exists that allows connecting from HTPC to PC.