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
Posts by HiassofT
-
-
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
-
The Xbox 360 remote should work out of the box. If it doesn't work for you please be more specific about what's not working, following the troubleshooting steps in the wiki Infrared Remotes [LibreELEC.wiki]
Do you get keycodes from ir-keytable -t? If not post the ir-keytable output of the non-working buttons.
Do the keycodes show up in kodi's debug log and if yes which actions are executed? Post the log lines with the info about non-working or unmapped buttons.
so long,
Hias
-
The CPU is quite busy during startup, kodi runs a bunch of housekeeping tasts like checking for new addons so it means it'll draw more power than when kodi is idle or playing a h264 movie. If you have a self-powered USB HDD connected it'll draw quite a bit of power during startup as well.
Get a proper power supply and the lightning bolt will disappear.
The lightning bolt is a warning sign, depending on how low the voltage drops the system may lock up and / or the sdcard may get corrupted.
As I wrote before for the RPi2/3 the official 5.1V/2.5A supply is recommended.
so long,
Hias
-
The lightning bolt means you have an inadequate power supply and need to get a better one (and/or a better USB cable if your PS has an USB plug instead of a fixed attached cable).
BTW: the official RPi PS is known to work well.
so long,
Hias
-
If ir-keytable -p all -t didn't output anything then either eventlircd or kodi were running in the background or the remote uses an odd protocol that's not supported by in-kernel decoding.
I haven't looked in detail at your lircd.conf file but it looks like it might indeed by the Panasonic protocol, which isn't supported (yet).
So, just use your lircd.conf file, you only have to change the KEY_ names to match the official key names input-event-codes.h\linux\uapi\include - kernel/git/torvalds/linux.git - Linux kernel source tree
In LibreELEC 8.2 you have to enable Lirc in LibreELEC Settings, in LE 9 and the current alpha versions lirc will be started automatically when a /storage/.config/lircd.conf file is present.
Also read the info in the wiki Infrared Remotes [LibreELEC.wiki]
so long,
Hias
-
ir-ctl -r will show you the raw signals and you can use it as a simple check if something is received. If you have bad batteries, bad reception or interference you could still get "something", but that doesn't neccessarily mean it's a valid signal that can be decoded.
By looking at the exact pulse/space durations it's possible though to see if it's garbage, a valid remote signal or some unsupported protocol.
In case of MCE remotes the most likely cause is bad batteries, bad reception or interference - that protocol is well supported and also your IR receiver is know to work well.
so long,
Hias
