Leaderboard

Any progress on this one? Love to add some extra functions :)

It's easy: Just map the select button on your remote with the OUYA-Controller Button for O: Therefore you need to add/replace it to your Keyboard-Layout-file: Which would be (for the enter key #28:) key 28 BUTTON_A or for the backspace (I think it's del in the linux keymap and then #43) and therefore the corresponding A-Key on the Ouya Controller key 14 BUTTON_B The naming of the OUYA controller buttons ABYX comes from the XBOX controller - have a look at one and you'll quickly understand it. http://www.geekys.net/ekmps/shops/geekys/images/original-xbox-controller-375-p.jpg You could also follow my tutorial at post #26 - that'll fix everything ;) Additionally, I wrote another guide on this: http://www.peterfranssen.de/2013/08/14/key-bindings-of-ouya-controller-for-keylayouts/

Hey guys! I'm new here and I must say that this article helped me a lot. I managed to get my OUYA working with FLIRC, XBMC and an Apple Remote. In case anyone else wants to accomplish this, I created a guide (in English) on how to do so. I modified the files you provided above in order to have full functionality. Cheers for the great work you guys do! Here's my tutorial: http://www.peterfranssen.de/2013/08/04/getting-flirc-to-work-with-ouya-and-xbmc/

I have an update to this. You might have noticed that the .kl file gets wiped every time there is a system update if it is put in /system/usr/keylayout/. Since Ouya has had an update a week this is a problem. Here's the solution for that... In the android dev site I found this information about the .kl files: The major difference between /system and /data (not noted here) is that /system is what is wiped and replaced when the Android image is updated, so it is a bad spot to put user fixes. /data is where all your user settings and packages go and they are left untouched on an Ouya system upgrade. So, to put it in a nutshell, but the Vendor_20a0_Product_0001.kl file in /data/system/devices/keylayout. You will probably need to create these directores on your Ouya. I did on mine and it works as this is a basic Android behavior for Android keylayout files. I held off on posting this to make sure that I was correct. After the Ouya system upgrade from this week it still continues to work.

Sorry that I don't check this thread too much. I am going to attach my current .kl file for you to take a look at. I am not sure it's finished. It isn't well commented, but I can tell you that my changes are "key 1" and "key 28". Key 1 and Key 28 are what Android would see as "ESC" and as "Return" respectively. Ouya doesn't map those correctly to their usual uses, or at least it It actually doesn't affect any Ouya usability at all because you are ONLY redefining keys in resepect to FLIRC itself. It shouldn't affect anything else. I have to admit that I didn't understand the problem with the "HOME" key until just a few minutes ago, so I don't think the home key is mapped on my .kl file. Maybe I can experiment with that this weekend and that working as well. One last thing: don't put the .kl file where it says above. It will be erased every time there is a system update. I was about to post on that when I saw your question to me. --dcl Vendor_20a0_Product_0001.kl.zip