yashsingh1/xdaforums huggingface dataset:
[Android General] PMDColeslaw:
Is there a tutorial somewhere on how to make the touch mapping work for new games? I just bought the Dark Knight Rises game and would love to use my controller with it. If no tutorial then maybe a master list of created touch profiles people could share would be awesome.
[Android General] primoitt:
Hi

Is Sixaxis app working on Galaxy Y devices?

Any Y's owner can answer me?

Thx in advance:good:
[Android General] andrasandhi:
hmm, buy original one.

i have this issue before, buying a sixaxis (not original) then try to pair on my xperia, but dont work, LEDs still blinking.

for sure, i try on PS3 from my friend, and really, it dont work. so i exchange to original one.

gamepad on ur phone/tablet?

see HEREhttp://xdaforums.com/showthread.php?t=1890121
[Android General] ArcticFish:
U connected them by usb first right and then paired controller?

Sent from my SGH-T989 with Darthstalker
[Android General] ma3almakshof:
thanks

thanks

i will try orignal ps3 control
[Android General] Zardox:
Hello guys!

Have been checking out fpse and i think is ****ing great!! ;P

But i got a problem with my sixaxis controlls. iv got the sixaxis program, have reprogram the bluethoot address on the hand controlls

the program finds the both controlls..

But when im trying to play with two hand controlls it don't work..

Trying tekken 3 on my htc one x. But it only read one hand controll. And i don't know why.. The sixaxis app says it see two connected.

Googling my ****ing ass off now for the last 2 days. Been on more then 40 google sites search .

Sorry for my crappy english, but hope you understand.. I really want to get this working. Want to play tekken 3 with my friend on the TV ;)
[Android General] andrasandhi:
woaahh, R u really try that with 2 pads?

i only have 1 n never try connected 2 pads.

great if thats working.

hmm, i think its bcoz from sixaxis apk's bug, maybe.
[Android General] Zardox:
Yea, its only the ps1 that i can't have two users on, but if i play n64 i just connect the two pads and connect my phone to the tv and after that you can play :) Fun as hell.

Htc one x as a n64,gameboy , sega, and so on =)
[Android General] andrasandhi:
oh, its just ps1 emu.

great! so i want to told my friend to have sixaxis pad, then i wanna play Sega Sonic 3 on my phone with him (wanna playing with Tail for helping Sonic to fly lol)
[Android General] zenisnotchosen:
I'm hoping someone can shed some light on my problem. I know aftermarket controllers aren't supposed to work, and the typical outcome is that it does not pair and all 4 LEDs continue to flash. My problem is my aftermarket controller does pair, LED 1 goes solid, and it indicates the controller is connected. However when I try to use it no button presses register. I even tried an official Sony controller to make sure it isn't just a problem with the aftermarket controller and the exact same thing happens. The only thing I can see that might be causing some or all of the problem is when I use the Sixaxis Tool or MotionJoy to change the MAC address of the controller if I refresh a few times I see the MAC address reverts back to its original value, both with the Sony controller and the aftermarket. I've also tried pairing using USB directly to my tablet using Sixaxis Controller and the same thing happens. It does pair but no button presses register. I have tried using touch profiles, regular keyboard input, gamepad input, mouse emulation, and every option I can adjust. I have tried it with every emulator, game and app I can think of but it always has the same outcome. Change MAC address, pair controller, LED 1 goes solid, Sixaxis indicates controller connected, no button presses register, Sixaxis indicates controller disconnected if I plug USB back in causing it to disconnect. Anyone have any ideas, suggestions, or similar experiences?
[Android General] xxKamikazexx:
Can anybody confirm if this works on cm10?
[Android General] Spikelangelo:
Confirmed. CM10 on my Acer a500
[Android General] lukassky:
Hi all. I've been testing this apk under Galaxy Nexus GSM 4.1.2 and it really was a big mess! Once the Compatibility Checker was running, I press START. Then my GNex rebooted and it falled into a loop.

Looking at some logs it was impossible to find out what's going on. Then, under shell, I uninstalled it (the app) but was the same issue... loopin.

At the end i had to wipe data/cache and install all my apps and so.

Take care with this app..
[Android General] zenisnotchosen:
You are the only person I've known to have this problem. I've read all other forum posts available about it and no one else has posted this problem. Maybe it was unrelated to Sixaxis Controller.

Sent from my Streak 7 using witchcraft
[Android General] LiudvikasLTU:
Got the same problem. I have huawei ascend p1, exact same specs as Gnex GSM.
[Android General] LiudvikasLTU:
Can anyone help? Common...
[Android General] DeadlyBrink:
Xperia S

Works fine with Xperia S (2011)

CM 10 nozomi
[Android General] LiudvikasLTU:
There is some hardware issues i guess...

Maybe bluetooth 3.0?
[Android General] Okoplota_Sigamota:
What am I missing here??

It just got stucked here..im using latest JB fox hound rom rooted.

Please help.
[Android General] SaschaHa:
@Okoplota_Sigamota:

Same problem here. Sixaxis couldn't start the driver. It stays in Starting driver...

1. Yes I've root and Sixaxis has the permission

2. BusyBox is installed

3. On SGS2 (ICS) it worked fine, on JB (PA 2.52) it does only for one time, then same problem

4. The last line at the bottom "Click start to show Local Bluetooth Adress"... there has to be "Local Bluetooth Adress ....", but it doesn't

-> Samsung Galaxy Note 2, JB 4.1.1
[Android General] lukeyboymac:
So I'm trying to get this working with mame4droid. I can use the controller but after about 20 seconds it gets stuck in a direction - i.e. the character starts walking left or ducking. I've tried 2 different official controllers and still the same. Basically prevents playing the games. I've tried to reinstall both mame4droid and sixaxis. Has anyone had this before or have an idea how to fix it? Thanks
[Android General] zenisnotchosen:
I've tried using an official controller and the same thing happens. Pairs fine and LED 1 is solid but no button presses do anything. Using Dell Streak 7. The only thing I can think of that could be the issue is that right after changing the MAC address of the controller with the Sixaxis Pair Tool or MotionJoy even though it pairs fine if I refresh the MAC address before unplugging the USB it reverts back to the original default. Again this is both with original Sixaxis and an aftermarket Sixaxis. Anyone else have any similar experiences?

Sent from my Streak 7 using witchcraft
[Android General] lambstone:
Can I use touch profiles with a wired controller?

The android device that I want to use it with does not have bluetooth but Android does recognise the sixaxis controller.
[Android General] Spikelangelo:
Yes you can use touch profiles with a wired controller.
[Android General] lambstone:
How does that work? When I plug in my controller it just detects as an input device. I can use the controller with games such as shadowgun that natively support gamepad controls. However when I tried to play a game with my own touch profile it doesn't work.
[Android General] Spikelangelo:
Did you remember to actually select the touch profile from the drop down box on the sixaxis app?
[Android General] lambstone:
Yeah I did. Could it be that touch profiles do not work unless you're connected to the sixaxis app via a wireless controller?

Like I said. I am using a wired controller.
[Android General] Spikelangelo:
I don't see why wired or not would make a difference. I'll try mine wired tomorrow when I get home and let you know if mine work.
[Android General] lambstone:
afaik, the touchprofiles are enabled when you click "start" in sixaxis. Since the device that i use does not have bluetooth, "start" does not do anything. hence i don't think the touchprofiles would be enabled even though it is selected.
[Android General] shaunyx:
is there a way that a fake ps3 controller can work with this sixaxis controller app. using other application(usb/bt joystick center 6, and ps3 pairing tool) worked with my controller but with Wire connected from ps3 cont to my usb otg. I want it to use wirelessly
[Android General] Spikelangelo:
Ok I played around with touch profiles and wired vs wireless. You are right, the touch profiles only seem to work when using bluetooth. I also tried using it wired and also starting the service. The service starts but doesn't connect to the controller because it's wired. I can still use the controller a wired but the touch profiles still do not work. I would have thought it would work regardless of how it connected. Guess not.
[Android General] zenisnotchosen:
You are correct, touch profiles only affect Bluetooth controllers connected and paired through the app.

Sent from my Streak 7 using witchcraft
[Android General] wajih.boukaram:
Gasia gamepad

Hello,

I unwittingly bought an unofficial ps3 gamepad by gasia (that's what dmesg output tells me), and it doesn't work with the sixaxis app.

I get the Client 1 disconnected message after a while when trying to pair.

Is there any way we can possibly get it to work using information from this patch here?

https://aur.archlinux.org/packages.php?ID=63437

I already have an official controller and that one works fine, so this is more of an adventure than a necessity.

I am an experienced C/C++ programmer and I'm more than willing to help with anything (either coding or testing or whatever).

Wouldn't it be nice to be able to start supporting unofficial gamepads?

Sorry if this has come up before!
[Android General] zenisnotchosen:
It has come up many times before, including from me. Unfortunately so far there is no support for unofficial or aftermarket controllers on Android. You can pair them on a PC and use them though.

I have an unofficial controller as well, but the problem I have is that it pairs fine using this on my Streak 7, LED 1 goes solid, says Client 1 Connected, but no button presses register from the controller, and no other functions of the app do anything. Then if I turn off the controller it says Client 1 Disconnected.

Sent from my Streak 7 using witchcraft
[Android General] wajih.boukaram:
Hi,

I actually meant if trying to use that patch has come up before. I saw that several people requested unofficial support before, but it's obvious nothing will come of just asking for support if the dev has no help in terms of testing or even coding since he doesn't have that unofficial controller. I'm offering that help so that the app can maybe start supporting unofficial controllers (which would be nice - the controller I bought was much cheaper than the official one and works fine on my ps3 but not on the app).
[Android General] zenisnotchosen:
Oh, gotcha. Sorry I misunderstood. No I've not read anywhere about someone trying that patch, but I don't think it's a matter of testing or having the exact controller, it seems to be a universal problem with all unofficial controllers. With mine I think it's a MAC address problem. When I change the MAC address if I refresh it changes back on it's own, whether I use the SixAxis Pair Tool or MotionJoy. My controller was much cheaper as well. It was only $13 new on Ebay. I also have the exact same problem with an official controller. I tried using my nephew's official controller and it did the exact same thing. Pairs, says Client 1 connected, LED 1 on controller goes solid, but no button presses register in the SixAxis app, not do any functions like touch profiles or mouse function work. I can't find anyone else that has had the same problem as me though.

Sent from my Streak 7 using witchcraft
[Android General] sir_earl:
I have tried many things to get third party controllers working, including the hack shown in that patch. Unfortunately nothing has worked to date. This weekend I've been rewriting the bluetooth drivers for Android 4.2 at the very lowest level of the stack (HCI), and have just had some signs of success with one of my third party controllers (it's not a Gasia as far as I'm aware, but I think it's probably the same issue as the Gasia). The controller starts reporting, but then goes flakey and disconnects after a few seconds, but it's a promising sign. With any luck I'll be able to figure out why it's doing that and potentially start supporting at least some third party controllers. What that means, assuming I have success, is that from Android 4.2 I will be able to support such controllers. It might also be possible to rewrite the pre-4.2 drivers to work with third party controllers as well, but it will take quite some time, so it will come much later, if at all.
[Android General] wajih.boukaram:
Wow that sounds like great news! If there's anything I can do to help, testing debugging whatever, please let me know.

I'll be glad to help :)
[Android General] sir_earl:
Update: Turns out the controller was actually almost flat. After a charge it seems very solid! I just need a clean way of determining whether the hack should be used for fake controllers - the fake controller I have doesn't seem to have any way of telling it apart from originals, other than it simply not working with the normal connection method. I assume there's something obvious I'm missing, as it's obviously fine with a PS3.

Aside from that, I'm getting fairly close to finishing work on the update. I've basically re-written the whole driver to accommodate the new Bluetooth method and existing methods concurrently, so there's a fair amount of testing to do, but all going well I should be able to release mid-week.
[Android General] wajih.boukaram:
Sounds like great news!

What does dmesg report your fake controller as? Same as the official one?

If you'd like me to do tests with mine, I'd be glad to oblige!
[Android General] sir_earl:
Turns out it is actually a Gasia gamepad (so you're in luck!). I'll see if my other fake is also a Gasia when I get home. Anyway, I have a solution that works with both original and Gasia now, so all that remains is to finish work on the reintegration of the legacy bluetooth driver.
[Android General] zenisnotchosen:
What would cause my fake, and an official for that matter, controller to pair fine but not register any button presses or be able to utilize any features like mouse and touch emulation?

Sent from my Streak 7 using witchcraft

---------- Post added at 07:01 AM ---------- Previous post was at 06:58 AM ----------

Also great news about the update. Thanks a bunch for your hard work.

Sent from my Streak 7 using witchcraft
[Android General] sir_earl:
Not sure, but are you sure the official controller is actually genuine? Are you able to post the dmesg output given when you connect it via USB? I'll probably post a test version here soon, and it would be interesting to see if it fixes your issue.
[Android General] sir_earl:
Just finished rewriting the drivers for pre-4.2 versions of Android to support Gasia gamepads, so we should see better fake controller support across the board. I have to say though, the analog sticks on the Gasia handle very poorly compared with the original - it's almost night and day. Hopefully some of the newer ones aren't so bad though!

As an added bonus to this rewrite, I've solved the somewhat jerky movement of the analog touches and mouse by moving the touch emulation code to a separate thread - turns out relying on the timing of the controllers reports was a bad idea. Looking around in FPS games is now buttery smooth (as if that word hasn't already been flogged to death, but I promise the difference is very noticeable and not just a placebo!).
[Android General] zenisnotchosen:
Positive, it came with my nephew's PS3. I will try to post the dmesg for you as soon as I get a chance, and when I can get ahold of his controller again to post from that as well. I've not read any other posts anywhere on the Web of someone else having the same problem as me, with official or fake controller. I'm also the only person I've found to be able to successfully pair a fake controller and have LED 1 go solid, the app say Controller 1 Connected, and say Controller 1 Disconnected when I turn off the controller; and again the same thing happens with the genuine controller. I'd be happy to help out any way I can and test anything I can for you and find out whatever I can, just let me know.

Sent from my Streak 7 using witchcraft
[Android General] sir_earl:
Hmmmm... Well I've definitely heard from users that have successfully used the app with the Streak 7, but I have no idea what firmware versions they were running. Can you try connecting the controllers in the compatibility checker, as it will dump the button presses out as text so we can see if it's definitely the controllers / bluetooth that is at fault...
[Android General] zenisnotchosen:
it didn't register button presses either, but I will try it again later tonight. I will also try it again on my Thunderbolt, and if I have time my original Droid. I will have to wait to try the official controller til I have a chance to get it from my nephew.

Sent from my Streak 7 using witchcraft
[Android General] Trunkam:
Sir earl

I just want to say that you make my day with this app.. and I really cannot understand how I missed this till last week... but anyway..

I now have 2 pad: one Sony and one compatible and obviously your paid app.

And with my girl 2sgs3, tab an other.. yes I'm a bit geek :)

If you need testing for new driver count on me!

...Tapatalk'ed
[Android General] Act7:
ok

good
[Android General] gabster21:
Replying to an old post but I think I'm having the same issue. Everything works perfectly in GTA3 using gamepad mode on Note 2 except the right analog stick:

I can't use it to look around when I'm walking (nothing happens). When I stop and use the right analog stick it zooms in to first person view and looks around while my character is standing still.
[Android General] sdemius:
Hello all and sir_earl.

I have a fake (Gasia) gamepad. I tried to modify "sixaxis_driver" to make it work with my controller.

After many experiments, I found out that the driver hangs on function accept() of data socket. Control socket accept ok.

I tried my gamepad on linux with apps QtSixA and it works well.

sir_earl, may be you know what could be the problem?

ps. Sorry fo my English
[Android General] sir_earl:
I'm fairly sure that's the standard behaviour with a gamepad. Can anyone who has used a gamepad via USB with GTA 3 confirm? You may be able to fix this issue by creating a touch profile that maps the right analog stick to the right side of the screen though.
[Android General] sir_earl:
I wasn't able to do it with the source code, so I'd be impressed if you did manage to get it working with reverse engineering ;)

As I mentioned a little earlier, the next release in a couple of days will include support for Gasia gamepads (and hopefully others, but I'm not sure), because I have rewritten the drivers to use HCI directly rather than the bluez implementation of l2cap sockets.

I'll upload a test version of the compatibility checker within the next 24 hours so I can get some feedback before pushing out the main app.
[Android General] jaimeomg:
Hi there. I've been trying to get my sixaxis controller working on my Player Momo11 Bird tablet, but am getting the same error message every time. It says: "Controller not reporting. Fake or third party controller" (not exactly, but I hope you get the idea).

My controller is definitely not fake, so could the error have something to do with my generic Bluetooth dongle?

Really hope you can help me out as I love this on my Galaxy S3!
[Android General] sir_earl:
Yes it's very likely your bluetooth dongle that's causing the issue, especially if you've used the controller successfully with your Galaxy S3. To be honest, I'm surprised you were even able to get that far if you're using a dongle. It might be worth trying the new version that I'm releasing soon, as it's using a lower level protocol which might work better with your dongle. If you check back here over the next couple of days, I'll be posting a test version that you can try out.
[Android General] jaimeomg:
Excellent. Looking forward to trying it out.

Thanks!
[Android General] Larry94:
Greetings! Not sure if you remember me, but I helped you test the gamepad features and stuff about this time last year. Noticed the note on the play store page about compatibility issues with 4.2, and what do ya know!? I just bought a Nexus 7 yesterday. I'm on 4.2.1 and rooted, so shoot me a PM or visit the good ole IRC room if you'd like me to test anything. :)
[Android General] sdemius:
I think without l2cap sockets is better :)

We look forward to updates!
[Android General] sir_earl:
Ok - here is a test version of the compatibility checker that should work on Android 4.2 and should also support Gasia gamepads and possibly others. There is one known issue, which is that the fake controllers aren't disconnecting once the app is stopped. Until I fix this issue, the only way to turn the controller off is to update its master address with the pairing tool, or wait for its battery to die - obviously I'm working on a fix for this.

I'd appreciate as much feedback as possible across as many devices and types of fake and after market controllers as possible. Please report any issues you have along with the device, type of controller (dmesg output would be useful here) and firmware versions. It would also be useful to know whether the existing version of the app was working on your device.

Thanks for your help!
[Android General] jaimeomg:
I have also tried this version with my Ployer Momo11 Bird tablet. It isn't working at all for me unfortunately.

On "connection type 1", I am getting the error

"Could not load HCI library

Error: Failed to configure bluetooth"

Then, connection type 2 successfully configures bluetooth, but then sticks on "listening for controllers"

Hope this helps...

Thanks for your hard work!
[Android General] sdemius:
This version will use HCI directly only in 4.2?

Now I do not have the device with 4.2.
[Android General] tarbos00:
The exact same thing is happening to me on my Nexus 10 with JB 4.2.1.
[Android General] Trunkam:
i tried both on my SGS3 and samsung Tab2 7. with a non sony controller (i hate call it fake.. with ps3 is great..)

skipped connection 1 , i'm on 4.1.1 in both deveice and connected in connection 2 but...

it start vibrating till the end of the world... or his battery :)

so i changed BT mac address and it stopped.

i would like to help giving you some info on the controller but i do not know how to have dmsg from controller..

____________________________

wow.. i tried looking some info and even if i'm really white belt with that, i found this in Dmesg :)

New USB device strings: Mfr=1, Product=2, SerialNumber=0

<6>[20883.088940] c3 usb 2-1: Product: PS(R) Gamepad

<6>[20883.088968] c3 usb 2-1: Manufacturer: Gasia Co.,Ltd

<6>[20883.089001]

so yes is Gasia

hope this help

at least i've learned something
[Android General] sir_earl:
Thanks for that. I'm fairly sure I know why that's happening, so I'll upload another test version shortly.
[Android General] sir_earl:
So I assume you've tried to connect the controller after that, but nothing happens? Can you send me a logcat from just after attempting this?
[Android General] sir_earl:
No, I've actually rewritten the old driver to use HCI as well, so it should allow Gasia gamepads to connect to any device.
[Android General] sir_earl:
I was worried that might happen with some fakes. I did experience this once during my testing, but couldn't reproduce it, so hoped I'd fixed it. Does it happen every time you try to connect it? I'll upload another test version shortly that explicitly sends a vibrate off command after a little delay - maybe it just needs a kick in the backside.
[Android General] Trunkam:
Yes it happens every time

I’ll test :)

Inviato dal mio GT-P3110 con Tapatalk 2