I'm using a logitech K400 keyboard/mouse combo on the OUYA. Everything seems to mapped out pretty well, but I don't seem to have any buttons mapped to output for the O U Y A buttons. I'm currently rooted. What's the best way to map these buttons onto the keyboard.
JGonzo10 said:
I'm using a logitech K400 keyboard/mouse combo on the OUYA. Everything seems to mapped out pretty well, but I don't seem to have any buttons mapped to output for the O U Y A buttons. I'm currently rooted. What's the best way to map these buttons onto the keyboard.
Click to expand...
Click to collapse
I was able to map some functions onto my Logitech keyboard by modifying a file called generic.kl ; /system/usr/keylayout
All I really did was to map HOME and BACK to function keys though. Didn't do anything with the O U Y A buttons. But should be doable.
Note that an ota will rewrite the file. So make a backup of the modded file if you're gonna allow an ota.
. You might also try something like this: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner
Haven't tried the app myself though-- and you'll need to side load it, or have play store installed.
Either way you have to be rooted.
I also found that if you do something wrong (can't remember exactly what it was) when modifying the generic.kl file, it may render the keyboard useless. So if you go that route, back up that file before doing any changes in case you need to revert to it.
Cheers.
Sent from my SGH-M919G using xda app-developers app
Oscar_david said:
I was able to map some functions onto my Logitech keyboard by modifying a file called generic.kl ; /system/usr/keylayout
All I really did was to map HOME and BACK to function keys though. Didn't do anything with the O U Y A buttons. But should be doable.
Note that an ota will rewrite the file. So make a backup of the modded file if you're gonna allow an ota.
. You might also try something like this: https://play.google.com/store/apps/details?id=innerlife.keyboard.multilanguagekeymapredefiner
Haven't tried the app myself though-- and you'll need to side load it, or have play store installed.
Either way you have to be rooted.
I also found that if you do something wrong (can't remember exactly what it was) when modifying the generic.kl file, it may render the keyboard useless. So if you go that route, back up that file before doing any changes in case you need to revert to it.
Cheers.
Sent from my SGH-M919G using xda app-developers app
Click to expand...
Click to collapse
Thanks! I will try this tonight. All I'm really looking to map is the "O" to navigate the menus. Unless I'm missing something and there is already a button on the keyboard mapped for that.
Related
I got my wiimote to map the keys and works great for snesoid. But having no luck with N64 and NES.... they map the keys fine but nothing happens when I actually press them in game
have you enabled the option for bluetooth gamepads and also make sure the wiimote ime is active? Works fine for me
SNES works fine, not the others
ive done everything right. I can go into settings, input, key mappings and it recognizes all the keys I press on my wiimote to map it, but when I go into the game NOTHING happens.
this is ****ing annoying
Same thing happened to me. In the emulator, go to menu, settings, other settings then check "use input method"
Worked perfect for me after that.
Sent from my DROIDX using XDA App
DroidHam said:
ive done everything right. I can go into settings, input, key mappings and it recognizes all the keys I press on my wiimote to map it, but when I go into the game NOTHING happens.
this is ****ing annoying
Click to expand...
Click to collapse
Same thing happened to me. In the emulator, go to menu, settings, other settings then check "use input method"
Worked perfect for me after that.
Sent from my DROIDX using XDA App
EDIT: don't mind the double post, XDA App gave me an error submitting the first time.
got it, thx
I just got this keyboard, amazon.com/gp/product/B004L9MBH6/ref=oh_details_o01_s00_i01
There are a few function keys that currently are not assigned a function. Is there a way to program those keys to perform tasks?
My tablet is a Nx 10, stock.
Thanks in advance.
You could edit the specific device file in the system/usr/keylayout folder.
Or the easy way:
https://play.google.com/store/apps/...sImNvbS5hcGVkcm9pZC5od2tleWJvYXJkaGVscGVyIl0.
Sent from my EVO using xda app-developers app
Quote,
”Or the easy way:”
I'm into easy,
Thanks
Currently my favorite keyboard (harcker's keyboard) works, but the right side of the keyboard it cut off by the navbar. Other keyboards like swype have fixed this issue and I imagine it's not that hard to do. If anyone knows of a fix, please share.
But for now, we should all vote for this bug so that Klaus notices it.
http://code.google.com/p/hackerskeyboard/issues/detail?id=342&start=100
Let's get this thing working!
Remove the nav bar. Add LMT. Problem solved.
Sent from my KFHD using xda premium
You could use button savior. I actually prefer LMT, for more customization.
miztah1999z said:
You could use button savior. I actually prefer LMT, for more customization.
Click to expand...
Click to collapse
Tis the method I employ
hmm, I already tried this, but I couldn't get LMT to work (I'm running kinology). It just kept saying "LMT" has stopped.
Is there an apk for lmt?
Edit: found it.
Sent from my KFTT using Tapatalk HD
I have the stock navbar disabled, Hacker's Keyboard, Button Savior, LMT & Homeflip. The only thing I can't do...is find space to type in.
Used xsposed installer an xsposed app settings set all apps that use keyboard to fullscreen
Sent from my KFTT using xda premium
Visit the Kinology ROM thread in the 7" Android Development forum and pose the question to the ROM creator psych0phobia. He has fixed the keyboard issue by adding a right side padding code. This may be able to be applied to any keyboard. You'll have to ask.
Sent from my KFTT using xda app-developers app
Katalystik said:
Visit the Kinology ROM thread in the 7" Android Development forum and pose the question to the ROM creator psych0phobia. He has fixed the keyboard issue by adding a right side padding code. This may be able to be applied to any keyboard. You'll have to ask.
Click to expand...
Click to collapse
Actually, I think there's already a link to a working version in the thread.
Out of curiousity, what did you do to fix the keyboard issues psych0? Looking at appling it to my swype 3 keyboard on my stock rooted ROM.
Katalystik said:
Out of curiousity, what did you do to fix the keyboard issues psych0? Looking at appling it to my swype 3 keyboard on my stock rooted ROM.
Click to expand...
Click to collapse
It's not a generic thing. The AOSP keyboard happens to have side margins in the layout files. Unfortunately, they specify a single value for both sides. I had to hack the .smali a bit to make the value only apply to the right side. (Yes, I probably could have just rebuilt from source with my change, but it was faster for me to just hack it in.)
psych0phobia said:
Actually, I think there's already a link to a working version in the thread.
Click to expand...
Click to collapse
psych0phobia said:
It's not a generic thing. The AOSP keyboard happens to have side margins in the layout files. Unfortunately, they specify a single value for both sides. I had to hack the .smali a bit to make the value only apply to the right side. (Yes, I probably could have just rebuilt from source with my change, but it was faster for me to just hack it in.)
Click to expand...
Click to collapse
Is there any way you can release the keyboard as is as an apk? sick of having the p cut off on mine but don't want to jump to Kinology yet as I had a close shave with my KFTT last night, thought I'd bricked the bugger, no file explorer would read the /data folder and i got the red triangle on one boot (didnt persist once i'd rebooted though)
Would be much appreciated.
Here the link for modified Hacker's keyboard:
timurg said:
Just install it:
http://www.mediafire.com/?0smme0qbwcb0vm1
you can dl dictionaries from Google Play:
https://play.google.com/store/apps/developer?id=Klaus+Weidner
Click to expand...
Click to collapse
Is there any way to remap keys on 3rd party controlers change the order they come up.
I have an old Gravis Gampad Pro USB I wanted to sue with S/NES and PS1 emulaters but the ouya maps the buttons crazy (ex gamepad r2=ouya Y) and USB controlers come first no matter what as far as I can tell. I wwant to remap the Gampads keys to match the ouya layout to use it or change the Ouya controler from 3 to 1
Sent from my OUYA Console using xda app-developers app
The Old One said:
Is there any way to remap keys on 3rd party controlers change the order they come up.
I have an old Gravis Gampad Pro USB I wanted to sue with S/NES and PS1 emulaters but the ouya maps the buttons crazy (ex gamepad r2=ouya Y) and USB controlers come first no matter what as far as I can tell. I wwant to remap the Gampads keys to match the ouya layout to use it or change the Ouya controler from 3 to 1
Sent from my OUYA Console using xda app-developers app
Click to expand...
Click to collapse
There are 2 things that you can try. Not sure, but you might need root, I have not used either on a stock device, so I can't remember.
The first is tincore keymapper. It can map some things, but I don't know if it will help in this situation, as I am still trying to figure it out.
The other option is an app called onlive helper. I have used it in the past to map my onlive controller to work for the Zenonia series. I had to use another program to find the key codes my controller used, but I can remember which one (sorry). You edit a txt file with the mapping for the button press you want it to be.
I am not sure if this will work on the Ouya, as I have not tested it, but in theory it should, as long as you can figure out what to map the keys as.
Sent from my Verizon Galaxy Note 2 using Xparent Skyblue Tapatalk 2
Did anybody tried "tincore keymapper", is it can be solution for hard gaming??
Simonius007 said:
Did anybody tried "tincore keymapper", is it can be solution for hard gaming??
Click to expand...
Click to collapse
I haven't been able to get it to work for the ouya
Hi, I'm running Slim 4.3 Build 1 (http://forum.xda-developers.com/showthread.php?t=2393971) on my lcd version nexus s and really like the on screen buttons included with the rom. Is there any way to remove the back light from the capacities buttons and stop them vibrating?
Thanks
If you download Nexus S Tools from the Play Store, you can disable the capacitive lights, and there's a file somewhere in system/usr that has the keycodes for the capacitive buttons (you'll know what file it is when you see it, there's like 4 lines for back, home, search, and menu). What you gotta do is put a # in front of each line and reboot, then the capacitive buttons will be disabled.
Sent from my M470BSA using xda app-developers app
Thanks for the response
Do you mean NS tools?
https://play.google.com/store/apps/details?id=mobi.cyann.nstools&hl=en
I couldn't find anything called "Nexus S" tools.
Bit of a noob mate , how do I find the system/user and edit it?
continuum51 said:
Thanks for the response
Do you mean NS tools?
https://play.google.com/store/apps/details?id=mobi.cyann.nstools&hl=en
I couldn't find anything called "Nexus S" tools.
Bit of a noob mate , how do I find the system/user and edit it?
Click to expand...
Click to collapse
Yes, ns tools, but others support bln as well...
Sent from my Nexus S using xda premium
continuum51 said:
Thanks for the response
Do you mean NS tools?
https://play.google.com/store/apps/details?id=mobi.cyann.nstools&hl=en
I couldn't find anything called "Nexus S" tools.
Bit of a noob mate , how do I find the system/user and edit it?
Click to expand...
Click to collapse
To edit the file, download a file explorer (ES File Explorer is what I use) and enable "root explorer" then go into settings and make sure /system is set to "R/W" (there's a little check box somewhere).
From there go into /system/usr/keylayout/cypress-touchkey.kl and open it as text. Then put a # in front of every line that doesn't have one and then reboot
Sent from my Nexus S 4G using xda app-developers app
beneath-a-burning-turtle said:
To edit the file, download a file explorer (ES File Explorer is what I use) and enable "root explorer" then go into settings and make sure /system is set to "R/W" (there's a little check box somewhere).
From there go into /system/usr/keylayout/cypress-touchkey.kl and open it as text. Then put a # in front of every line that doesn't have one and then reboot
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Do you know if there's a similar procedure to remove also the backlight??
I'd like to keep them always off without changing kernel or rom, i'm on 4.1.2 stock.
MarkRain said:
Do you know if there's a similar procedure to remove also the backlight??
I'd like to keep them always off without changing kernel or rom, i'm on 4.1.2 stock.
Click to expand...
Click to collapse
As long as you have root, NSTools is always my go-to option since its designed for this phone specifically, so I'd give that a whirl. I don't know exactly what file controls the backlight so I can't help you there
Sent from my M470BSA using xda app-developers app
beneath-a-burning-turtle said:
As long as you have root, NSTools is always my go-to option since its designed for this phone specifically, so I'd give that a whirl. I don't know exactly what file controls the backlight so I can't help you there
Sent from my M470BSA using xda app-developers app
Click to expand...
Click to collapse
I already tried NStools, but it require a modified kernel to edit the capacitive keys backlight.
Thank you anyway
^Same, I'm trying NStools but I don't thin the kernal is letting me do much. Any recommendations on a good krnal to flash with slim?
Marmite that comes with slim rom is good. I have disabled the back lights using that and nstools in the past. But often they would flicker if you touched them which bugs me.
In the settings somewhere you should be able to disable the hardware keys without altering any system files. I am not on that rom anymore so I can't tell you exactly where!
Ended up using nstools + disabling vibration
esexplorer is pretty complicated
Thanks for the help everybody