Hello. I got a weird issue, pretty much the same as this guy:
Okey, so I installed “CoreELEC-Amlogic-ng.arm-9.1-nightly_20190806-Generic.img” and it booted fine, no issues. I followed this guide (How to Remote Control Configuration for Dummies Using Windows and SSH) and the remote worked until I rebooted. Now, it does not register anything when I stop kodi and eventlircd, and run the command “ir-keytable –t” and spam the remote. I did a reinstall and got the remote working again, but the same thing happen when I rebooted.
also did those commands and got this:
ls -la /flash/remote.conf : No such file or directory
ls -la /storage/.config/remote.conf : No such file or directory
fdtget -t s /flash/dtb.img /meson-remote/ status : disabled
fdtget -t s /flash/dtb.img /meson-ir/ status : okay
hi mates, I mapped all remote, but how will it be to wake up from a power off, by the RC button?? it doesnt work to me with these mapped keys, I try to power ON with first one, 0x140 KEY_POWER
hi, I hope the n5 max will be possible to fix as T95 x2 or the old magicsee n5 both are able to power ON by remote button. but certainly I dont know which is the bootloader limitation on N5 Max, and how difficult is it to fix, so I dont know if what I am asking will be a reality someday. best wishes to the development on this way.
just one more thing, using rc-keymap with meson-ir, the remote works slowlier than with a X92 tvbox remote.conf almost full compatible, it works fluidlier. I dont know why this different behaviour… I just wonder a key function, the delete back, which would be the function??
thanks a lot.
Regards
Some devices are okay and have been configured correctly and others have not, its luck of the draw, sometimes upgrading to the latest Android version or flashing a firmware from a similar device can help.
You can use remote.conf on any device, you just need to extract the file from the Android firmware or look at the thread on here that has a collection of them for one that is compatible.
ok thank you, we will see if next android bootloader fixes this bug. if you need some supporter with n5 max, feel free to ask me anything to test if it is necessary,