WETEK Core - LibreELEC-WeTek_Core.arm-8.90.006 - ir-remote not working

roel · November 5, 2018 at 8:35 PM

I tried my favorite ir-remote on the latest libreelec alpha 8.90.006 but it doens't work.

When I ssh in the box and I run ir-keytable (after killing kodi and lircevent) I get htis message:

LibreELEC-core:~ # ir-keytable

/sys/class/rc/: No such file or directory

No devices found

So it doesn't find a IR-receiver. lsmod gives me this:

LibreELEC-core:~ # lsmod

Module Size Used by

hci_uart 19283 1

bluetooth 272799 2 hci_uart

8021q 16235 0

snd_usb_audio 98788 0

snd_usbmidi_lib 16198 1 snd_usb_audio

snd_hwdep 4673 1 snd_usb_audio

snd_rawmidi 15409 1 snd_usbmidi_lib

dhd 599647 0

cfg80211 204326 1 dhd

mali 161146 0

dmesg | grep meson results in this:

LibreELEC-core:~ # dmesg | grep meson

[ 0.000000@0] mesonfb0(low) : 0x09100000 - 0x0d900000 ( 72 MiB)

[ 0.000000@0] mesonfb1(low) : 0x0d900000 - 0x0da00000 ( 1 MiB)

[ 0.000000@0] mesonstream0(low) : 0x0da00000 - 0x0fa00000 ( 32 MiB)

[ 0.000000@0] meson_serial_console_setup

[ 3.041486@0] meson_cs_dvfs_probe, table count:29, use_pwm:1, pwm controller:2

[ 3.152319@0] [DVFS]aml_dvfs_register_driver, driver meson-cs-dvfs regist success, mask:1, source id:1

[ 3.714056@0] don't find to display_size_default from mesonfb-dts

[ 6.958855@2] meson-eth: probe of meson-eth failed with error -1

[ 7.322655@2] input: aml_keypad as /devices/platform/meson-remote/input/input4

[ 8.176711@3] enter meson_pm_init

[ 8.181558@3] enter meson_pm_probe!

[ 8.186291@3] meson_pm_probe done !

[ 8.213367@3] meson_cpufreq: no voltage_control prop

Somebody an idea?

**CvH** · November 6, 2018 at 9:00 PM Official Post

maybe this helps ? Infrared Remotes [LibreELEC.wiki]

roel · November 7, 2018 at 10:19 AM

CvH,

problem is this:

/sys/class/rc/: No such file or directory

No devices found

What means no ir-receiver is found. If it doesn't find a IR receiver I can't continue with the wiki-page. I already have all files cause I already did it for my Khadas VIM.

Normally when a IR receiver is found the meson-ir module should be loaded.

Probably it does have something to do with the kernel as Balbes150 doesn't get the IR working also on his S812 builds (although I don't know the current status of it).

**CvH** · November 7, 2018 at 1:35 PM Official Post

HiassofT any idea ?

**HiassofT** · November 7, 2018 at 1:57 PM

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

roel · November 7, 2018 at 3:42 PM

Strange,

I already used it with libreelec and a IR-remote. I never used the rf-remote as it is not a good match with kodi.

I will check that again with a older version of libreelec.

**HiassofT** · November 7, 2018 at 3:50 PM

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

roel · November 7, 2018 at 9:19 PM

HiassofT,

just tried it with libreelec 8. The IR-remote works like a charm with my remote.conf.

I know you changed to meson-ir. it's why you need to do the ir-keytable stuff. Previous with amremote it was just copying your remote.conf into /storage/.config.

See my dmesg from LE8 on the core in attachement as proof:dmesg.txt

roel · November 21, 2018 at 10:50 AM

Are there plans to implement meson-ir in the 3.10 kernel? Or should I open a thread on the wetek forum for these kind of things?

roel · December 13, 2018 at 8:48 PM

With the latest version the remote is working again the old fashion way. Just place the remote.conf of your remote in the configuration map as it was with libreelec 8.

foxyboy · February 21, 2019 at 6:02 PM

roel, im in a similar issue with LE9.0 and a wetek play 1 openelec edition, the remote which is openelec branded is RF and operation in LibreElec is awful. You say its working again the old fashion way ?

Could you possibly attach the file you are using in /storage/.config/remote.conf

roel · February 22, 2019 at 8:36 AM

foxyboy,

I was talking about IR, not RF. If you want to adjust button presses from your RF remote, you better use the keymap-editor addon https://kodi.wiki/view/add-on:keymap_editor

Or make a custom remote.xml according to the Kodi wiki: Keymap - Official Kodi Wiki

powerarmour · February 23, 2019 at 1:30 PM

I can fully understand why meson-ir is now the new default, but that doesn't mean that it's not bloody awful in regards to current usability.

The WeTek Play 2 remote for example is almost laughable in how it performs now.

foxyboy · February 25, 2019 at 10:18 AM

Id have to agree Wetek Play 1 is the same. At the very least let it be configurable, i believe coreelec facilitates both

roel · February 25, 2019 at 12:29 PM

To all,

meson-ir is not enabled on the Wetek core and I assume also not on the wetek play 1. The kernel is to old and I assume they don't want to implement it. IR-remotes still work the old fashion way with the remote.conf. But I assume you guys are talking about the original remote that is RF 2,4 GHz as far as I now, so your problems will be somewhere else. Maybe you should give detailed problems of the remote and start a new thread.

foxyboy · February 27, 2019 at 3:25 PM

Im not entirely sure how LE9.0 IR operates where the Wetek Play 1 is concerned.

I attempted to create a new remote.conf with a alternative remote, i was able to get the keycode of the alternative remote used

but i never was able to capture the button press events so wasnt able to populate a file.

It seems like it was ignoring key presses.

roel · February 27, 2019 at 3:50 PM

You should do it with dmesg. Did you read this post: Create remote.conf from scratch

Otherwise which remote do you use? Probably there is already a remote.conf for your remote. Look here: remote.conf repository

calex71 · March 1, 2019 at 11:53 PM

I've had a go at the .conf route myself with the openelec box/remote and not had good results. Had to reflash twice. I could live with the limited functionality and use kore for anything I need to do the remote doesn't but the favourites button not working is a right pain.