NOTICE: Account creation on the wiki has been temporarily disabled until the wiki is moved to OpenID. If you need an account before then, please request one here: http://forum.xbmc.org/showthread.php?tid=165868

Remote control reviews

From XBMC
Jump to: navigation, search

 Controls: Keyboard controls Remote controls RC reviews Keymap files Modifying keyboard.xml Custom keymaps lircmap.xml 

This is a (probably futile) attempt to keep up with the vast range of MCE remotes out there, and give some indication of how well they work with XBMC.

If you are adding a review please try to be as detailed as possible about the remote. For example:

The article groups the Microsoft compatible (also known as eHome or RC6) remotes together first, as these are most configurable when you're using them with XBMC. Other than this there's no significance to the order of the reviews.

1 eHome/RC remotes

The remotes in this section all use the Microsoft eHome driver on Windows. See Using a Microsoft remote control in Windows for details. This type of remote is supported out of the box by XBMC Live.

eHome remotes are generally more expensive than the non-eHome remotes, but they are highly configurable and work very well with XBMC. Many universal handsets, for example the Harmony remotes, have emulation for eHome/RC6 handsets built in so they will work with an eHome IR receiver.

Note that Microsoft has modified the programming and device specification for remote controls several times. For example, in Vista, the Port Driver/Class Driver Model was added. This means that there may be some transceivers which may not function fully, if at all, on systems prior to Vista. For the curious (or bored) there is a specification for the Windows Media Center remote.


1.1 Microsoft Media Center Remote Control

[view] [edit]
Microsoftlearningremote.jpg
There are several versions of this remote:
Mcelearningsmalla.jpg
Microsoft - Microsoft Logo at bottom of remote and on receiver
Mceteletextsmall.jpg
Microsoft with Teletext - Microsoft Logo at bottom of remote and on receiver, plus Red,Green,Yellow,Blue and a 'teletext' button.
Remote-microsoft.jpg
Dell - No Logos on remote or receiver and no TV standby or volume learning ability

All these variants of the MS remote will work out of the box with XBMC Live, though with a standard Linux install you'll need to install and configure Lirc. To get it to work on Windows you need to configure it to simulate key-presses. See Using a Microsoft remote control in Windows for details.

remote wake on USB? multi-device control? volume learning? universal-remote code available? IR transmit? linux/osx/windows?
Microsoft  ? N* Y  ?  ? all
MS w/ Teletext Y N* Y  ?  ? all
Dell Y N N  ?  ? all



1.2 AIM RC6 Media Center Remote Control

[view] [edit]
Remote pic wiki.jpg

AIM, Ahead In Multimeadia is a registered trademark of Formosa21 Inc. This is a Microsoft Windows Media Center compatible remote control labeled (RC6) for Windows 7 32bit and 64bit as well. Model Number: RC118 other compatible models made by the same company are RC125 and RC126, which use the same hardware but with different button layout. The receiver Model number: IR605A

RC6 remotes is the best you can buy specially after Microsoft's own remote was discontinued; there are so many cheap/clone remotes but spending a few more bucks should leave you satisfied.

This RC6 remote like any other RC6 Microsoft Certified remote will work with any Windows platforum that was released after Windows XP. It's certified for Windows 7 32bit or 64bit. I can not confirm that it works with Linux, but in Maplin's Questions section someone confirmed that it works with Linux and it's detected as an lirc_mceusb2 device.

This Remote is fully comaptible with Microsofts eHome default Driver "Microsoft eHome Infrared Transceiver" no additional drivers required, it will be automatically detected and installed by Windows. It has a dedicated website that has all the required setup files available, the .reg file on site should work with any compatible RC6 MCE remote. by using the latest config.reg file all the buttons work in XBMC.

All buttons are capable of sending IR WM_APPCOMMANDS or Keystrokes, fully configurable.


1.3 HP MCE Remote

[view] [edit]
newer version
older version

Both versions are compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the HP remote.

On Windows XP Pro SP3 the receiver was recognised and installed automatically. There are reports that Windows XP may not automatically detect the receiver unless you edit irbus.inf as described in http://it.megocollector.com/?p=8. It is not clear when this hack is needed. Several drivers are available from HP (ex. http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=vc-100849-1&prodTypeId=12454&prodSeriesId=4210074). Note that there are several different remotes and drivers. It can be difficult to identify the appropriate driver.

With the Remote-XBMC.reg config all the buttons work in XBMC except for the "T" and "Print" buttons. To configure these buttons add the following to the .reg file:

  4E,00,00,00,04,01,22,\ ; Print button on HP remote - sends ctrl-5
  5A,00,00,00,04,01,23,\ ; T button on HP remote     - sends ctrl-6



1.4 HP Pavilion HDX Remote

[view] [edit]
HPPavilionHDXRemote.jpg

This is a newer version of the HP remote. An important difference from the older HP remotes is that it has a unified Play/Pause button instead of separate Play and Pause buttons. Like the older remotes it uses the Microsoft eHome drive so the buttons can be configured by modifying the registry. The Play/Pause button is number 6E. To configure this to send a VK_MEDIA_PLAY_PAUSE multimedia keypress use:

6e,00,00,00,01,cd,00

There is also a version of this newer HP remote with red / green / yellow / blue buttons as the top row of four. On that (and I assume the one pictured) the button numbers for the replay button (top-middle) and the TV button (top-right) are 80 and 39 respectively. Hope that helps

If using this one or the newer HP remote such as:

in combination with OVU400102/71 HP usb IR receiver on a Ubuntu system, then the Play/Pause button will need a special code 0x00007b91 in the /usr/share/lirc/remotes/mceusb/lircd.conf.mceusb

Note that the HP IR USB receiver OVU400102/71 uses a Fintek chipset. There have been various problems reported with using this device on XP. In some cases, it is recognized as an eHome device, but then does not send keys as an HID device, (however it worked with the EventGhost MCE Remote plugin). In other cases, it was not recognized as a Microsoft eHome device (a patch from HP may be required), but as a FinTek eHome device (after getting the (hacked) Fintek driver). The FinTek driver does not work on some XP configurations (cause unknown).


1.5 Asrock Remote

[view] [edit]
AsrockRemote.jpg

The Asrock ION PC's come with a remote control and some models the HT Also include a internal CIR receiver.

1.6 Windows

1.6.1 Information

This is compatible with the Microsoft remote, and in Windows 7 (and possibly Vista) the .reg files used to reconfigure the MS remote will also work with the Asrock remote. The .reg files will not work in Windows XP because Windows XP does not detect the remote as an eHome device and install the eHome driver. It is possible the eHome drive could be installed with suitable modifications to irbus.inf (see the review of the HP remote above) but so far this has not been explored.

1.6.2 Configurition

With the Remote-XBMC.reg config all the buttons work in XBMC except for the four buttons in the row above the coloured buttons. To configure these buttons to send the standard Media center keyboard shortcuts add the following to the .reg file:

  47,00,00,00,04,01,10,\ ; Asrock remote: Music    - sends ctrl-M
  49,00,00,00,04,01,0C,\ ; Asrock remote: Pictures - sends ctrl-I
  4A,00,00,00,04,01,08,\ ; Asrock remote: Movies   - sends ctrl-E
  50,00,00,00,04,01,04,\ ; Asrock remote: Radio    - sends ctrl-A
Note: Some Asrock ION330HT ship with a Nuvoton W836x7HG CIR Device Driver with is not RC6 compatible. In this case the Windows registry fix for the ehome driver will not work. This is not true for Linux.

1.7 Linux Ubuntu

1.7.1 Information

Asrock ION330HT with remote and internal CIR receiver compatible with any MCE remote.

From Ubuntu 11.10 and up-to 12.10 including 12.04LTS getting the internal CIR + remote to work with Lirc + XBMC is rather a simple process.

1.7.2 Configuration

If Lirc is not installed we install it now:

sudo apt-get install lirc

If LIRC is already installed do:

sudo dpkg-reconfigure lirc

Remote control configuration:

IR transmitter, if present:

Next change the default configuration to work with the Nuvoton remote

sudo nano /etc/lirc/hardware.conf

Change the following 3 lines from:

REMOTE="Windows Media Center Transceivers/Remotes (all)"
REMOTE_MODULES="lirc_dev mceusb"
REMOTE_DRIVER=""

Into the following

REMOTE="Nuvoton Transceivers/Remotes"
REMOTE_MODULES="lirc_dev nuvoton-cir"
REMOTE_DRIVER="default"

Save changes with ctrl+O to save file & ctrl+X and close nano.

Restart LIRC to apply the changes

sudo service lirc restart

And the remote should now be working with XBMC.


1.8 Mediagate GP-IR02BK

[view] [edit]
Remote-IR02BK.jpg

Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Mediagate. The remote is currently available on Amazon UK and US.

There are some additional buttons not on the official MS remote. These can be configured using the following in the .reg file:

  27,00,00,00,04,03,04,\ ; Zoom     - sends ctrl-shift-A
  47,00,00,00,04,01,10,\ ; Music    - sends ctrl-M
  49,00,00,00,04,01,0C,\ ; Pictures - sends ctrl-I
  4A,00,00,00,04,01,08,\ ; Movies   - sends ctrl-E
  50,00,00,00,04,01,04,\ ; Radio    - sends ctrl-A
  5a,00,00,00,04,03,09   ; Teletext - sends ctrl-shift-F



1.9 Mediagate MG-IR02BK

[view] [edit]
Remote-MG-IR02BK.jpg

Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Mediagate.

There are some additional buttons not on the official MS remote (and not on the GP-IR02BK):

  27 - Zoom
  4B - DVD Angle
  4C - DVD Audio
  4D - DVD subtitle



1.10 DEC-200B

[view] [edit]
Remote-200B.jpg

Compatible with the MS remote. Works out of the box with XBMCLive. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry.


1.11 AVS Gear HA-IR01SV

[view] [edit]
Remote-HAIR01SV.jpg

Compatible with the MS remote. Frequently works out of the box with XBMCLive - some versions ship with new receivers whose product IDs are not always included with LIRC such as ID 0011 from VENDOR_TOPSEED. If the remote doesn't work and/or the light on the receiver stays on once a button is pushed, the reciever needs adding to LIRC. Instructions are here. Not tested (so far) with the Windows and OSX versions. Don't know if it's configurable with the registry. Currently available from Amazon UK (search for HA-IR01SV). Googling suggests it is widely available.


1.12 Hauppauge Media Center Remote Control Kit

[view] [edit]
Remote-hauppauge.jpg

Compatible with the Microsoft remote, and the .reg files used to reconfigure the MS remote will also work with the Hauppauge.

Note that this is not the same as the Hauppauge 45 button remote that plugs into the Hauppauge PCI/USB card. The Hauppauge 45 button remote has caused some hair tearing and wouldn't be the first choice for an XBMC remote. If you are using a 45 button remote in Windows use third party open source software like Event Ghost http://www.eventghost.org/ You can configure the remote to send key-presses & map it to the keys in keyboard.xml


1.13 AURC-002

[view] [edit]
AURC002.jpg

Manufactured by Acowin Industrial Limited; see http://www.acowin.com.hk/product535.html. Microsoft MCE clone with a cloned HP receiver. Compatible with the .reg files used to reconfigure the official Microsoft remote and receiver.


1.14 Microsoft XBox 360 Universal Remote Control

[view] [edit]
Xbox 360 remote.jpg

This will work on Windows (I've tested on XP and 7) with the Microsoft receiver or a compatible receiver like the HP (the remote does not come with a receiver) though need a minor registry tweak. Navigate to:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HidIr\Remotes\745a17a0-74d3-11d0-b6fe-00a0c90f57da

then change the value of CodeSetNum0 to 8, and delete the three entries CodeSetNum1, CodeSetNum2, CodeSetNum3. You need to reboot for the change to take effect.

There are some buttons that aren't on the standard MS remote. The button numbers for these are:

  28 - Open/close
  64 - XBox button
  4F - Display
  51 - Title
  68 - Blue/X
  66 - Green/A
  6C - Channel up
  6D - Channel down

The volume and mute buttons do not work.


1.15 Philips 5100 4in1 Vista MCE Remote

[view] [edit]
Philips5100-4in1 landscape.jpg

Philips have produced a family of remotes in this range designed for different sales regions each with different features. This one has the ability to control 4 devices (PC, TV, Sat, Amp) and can be programmed using the manufacturer codes database supplied. It also has the ability to learn functions from other remotes to replace any of its buttons, making it very versatile once customised to your home cinema setup. However, the keys are not backlit. The supplied infra-red usb receiver only works with Vista, Windows 7 and Linux.

Note: Also works with the Official Microsoft MCE receiver as it sends the same signals (RC-6), meaning it can be used on Windows XP via this receiver.

Discontinued - (Can be found on ebay UK)


1.16 Microsoft MCE Keyboard Remote

[view] [edit]
Microsoftmcekeyboard.jpg

Similar to the buttons to the Microsoft MCE remote, but with a full keyboard and a 'nipple' for moving the mouse. Range is limited and it requires a direct line of sight to the receiver. Can be operated on the users lap. The keyboard has a very nice feel, though the mouse nipple is hard to use.

Works with the Official Microsoft MCE receiver and with compatible RC6 receivers like the HP receiver.


2 Non eHome/RC remotes

These remotes usually work by emulating a keyboard, that is when you press a button on the remote XBMC receives a key press just as if a key had been pressed on the keyboard. Most of the remotes emulate multimedia keyboards or send Windows Media Center keyboard shortcuts like ctrl-shift-P for Play.

XBMC has all the required keyboard mappings for these remotes so they should work out of the box. However they usually cannot be configured so they have some limitations. For example, on Windows the green button will start Windows Media Center and this can't be changed without considerable messing around.

These remotes will work with XBMCLive as long as Ubuntu recognises them as a keyboard, which isn't always the case.


2.1 VRC-1100

[view] [edit]
Remote-VRC1100.jpg
See also How-to:Configure VRC-1100 remote for Ubuntu

There is no manufacturer's name on this remote or the manual, but they appear to be from Ortek (http://www.ortek.com/html/pdt_view.asp?area=25&cat=154&sn=65). They are widely available on eBay. Maplin UK also sell an own-brand remote control (product code N18HC) that seems to be identical, and it is also sold as Hama 52451. The remote simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse, although it's no match for a proper mouse or trackpad.

Note that the the i button sends a right mouse click, which isn't much use in XBMC as the right click can't be mapped to an action. There is no way round this without using some helper app like Eventghost, but the Info action could be mapped to one of the other buttons.

If you want to add mappings for the four colored keys and the four keys below them here are the entries you need in keyboard.xml. The top left (Internet Explorer) key can't be trapped through keyboard.xml, but in appcommand.xml this button is <browser_home>.

<t mod="ctrl,shift">Notification(Key, Yellow, 3)</t> <!-- Yellow button -->
<m mod="ctrl">Notification(Key, Blue, 3)</m>         <!-- Blue button -->
<i mod="ctrl">Notification(Key, Green, 3)</i>        <!-- Green button -->
<e mod="ctrl">Notification(Key, Red, 3)</e>          <!-- Red button -->
<o mod="ctrl">Notification(Key, u/Yellow, 3)</o>     <!-- Button under Yellow -->
<g mod="ctrl">Notification(Key, u/Blue, 3)</g>       <!-- Button under Blue -->
<t mod="ctrl">Notification(Key, u/Green, 3)</t>      <!-- Button under Green -->
<m mod="ctrl,shift">Notification(Key, u/Red, 3)</m>  <!-- Button under Red -->

The * button sends a numpad-* keypress. XBMC v10.1 sees this as <eight>. XBMC v11.0 sees it as <numpadtimes>.

The # button sends a sequence of keypresses: numlock, alt, numpad-three, numpad-five, numlock. This generates a keypress with the ascii value 35 i.e. '#'. In v10.1 you can map this using <five mod="alt">.

For full Linux support see http://trac.xbmc.org/ticket/8827


2.2 Speedlink SL-6399

[view] [edit]
Remote-SL6399.jpg

Cheap and cheerful remote. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX.

Apparently there are different usb receivers that come with the remote.

ID 1241:1503 Belkin Keyboard       // all keys seem to work
ID 1241:e000 Belkin                // keys Start, RTV, Videos, Music, Pictures, MyTV don't work

There are several extra buttons not on the standard MS remote. If you want to add mappings for these keys here are the entries you need in keyboard.xml.

<t mod="ctrl">Notification(Key, TV power, 3)</t>          <!-- TV power -->
<menu>Notification(Key, More, 3)</menu>                   <!-- More -->
<z mod="ctrl,shift">Notification(Key, Aspect, 3)</z>      <!-- Aspect -->
<e mod="ctrl">Notification(Key, Red/Videos, 3)</e>        <!-- Red/Videos -->
<m mod="ctrl">Notification(Key, Green/Music, 3)</m>       <!-- Green/Music -->
<i mod="ctrl">Notification(Key, Yellow/Pictures, 3)</i>   <!-- Yellow/Pictures -->
<t mod="ctrl,shift">Notification(Key, Blue/MyTV, 3)</t>   <!-- Blue/MyTV -->
<g mod="ctrl">Notification(Key, Guide, 3)</g>             <!-- Guide -->
<o mod="ctrl">Notification(Key, RTV, 3)</o>               <!-- RTV -->
<f1>Notification(Key, Help, 3)</f1>                       <!-- Help -->
<return mod="alt">Notification(Key, Maximise, 3)</return> <!-- Maximise/restore -->
<a mod="ctrl">Notification(Key, Radio, 3)</a>             <!-- Radio -->
<m mod="ctrl,shift">Notification(Key, DVD, 3)</m>         <!-- DVD -->
<a mod="ctrl,shift">Notification(Key, Audio, 3)</a>       <!-- Audio -->
<u mod="ctrl">Notification(Key, Title, 3)</u>             <!-- Title -->



2.3 Unbranded MCE remote

[view] [edit]
Remote-unbranded.jpg

There is no manufacturer's name on this remote or the manual, and it is sold via numerous Asian resellers, but on the PCB of the receiver you can read the OEM name www.tigerfly.net. It can be used with Logitech Harmony Remote Software by picking Computer>>Media Center PC>>Chinavasion>>CVSB-983.

They are available on Ebay and DealExtreme for as little as ~$10 including shipping (often marketed as e g $2 for the device and $8 for shipping but since the cost for two is $20 this is just a trick). It's cheap and feels a bit flimsy, but it works well enough. It simulates the MS Media Center keypresses and will work out of the box on Windows, Linux and probably OSX. It also simulates a mouse including mouse buttons, although it's no match for a proper mouse or trackpad.

It isn't very configurable and certain buttons don't work as they should: The fast forward and rewind buttons skip forward or backwards instead of moving gradually. This is because they send a bunch of keypresses (ctrl, shift, arrow, letter "B" etc). If the software is set to detect ctrl + arrow (left or right) it probably works.

If you want to add mappings for the four coloured keys here are the entries you need in keyboard.xml. Every button can be mapped, with one possible exception (the red Power button).

<f1 mod="ctrl,alt">Notification(Key, Green, 3)</f1>  <!-- Green -->
<f2 mod="ctrl,alt">Notification(Key, Orange, 3)</f2> <!-- Orange -->
<f3 mod="ctrl,alt">Notification(Key, Blue, 3)</f3>   <!-- Blue -->
<f4 mod="ctrl,alt">Notification(Key, Yellow, 3)</f4> <!-- Yellow -->

Update 16th Jan: the rewind button sends three keypresses, left, then ctrl-left, then ctrl-shift-B. The left press causes the video to jump back 30 seconds. With the later releases of XBMC the ctrl-shift-B then starts the rewind (release v9.11 ignores ctrl-keypresses).

Update 1st Nov 2010: Requires a minor kernel patch to support all buttons in Linux. See patch in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/607062. Once patched, works well with Linux.

Update 12th June 2011: I've bought one recently. They must have changed hardware or whatever because mine works well with XBMC out of the box both on Win7 and Linux Ubuntu. Most keys are functioning correctly and 4 colored keys can be mapped by adding the following entries in keymap.xml:

<keyboard>
   <one mod="ctrl,alt">YourAction1</one> <!-- Green -->
   <two mod="ctrl,alt">YourAction2</two> <!-- Orange -->
   <three mod="ctrl,alt">YourAction3</three> <!-- Blue -->
   <four mod="ctrl,alt">YourAction4</four> <!-- Yellow -->
   ...
</keyboard>

Update November 6, 2011: This remote works out of the box on a vanilla install of Ubuntu (11.1). It is auto-detected as a keyboard and mouse. It is no good for typing. It is only slightly better for moving the mouse pointer around the screen. The buttons are dependable though, and if you are looking for a cheap remote that does the job this should be a candidate. Here is a more complete map for every key on the remote except the Red Power Button. These changes go in your keyboard.xml file. Make sure that there are no duplicate mappings (with PVR settings). The default behavior is to pop up a notification with the key combination passed. You should probably replace this behavior with what you want.

	
	<keyboard>
	...
	<!-- Generic MCE Remote Keys -->
	<one mod="ctrl,alt">Notification(Key Pressed, Ctrl+Alt+1)</one> <!-- Green -->
	<two mod="ctrl,alt">Notification(Key Pressed, Ctrl+Alt+2)</two> <!-- Orange -->
	<three mod="ctrl,alt">Notification(Key Pressed, Ctrl+Alt+3)</three> <!-- Blue -->
	<four mod="ctrl,alt">Notification(Key Pressed, Ctrl+Alt+4)</four> <!-- Yellow -->
	<f4 mod="alt">Notification(Key Pressed, Alt+F4)</f4> <!-- The [X] Button-->
	<o mod="ctrl">Notification(Key Pressed, Ctrl+O)</o> <!-- The Open File button-->
	<leftwindows>Notification(Key Pressed, Left Windows Key)</leftwindows> <!-- The Windows Button -->
	<launch_mail>Notification(Key Pressed, Launch Mail)</launch_mail> <!-- The Mail Button -->
	<browser_home>Notification(Key Pressed, Launch Browser)</browser_home> <!-- The IE Button -->
	<d mod="leftwindows">Notification(Key Pressed, LeftWin+D)</d> <!-- The Desktop Button -->
	<e mod="leftwindows">Notification(Key Pressed, LeftWin+E)</e> <!-- The My Computer Button -->
	<tab mod="alt">Notification(Key Pressed, Alt+Tab)</tab> <!-- The Switch Windows Button -->
	<return mod="alt">Notification(Key Pressed, Alt+Return)</return> <!-- The Full Screen Button -->
	<!-- Haven't gotten Power Button to work -->
	...
	</keyboard>
	    
	<!-- Button between L and R mouse buttons shows up as a joystick button -->    
	<joystick name="HID 073a:2230"> <!-- This might be different for your remote -->
	<button id="79">Notification(Key Pressed, Joystick Button 79)</button> 
	</joystick>

	<!-- End Generic Remote Keys -->


XML above tabulated :

<keyboard>
    <one mod="ctrl,alt">    CustomAction01    (Key Pressed, Ctrl+Alt+1)        </one>              <!-- Green -->
    <two mod="ctrl,alt">    CustomAction02    (Key Pressed, Ctrl+Alt+2)        </two>              <!-- Orange -->
    <three mod="ctrl,alt">  CustomAction03    (Key Pressed, Ctrl+Alt+3)        </three>            <!-- Blue -->
    <four mod="ctrl,alt">   CustomAction04    (Key Pressed, Ctrl+Alt+4)        </four>             <!-- Yellow -->
    <f4 mod="alt">          CustomAction05    (Key Pressed, Alt+F4)            </f4>               <!-- X Button-->
    <o mod="ctrl">          CustomAction06    (Key Pressed, Ctrl+O)            </o>                <!-- Open File button-->
    <leftwindows>           CustomAction07    (Key Pressed, Left Windows Key)  </leftwindows>      <!-- Windows Button -->
    <launch_mail>           CustomAction08    (Key Pressed, Launch Mail)       </launch_mail>      <!-- Mail Button -->
    <browser_home>          CustomAction09    (Key Pressed, Launch Browser)    </browser_home>     <!-- IE Button -->
    <d mod="leftwindows">   CustomAction10    (Key Pressed, LeftWin+D)         </d>                <!-- Desktop Button -->
    <e mod="leftwindows">   CustomAction11    (Key Pressed, LeftWin+E)         </e>                <!-- My Computer Button -->
    <tab mod="alt">         CustomAction12    (Key Pressed, Alt+Tab)           </tab>              <!-- Switch Windows Button -->
    <return mod="alt">      CustomAction13    (Key Pressed, Alt+Return)        </return>           <!-- Full Screen Button -->
</keyboard>

And yes, sometimes between then and now, the command for color button changes. f1, f2, f3, and f4 becomes one, two, three, and four caused by keyboard.xml auto update from the repository.


2.4 IRF Media W-01RN

[view] [edit]
Unbranded remote.jpg

There is no manufacturer's name on this remote or the manual, but it works very well with XBMC Dharma PVR on Windows XP Sp3. No additional software required (p.e USB drivers ). Live TV channels are showned trought Media Portal Server 1.1.3.0 installed on same computer as XBMC. The name is believed to be "W-01RN_USB_V3.1" from iRF Media Technology Co., LTD. http://www.irfmedia.com

The Remote is MS compatible and using it is possible move mouse pointer with arrows button.

No reconfiguration needed. It is possible buy this remote also online website (like ebay).

Works in linux after some configuration, see forum thread.


2.5 GoTView PC Remote

[view] [edit]
No image.jpg

The GoTView PC Remote control looks exactly like the "unbranded remote" above. It is also detected as MCE remote by lircd, but has slightly different keycodes, which are incompatible with xbmc defaults. To make things work correctly, add something like the following before the </keyboard> </global> lines in your /usr/local/share/xbmc/system/keymaps/keyboard.xml file

 
      <one mod="ctrl,alt,shift">ContextMenu</one>
      <two mod="ctrl,alt,shift">ActivateWindow(PlayerControls)</two>
      <three mod="ctrl,alt,shift">ActivateWindow(music)</three>
      <four mod="ctrl,alt,shift">ActivateWindow(pictures)</four>
      <five mod="ctrl,alt,shift">ActivateWindow(video)</five>
      <home mod="ctrl,alt,shift">ActivateWindow(MusicPlaylist)</home>
      <r mod="ctrl">Queue</r>
      <h mod="ctrl,alt,shift">Info</h>
      <b mod="ctrl,alt,shift">ActivateWindow(MusicOSD)</b>
      <f mod="ctrl,alt,shift">ActivateWindow(VisualisationPresetList)</f>
      



2.6 Generic PS3 remote

[view] [edit]
Fut-ps3.jpg

There are many generic IR PS3 Remotes. I tried a couple of units from Chinese on-line shops and the keys stuck or were unreliable. Also some of the USB "Dongles" were very directional.

I settled on this particular unit as it appears in Windows device manager as a UID-Gampad and the key=presses test in the control panel

and is detected under Linux as ID 1130:0202 Tenx Technology, Inc. and cat /proc/bus/input/devices -> results in:

I: Bus=0003 Vendor=1130 Product=0202 Version=0110
N: Name="YuanChen Game Controller"
P: Phys=usb-0000:00:1d.2-2/input0
S: Sysfs=/devices/pci0000:00/0000:00:1d.2/usb4/4-2/4-2:1.0/input/input5
U: Uniq=
H: Handlers=event5 js1 
B: EV=1b<br/>
B: KEY=fff 0 0 0 0 0 0 0 0 0
B: ABS=3002f
B: MSC=10



2.7 Xbox 360 Wireless Controller for Windows

[view] [edit]
XBox360WirelessController.jpg

The Xbox 360 Wireless Controller for Windows, which is sold by Microsoft with a separate receiver, works with XBMC on Windows XP, Vista, and 7 using standard Microsoft Drivers. The controller, along with the wired edition controller, should be plug-and-play on Windows (tested with Windows 7. Awaiting confirmation on Vista and XP) since XBMC 12 Frodo.

Many other unofficial 360 controller models have been reported as compatible with XBMC and added to the device list. If you run into one that does not work automatically, please use the instructions in the forum thread linked below to report the device name and make it work.

For Linux, there are two options: the built-in Xpad kernel drivers bundled with most Linux distributions or the Xboxdrv userspace drivers package, available here: Homepage and Binaries or Git-Source (or use your package manager). Xpad should work out of the box with no configuration. However, Xboxdrv doesn't map the same way or use the same device name, so if you want to use it with XBMC, use the --mimic-xpad argument. This will cause it to use the same mappings and device names as Xpad, the only currently supported method.

Work is still progressing on Linux support. In particular, use of the 360 triggers in Linux can cause some axes of the thumbsticks to fail until XBMC is restarted. See the Forum link below for more information.

The following gallery shows the function of each button when navigating menus and during video playback.


Attention talk.png See Fix Xbox 360 controller support (keymap xbox 360 controller) forum discussion


2.8 XBox DVD Remote

[view] [edit]
Remote-xbox1.jpg
See also: How-to:Wire your XBOX DVD-Remote for USB

The original DVD remote for XBox 1. This is a simple well working remote, almost out of the box experience and it has a good support in XBMC.

This remote won't work "out of the box" with Windows as it doesn't send keystrokes and can't be configured to do so. It can be made to work with a helper app like Eventghost or IR Server Suite. See http://forum.xbmc.org/showthread.php?t=45337 for the details.

2.8.1 Controls



2.9 Flirc

[view] [edit]
Flirc.jpg

Flirc is a small USB device that plugs into your computer and pairs with your same television remote, or any remote that you want to use. It's basically a universal IR receiver. The best part about flirc is that it mimics a keyboard so every media center application understands it without any drivers. Flirc runs across all platforms.

Flirc Website

It is a small project run by Jason Kotzin with a portion of each sale going to a cancer charity


2.10 Boxee Box remote

[view] [edit]
Boxee Box remote.jpg
See also: Alternative keyboard.xml for Boxee Box remote

This remote comes with the Boxee Box from D-Link, but is also sold separately. It comes with at small USB receiver, and works out of the box as an external USB keyboard. On the front face it has navigation buttons, OK, Esc, and a Play/Pause button. On the back face, it has an almost complete QWERTY keyboard.

It is possible to use the receiver board built into a Boxee Box with other devices. Some soldering will be required for this. See here for details.


2.11 Android remotes

[view] [edit]
Official XBMC Remote for Android.png

The Official XBMC Remote for Android by Team-XBMC is available on the Android Market. It lets you browse your XBMC library to select items to play and provides transport controls as a touch screen remote.

Several unofficial Android XBMC remotes are also available:


Additionally, on the Windows platform, if you are willing to run a background program on your XBMC, there are several products on the Android market that act as a PC remote.




2.12 Apple remote

[view] [edit]
First (white) and second (silver) generation Apple remotes.

There are two versions of the Apple remote, the first generation white one with 6 buttons, and the second generation silver one with 7 buttons. These remotes have sometimes come with Mac computers and Apple TV units, but can also be purchased separately. The white version is no longer made, but can be found on eBay. Both versions have identical functions and be used interchangeably. Currently the "Play" button on the silver version functions the same as the middle "select" button (with some exceptions; for instance "Play" on a folder in files-view plays all files in the folder). The remotes can also be paired to a specific device to prevent one remote from controlling two devices at once (or vice versa).


2.13 Motorola Nyxboard Hybrid

[view] [edit]
Motorola Nyxboard Hybrid.png
See also: Alternative keyboard.xml for Nyxboard

Flip keyboard remote that has a basic button side and a full QWERTY keyboard side. Uses an RF dongle that is seen as a standard keyboard and also has an IR mode that can learn IR remotes. Available for sale from Pulse-Eight: http://pulse-eight.com/store/products/96-motorola-nyxboard-hybrid.aspx


2.14 Tivo Slide

[view] [edit]
Full-tivo-slide-remote.png

Tivo Slide is made for use with the Tivo DVR, but can be used with an HTPC. It features both IR and Bluetooth, and has a slide-out QWERTY keyboard. It functions well under Windows, though a program to remap the keys is needed (EventGhost, Intelliremote, etc.). It is functional under XBMCBuntu 11.0 Eden, though there are 4 buttons which do not work. Support for these buttons is in the Linux kernel, the next release of XBMCBuntu should work fine. Detailed information on getting Tivo Slide to work with XBMC


2.15 Emprex 3009URF III

[view] [edit]
Emprex 3009ARF.jpg

Product link. Note that this has apparently been discontinued and replaced by the identical looking 3009ARF III.

A cheap, but in my experience decent, keypress-sending remote which uses 2.4GHz RF rather than IR. Range is good and it works even if pointed directly away from the TV, also my XBMC box is directly above my wifi AP yet no interference is apparent. All basic functionality such as volume, navigation, information and subtitle control OSD works well out of the box in XMBC 11.0 Eden running on Debian. (It also worked in LinuxMCE although some configuration was required.) I haven't tried to configure the colour buttons etc. The power button does not cause a suspend/power off but is noticed by the system (screen undims) and so could presumably be made to work.

Vendor appears as "Behavior Tech. Computer Corp." aka "BTC" in lsusb and /proc/bus/input/devices respectively.

I: Bus=0003 Vendor=046e Product=5578 Version=0111
N: Name="BTC USB MCE Cordless Remote Control."
P: Phys=usb-0000:00:12.1-2/input1
S: Sysfs=/devices/pci0000:00/0000:00:12.1/usb2/2-2/2-2:1.1/input/input7
U: Uniq=
H: Handlers=kbd event7 
B: PROP=0
B: EV=1f
B: KEY=837fff 2ff3b7 bf2d4c44 0 0 1 f84 8b37c000 667bfa d941dfed 9e0000 0 0 0
B: REL=40
B: ABS=1 0
B: MSC=10


Personal tools
Namespaces
Variants
Actions
Navigation
Wiki help
Google Search
Toolbox