So I'm currently running Steel Droid v3.0 on my Droid 3. I want to play SNES roms on my droid with a PS3 controller. I installed Six Axis Controller, successfully configured the controller to my phone and activated the controller as the primary input method.
My issue is that when i go to map the keys is an emulator like Super GNes, none of the key bindings change.
Has anyone else had this issue??
Warshanks said:
So I'm currently running Steel Droid v3.0 on my Droid 3. I want to play SNES roms on my droid with a PS3 controller. I installed Six Axis Controller, successfully configured the controller to my phone and activated the controller as the primary input method.
My issue is that when i go to map the keys is an emulator like Super GNes, none of the key bindings change.
Has anyone else had this issue??
Click to expand...
Click to collapse
No, keybindings work great for me (at least w/fpse).
Sixaxis controller problem
I have a issue where everything runs fine before i enable touch profiles, but once i enable touch profile there is no way to get back to the game because my phones touch screen response is offset. ill click the games app on the bottom left, but it will move a app in top middle. i dont understand why. also it wont do basic functions like scrolling up and down once im in the games (BTA and Modern combat 3). this has become frustrating because i cant even get into game modes because i cant select them. why does touch screen work poorly once touch profile is on? if you know answer help please!
warshanks: not sure if this helps but the way i have mine set up is like this. It may not be super efficient but it works.
(im running maverick 4.0 on my xt860, not sure if that is relevant)
1) I set my physical key bindings in the emulator (NESoid) to actual keys on my phone's keyboard. (so like, W for up, X for down, etc.)
2) I installed Sixaxis, and went into ITS key bindings/settings (Preferences, Input Mappings, 1st Controller mappings). I would pick "up" in the list (which represents Up on the regular arrow pad on the controller), and it shows a list of keys to bind it to.. since W is my "up" in NESoid, I choose W. Then do the rest to match the other bindings that I did in NESoid.
3) I also wanted to map some Android stuff to it, so I mapped R1 to call "Menu", the left analog stick to control the regular keyboard arrow keys (to navigate homescreen or whatever), L1 to "Back", and R3 (right analog stick push-button) to "OK" or "ENTER".
SO whenever I activate the SixAxis app, and switch SixAxis as my default input method, I'm ready to play. Unfortunately, I would probably have to change my preferences/binding in SixAxis if I switch to another emulator... but for now I'm just sticking with NESoid (my favourite)
Related
Okay so I downloaded the app and all is well. The controller seems synced (it is in position 1, though not listed in bluetooth menu. I enable input on nesoid, but nothing happens... am I missing something stupid?
cstrife999 said:
Okay so I downloaded the app and all is well. The controller seems synced (it is in position 1, though not listed in bluetooth menu. I enable input on nesoid, but nothing happens... am I missing something stupid?
Click to expand...
Click to collapse
Bumpy 10 characters...
At some point I will make this more clear in the description, but to use the controller with the Droid x2, 3 and Bionic, you must enable 'Bypass IME' in preferences. As a bonus, this will also allow you to use a normal soft keyboard at the same time as the controller, as you will no longer need to switch the active IME.
bought this app last night after my post. got it up an running this morning. i'm a megaman junkie. took a little messing with to figure this out, but you just made my lunch breaks a fantastic part of my day. ))) !!!!
sir_earl said:
At some point I will make this more clear in the description, but to use the controller with the Droid x2, 3 and Bionic, you must enable 'Bypass IME' in preferences. As a bonus, this will also allow you to use a normal soft keyboard at the same time as the controller, as you will no longer need to switch the active IME.
Click to expand...
Click to collapse
I think it's clear enough in the description, I suspect the op "downloaded" the v0.1 apk that's floating around the net.
Earl, I have a question about syncing. Once I sync the controller with the phone using the PC app, will I need to go through the process each time I use the controller on the PS3 afterwards, or is it like a bluetooth headset that I can switch back and forth between the PS3 and the phone based on which one has bluetooth on for pairing when I turn the controller on?
Is there a certain way I have to map the buttons? I have the IME option checked and my dpad seems to be working, but none of my other buttons like start, A, B work and Im assuming their mapped wrong but they are set to BUTTON START, BUTTON A etc dont know what Im doing wrong here
** Nevermind I figured it out. They have to be set to the hardware key mappings in the emulator its working good now
That IME thing got it working thanks guys!
cvmaas said:
I think it's clear enough in the description, I suspect the op "downloaded" the v0.1 apk that's floating around the net.
Earl, I have a question about syncing. Once I sync the controller with the phone using the PC app, will I need to go through the process each time I use the controller on the PS3 afterwards, or is it like a bluetooth headset that I can switch back and forth between the PS3 and the phone based on which one has bluetooth on for pairing when I turn the controller on?
Click to expand...
Click to collapse
The controller can only store a single master address, and will only ever talk to that master, so unfortunately you will need to use the PC tool to change the address back to the phone before use. In theory it should be possible to change your phones bluetooth address to match your PS3 using bdaddr or some other method, but I haven't done any research into that.
Had the same problem with my Droid Inc. Though this time the wiimote app will poll buttons when they are pressed, its just that the emulator apps seem to not notice it at all. Does the droid 3 have this same problem as the Dinc? If so is the only way to fix it is through changing the kernel which we can't do yet?
Thanks alot
I can't remember if I've tried this on the D3 yet. It worked fine on the OG and OK on the Xoom.
It can be very finicky at times. I assume you're using Wii Controller IME?
Make sure the emulator is set to 'Use input method'. In nesoid, for example, you have to goto Settings > Other settings > Use input method.
Yes I understand that, I have used wiimote apps before on my Xoom and other phones. I know HTC Sense phones have this problem because of the bluetooth stack. I just find it odd that I see the buttons polling but no matter that settings I use in the emulator, it never works. I mirror the settings from my Xoom and other phones with no luck.
Try Nes.emu (from market)
Some emulators like Nes.emu have built in support, I highly recommend giving Nes.emu a try. The same developer also has emulators for other systems (snes, genesis, etc...).
I have an HP bluetooth keyboard (made for some HP tablet, but works fine for typing) that I use on my KFHD7. I know that when my kindle was running 7.2.3 the extra buttons on the top of the keyboard designed to work with the HP tablet worked (like volume up, volume down, lock screen, ect.) but that recently they have stopped working. Some other keyboard shortcuts have also stopped working (like alt+tab to switch between recent apps). I attributed this change to the update of my KFHD7 to 7.3.0, but I'd like for someone else to confirm this.
In short, I would like to know if anyone else uses a bluetooth keyboard and upon updating to 7.3.0 if the behavior of the keyboard changed. I would also like to know if there is any way for me to get the old features back (alt+tab is really the one I miss most).
Also, for developers running 7.2.3, I was thinking that since the recent apps button on the KFHD7 was turned into a favorites button instead, if by using some sort of alt+tab function it could enable some sort of recent apps button? I really have no idea on this as I don't have any sort of coding experience, and I have limited knowledge about android systems. But I thought I might as well make a suggestion.
Thanks in advance!
Note: I'm still working on this, and this guide may miss a few things/be incomplete. I'll subscribe to this thread but if I don't reply you can PM me.
I had a Droid 3 but the ribbon cable developed a nice hearty tear. I haven't taken the money to buy a new one to put it together, and since my wife's Droid 3 has a busted glass screen but everything else works, she'll probably assemble it herself. So that left me phoneless. To save a buck, I got a cheap wireless plan locally ($19.99 unlimited talk/text), but I am on a dumb phone. I really only wanted a MP3 player and the ability to surf the web casually without getting on the computer.
The biggest problem is that Android is too dependent on touch interface, which I didn't have due to the infamous bad digitizer ghost issues. So that left me a little irritated, since it was sitting in my drawer and collecting dust. So after much research, tweaking, and playing, here is what I got so far:
1) Download your ROM of your choice. I wanted Jellybean since we had it and I think ICS/JB look prettier than GB anyway. So I chose CM10.
2) The biggest problem will be the lack of touch input. This causes three problems: setting up the phone, using the back/home/menu/search buttons, and unlocking the screen. I got past this by first using a data cable and connecting via ADB. I can't find the app since I'm at work but it's on Google Groups and a bit of searching should help you find it. If you scroll down a bit someone updated it for JB. You just need Java and ADB.
3) The next problem was the keys. In /system/usr/keylayout/sholes-keypad.kl edit this file (adb pull /system/usr/keylayout/sholes-keypad.kl is your friend then adb push). Remap key 100 (right alt) to home wake_dropped, key 54 (right shift) to back wake_dropped, and 139 to menu wake_dropped (menu key don't work on JB on keyboard until this).
4) Install v6 Supercharger (easy to find and plenty of guides so I'm not going to hash that out). In there is a section of Bulletproof apps. Download from the Play Store the app Argus Touch Blocker and add it to the Bulletproof list. Then Enable the service and block the screen on any shaking.
5) The only browser that seems to work (have to use remote control over ADB to accept EULA) is Opera Classic.
If anyone else has suggestions/tips I'm open as well.
Original release thread here over at reddit.
Hey guys. This is a project I've been working on for a while.
EMPIO is an application that allows you to fully remap your controller. At the moment, it supports Ouya and wired/wireless PS3 controllers (tested with sixaxis).
The biggest feature of this app is that it allows you to map your controller to TOUCH SCREEN presses - even though there's no touch screen on the console!
Upon launch, you're greeted with a setup activity that gives you some information about the app. The main screen is a 2x3 grid of the applications you have installed. Pressing U brings up the options menu. Pressing Y brings up a basic file browser to install an apk.
Upon selecting an app to run, it checks your license to determine features and also checks if your console is rooted. If it's not rooted, it asks you to return after rooting it. Then it runs the background service.
I might be able to have it root itself in the future but I'd rather not.
The service gets exclusive control over your controller and loads the map file on the internal storage. Once the map is loaded, it interprets whatever your controller is doing and maps it to whatever you specified.
* Current supported controllers:
1. Ouya
2. PS3 Sixaxis wired/wireless
* Future planned controller support:
1. 360
2. wiimote
3. custom
* Features:
1. Map controller to various things
2. Add cycles - a grid of points you can cycle through
3. Multiple sets - set of mappings, includes cycles and button maps
4. Assign a map to be called when pressing a cycle point
5. Assign a map to be called when selecting/cycling to a point
6. Map analog stick to on screen analog - choose center position, radius, and deadzone. Analog stick moves around the center position, up to the radius and stops when the deadzone is reached
7. Set a variable and then retrieve it later
* Current map types:
1. Button/key
2. Touch
3. Callback
* Future planned map types:
1. drag
2. gesture
3. Macro (touch & button)
The free version will allow only key/touch mappings. ie: map buttons to other buttons or touch screen presses.
The paid version will have an on screen map creation tool, will root the console, and allow all other map types as well as any functions (cycle, cycle callbacks, etc)
Full documentation will be available at reddit/r/empio as I have time to add it.
This app is **BETA** as it is not anywhere near "completion".
**note** this requires you to create the mapping file on your computer first. The on screen mapping tool is not setup yet, however it will be one of the next features.
The paid version of the app is $4.99. I'm a student and it's a ton of work doing this on my own, so even if you don't need the pro version I appreciate donations.
If you have any questions, feel free to post them.
EMPIO Subreddit with information: http://reddit.com/r/empio
APK File: - Temporarily removed due to license bug - IF YOU'RE USING IT, DON'T PAY FOR IT. If you do, I'll refund you - the license does not save correctly.
**PLEASE POST ANY BUGS THAT YOU EXPERIENCE**
Thanks for checking it out! I'll have pictures and a video up soon.
cool
thanks buddy! i cant wait to get home to try this!
jaedolla said:
thanks buddy! i cant wait to get home to try this!
Click to expand...
Click to collapse
Let me know what you think! If you have any problems let me know and I'll help you set it up. Documentation is a little lacking since I've been busy with school, but I'll help anyone out with making map files until I have more time to write stuff up
pspkicks316 said:
Let me know what you think! If you have any problems let me know and I'll help you set it up. Documentation is a little lacking since I've been busy with school, but I'll help anyone out with making map files until I have more time to write stuff up
Click to expand...
Click to collapse
Thanks for this app dude...this is awesome, i currently installed the app on my OUYA then when i start the game app it says "Creating controller mapper" then "Staring controller mapper" after that it says SUPERUSER GRANTED TO EMPIO. when the game starts in the bottom left corner it says CURRENT SET: OUYA but it wont do anything...I was wondering if you can please help me map some buttons or give me some instructions on how to use this tool?
Can it allow to use PS3 controllers on games that only use the OUYA controller?
Some apps have this annoying feature that checks for updates automatically and then won't let you use them even though you paid for them until you update. Is this app like that or will it ever be?
This app don't have many features as it is which is a bummer, but it's a good start :good:. I feel like i have to buy the paid version of this app to see what it can offer but not being able to get the free version working or mapped and haven't seen it working yet and the instruction are not very clear is what keeps me from buying the full paid version...
Pkmns said:
Can it allow to use PS3 controllers on games that only use the OUYA controller?
Click to expand...
Click to collapse
Yes, it will by default map the PS3 controller buttons to the standard Ouya ones, allowing it to be used in ANY app or game. However, depending on how the app/game detects the buttons, some tweaking will be needed to get it fully working.
Asadullah said:
Some apps have this annoying feature that checks for updates automatically and then won't let you use them even though you paid for them until you update. Is this app like that or will it ever be?
Click to expand...
Click to collapse
As of right now, since it's not on any market, it can't do this. With that said, I find this annoying too and won't be adding that.
cronikman84 said:
This app don't have many features as it is which is a bummer, but it's a good start :good:. I feel like i have to buy the paid version of this app to see what it can offer but not being able to get the free version working or mapped and haven't seen it working yet and the instruction are not very clear is what keeps me from buying the full paid version...
Click to expand...
Click to collapse
Actually, there's a ton of features. The mapping system is very extensive as it is. The free version will let you play any basic touch app, but if you need anything more advanced then the pro version is needed. Free is just touch/key mappings.
From what you said, the app is working fine. Once you start it, everything should work the same; all buttons work normally. That's because it's using the default Ouya map. You have to create a map for each specific game. I'm currently working on an on-screen mapping utility, but for now you have to do it manually.
To do this, plug your Ouya into your computer and find your app/game's mapping file in /sdcard/Ouya Mappings/package.name.ini
That .ini file is the map for the game. Each game/app has it's own, based on the package name.
If this file isn't there, enable map file auto-create in the settings.
At first, the file will be blank. You can follow the information HERE to start working on your map.
To get your x/y coordinates, you can take screenshots and then use mspaint to get the coordinates of where you want to touch the screen (if you're doing touch mappings). In mspaint, the bottom left corner has the x,y coordinates of the mouse on the picture. Just put those values into your map file when needed.
Let me know what game you're trying to play and I can help you out a bit more.
pspkicks316 said:
Actually, there's a ton of features. The mapping system is very extensive as it is. The free version will let you play any basic touch app, but if you need anything more advanced then the pro version is needed. Free is just touch/key mappings.
From what you said, the app is working fine. Once you start it, everything should work the same; all buttons work normally. That's because it's using the default Ouya map. You have to create a map for each specific game. I'm currently working on an on-screen mapping utility, but for now you have to do it manually.
To do this, plug your Ouya into your computer and find your app/game's mapping file in /sdcard/Ouya Mappings/package.name.ini
That .ini file is the map for the game. Each game/app has it's own, based on the package name.
If this file isn't there, enable map file auto-create in the settings.
At first, the file will be blank. You can follow the information HERE to start working on your map.
To get your x/y coordinates, you can take screenshots and then use mspaint to get the coordinates of where you want to touch the screen (if you're doing touch mappings). In mspaint, the bottom left corner has the x,y coordinates of the mouse on the picture. Just put those values into your map file when needed.
Let me know what game you're trying to play and I can help you out a bit more.
Click to expand...
Click to collapse
i'm trying to play Gangstar Vegas from gameloft, i also want to buy the full version of the app and give it a try, where can i get it from?