Dualshock 4 recognized as Audio Device

[mentalBalanced]

Hey, dudes,

I'm using a Xiaomi Mi Notebook Pro (the 8th gen i-7) and when I plug my dualshock 4 v2, windows (10) recognizes it as a wireless controller. Under settings>devices, it shows up as an "audio controller". I tried troubleshooting and it suggested that it might not be working because I'm using a USB 2.0 cable on a usb 3.0 port, but this was never an issue with my tower, where I would always plug the USB cable in the 3.0 port. Tried installing/updating/uninstalling and then installing the drivers, switching ports; nothing worked. Any ideas?

[I_WORK_AT_IT]

I think the issue is in Xiaomi... 

You can try downloading drivers but I doubt it will ever work.. what kind of drivers were you using ?

Throw that peace of metal out and buy MacBook

[TheNuzziNuzz]

7 minutes ago, I_WORK_AT_IT said:

I think the issue is in Xiaomi... 

You can try downloading drivers but I doubt it will ever work.. what kind of drivers were you using ?

Throw that peace of metal out and buy MacBook

No, and no not a good idea. He clearly doesn't have the money for that, and this is a software issue anyway. It would be worse on Mac because drivers don't exist.

 

Check out https://github.com/nefarius/ScpToolkit

[mentalBalanced]

20 hours ago, I_WORK_AT_IT said:

Throw that peace of metal out and buy MacBook

No. I'd be throwing away both my Xiaomi and my money.

20 hours ago, TheNuzziNuzz said:

No, and no not a good idea.

Yes.

20 hours ago, TheNuzziNuzz said:

It would be worse on Mac because drivers don't exist.

Lmao.

 

I have tried the ScpToolkit solution, but it hasn't worked. I'm using Bluetooth to connect the controller for now, but I'd really like to be able to use a usb cable.

[TheNuzziNuzz]

11 minutes ago, mentalBalanced said:

No. I'd be throwing away both my Xiaomi and my money.

Yes.

Lmao.

 

I have tried the ScpToolkit solution, but it hasn't worked. I'm using Bluetooth to connect the controller for now, but I'd really like to be able to use a usb cable.

Could you explain what isn't working? Without the drivers the computer shouldn't recognize the controller at all in any games.

 

Also if you install the SCPtoolkit Bluetooth drivers properly the blurtuth dongle will not work with any other device.

[mentalBalanced]

1 hour ago, TheNuzziNuzz said:

Could you explain what isn't working? Without the drivers the computer shouldn't recognize the controller at all in any games.

 

Also if you install the SCPtoolkit Bluetooth drivers properly the blurtuth dongle will not work with any other device.

I installed the toolkit, but the controller was still recognized as an audio device and it didn't turn up in ds4win. Dead Cells (has support for controllers without any need for 3rd party programs) didn't recognize it, either. Not sure if it's connected, but when I first installed ds4win, the site was down and the driver wouldn't install. I then tried SCP (to no avail). Since then I've actually installed the ds4win driver (since the site is back up) and it does detect the controller (only via Bluetooth), but it doesn't work in Dead Cells. All I want is for my computer to recognize the device properly when I plug it in.

I'm not using a dongle. I'm using my laptop's built-in Bluetooth.

[TheNuzziNuzz]

3 hours ago, mentalBalanced said:

I installed the toolkit, but the controller was still recognized as an audio device and it didn't turn up in ds4win. Dead Cells (has support for controllers without any need for 3rd party programs) didn't recognize it, either. Not sure if it's connected, but when I first installed ds4win, the site was down and the driver wouldn't install. I then tried SCP (to no avail). Since then I've actually installed the ds4win driver (since the site is back up) and it does detect the controller (only via Bluetooth), but it doesn't work in Dead Cells. All I want is for my computer to recognize the device properly when I plug it in.

I'm not using a dongle. I'm using my laptop's built-in Bluetooth.

I would say try without Bluetooth at all. Also uninstall all drivers (in device manager) then start all again