Hard to tell, most likely though I'd guess it's an electrical connection problem. Just re-read the thread and you didn't mention if you used a 3.3V>5V level-shifter (eg 74HCT08 or 32) between the RPi and the LED strip. Without it operation will be borderline and it could be that you just were lucky it worked on the RPi3.
so long,
Hias
All the test images are working fine here.
so long,
Hias
The documentation for LIBINPUT_IGNORE_DEVICE indicates that the device will not be set up by libinput. I can see why that would prevent Kodi from grabbing it. But won't that also prevent an open and read in python?
No, accessing the kernel input event device will work fine.
so long,
Hias
Sorry, can't really comment on RF remotes, maybe someone else has a recommendation.
If you have an IR receiver on your RPi configure your Harmony to the Microsoft Media Center profile - this will work out of the box with LibreELEC.
CEC may be another option.
I'm mainly using an IR remote on my RPi, sometimes just CEC for basic navigation and if I need to enter lots of text I have a Logitech K400.
so long,
Hias
FYI: you can prevent kodi from grabbing and using the input device by setting the LIBINPUT_IGNORE_DEVICE udev ENV variable in a udev rule - see libinput: Static device configuration via udev and LibreELEC.tv/98-eventlircd.rules at master · LibreELEC/LibreELEC.tv · GitHub for an example.
so long,
Hias
It's probably the same issue as reported with other RF air mice from asia. Try disabling mouse and touchscreen support in kodi. See eg here Problems with remote controls
so long,
Hias
No ETA for a RPi firmware fix so far, so it could take a bit. It's on the RPi folks' TODO list but not too high priority.
so long,
Hias
What kind of output do you expect from a serial port device at boot time?
Nothing.
Homebrew IR receivers connected to a serial port don't report themselves to the system so it's not possible to detect if they are connected or not.
Loading serial_ir will always succeed, whether you have a receiver connected or not. But of course, if nothing is connected you won't get anything from ir-keytable -t or ir-ctl -r. Just test it for yourself - either with serial_ir on a x86 PC or with gpio-ir-receiver on RPi.
so long,
Hias
I recently ran into that issue as well and PRed a fix for that: connman: ignore kernel-managed netdev and improve resolv.conf handling by HiassofT · Pull Request #3883 · LibreELEC/LibreELEC.tv · GitHub
This fix is included in Milhouse nightly builds since #1002 and should make it's way into the next LibreELEC release if testing goes fine.
LibreELEC Testbuilds for x86_64 (Kodi 19.0)
LibreELEC Testbuilds for RaspberryPi (Kodi 19.0)
Some feedback / test results would be highly appreciated.
so long,
Hias
We know the IR receiver is attached, and the serial_ir driver has been loaded. That's enough for me to trust the /dev/lirc0 output.
The Android-x86 Linux (yes, I'm sure it's Linux) can handle it, which makes it very likely to work with LE, too.
Sorry, this is utter nonsense. The serial_ir driver will load whenever there's an UART present. And as the OP already wrote in his first post that he's not getting any output chances are very high there's nothing attached there.
Please stop spamming threads with nonsense posts if you have nothing useful to contribute.
so long,
Hias
If you have a look at the start posting (ir-keytable output), you can see that the LIRC device is ready to go.
Sigh. If you had paid more attention then you'd noticed that this was the serial_ir module the OP had loaded and as the SOC has a built-in UART the module load succeeded. This doesn't mean that there's an IR receiver attached to the serial port.
Serial port IR receivers were mainly homebrew stuff some 15 years ago when PCs usually had at least one serial port. Chances of finding that in some commercial stuff from the last 5 years - as this box - are very, very low, as I mentioned in my first post here.
so long,
Hias
Your Android-x86 OS probably has LIRC enabled, and that's why it's working. Under LE you have to enable / configure it as mentioned.
Sorry, but this is nonsense. LIRC needs an IR device/driver where it gets it's signals from and this is missing with the box. Running LIRC won't help.
so long,
Hias
I had a look at the Intel Z3700 series datasheet and it doesn't mention a built-in IR receiver.
My guess is the manufacturer might have connected a TSOP IR receiver to some GPIO and software decoded the signals in an Android driver - or something like that.
As there doesn't seem to be any real info available about this box (links to forum posts with BIOS are all dead now) I'd guess chances of getting the IR receiver working is about zero.
Probably best to just buy an MCE USB receiver (eg an HP branded one from ebay), these work out of the box with LibreELEC.
so long,
Hias
Thanks for the logs!
There are no signs of an IR receiver present in the logs (usually you'd see the nuvoton, winbond, ITE etc ACPI PNP IDs in dmesg).
I'd recommend checking the BIOS settings, usually the CIR (consumer IR) port has to be enabled manually.
so long,
Hias
It would be very unlikely if the box had a built-in IR receiver connected to a serial port. So it would be interesting to know what kind of IR receiver is used in this box and how it's connected.
Can you post some more info about this box plus dmesg, lsusb and lspci output.
so long,
Hias
Please open an issue on the inputstream.adaptive github repo Issues · peak3d/inputstream.adaptive · GitHub If you want specific features/commits from master or Matrix branches backported to the Leia branch. Once they have been included in a new Leia release we'll pick them up automatically.
so long,
Hias
OK, you can drop hdmi_enable_4kp60=1 from config.txt, 4kp50/60 isn't supported by the receiver (at 4:4:4 RGB). But 4kp24-30 should work according to the specs you posted. Puzzling.
Could you test this build: libreelec-rpi4.arm-9.1-devel-20190928101045-ea02c4d.img.gz
This is current LibreELEC 9.2 development tree plus latest 4.19 kernel and firmware (about what's to become the next 9.2 release).
so long,
Hias
Please test with LibreELEC 9.2 beta 1 and make sure you have hdmi_enable_4kp60=1 in config.txt and enabled "Ultra HDMI Deep Colour" (or whatever the option to enable 4:4:4 chroma is named) on your TV/receiver.
4kp50/60 is disabled by default on RPi4 (as it needs higher internal clocking and increases temperature) and it only supports 4:4:4 output (not 4:2:0), which is often disabled on TVs.
so long,
Hias
