Posts by chewitt

I have an untested device-tree for the GT-King in my repo .. I'll pick a couple of people to test it and give feedback. Once we have at least one "box" device-tree for S922X it should be a simply copy/paste exercise to create more - the only thing that's likely to be different is the Ethernet spec and the remote control keymap.

Both HardKernel and Khadas are producing decent hardware. I personally prefer the VIM3 over N2 as it has eMMC and Bluetooth on-board; both of which make my development and testing work easier - one less SD card needed, and I can use a BT remote (which I prefer) instead of IR. In theory VIM3 also has WiFi but in practice the chip is not supported in the mainline kernel yet (and Ethernet is better anyway) so that's not a big factor. I'm sure Minix make reasonable hardware too, but I've never personally had anything to do with them. Do they have any S905X2/S922X product?

NB: I do not work for Khadas or any other box/board vendor .. fiddling with ARM boards for a living would never fund my Porsche habit

LE doesn't look at any "box" devices but one of the main upstream support targets is S905X2 so G12A hardware is well supported. S905X3 is being sampled to manufacturers but I'm not aware of anyone shipping product with it yet. LE prefers "board" devices because the manufacturers who sell them take fewer shortcuts and provide better customer support. Boot on the VIM3 is not as fancy/complicated as the N2.

I have a pre-production VIM3 board which works fine (same as the N2). Once we have multi-channel LPCM audio and mainline u-boot support working (soon hopefully) I'll be using it as the family daily-driver. I'll submit the device-tree so it goes upstream before/for the Linux 5.3 merge window.

You can delay when autostart.sh runs, but you cannot control when it finishes or the sequence with Kodi start.

If you move commands to a systemd .service file in /storage/.config/system.d/ you can control the sequencing, e.g.

[Unit]
Description=EPG Download ServiceAfter=network-online.target nss-lookup.target
Wants=network-online.target nss-lookup.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/usr/bin/wget http://XXXX:XXXXX@XXXXX/guide-zatoo.xml -O /storage/.kodi/userdata/guide-zatoo.xml

[Install]
WantedBy=multi-user.target

I won't guarantee this ^ will work as I'm no systemd expert, but "After=network-online.target nss-lookup.target" ensures the network is up, and then "WantedBy=multi-user.target" ensures it runs before Kodi startup.

You cannot install using that script because it assumes a conventional distro with package management tools. LE doesn't support that.

If you install the Docker add-on, you can install the HA docker container.

You need to create a keymap. It's not hard, see: Infrared Remotes [LibreELEC.wiki]

No idea, but probably foul code in the legacy kernel. You already have a good solution.

HEVC on G12 hardware will take a while as a 10-bit video pipeline and some other 4K related things need to be completed first. Please stop testing and reporting HEVC crashes until we tell you that it's usable. Currently there is no firmware and it will crash (needing reboot) 100% of the time.

Win10 requires an authenticated connection so you will need to set a Samba password in LE settings. The samba server is using SMB2/3 so you will need to manually configure the LE source in the Win10 Kodi instance via hostname or IP (and user/pass).

It would be easier to just run LE from a USB stick; at the syslink boot prompt (before the installer runs) type "run" and it you'll end up with a bootable USB with persisitent storage. There are threads elsewhere in the forum if you search for them which explain the sequence and bootloader changes needed to dual-boot. It's not something we support (and have no plan to support) as it's not a straightforward process.

Quote from havhav

someone could adapt acestream_3.1.42_Py2.7.16 + _LinaroNDK_webUI_ARMv7.tar.gz
to work on amlogic S812?

Anything involving acestream is piracy .. so you are asking for help in the wrong forum.

In other news .. we have multi-channel LPCM working on GX hardware. Amlogic's older audio hardware technically supports only 2.0 and 7.1 (2-ch/8-ch) output so the next step will be to fake other output configurations like 2.1/4.0/5.1. No pass-through yet either, but it's a step in the right direction. I also need to test the same changes on G12 hardware - maybe in the next couple of days if I have time. Once current patches are cleaned up a little they will appear in testing images.

Quote from marcogomes

I have a brand new install of LibreElec on a RPi3. Movies are downloaded by CouchPotato from Thoradia and processed to my usb-hard-drive/movies folder.

In other words you are a movie pirate. You appear to be asking for help in the wrong forum.

You're missing the obvious submission of information about the hardware and logs from the box that might help us understand what the issue is. We are not clairvoyant.

Show us the whole log file instead of the edited file .. that edited out the bits that help us.

No, because the 3.10 kernel codebase is too old to sensibly patch overlayfs support in.

Update is part of the libreelec settings add-on, and judging by the bump in users for the latest version that takes place when we enable a release for auto-update the system generally works fine - but you may run into some local issues. Our userbase keeps getting larger and we've noticed the response times for the JSON file that provides available files info are getting slower and sometimes this times out - and my guess (without debug log evidence we can only guess) that the request fails and thus update isn't triggered. There are also some traffic management controls in-place on the update server that you could run into if there are many LE devices in your network, but that's also unlikely. Kodi debug log (as the settings addon runs under Kodi) would be a starting point.