IR Remote Issues with Khadas VIM1S Running Android 11

[WRMOS]

Hello Khadas Community,

I’m having trouble getting IR remotes to work with my Khadas VIM1S running Android 11. Despite trying various remotes, the device does not seem to recognise any signals. Here’s a detailed summary of my system configuration and the steps I’ve taken so far to debug the issue:

System Details

uname -a

Linux localhost 5.4.125-android11-2-gb7479a45e76d #1 repo:r-amlogic SMP PREEMPT Thu Dec 12 14:12:47 CST 2024 armv8l

Observations:

1. The IR hardware (ir@8000) is recognised in the device tree:

cat /proc/device-tree/ir@8000/status
okay

cat /proc/device-tree/ir@8000/compatible
amlogic,meson-ir

2. The meson_ir driver is loaded:

lsmod | grep -i ir
meson_ir 57344 0
aml_irblaster 24576 0

3. Monitoring /dev/input/eventX (event5, event6, event7) shows no output when buttons are pressed on the remote:

cat /dev/input/event5
[No output]
cat /dev/input/event6
[No output]
cat /dev/input/event7
[No output]

4. Using Khadas Settings → Remote Controller Customize, the system does not recognise any of the IR remotes I’ve tried.

5. Running dmesg shows the following errors:

dmesg | grep -i ir
synth uevent: /devices/platform/fe084040.ir/input/input7: failed to send uevent
synth uevent: /devices/platform/fe084040.ir/input/input5: failed to send uevent
synth uevent: /devices/platform/fe084040.ir/input/input6: failed to send uevent

These errors indicate the driver is failing to send events to user-space for the IR input devices.

Steps I’ve Tried:

1. Verified that the IR node is present and marked as okay in the device tree.
2. Reloaded the meson_ir driver and monitored kernel logs.
3. Attempted to test raw signals using:

cat /dev/input/event5
[No output]
cat /dev/input/event6
[No output]
cat /dev/input/event7
[No output]

4. Tested multiple IR remotes (including generic remotes and TV remotes) in both Khadas settings and direct input monitoring.

5. Verified that the remotes are emitting IR signals using a smartphone camera (flickering light observed).

Questions:

1. Are there ways to confirm signal reception in software, such as debugging the meson_ir driver or monitoring memory-mapped registers for IR input?
2. Could the synth uevent errors point to a misconfiguration in the device tree or driver? How can I investigate this further in software?
3. Are there user-space commands or tools that could help capture or interpret raw IR signals directly?

I’d appreciate any insights or suggestions on how to proceed with diagnosing and resolving this issue. Thank you for your time and support!

[xiong.zhang]

Check if this post is helpful to you

VIMS1 Android 11 Remote Keymapping

Hi Team, We have custom build the Android 11 for VIM1S. Now we have RCU800 remote planned to use with VIM1S. But execpt one key, all other keys are not working with VIM1S. Can you point me the keymapping in .dts or any source location ? how to adapt RCU800 remote for VIM1S ? Regards. Stalin

[WRMOS]

Thank you for the response, but the post seems to focus on key mappings, which isn’t the root of my problem. My issue is that the IR sensor itself doesn’t appear to be detecting or processing any signals from remotes, regardless of the mapping.

What I’m Trying to Find Out:

1. Is there a way to see the raw signals coming from the IR sensor, either through software or by monitoring a memory-mapped register? For example, can I inspect the hardware output directly before it gets processed by the meson_ir driver?

2. Are there any driver-level debugging options or logs that can help determine whether the IR sensor is receiving signals?

3. Is there any documentation for the meson_ir driver or other resources that explain how it processes IR signals? This might help me figure out why signals aren’t being detected.

Using Khadas Settings → Remote Controller Customize, none of the IR remotes I tested are recognised.

What I’m Asking For:

I’m not looking to adapt a specific remote or adjust key mappings yet—I first need to verify that the IR sensor is working and capturing signals. Any advice on how to monitor the raw IR input, debug the driver, or access relevant documentation would be greatly appreciated. Thank you!

[xiong.zhang]

Turn on the debug switch of ir

echo 1 > /sys/class/remote/amremote/debug_enable

View map mapping

cat /sys/class/remote/amremote/map_tables

After opening debug and debugging, you can use the remote control to capture the log of the serial port and send it to me for review