I have XBMC (gotham Alpha 1) working on Ouya, but am running into one snag with the remote: I have a MCE remote control which works mostly fine, with one exception: the 'back' button doesn't work.
The remote acts as a keyboard, and acts as if 'backspace' is pressed which is normally interpreted correctly by XBMC on windows.
However, it appears that the Ouya itself has a keyboard mapping quirk where a USB keyboard's backspace is instead mapped to the 'delete' key. (Unfortunately not unusual on some mostly older Linux flavors either) This is further confirmed by the text editing fields inside XBMC, e.g. to add a video source. Hitting backspace there removes the character to the right of the cursor, which is the normal 'delete' key behaviour.
So... since XBMC is interpreting it as the 'delete' being pressed instead of backspace, instead of going to the previous page it brings up a dialog box asking if I'm sure that I want to remove the current file from my library... Which of course makes navigation near impossible.
Since this will affect many remotes as well as (USB?) keyboards, perhaps the developers may want to account for that discrepancy on Ouya console?
Anyway -- in the mean time, I was looking to see if I could override the behaviour myself. I have adb set up, and a able to drop a keyboard.xml file into what I presume is the correct location: /storage/sdcard0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/keymaps
Unfortunately, it appears to have no effect at all so far
The contents of my test file:
<keymap>
<global>
<keyboard>
<delete>back</delete>
</keyboard>
</global>
</keymap>
I can do everything else with my remote, except I have to use the ouya controller's 'A' button any time I want to go back to the previous screen which is a bit unfortunate...
One more thing: running Key Test on the Ouya returns the following when pressing the back key on the remote:
keycode: 67
Keyevent: KeyEvent { action=ACTION_DOWN, keycode=KEYCODE_DEL, scancode=14, metastate=0, flags=0x8, deviceID=17, source=0x101}
I tried <key id="67">back</key> as well, with no luck either.
The remote acts as a keyboard, and acts as if 'backspace' is pressed which is normally interpreted correctly by XBMC on windows.
However, it appears that the Ouya itself has a keyboard mapping quirk where a USB keyboard's backspace is instead mapped to the 'delete' key. (Unfortunately not unusual on some mostly older Linux flavors either) This is further confirmed by the text editing fields inside XBMC, e.g. to add a video source. Hitting backspace there removes the character to the right of the cursor, which is the normal 'delete' key behaviour.
So... since XBMC is interpreting it as the 'delete' being pressed instead of backspace, instead of going to the previous page it brings up a dialog box asking if I'm sure that I want to remove the current file from my library... Which of course makes navigation near impossible.
Since this will affect many remotes as well as (USB?) keyboards, perhaps the developers may want to account for that discrepancy on Ouya console?
Anyway -- in the mean time, I was looking to see if I could override the behaviour myself. I have adb set up, and a able to drop a keyboard.xml file into what I presume is the correct location: /storage/sdcard0/Android/data/org.xbmc.xbmc/files/.xbmc/userdata/keymaps
Unfortunately, it appears to have no effect at all so far
The contents of my test file:
<keymap>
<global>
<keyboard>
<delete>back</delete>
</keyboard>
</global>
</keymap>
I can do everything else with my remote, except I have to use the ouya controller's 'A' button any time I want to go back to the previous screen which is a bit unfortunate...
One more thing: running Key Test on the Ouya returns the following when pressing the back key on the remote:
keycode: 67
Keyevent: KeyEvent { action=ACTION_DOWN, keycode=KEYCODE_DEL, scancode=14, metastate=0, flags=0x8, deviceID=17, source=0x101}
I tried <key id="67">back</key> as well, with no luck either.