Remote for Odroid N2

In my haste I posted the incorrect link. I’ve corrected that.

Does the Xiaomi MiTV remote work out of the box as is without having to modify any of the CoreELEC Kodi OS files?
Does the IR version work just as well as the bluetooth version?
Will any bluetooth dongle work or does it have to be Odroid one?

I believe it’s fully mapped out of the box, but needs to be paired first (it is after all, bluetooth). That said, I’m not a big fan of the basic mapping (on any remote with Kodi) and have added some long-press functions and made changes like switching the power button from actually shutting down the machine to bringing up the shutdown sidebar, etc.

The Kodi Keymap Editor add-on can be used to remap single-press functions. But unless the add-on now supports long-press (it’s been a while since I used it), those need to be done by manually editing your keymap file.

EDIT: As it turns out, there’s a fork of Keymap Editor that does support long press:

Do you have a specific guide on how to train your N2 to use a remote?

There is a generic guide for using the inbuilt functionality on the forums.

This will configure almost all remotes to use the built in IR receiver.

I tried this guide, but couldn’t make it work.

When you have created your map file it needs to be saved in the following location.


It appears some code is missing, no?

This guide has never failed me so I can’t see what has gone wrong. I am using it at the moment on all boxes.

So I created a .toml file in Notepad as such:

name = "sony"
protocol = "nec"
0x10012 = "KEY_VOLUMEUP"
0x10013 = "KEY_VOLUMEDOWN"
0x1ae242 = "KEY_HOME"
0x1ae23c = "KEY_RIGHT"
0x1ae23b = "KEY_LEFT"
0x1ae239 = "KEY_UP"
0x1ae23a = "KEY_DOWN"
0x1ae23d = "KEY_ENTER"
0x1ae229 = "KEY_INFO"
0x1ae218 = "KEY_STOP"
0x1ae215 = "KEY_POWER"
0x1ae21a = "KEY_PLAYPAUSE"
0x1ae243 = "KEY_ESC"
0x1ae263 = "KEY_SUBTITLE"
0x1ae23f = "KEY_CONTEXT_MENU"

and an rc_maps.cfg like so:

meson-ir * sony.toml

I try to access this location


But the only location I can see through Windows Explorer is:


I copied the files into the “appropriate” location, but no matter what dir structure I use, it cannot find it:

CoreELEC:~ # /storage/config/rc_keymaps/sony.toml
-sh: /storage/config/rc_keymaps/sony.toml: not found
CoreELEC:~ # /storage/.config/rc_keymaps/YOURMAPNAME.toml
-sh: /storage/.config/rc_keymaps/YOURMAPNAME.toml: not found
CoreELEC:~ # /coreelec/config/rc_keymaps/sony.toml
-sh: /coreelec/config/rc_keymaps/sony.toml: not found
CoreELEC:~ # /config/rc_keymaps/sony.toml
-sh: /config/rc_keymaps/sony.toml: not found
CoreELEC:~ # /configfiles/rc_keymaps/sony.toml
-sh: /configfiles/rc_keymaps/sony.toml: not found
CoreELEC:~ # /storage/.config/rc_keymaps/sony.toml
: not foundonfig/rc_keymaps/sony.toml: line 1: [[protocols]]
/storage/.config/rc_keymaps/sony.toml: line 2: name: not found
/storage/.config/rc_keymaps/sony.toml: line 3: protocol: not found
: not foundonfig/rc_keymaps/sony.toml: line 4: [protocols.scancodes]
/storage/.config/rc_keymaps/sony.toml: line 5: 0x10012: not found
/storage/.config/rc_keymaps/sony.toml: line 6: 0x10013: not found
/storage/.config/rc_keymaps/sony.toml: line 7: 0x1ae242: not found
/storage/.config/rc_keymaps/sony.toml: line 8: 0x1ae23c: not found
/storage/.config/rc_keymaps/sony.toml: line 9: 0x1ae23b: not found
/storage/.config/rc_keymaps/sony.toml: line 10: 0x1ae239: not found
/storage/.config/rc_keymaps/sony.toml: line 11: 0x1ae23a: not found
/storage/.config/rc_keymaps/sony.toml: line 12: 0x1ae23d: not found
/storage/.config/rc_keymaps/sony.toml: line 13: 0x1ae229: not found
/storage/.config/rc_keymaps/sony.toml: line 14: 0x1ae218: not found
/storage/.config/rc_keymaps/sony.toml: line 15: 0x1ae215: not found
/storage/.config/rc_keymaps/sony.toml: line 16: 0x1ae21a: not found
/storage/.config/rc_keymaps/sony.toml: line 17: 0x1ae243: not found
/storage/.config/rc_keymaps/sony.toml: line 18: 0x1ae263: not found
/storage/.config/rc_keymaps/sony.toml: line 19: 0x1ae23f: not found

What the hell am I doing wrong?

Hopefully you don’t used Windows Notepad. You need a UNIX compatible editor.

Your error is a wrong file encoding.

I just installed VIM; I’ll go about creating those files shortly.

What about the location; is /storage/.config/rc_keymaps/ is from Windows Explorer, and if so, what aren’t I seeing it?

The storage location is a Linux file system. You are seeing the samba share of that location which is why it looks different. If I were doing it I would ssh into the box and do it all via nano. Windows uses putty in place of ssh.
Doing everything directly from Windows explorer is frought with potential issues and as pointed out Windows will mangle the file format.

At least you managed to generate the file which means the functionality you need is working fine.

So I have been using PuTTY to SSH into my N2, or so I thought?

What should I be using to SSH into the N2 from Windows (7)?

And you lost me at “all via nano”.

PuTTY is the Windows version of the standard Linux tool SSH. Nano or VIM are two simple console based text editors in Linux, I find Nano to be considerably easier to use than VIM but others will disagree. There are tutorials on using all these tools on the web. You must have been using PuTTY to create your codes in the first place.
You need to learn how to navigate through file structures to create your files via Nano/VIM. The learning curve to use Linux tools is quite steep initially but if you are serious about computing you will encounter Linux systems at every turn so they will serve you well. Windows deliberately makes doing all of these things hard - even getting to a decent console is a pain in Windows.


I’d rather just use my FLIRC device which has served me well for many years.
The issue is that when connected to my N2, sometimes it registers multiple key presses, sometimes incorrect key presses etc.

What could be causing this considering a USB keyboard connected to the N2 works just fine?

The built in IR receiver maybe registering key presses as well as your Flirc. Try covering the IR and see if it makes a difference.

That was my very first thought too… it made no difference.

At this point, I’d be happy just to buy a compatible remote.

What are the three “best” IR remotes that just work with CoreElec (N2+)?

Just choose one?