Magicsee N5 Max remote issue

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.

Device: Magicsee N5 Max 2 GB ram, 16 GB storage
I use the remote included: https://imgur.com/FAwEnHJ

Remotemap:
0x140 POWER
0x116 KEY_UP
0x11a KEY_DOWN
0x150 KEY_RIGHT
0x151 KEY_LEFT
0x113 KEY_OK
0x119 KEY_BACK
0x111 KEY_HOME
0x14c KEY_OPTION
0x110 KEY_VOLUMEDOWN
0x141 KEY_MUTE
0x118 KEY_VOLUMEUP
0x14e KEY_1
0x10d KEY_2
0x10c KEY_3
0x14a KEY_4
0x109 KEY_5
0x108 KEY_6
0x146 KEY_7
0x105 KEY_8
0x104 KEY_9
0x101 KEY_0
0X142 KEY_DELETE
0x143 KEY_RED
0X10f KEY_GREEN
0X156 KEY_YELLOW
0X157 KEY_BLUE

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

Any tips are welcome!

Type remoteinfo on SSH and paste the link.

http://ix.io/1R0w

I used the remotemap2.txt
I just got asked if I wanted to update. Should I do it or wait?

Read the guide again and look at the example remote file.

Your missing the very first line which defines your remote type and name which you must use in rc_maps.cfg NOT the filename.

1 Like

Well, I feel stupid now, like you said, forgot to add the first line. Everything working now. Thanks!

“# table yourboxdescription, type: NEC”

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

0x140 KEY_POWER
0x1f1 KEY_POWER2
0x1f2 KEY_SELECT
0x1f3 KEY_PAGEUP
0x1f4 KEY_PAGEDOWN
0x14e KEY_1
0x10d KEY_2
0x10c KEY_3
0x14a KEY_4
0x109 KEY_5
0x108 KEY_6
0x146 KEY_7
0x105 KEY_8
0x104 KEY_9
0x106 KEY_TEXT
0x101 KEY_0
0x142 KEY_DEL_EOL
0x111 KEY_HOME
0x119 KEY_BACK
0x14c KEY_MENU
0x100 KEY_CONTEXT_MENU
0x116 KEY_UP
0x11a KEY_DOWN
0x151 KEY_LEFT
0x150 KEY_RIGHT
0x113 KEY_ENTER
0x110 KEY_VOLUMEDOWN
0x141 KEY_MUTE
0x118 KEY_VOLUMEUP
0x143 KEY_LIST
0x10f KEY_AUDIO
0x156 KEY_SUBTITLE
0x157 KEY_FAVORITES

I am using the last nightly 2019-08-10 ng-generic with dtb 4gb, magicsee N5 Max - 64GB 4gb

Thank you,
Regards,

@daveraver you can’t, this is a common problem with Chinese TV boxes due to a poorly configured bootloader.

We fixed this on SBC’s.

1 Like

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.

1 Like

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,

Regards,