stacyk819
-
Posts
13 -
Joined
-
Last visited
-
Days Won
1
Posts posted by stacyk819
-
-
Well, I have been dealing with setting up Flirc with an Ouya and a Harmony One today. Part of the reason I bought the Ouya was promises it will work with XBMC. It seems like it will work pretty well, especially when there is an Ouya optimized version.
Anyway, I've got everything pretty much working in XBMC by remapping some keys in Keyboard.xml (such as mapping "b" to back and "c" for context menus) and then setting Flirc to emulate those keys. Other mappings are quite easy, like mapping the Harmony's "ok" key to "return" on the keyboard. This works nicely in XBMC.
I'd like to get it to work fine with the OUYA interface as well. I've tried some ways to do this, but the problem that OUYA UI hasn't quite standardized itself yet. For instance in the "Make" menu, you can hit the return key and it selects, but in the other a keyboard return does nothing. Android itself usually has trouble with the ESC key, but oddly in OUYA it works in some circumstances and doesn't work in others.
So the next idea is to use an Android program like Exernal Keyboard Helper to do some internal Android remapping so that those Harmony keys emulate keys on the OUYA controller. However I haven't been successful in that yet either. Here is part of the generic.kl file.
key 304 BUTTON_A
key 305 BUTTON_B
key 306 BUTTON_C
key 307 BUTTON_X
key 308 BUTTON_Y
key 309 BUTTON_Z
Do constants like BUTTON_O work in this file? Does anyone know? They aren't present in External Keyboard Helper... has anyone tried to edit the generic.kl directly to emulate the controller buttons.
Hi I just read your post more carefully... Clearly you did not read my guide at all because otherwise you would have flirc working perfectly with your ouya menu and xbmc. external keyboard helper does not work very well with ouya because it is not actually able to map the keys correctly (ouya changes a few things around from stock android) for example you can map the menu and home button with external keyboard helper but they will not work for all programs, you need to create a new keymap. I am gong to delete my earlier comment about that program because it will likely confuse more people. in order to get it working you need to create a custom key layout and name it "Vendor_20a0_Product_0001.kl" you can use either the generic keylayout or the ouya one as a template.
you also do not need to map the keys c, i etc because xbmc for android recognises the context menu as the menu button and back as the back button.
you should delete the Keyboard.xml file and just edit the android keymaps located in /system/usr/keylayout/ or just copy the file i attached and follow my instructions and everything will work perfectly...
also this version of xbmc works really well with ouya http://forum.xbmc.org/showthread.php?tid=152005
-
I attached a copy in case you dont want to go grab it from your ouya.. you can probably just change the key numbers to whatever you have set on your remote/flirc and rename it to "Vendor_20a0_Product_0001.kl" idk though i havent tried like i said I dont use the ouya launcher but i can navigate fine just useing to normal buttons using my keymap though i havent messed with it too much though as enter and back only function as the O and A keys
-
1
-
-
Well, I have been dealing with setting up Flirc with an Ouya and a Harmony One today. Part of the reason I bought the Ouya was promises it will work with XBMC. It seems like it will work pretty well, especially when there is an Ouya optimized version.
Anyway, I've got everything pretty much working in XBMC by remapping some keys in Keyboard.xml (such as mapping "b" to back and "c" for context menus) and then setting Flirc to emulate those keys. Other mappings are quite easy, like mapping the Harmony's "ok" key to "return" on the keyboard. This works nicely in XBMC.
I'd like to get it to work fine with the OUYA interface as well. I've tried some ways to do this, but the problem that OUYA UI hasn't quite standardized itself yet. For instance in the "Make" menu, you can hit the return key and it selects, but in the other a keyboard return does nothing. Android itself usually has trouble with the ESC key, but oddly in OUYA it works in some circumstances and doesn't work in others.
So the next idea is to use an Android program like Exernal Keyboard Helper to do some internal Android remapping so that those Harmony keys emulate keys on the OUYA controller. However I haven't been successful in that yet either. Here is part of the generic.kl file.
key 304 BUTTON_A
key 305 BUTTON_B
key 306 BUTTON_C
key 307 BUTTON_X
key 308 BUTTON_Y
key 309 BUTTON_Z
Do constants like BUTTON_O work in this file? Does anyone know? They aren't present in External Keyboard Helper... has anyone tried to edit the generic.kl directly to emulate the controller buttons.
THe OUYA controller keymap is called "Vendor_2836_Product_0001.kl" located in the same folder check that out if you want to map the remote to OUYA functions
You can use this app: https://github.com/downloads/chrisboyle/keytest/KeyTest.apk to find out which keys correspond to which OUYA buttons
-
Even if you can get it on the playstore, you would still need to root. You cannot mount /system/ without superuser permissons... Its not a bad idea though because it will (sort of) simplify one step.
-
EDIT: Easier method/ way not to mess up your default keyboard layout.
So on android you can create different key layouts for individual keyboards as long as the file names indicate the device (see attached)
I created a key layout for flirc and restored my stock generic one so that other keyboards arent affected.
Instructions
Step 1: root/ install superuser
Step 2: move attached file (unzipped of course) to /system/usr/keylayout/
Step 3: on Flirc software program the following buttons for android commands ie: program the buttons on your remote to the keys which correspond to the following android commands
esc: back
home: home
F2: MENU
F3: play/pause
F4: play/pause
F5: Stop
F6: rewind
F7: previous track
F8: next track
F9: fast forward
Done
all other keys are default, of course you can edit the key list to whatever you want...
-
1
-
-
Thanks one note for android devices in general. Though "Generic.kl" is the default keymap for ouya "qwerty.kl" is the default for a lot of older devices. Also I'm not sure if the function "HOME ALT" works on all devices though "HOME" should work on most
-
HI i just realized all the problems that i was having were with the external keyboard helper program i was using i mapped the keys manually and everything works now, that program is a huge pos and a waste of money
-
nevermind i think both issues were with the keymapping program i was using i just mapped the leys manually and ghot rid of the program and its working pretty well now
-
Also I was wondering if any one can confirm the keyboard fix for sticky keys. I installed the version of xbmc posted here and it's not a huge issue but the keys do still repeat some of the time
-
Yeah in order to fix that you need to changed the key map in android (see my guide) it might be qwerty.kl on your device
escape is button 1 which you can changed to "BACK VIRTUAL" I'm not sure what button backspace is but you can find out using this app: https://github.com/downloads/chrisboyle/keytest/KeyTest.apk.
If you want one of the buttons to bring up the context menu or android menu in other apps program it to "MENU VIRTUAL" also the home button function is probably "HOME" on your box though it is different on ouya which I use.
I have one question which is driving me nuts. Does anyone know how to map the android media buttons ie: media play, pause, stop ,ff, etc the those functions on xbmc? They work on nearly every other app but not xbmc so I don't want to change them to the letter keys. I heard there is an XML file that stores this info but do not know where is is or how to specify the media keys
-
EDIT: so mapping the keys (menu and back) using the app worked in android but not in xbmc, in order to get around this, you need to set the keys you want in the "Generic.kl" file to
HOME VIRTUAL
and
BACK VIRTUAL
for some reason when they are not virtual, it crashes xbmc
-
Hi I just got flirc and ouya today and spent the last few hours getting it working with my ouya. Obviously android recognises it as a usb keyboard so some functions work right away but you need to get a little tricky if you want everything to work seemlessly including android home, menu, back buttons.
Step 1: install superuser
follow this guide:
http://forum.xda-developers.com/showthread.php?t=2270589
if you do not understand how to do this i cannot help you.
Step 2: install a file manger, I use es file explorer
step 3 navigate to system/usr/keylayout and find the file "Generic.kl"
this file is the default key map and maps android functions/ characters to coresponding keys on the keyboard
Step 4: edit file
NOte: on es file manager you need to enable r/w access by going to tools> root explorer
using this file you can set android use certion functions for different keys. I didn't change this too much but made one really important edit. Key 102 which corresponds to the "home" key on most usb keyboards is by default set to "MOVE_HOME" which means go to the top of the page you need to change this to "HOME ALT" which is a special function that ouya made to be the home button.
Note: for most android devices "HOME" is the home key but this brings up the menu on ouya, the reason they did this is so they can have single tap bring menu and double bring home.
Done
This seems really simple and isnt too bad the tricky part was figuring out about the "HOME ALT" function which as far as I know I am the only one to figure out.
PS: this is off-topic I hate the ouya launcher but installed nova launcher and open launcher for google tv both of which work really well, I have it set to open nova at start (sort of a desktop) and open open launcher with the home button (which goes over the media or apps and is great for multitasking etc. I have attached the apk which is very hard to find because you need a google tv to get it from the playstore
https://dl.dropboxusercontent.com/u/17958951/Open-Launcher-for-GTV.apk
-
2
-
[GUIDE] getting Flirc to work with OUYA
in How To
Posted
Okay that makes sense...
Do you mean you cannot use su with adb? If thats true, you may need to reflash the image with recovery. you can download it here : http://forum.xda-developers.com/showthread.php?t=2266629
this will tell you how to get into recovery: http://forums.ouya.tv/discussion/1380/recovery-mode
if you can still use adb with su privlages however you don't need to do that.
in order to root, you should follow the instructions in post #8 in the xda i put in the first post here (http://forum.xda-developers.com/showthread.php?t=2270589) starting with pushing su to your sdcard ie: adb push su /sdcard/su
all of the files from the superuser zip need to be located in the sdk/platform-tools directory on your computer