..:: PCSX2 Forums ::..

Could someone send a set of logs for any controller working over WiFi so I can see where its different for my fake? Thanks

Hello!  I'm having a bluetooth issue.  First off, the wrapper works great, and thank you so much for providing ongoing support.

Here's my issue.  All 4 of my PS3 controllers work great when attached with USB, but as soon as I disconnect them, they stop.  The lights on the controllers flash for 10-20 seconds as if trying to link via bluetooth but unable to.  I've been banging my head against this for a solid 12 hours and haven't come up with a solution, so I'm hoping a fresh pair of eyes will help.  First I tried Scarlet Crush's latest version, then I tried applying your update, and they both do the same thing.

My situation is a bit unique as I am using a bluetooth attachment provided with my motherboard.... not a USB dongle or a laptop bluetooth receiver.  The hardware ID is USB\VID_8087&PID_07DC, which is not in the supported list - only 07DA is.  I used the Zadig utility as instructed and it SEEMS to be working.  SCP Monitor shows:

Host Address : E8:2A:EA:02:FB:47

I double checked and this is the MAC of my bluetooth adapter.  I poked around in the ScpService.log file and I can clearly see where I've connected via USB and disconnected (Notify [Arrival] and Notify [Removal] are pretty straightforward).  After each disconnect there's a bunch of stuff that I don't understand, but it certainly seems to be telling me that the bluetooth connection was successful.... nine times.  Here is the log:

I'm using Win7 x64.  There's not a whole lot of information about my bluetooth adapter; it came with my motherboard which is MSI Z97 XPOWER AC.  You can't even find the drivers to download from MSI's website, but it seems to be a generic intel adapter and as such requires that driver.  When installed properly (not using scp) it shows up as a "Microsoft Generic Bluetooth Adapter."
Some background you're probably not interested in explaining why I want bluetooth and why I don't want to buy a USB bluetooth dongle:

My wife and I are super excited about the upcoming Steam release of Tales of Zestiria.  We want to play together, but my desktop setup is not conducive to running two wired controllers.  It would work for me but not so much for her.  That's why I'm trying so hard to get the bluetooth to work.  Normally I would just go out and buy a bluetooth dongle, but we are currently living in Japan and I have no way of knowing what the hardware ID is to see if it's supported or not, so I don't want to waste the money.  Another reason that I don't want to take my chances with a bluetooth USB dongle is that Tales of Zestiria is coming out in less than a week (Tuesday) and I simply don't have the time to order one off of Amazon, wait 2 days for it to show up, test it, find that it doesn't work, order another one... etc.


Thanks for any help in advance.

(10-15-2015, 03:19 AM)theunbeliever Wrote: [ -> ]Some background you're probably not interested in explaining why I want bluetooth and why I don't want to buy a USB bluetooth dongle:

My wife and I are super excited about the upcoming Steam release of Tales of Zestiria.  We want to play together, but my desktop setup is not conducive to running two wired controllers.  It would work for me but not so much for her.  That's why I'm trying so hard to get the bluetooth to work.  Normally I would just go out and buy a bluetooth dongle, but we are currently living in Japan and I have no way of knowing what the hardware ID is to see if it's supported or not, so I don't want to waste the money.  Another reason that I don't want to take my chances with a bluetooth USB dongle is that Tales of Zestiria is coming out in less than a week (Tuesday) and I simply don't have the time to order one off of Amazon, wait 2 days for it to show up, test it, find that it doesn't work, order another one... etc.


Thanks for any help in advance.

Hi,

quick hint; just buy a Bluetooth 4.0 compatible dongle from a known brand in your location, if it's a genuine 4.0 specification I'm pretty sure it'll work.

(10-12-2015, 04:35 PM)Nefarius Wrote: [ -> ]Don't worry, my "GIVE ME YOUR MONEY!!^11" post from above had nothing to do with your previous posts, I just felt like I should at least post one hint

No need to apologize, I'm very glad someone's willing to dig deeper into the inner workings of the Bluetooth magic. I myself also had a lot to read and research since the takeover of the project, the more brains combine the faster we'll succeed I hope

Back to topic; yeah, I guess you're on the right track; the Role_Change command is missing from the faulty connection attempt. I guess since Scarlet.Crush mainly focused on stand-alone dongles and genuine controllers he might have hard-coded stuff that won't work under certain conditions. I sure can provide a build with said changes but wouldn't it be a lot faster if you'd compile it yourself?

EDIT: the genuine DS3 still connects after the code change; fake ones still having different troubles.

Hi Nefarius, I'm glad to announce that I've found a fix for the bluetooth issue when controller doesn't connect after reboot/sleep 

How could I share the changes with you, so you can test from your side and implement it in your releases if all is good?

The changes are just a few line modifications in btdongle.tasks.cs, some tweaking of the logic when the controller first requests for connection. Hopefully that won't break anything for people not having this issue

(10-15-2015, 11:15 AM)WkNaZA9 Wrote: [ -> ]Hi Nefarius, I'm glad to announce that I've found a fix for the bluetooth issue when controller doesn't connect after reboot/sleep 

How could I share the changes with you, so you can test from your side and implement it in your releases if all is good?

The changes are just a few line modifications in btdongle.tasks.cs, some tweaking of the logic when the controller first requests for connection. Hopefully that won't break anything for people not having this issue

Hi,

woha, that's great news! Well, do you happen to know how a "pull request" on Github works? That's be the easiest for me. If not; get WinMerge and create a patch:

Open up the original file and your modified one, go to Tools and Generate patch...



Then save the patch to a file:



The patch.diff contains your changes which I can review and import, just submit it here

(10-15-2015, 11:31 AM)Nefarius Wrote: [ -> ]Hi,

woha, that's great news! Well, do you happen to know how a "pull request" on Github works? That's be the easiest for me. If not; get WinMerge and create a patch:

Open up the original file and your modified one, go to Tools and Generate patch...



Then save the patch to a file:



The patch.diff contains your changes which I can review and import, just submit it here

Unfortunately I'm not familiar with the Github stuff, so I've created the .diff file instead.
Attached logs too, so you can see how well it works now even after reboot

(the controller takes a while to connect though, but in my tests I rebooted few times, powered off, sleep, etc and worked fine all the times \0/ ).

Let me know how it goes in your tests with different controllers, I'm interested to know if the patch will be applied in the main branch

PS: I've added few comments in the patch to make the changes/logic easier to understand. Also some lines from the original code that are not needed were commented too.

(10-15-2015, 10:22 AM)Nefarius Wrote: [ -> ]Hi,

quick hint; just buy a Bluetooth 4.0 compatible dongle from a known brand in your location, if it's a genuine 4.0 specification I'm pretty sure it'll work.

I live in an extremely rural area - the only electronics store that's less than an hour away doesn't have anything like this.  As for "known brands," I've never heard of プラネックス (PLANEX), バッファロー (iBUFFALO), アイ・オー・データ (I-O DATA), or LOHASIC - these are the first four brands that come up as results on Amazon.  Have you?

We are both too busy with work to be able to manage to go to Fukuoka City before Tuesday.  If you can't or are unwilling to help, that's fine, I was just hoping to get this working before release =) Thanks for the reply!

(10-15-2015, 12:51 PM)theunbeliever Wrote: [ -> ]I live in an extremely rural area - the only electronics store that's less than an hour away doesn't have anything like this.  As for "known brands," I've never heard of プラネックス (PLANEX), バッファロー (iBUFFALO), アイ・オー・データ (I-O DATA), or LOHASIC - these are the first four brands that come up as results on Amazon.  Have you?

We are both too busy with work to be able to manage to go to Fukuoka City before Tuesday.  If you can't or are unwilling to help, that's fine, I was just hoping to get this working before release =) Thanks for the reply!

You'll be interested to know that my bluetooth device is also USB\VID_8087&PID_07DC  (intel, integrated in laptop's motherboard)


Let's see if nefarius applies the patch I provided 2 posts above, that might solve the issue for you too (the symptoms from your logs above are exactly the same I was facing)
-Just be patient

(10-15-2015, 12:59 PM)WkNaZA9 Wrote: [ -> ]You'll be interested to know that my bluetooth device is also USB\VID_8087&PID_07DC  (intel, integrated in laptop's motherboard)


Let's see if nefarius applies the patch I provided 2 posts above, that might solve the issue for you too (the symptoms from your logs above are exactly the same I was facing)
-Just be patient

I hope so =) I hunted through the forums and it seemed like one other guy had the same problem as me back when scarlet crush was still posting, but he never got an answer, so I can't be the only one having this issue with this generic intel bluetooth adapter.

(10-15-2015, 03:52 PM)theunbeliever Wrote: [ -> ]I hope so =)  I hunted through the forums and it seemed like one other guy had the same problem as me back when scarlet crush was still posting, but he never got an answer, so I can't be the only one having this issue with this generic intel bluetooth adapter.

It should work as long as it's bluetooth 2.0 I think, you'll just need to add 1 line to scpcontrol.ini if the device isnt supported initially. My bluetooth device for example is a Broadcomm one built into my Asrock motherboard and it wasnt supported by this SCP server. 
All I had to do was Copy the bluetooth adaptor hardware ID, go to SCPControl.ini and under [Bluetooth Dongles] you will see a long list of 'HardwareID = xxxx...'. Those are IDs for other bluetooth devices. All you have to do is add your ID to this list. Just go to the bottom of your list add a line with HardwareID = "Your ID". So for me it was " HardwareId = USB\VID_13D3&PID_3404 " (without ""). Dont touch device GUID. Then save the file. Go to SCPDriverInstall.ini and install it again. It should replace your bluetooth driver with the one made to work with SCP Server and bluetooth should now work. Dont use Zadig.exe because this does the same kind of thing and zadig was made for scarlet crush's SCP Server. This solution was provided by Nefarious and worked for me. I think it should be included in the FAQ i think. So it whould work for for any bluetooth adaptor with 2.0 and above.  If it still doesnt work for you, try this method with the new adaptor you plan on getting, it has to work. Also if SCPService is running in the background the bluetooth will connect and make a 'pop' sound without even needing SCPServer.exe running

Hopefully WkNaaZA9's patch for bluetooth on reboot works because I have that issue