Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

PS3 Controller doesnt connect via Bluetooth. #872

Closed
Sakare opened this issue Aug 4, 2017 · 6 comments
Closed

PS3 Controller doesnt connect via Bluetooth. #872

Sakare opened this issue Aug 4, 2017 · 6 comments

Comments

@Sakare
Copy link

Sakare commented Aug 4, 2017

I installed ScpToolkit and everything workes fine. I can use my ps3 when it is connected via usb cable. But when i unpluge the cable, my Bluetooth won't work with my Controller. The ps3 Controller 4 red dots just Keep blinking. I also tryed the ps3 Controller reset button. Bluetooth Shows as Bluetooth Host (ScpToolkit). Any Help ?

@FragileHearts
Copy link

https://www.youtube.com/watch?v=RuxXUKN1vz8

try using this fix

@Sakare
Copy link
Author

Sakare commented Aug 4, 2017

Sadly doesnt help!

@FragileHearts
Copy link

Have you tried adding your bluetooth dongle Hardware ID into ScpCintrol.ini? Try using that, I fixed mine using this method.

Firstly, wipe your current driver installation using ScpCleanWipe
Then, add your BT dongle hardware ID into the ScpControl.ini. You can find your BT Dongle Hardware ID in device manager, under the "Details" Tab. On the drop down list pick Hardware IDs. Right click on the first value you find and paste in into the ScpControl.ini

Proceed with the installation as usual. This time when you get to the step where you install the BT Dongle, you will see the dongle id on the top right selection box. select that, and select initialize. If the ID goes down to the bottom right selection box, it mean you can use your dongle with SCP. if not, bad luck then.

@Sakare
Copy link
Author

Sakare commented Aug 4, 2017

It is alrdy on the ini.

@JackCobourn
Copy link

Along with running the ScpCleanWipe, try uninstalling the drivers for the Bluetooth adapter in Device Manager. This, along with a few restarts, got it working for me.

@Zcehtro
Copy link

Zcehtro commented Aug 15, 2017

I too am having this issue.
According to many, it's likely the Windows 10 Creator's Update that broke compatibility.
We'ed need the author, Nefarious, help.
Sadly, he hasn't been active on this for a long time... :(

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants