Controller is always disconnecting randomly when using Bluetooth.
See original GitHub issueLog: DS4Windows Error 1167.txt
I get this Error 1167 every time I play using Bluetooth. I’m forced to always play through USB connection because of this. The error doesn’t occur if I turn off Enable Output data to DS4, so I know it’s not a problem with my Bluetooth connection. I had this problem with version 2.1.3 as well, but I didn’t try other versions before that.
Issue Analytics
- State:
- Created 3 years ago
- Comments:20
Top Results From Across the Web
Controller keeps disconnecting from Bluetooth
1. Run Bluetooth Troubleshooter · 2. Take actions related to Bluetooth driver · 3. Head to following Microsoft help on Bluetooth issue and...
Read more >Xbox controller keeps disconnecting from my PC : r/gaming
SOLUTION FOUND: The controller is in need of a firmware update, to do that via the PC download the "Xbox Accessories" app from...
Read more >Bluetooth keeps disconnecting [Solved]
If there's something wrong with your Bluetooth driver, the connection will constantly cut out. In this case, you could uninstall your Bluetooth ...
Read more >[Solved!] Bluetooth Keeps Disconnecting on Windows
To solve the issue, you need to modify the Bluetooth Power setting. Use Windows Search to search for device manager and then select...
Read more >Xbox One Controller Keeps Disconnecting From PC ...
If your Xbox One controller keeps disconnecting from the PC Bluetooth connection, it could be because you have enabled several Bluetooth ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@Newtype14 The BlueYeti device is shown as “gamepad” only in debug version because the debug version tries to use all devices with usageFlag=0x05 value. The vanilla version doesn’t try to use it as gamepad because the VID/PID is not registered as DS4 gamepad.
Do you still have those old ScpToolkit/ScarletCrush drivers installed? Those are known to cause problems in BT connections when some other “driver” tries to use the same BT host with gamepads. ScpTookit and ScarletCrush drivers hijack the BT stack and does all kind of nasty tricks (not recommended by Windows kernel driver docs).
Uninstall and traces of those old Scp drivers and apps (ie. literally remove those drivers using DriveStore Explorer app even when you no longer have apps using those drivers). https://forums.vigem.org/topic/250/scptoolkit-removal-guide