I recently rooted my nexus to connect my control using Bluetooth. I had everything set up but then it wouldn't read L1 or L3. I know it works because when I have the control connected directly through cable without the sixaxis app, all buttons work. I tried looking for others with this problem but nothing. I even changed the room to Cyanogenmod and still same issue. What am I missing here?
Related
First off I apologize if this is in the wrong section. I hope some one on here can help me, though, with the problem I am having. I have my PS3 controller connected to my Note 2 via micro usb to mini usb connector(The one included with The Gameklip). I bought it mainly for emulators, but I am having a problem setting up anything with the right analog stick(RS)
FPse(playstation emulator)- In button mapping, I can set all the buttons, including the LS, but nothing registers with any direction on the RS. The R3 button works but that is all.
n64oid(Nintendo 64 emulator-also tried MegaN64 same result). Pretty much the same deal with FPse. I wanted to set the C-buttons to the right analog but no dice. Also another problem arose. Both D-pad and the Left analog share button mappings, and I can't seem to separate them. Anyway to fix this?
I tried Dead Trigger, GTA III, and Shadowgun and the right analog worked perfectly fine, so I know it's not the controller. I've looked in countless topics on here and other forums but most of the solutions involve the Six axis app which only works with the controller connected via bluetooth-root required, but not connected directly, like I have.
Has anyone been able to get their right analog stick working in any emulators? Thank you for your time, and thanks in advance.
Bump. I also wanted to mention that while the controller is plugged all 4 of the lights on the ps3 controller are lit up and slowly blinking. Not sure why it just doesnt have the "player 1" light on
Bump. This problem has been plaguing me on multiple devices.
Having same problem, just need to find a 64 em that allows custom control mapping maybe?
I tried to pair Ouya Controller with the phone , it hasn't worked.
Is there any way to get the Ouya Controller working on the phone to play games?
I mean , it is a bluetooth controller and the Ouya is based on Android ; it should not be so different :silly:
Thanks for help!
kevinrus123 said:
I tried to pair Ouya Controller with the phone , it hasn't worked.
Is there any way to get the Ouya Controller working on the phone to play games?
I mean , it is a bluetooth controller and the Ouya is based on Android ; it should not be so different :silly:
Thanks for help!
Click to expand...
Click to collapse
I paired it to my Samsung Discover - Android 4.0.4 today as a test. I bought the phone yesterday as a replacement for a broken phone. Upon pairing everything seems to work fine. However, the buttons are mapped differently than the Ouya. The mouse pad works perfectly although the click isn't very sensitive.
U: Back
A: Ok
L2: Menu
DPAD: Random? long press menu function (Brings up current running apps list in an unpredictable manor)
LS: Up, Down, Left, Right
The mapping suggest that when paired with normal android the keys are not putting out the same values as when the controller is paired with an Ouya.
nexuslite said:
I paired it to my Samsung Discover - Android 4.0.4 today as a test. I bought the phone yesterday as a replacement for a broken phone. Upon pairing everything seems to work fine. However, the buttons are mapped differently than the Ouya. The mouse pad works perfectly although the click isn't very sensitive.
U: Back
A: Ok
L2: Menu
DPAD: Random? long press menu function (Brings up current running apps list in an unpredictable manor)
LS: Up, Down, Left, Right
The mapping suggest that when paired with normal android the keys are not putting out the same values as when the controller is paired with an Ouya.
Click to expand...
Click to collapse
How did you paired the controller with your device? Is your device running a stock rom?
kevinrus123 said:
How did you paired the controller with your device? Is your device running a stock rom?
Click to expand...
Click to collapse
I went to bluetooth settings turned bluetooth on. While it was scanning I held down the Ouya button on the controller until the middle two lights were blinking and it paired. The phone is 100% stock, not rooted, no special controller drivers.
I believe I tried the same thing with my Samsung Stratosphere - Android 2.3.5 and it wouldn't work. Could be a combination of bluetooth protocols and android versions preventing it from pairing.
nexuslite said:
I went to bluetooth settings turned bluetooth on. While it was scanning I held down the Ouya button on the controller until the middle two lights were blinking and it paired. The phone is 100% stock, not rooted, no special controller drivers.
I believe I tried the same thing with my Samsung Stratosphere - Android 2.3.5 and it wouldn't work. Could be a combination of bluetooth protocols and android versions preventing it from pairing.
Click to expand...
Click to collapse
Thanks , will try it again to pair ASAP
This worked great for me. Thanks for the info on the holding down. I wasn't doing it long enough.
Hi, I've got a V500 which I installed infecteds cm11 build, I've since bought an OTG cable and tried to plug in my 360 controller, but I'm having some issues, I downloaded a gamepad testing app and it seems like the button presses are registering, but it's not registering the releases. Is anyone else having this issue or could it just be my cable/controller/tablet?
I just tried with a brand new wireless 360 controller with the adapter and with that controller only the right bumper sticks. This seems like a really strange issue. Is there anyway I can find out what's causing it?
Hi chris
Nice to see I'm not alone with this issue as well.
As far as I've tested, whenever we press the A,B,X,Y,R1,L1 buttons they don't register the releases.
I've tried many different things, such as changing the keyboard layout for the controllers, and even making my own. Not successful though.
Well, I've managed to "bypass" this problem by configuring the gamepad keys on the games (the ones that we can configure, of course) to don't use these buttons I listed.
I changed the A,B,X,Y to the right analog stick, and the R1,L1 buttons to the R2,L2 Triggers (which are analogic).
Then the controller may work flawlessly.
Nice to know I'm not the only one to experience this issue. Weirdly I can use my 360 controller to navigate around the android interface, but struggle to get it to do anything when it comes to using it in game.
has anyone managed to get this to work?
I've tried the same cable with the same pad on my nexus 5 and it works perfectly, so there is something wrong with the USB driver.
All I want to do is play ps1 games on my tablet.
Hi, guys
When I pair my 2 controllers to my ouya (with cm11 kitkat) both controlers show the light "1", and both really act as player number 1. Is there a way to set one of them as 2? I tried to unpair, turn off bluetooth, reboot but the controllers wont change a thing. I know the chupacabra update got some management and then I can change it easily, I wonder if there is something similar that I could try.
Thanks!
danielhalond said:
Hi, guys
When I pair my 2 controllers to my ouya (with cm11 kitkat) both controlers show the light "1", and both really act as player number 1. Is there a way to set one of them as 2? I tried to unpair, turn off bluetooth, reboot but the controllers wont change a thing. I know the chupacabra update got some management and then I can change it easily, I wonder if there is something similar that I could try.
Thanks!
Click to expand...
Click to collapse
I have the same issue - but using a Gamestick controller and an Ouya controller! Did you have any luck sorting it out?
(Running std Ouya firmware but rooted w/xposed)
So, I have a Daydream Controller I'm trying to pair with my Nexus 5X. On Android Nougat, it was as easy as launching the Daydream app, and hold the home button to pair the controller. However, with Android Oreo, it does not work! I went to Bluetooth settings to check whether the device detects the Daydream Controller, but it doesn't. However, on my laptop, the controller shows up as "Daydream Controller"... Furthermore, I tried with some more devices (bluetooth headset is detected, my laptop is detected). What do you think the issue is? Am I missing out something?
Edit: I want to add that I have Magisk installed (I am rooted).