Posts by chewitt

Add "ssh" to cmdline.txt and the SSH service is forced on at boot. Now connect Ethernet to the RPi and the HDMI cable to the projector. Find an app called "Discovery" in the macOS app store (see Tildesoft) as this shows Bonjour devices and makes finding the IP address of the RPi and it's SSH service simple (look under SFTP). SSH into the RPi and run "kodi-remote" and you have a basic commandline remote control for the GUI to control the GUI with. You can also use numerous mobile phone remote apps to control Kodi. Installing and trying to use a VNC server is one of the most awkward ways I can think of to control things.

Find the name of the udev rule that mounts and sets options, copy to /storage/.config/udev.rules.d/<name> then edit the rule with whatever changes are needed, then save and reboot so the modified rule overides the embedded one.

The upstream kernel drivers for DesignWare HDMI have no support for HBR audio, only PCM, so there is no pass-through at this time.

Your link doesn't result in a logfile to view.

It should run, and no harm in trying..

Feel free to use every other OS lol.

Kodi logs aren't much use for degugging OS issues related to wireless (Kodi isn't the thing with the problem). You'll need to share the systemd journal, e.g. "journalctl -b 0 --no-pager | paste" and copy the URL (easier than copy/pasting to pastebin).

You might not whine, but there's a legion of others who will

amlogic: bump to Linux 5.7.x by chewitt · Pull Request #4467 · LibreELEC/LibreELEC.tv · GitHub should be merged soon, which will move things forwards a little.

Audio is PCM only at this time. Some work being done on HBR audio for Raspberry Pi has inspired some ideals for similr with Allwinner support, and since both Allwinner and Amlogic share the same DesignWare HDMI core IP this might lead towards support in Amlogic too. I'm not sure why CEC is not working.. but it's not something I test (my AVR deliberately disables it). I'll flag to one of the upstream maintainers.

Images are super fast to boot and the OS is much more efficient than the legacy kernel. The one issue is the hardware decoder (no HEVC) and seeking in video (doesn't work). If that situation improves I will release stable LE10 images. If it doesn't, I won't - because it's too core to the user experience and Amlogic users are a particularly whiny group. Newer hardware can get away with disabling hardware decode and still play everything under 4K but older S905/S905X devices need the hardware decoder to work.

If it's running Android 6.0 and a Mali 450 GPU it's not an S905X2 device, more likely to be GXBB (S905) or perhaps GXL (S905X). Use the AMLGX "box" image and see if any of the device trees work.

The AMLG12 "box" image on Index of / might work using the X96-max device tree. It looks like WeChip are at the garbage end of the box maker market though. All their designs are rip-offs of other vendors, and they even have the balls to sell pirate IPTV services from their website. If it works, it works. If it doesn't work, I'm not personally interested in chasing support for devices with that kind of pedigree.

No plans to add this as we don't need it for Kodi. It should be easier (and more beneficial) to experiment in the Raspberry Pi OS.

Odroid C2 is a Meson 9 (GXBB) device (not Meson8) which is fully supported in mainline Linux for ages. It doesn't have VP9 like newer devices (and HEVC is still work in progress) but it's still quite a nice board. You can find current test images here: Index of / .. search on "odroid" and you'll find a "board" image that includes mainline u-boot. Hardware decoding is still a challenge (no seeking) but.. see what works for you.

Not according to LMGTFY .. so you'll need to provide some bettter details of the hardware

Connman checks it is online as part of startup. It is harmless and there is a public declaraction that access to ipv4/6.connman.net is not logged. It can be disabled if needed. Copy /etc/connman/main.conf to /storage/.config/connman_main.conf and edit "EnableOnlineCheck=true" to false, save the file and reboot. The reason it's logged so many connection attempts is you're probably blocking it and thus it retries multiple times before giving up. If you allow it to succeed it doesn't need to retry.

LibreELEC is an OS not an App. It cannot be installed on mobile phones.