Netflix (again) changed their API and current 0.13.18 and 0.13.19 Netflix addon versions are broken (there's another bug in 0.13.19).
The latest version from the msl2 branch with API changes is working fine here: msl2.zip
See also Video playback is not working in 0.13.18 · Issue #555 · asciidisco/plugin.video.netflix · GitHub
so long,
Hias
Sorry for being newbish (I am actually new to this), but how do I access LE system partition? When I plugin the MicroSD into my PC, all I see is the Storage folder. I have 2 partitions, of which one is the EFI (I presume). But when I try to explore the sdb/sdb2, all I can see is the storage. How do I access the root, and extract SYSTEM file? I know I can use SSH to extract the SYSTEM file, but I cannot replace the SYSTEM file with a new one via SSH because read-only file system won't let me.
The SYSTEM file is in /flash, but you shouldn't replace it from a running system via ssh as that'll crash your box (it's being used and if you swap it out behind LibreELEC's back things will go really crazy - I accidentally did that once). You'd have to do that without LibreELEC running, eg from a Linux live boot or Windows on a separate partition.
Better switch to LE9 and use the kernel overlay approach then you don't have to patch your installation on each upgrade.
so long,
Hias
Doesn't LE 9 has new kernel modules and firmware overlay?
Hmm, yes, good idea! I should have thought about that 
The following approach should work:
Create a /storage/my-firmware/lib/firmware/brcm directory:
mkdir -p /storage/my-firmware/lib/firmware/brcm/and copy the brcmfmac43455-sdio.txt file in there.
Then configure the kernel-overlay system to pick up stuff from /storage/my-firmware:
echo "/storage/my-firmware" > /storage/.cache/kernel-overlays/90-my-firmware.confNow reboot and the firmware files should be picked up.
so long,
Hias
Thanks for the reply.
Wouldn't it be possible to unpack the ISO, make changes (copy the nvram configs), then compile the ISO and use that ISO to install new LibreELEC on my Mini PC?
Proceed at your own risk:
copy the SYSTEM file from the LE system partition to a linux box, then
run fakeroot, then run unsquashfs SYSTEM to extract the SYSTEM squashfs image to squashfs-root, then modify files in the extracted dir, then run mksquashfs squashfs-root SYSTEM -comp lz4 to create the SYSTEM squashfs file with the modified content and copy that over to the LE system partition.
so long,
Hias
mpd is a (binary) addon, to create the addon zip with all the necessary metadata you have to run scripts/create_addon. eg
PROJECT=RPi2 ARCH=arm scripts/create_addon mpdThis will call scripts/build and then create the addon zip in target/addons/...
Note that by default the addon ZIP won't be re-created if a ZIP with the same name and version number already exists in target/addons/... - which can be a bit annoying during development. But you can override that with ADDON_OVERWRITE="yes" (I added that to ~/.libreelec/options on my build PC).
so long,
Hias
The next LibreELEC release will contain libcec 4.0.3, the update is already in our master branch
libcec: update to libcec-libcec-4.0.3 · LibreELEC/LibreELEC.tv@827c6f8 · GitHub
so long,
Hias
You can override lirc_options.conf with your own setting via /storage/.config/lirc_options.conf - see the wiki Infrared Remotes [LibreELEC.wiki]
To load additional modules you can use the standard .config/modules-load.d /xxx.conf .config/modprobe.d/xxx.conf method.
gpio-ir-recv should be available but I never heard of gpioplug-ir-recv before. Usually gpio-ir-recv gets it's configuration (gpio, rc table) from devicetree and relies on proper pinmux/gpio setup via devicetree as well - this is what RPi and Rockchip are doing.
I'm not familiar with the Odroid C2 so maybe someone else has an idea and can chime in. You'll probably need to modify the devicetree, disable the meson-ir node and enable a gpio-ir one (in which case the module should automatically be loaded), plus add the pinmux settings.
so long,
Hias
It seems we hadn't enabled the dmesg applet in the initramfs busybox binary.
I opened a PR to fix that, when it's merged busybox dmesg will work (this should hopefully be included in the next LE alpha version)
so long,
Hias
You can still use lirc if you want or need to. Just make sure to disable in-kernel decoding as described in the wiki.
In LE9 lirc will automatically start if your have a /storage/.config/lircd.conf file (in LE8 you had to enable it in LE settings).
so long,
Hias
FYI: about an hour ago a fix was commited to the master branch. Latest master version is working fine here master.zip
so long,
Hias
I had some advices about remote config in mind
So if you know if mecool remotes are supported by upstream for example.
Only very few "AML box" remotes are supported out of the box (there are way too many of them), and IIRC mecool isn't among them.
If it's a popular remote someone probably creates keymap and posted it on the forum (in the large Amlogic remote thread).
But first make sure ir-keytable finds the meson-ir device, if it's not there you need to dig into the dtb stuff. If it's there everything you need to know is on the IR remote wiki page (plus keytables probably here on the forum).
so long,
Hias
Sorry, can't help there. dtb files for AML boxes running ancient 3.14 kernels isn't exactly my area
All I can say is that on Le Potato my MCE remote works out of the box.
so long,
Hias
Yes, I found a solution and it will be included in the next alpha release (which should be out real soon now)
eventlircd: prevent race with libinput / kodi · LibreELEC/LibreELEC.tv@ec0e7fb · GitHub
Please test with 8.90.007 (when it's out) and report back if it works.
so long,
Hias
Use a HDMI splitter which provides RCA and/or Toslink (optical) SPDIF output, extracted from the HDMI signal. You should be able to get them for about 20-40 bucks.
so long,
Hias
Hmmm. Could be that you need to use this amremote thing then?
We switched from amremote to meson-ir on the other Amlogic devices, like Odroid C2, Le Potato, ... which run on kernel 3.14. But I have no idea about Wetek Core. Maybe someone else can chime in here.
so long,
Hias
Not sure about Wetek Core but IIRC Wetek Play 1 (which should be similar) uses an RF remote - the IR is only used for power up and not available / exposed in Linux.
So ir-keytable etc can't work as there's no IR receiver.
so long,
Hias
You can keep your keyboard/mouse connected, that shouldn't be a problem.
so long,
Hias
The Flirc dongle acts like a keyboard, so there's nothing you need to configure on the LibreELEC side - leave Lirc disabled and ignore all the ir-keytable stuff on the LibreELEC infrared remote wiki page.
If you added configurations, changes to autostart, disabled daemons etc please revert all of them or start fresh from scratch. Changes there are most likely to just break things.
Configure the Flirc with the Kodi profile for your remote, using the Flirc configuration tool, and you should be done.
so long,
Hias
