Jump to content
Flirc Forums

Leaderboard

Popular Content

Showing content with the highest reputation on 08/05/2013 in Posts

  1. 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
    1 point
  2. 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 Vendor_2836_Product_0001.zip
    1 point
  3. 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.
    1 point
  4. 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... Vendor_20a0_Product_0001.zip
    1 point
×
×
  • Create New...