What steps will reproduce the problem? 1.Install BTstack from Cydia, respring. 2.Choose BTstack bluetooth stack in Settings. 3.Pair PS3 Dualshock 3 new, fully charged controlled with the device using SixaxisPairTool. 4.Press the PS button and let the controller connect. It starts the connection, the Bluetooth status bar indicator lights up, the leds on the controller keep flashing for about 10-15 seconds, but then it disconnects (BT status bar indicator grays out, controller stop flashing). 5. Exactly the same behavior using "Connector For All" - after opening a supported game (tried several), initiates the connection, says that it's connected, then leds are flashing and controls don't work for additional 10-15 seconds, then notifies that the controller has disconnected. 6.Restart the iPad/iPhone device, or restart the BTstack daemon manually (using launchctl). The Bluetooth stack automatically drops to "none", need to change manually again. This happens every restart.
What is the expected output? What do you see instead? 1. The controller should not disconnect. 2. Controls should work while in connected state. 3. Bluetooth stack configuration is expected to persist over daemon restarts.
What version of the product are you using? On what operating system? BTstack 0.8-3 on iOS 7.0.4, tried with iPad 3 and iPhone 4S - exactly the same behavior on both.
Please attach a package log, as described here: http://btstack.uservoice.com/knowledgebase/articles/69548-how-to-get- btstack-communication-log
and provide any additional information below.
Thanks a lot in advance!
- BTstack.log 9.75KB
- hci_dump.pklg 4.08KB
Comment #1
Posted on Feb 4, 2014 by Happy BearIn step 5 above, I meant "Controllers for All" tweak by cjori.
Comment #2
Posted on Feb 4, 2014 by Happy BearJust to verify that the controller is OK, tested it with MotioninJoy on Windows desktop, all works fine. So the problem seems somewhere between BTstack and "Controller for All"...
Comment #3
Posted on Feb 4, 2014 by Swift OxPlease have the developer of Controller for All look at this.
Comment #4
Posted on Feb 4, 2014 by Happy BearComment deleted
Comment #5
Posted on Feb 4, 2014 by Happy Bear@Matthias: Asked him, but please note that exactly the same happens with RetroArch when "Controllers for All" is not there. Recently I've also reinstalled the iPad as a new clean device in order to eliminate any potential conflicts, but still doesn't work.
Do the log and the sniffer outputs look normal from BTstack's side? Is there anything else I should test to troubleshoot the problem? Thanks a lot in advance!
Comment #6
Posted on Feb 5, 2014 by Swift OxPlease try Blutrol and Retroarch on iOS 6 with your controller. There are no significant changes from iOS 6 to iOS 7 to make BTstack behave differently. In the log, I can see the ds3 close the connection after the current app tries to configure it.
Comment #7
Posted on Feb 5, 2014 by Happy BearOK, tried the same controller on other iPhone4S/iOS 6.1 and latest Blutrol, and then Retroarch - the behavior is exactly the same everywhere: connects, LEDs flashing for 10-15 seconds, then disconnects. Logs for all attempts attached.
Then out of curiosity, also tried on Android phone with Sixaxis Controller, and it worked flawlessly, like it did with MotioninJoy yesterday.
So you were right that there is no difference between iOS 6 and 7, but it's likely to be related to BTstack.
Please assist.
- BTstack.log 16.41KB
- hci_dump.pklg 8.2KB
Comment #8
Posted on Feb 6, 2014 by Happy BearSeems that I've found the problem - the controller appeared to be one of these visually-identical knock-offs... When I connect it to Sixaxis @Android, they detect that it's fake and apply some workarounds to make it work. So no wonder that without these hacks it doesn't work.
Comment #9
Posted on Apr 2, 2014 by Quick OxHi Vadim, have you managed to get the sixaxis to work? I have the same issue. Looks like not worthwhile to buy cheap stuff, better to stick with original Sony controller.
Comment #10
Posted on Apr 2, 2014 by Happy BearHi, Yes, sixaxis works. No special configuration is needed - it automatically detects the device as fake, and adjusts itself accordingly. And I fully agree with you re originals - bought Sony PS4 ctrl recently, it is way more handy than any PS3, and works great via Ori's "Controllers for All"!
Comment #11
Posted on Jun 3, 2014 by Quick LionHi, Vadim. I read the topic, don't really get it when you answered nico's question: where you able to get it working on iOS? I believe you have it working on Android, but how about iOS?
Comment #12
Posted on Nov 17, 2014 by Massive BearI have the same problems. I bought a PS3 Controller and installed Controller for all. But I can't connect the controller and ipad
I press the PS button and let the controller connect. It starts the connection, the Bluetooth status bar indicator lights up, the leds on the controller keep flashing for about 10-15 seconds, but then it disconnects (BT status bar indicator grays out, controller stop flashing).
Comment #13
Posted on Nov 17, 2014 by Happy Bear@Mugi: it won't work, see comment #8 above. Just sold the knock-off and got an original PS4 controller instead, all works perfectly since then.
Comment #14
Posted on Nov 17, 2014 by Happy Bear@eikment: It might be that you have the same cause. Look at youtube - there are video tutorials how to identify whether your controller is fake, and if so - don't bother. Either use it with Android, or get an original one instead.
Comment #15
Posted on Nov 18, 2014 by Massive Bear@Vadim.Ba...@gmail.com
Are you shure that this is the only possibility? I bought the controller in a big electronic shop and payed a lot of money.
For me it is hard to believe that they sold me a fake controller.
Comment #16
Posted on Nov 18, 2014 by Happy Bear@eikment: it can be anything. Read the log files (BTstack.log and hci_dump.pklg), you might find some useful information there. Would still recommend checking whether the controller is original - open it and look inside, just in case. Also, try with other iPad / iPhone, and with some Android device via sixaxis.
Status: WontFix
Labels:
Type-Defect
Priority-Medium