XBian is a small, fast and lightweight media center distro, originally for the Raspberry Pi, based on a minimal Raspbian image. It is also available for CuBox-i.
See xbian downloads page for download and installation instructions, including how to flash the image from Windows, Mac or Linux
Also check the forums for other help and advice (note, the image linked near the top of the forum is outdated; the xbian downloads page has a turnkey installer and a more updated distribution).
Notice: XBMC has recently been renamed to Kodi. Some file names still refer to the old name
First, log in to the system using either telnet or ssh. Next, you need to determine what protocol your remote uses. The kernel of Xbian is built with many decoders, which are located here: /lib/modules/3.0.35-gb2e8f7c-dirty/kernel/drivers/media/rc
Sometimes you can search on the web to figure out which decoder will interpret your remote (NEC, Sony, etc), but another method is to list the keymaps that come with Xbian and see if your remote is listed:
For example, if your remote is a hauppauge, you can open the file and note that the first line states:
table hauppauge, type: RC5
which would indicate that the hauppauge remote needs the RC5 decoder.
Next, edit /etc/modules (use nano or something else) and add the decoder module so it starts on bootup; omit the “.ko” when adding to the file. If you want to cover your bases, you can add all the modules to the file so they are loaded at startup.
Now, reboot your Cubox-i so the module gets loaded. Verify that the module got loaded by running “dmesg” and look around the 3second mark for something similar to the following:
[ 3.389424] IR NEC protocol handler initialized
Run the commands
sudo service xbmc stop
Now press a key on the remote. A new line should be displayed that looks like
event MSC: scancode = 72cd5c
The scancode is the unique code for this button. With this code, you can create a remote file. This file must be created at /etc/rc_keymaps/. You can name it anything you want. In the rest of this guide, /etc/rc_keymaps/mycustomremote is used as a file name. The file has the following structure:
On the first line, give the name of the remote, and the type of remote. Valid types are (you might have to experiment a bit with the correct type):
Next, each button is on a single line. Each line begins with 0x, followed by the scancode you learnt from ir-keytable -t. Next is the name of the button. This should be a valid key name. See for a list of valid key codes.
If the special remote file is constructed, it can be tested.