Unfortunately, re-pairing my DS4s with the new driver (.160) doesn't work. The DS4s both get disconnected immediately, when trying to connect via BT:
Code:
2014-03-14 11:59:16.551 >> HCI_Connection_Request_EV [04]
2014-03-14 11:59:16.598 << HCI_Delete_Stored_Link_Key [0C12]
2014-03-14 11:59:16.613 << HCI_Remote_Name_Request [0419]
2014-03-14 11:59:16.613 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2014-03-14 11:59:16.613 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2014-03-14 11:59:16.645 >> HCI_Remote_Name_Request_Complete_EV [07]
2014-03-14 11:59:16.645 -- Remote Name : A4:15:66:63:9B:2B - Wireless Controller
2014-03-14 11:59:16.645 << HCI_Accept_Connection_Request [0409]
2014-03-14 11:59:16.645 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2014-03-14 11:59:16.816 >> HCI_Role_Change_EV [12]
2014-03-14 11:59:16.847 >> HCI_Connection_Complete_EV [03]
2014-03-14 11:59:16.863 >> HCI_Page_Scan_Repetition_Mode_Change_EV [20]
2014-03-14 11:59:16.879 >> HCI_Max_Slots_Change_EV [1B]
2014-03-14 11:59:16.925 >> L2CAP_Connection_Request [02] PSM [01]
2014-03-14 11:59:16.925 << L2CAP_Connection_Response [03]
2014-03-14 11:59:16.925 << L2CAP_Configuration_Request [04]
2014-03-14 11:59:16.925 >> L2CAP_Configuration_Request [04]
2014-03-14 11:59:16.925 << L2CAP_Configuration_Response [05]
2014-03-14 11:59:16.925 >> L2CAP_Configuration_Response [05]
2014-03-14 11:59:16.988 >> L2CAP_Disconnection_Request [06] Handle [0040]
2014-03-14 11:59:16.988 << L2CAP_Disconnection_Response [07]
2014-03-14 11:59:17.113 >> HCI_Link_Key_Request_EV [17]
2014-03-14 11:59:17.113 << HCI_Link_Key_Request_Reply [040B]
2014-03-14 11:59:17.113 << HCI_Set_Connection_Encryption [0413]
2014-03-14 11:59:17.113 >> HCI_Command_Complete_EV [0E] [00] [HCI_Link_Key_Request_Reply]
2014-03-14 11:59:17.113 >> HCI_Command_Status_EV [0F] [00] [HCI_Set_Connection_Encryption]
2014-03-14 11:59:17.128 >> HCI_Encryption_Change_EV [08]
2014-03-14 11:59:17.378 >> HCI_Disconnection_Complete_EV [05]
2014-03-14 11:59:38.641 >> HCI_Connection_Request_EV [04]
2014-03-14 11:59:38.656 << HCI_Delete_Stored_Link_Key [0C12]
2014-03-14 11:59:38.656 << HCI_Remote_Name_Request [0419]
2014-03-14 11:59:38.656 >> HCI_Command_Complete_EV [0E] [00] [HCI_Delete_Stored_Link_Key]
2014-03-14 11:59:38.656 >> HCI_Command_Status_EV [0F] [00] [HCI_Remote_Name_Request]
2014-03-14 11:59:38.687 >> HCI_Remote_Name_Request_Complete_EV [07]
2014-03-14 11:59:38.687 -- Remote Name : A4:15:66:63:9B:2B - Wireless Controller
2014-03-14 11:59:38.687 << HCI_Accept_Connection_Request [0409]
2014-03-14 11:59:38.687 >> HCI_Command_Status_EV [0F] [00] [HCI_Accept_Connection_Request]
2014-03-14 11:59:38.859 >> HCI_Role_Change_EV [12]
2014-03-14 11:59:38.890 >> HCI_Connection_Complete_EV [03]
2014-03-14 11:59:38.890 >> HCI_Page_Scan_Repetition_Mode_Change_EV [20]
2014-03-14 11:59:38.921 >> HCI_Max_Slots_Change_EV [1B]
2014-03-14 11:59:38.953 >> L2CAP_Connection_Request [02] PSM [01]
2014-03-14 11:59:38.953 << L2CAP_Connection_Response [03]
2014-03-14 11:59:38.953 << L2CAP_Configuration_Request [04]
2014-03-14 11:59:38.953 >> L2CAP_Configuration_Request [04]
2014-03-14 11:59:38.953 << L2CAP_Configuration_Response [05]
2014-03-14 11:59:38.953 >> L2CAP_Configuration_Response [05]
2014-03-14 11:59:38.999 >> L2CAP_Disconnection_Request [06] Handle [0040]
2014-03-14 11:59:38.999 << L2CAP_Disconnection_Response [07]
2014-03-14 11:59:39.124 >> HCI_Link_Key_Request_EV [17]
2014-03-14 11:59:39.124 << HCI_Link_Key_Request_Reply [040B]
2014-03-14 11:59:39.140 << HCI_Set_Connection_Encryption [0413]
2014-03-14 11:59:39.140 >> HCI_Command_Complete_EV [0E] [00] [HCI_Link_Key_Request_Reply]
2014-03-14 11:59:39.140 >> HCI_Command_Status_EV [0F] [00] [HCI_Set_Connection_Encryption]
2014-03-14 11:59:39.155 >> HCI_Encryption_Change_EV [08]
2014-03-14 11:59:39.389 >> HCI_Disconnection_Complete_EV [05]
BT was working flawlessly with the previous version (.139)
Folks, I was having the same troubles pairing over BT with the new 1.2.0.160, it might be because your BT is not compatible with ScpDriver install.
To fix this problem I manually installed the BT driver from the Zadig folder per the original directions and then installed the service from ScpDriver making sure I UNCHECKED "Bluetooth Driver" or else it seemingly will overwrite the compatible driver for your unsupported dongle.
(03-14-2014, 12:07 PM)wooden_shelf Wrote: [ -> ]Folks, I was having the same troubles pairing over BT with the new 1.2.0.160, it might be because your BT is not compatible with ScpDriver install.
To fix this problem I manually installed the BT driver from the Zadig folder per the original directions and then installed the service from ScpDriver making sure I UNCHECKED "Bluetooth Driver" or else it seemingly will overwrite the compatible driver for your unsupported dongle.
To quote from the update instructions:
Quote:** The DS3, BTH and Bus drivers have not changed, so you do not need to re-run ScpDriver.exe.
Furthermore, my dongle is on the supported list:
Code:
Installing devices with Id "USB\VID_0A12&PID_0001&REV_8891" using INF "C:\Windows\System32\DriverStore\FileRepository\bthwinusb.inf_amd64_neutral_bb65126544cdaf87\BthWinUsb.inf".
I tried your suggestion nontheless, but it didn't work and I had to re-install the driver the standard way.
@blah0r: The drivers that get installed on DS3/DS4/BTH Dongles are Microsoft WinUSB, after WinUSB has been installed it never needs to changed.
Can you repeat the re-pair process and zip up your ScpService.log and post as an attachment.
Did you press the OK button after enabling the DS4 Repair check box? [forgot to do it a couple of times while I was testing lol]
(03-14-2014, 01:43 PM)Scarlet.Crush Wrote: [ -> ]Can you repeat the re-pair process and zip up your ScpService.log and post as an attachment.
Sure, see attachement.
Quote:Did you press the OK button after enabling the DS4 Repair check box? [forgot to do it a couple of times while I was testing lol]
Yea, I missed that step the first time, but meanwhile I've tried it several times doing it the right way
@blah0r: need to see the log of when the re-pair happens, so
1. Disconnect your DS4 from USB.
2. Enable the DS4 Repair option.
3. Connect your DS4 to USB.
4. Wait a few seconds.
5. Disconnect from USB.
6. Press the PS button.
7. Wait 10 seconds.
8. Zip up and post your ScpService.log as an attachment.
(03-14-2014, 03:11 PM)Scarlet.Crush Wrote: [ -> ]@blah0r: need to see the log of when the re-pair happens, so
1. Disconnect your DS4 from USB.
2. Enable the DS4 Repair option.
3. Connect your DS4 to USB.
4. Wait a few seconds.
5. Disconnect from USB.
6. Press the PS button.
7. Wait 10 seconds.
8. Zip up and post your ScpService.log as an attachment.
Scarlet, I think the repairing process isn't getting triggered at all, maybe that's why it is missing from the service log.
I did the following:
1. stop service
2. update to .160
3. start service (entries around 14:16:xx in attached service log)
4. enable repair option (AND pressing OK
)
I then connected the DS4 via USB to three different USB ports (front, USB 3.0 rear, USB 2.0 rear). When attaching the DS4 to an USB port it hadn't been connected before, Windows started installing drivers.
However, non of my USB connection attempts produced any output in the service.log!
For sake of completeness I've tried to connect via BT afterwards, just getting the immediate disconnect again (around 14:22:xx in the log).
So it seems like the re-pairing process is never initiated.
@blah0: yeah, I don't see any USB connection happening in the log. Did you use Zadig to install WinUSB on to your DS4?
Pairing & Repairing are both done over USB, so if the service never sees the DS4 connecting via USB it can't Pair/Repair the Link Key.
(03-14-2014, 04:13 PM)Scarlet.Crush Wrote: [ -> ]@blah0: yeah, I don't see any USB connection happening in the log. Did you use Zadig to install WinUSB on to your DS4?
No, I hadn't installed WinUSB on my DS4 via zdiag. I did install it now and afterwards repairing worked.
Thanks for your help!
Hi, do any of you guys know if the DS 4 works with bluetooth on an Asus BT-21 (not the BT-211) dongle. It supports 2.0 and EDR but dont know about SSP ?
edit : Just saw this :Note - Secure Simple Pairing is used and requires a Bluetooth 2.1 + EDR (or later) dongle. on post 1854, answers my question. Nervermind.
Thanks @ Scarlet.Crush for the awesome drivers.