Device Type: Clone on first-party controller. #3

Closed
opened 2026-02-10 18:42:32 +03:00 by OVERLORD · 10 comments
Owner

Originally created by @e3ndr on GitHub (May 7, 2024).

Title. Is there any way for me to get you some debug data?

opera_KbIe5rQaGu

I have a "Glacier White" controller.

Originally created by @e3ndr on GitHub (May 7, 2024). Title. Is there any way for me to get you some debug data? ![opera_KbIe5rQaGu](https://github.com/dualshock-tools/dualshock-tools.github.io/assets/33337309/25983192-b723-4f1c-9599-53115035623e) I have a ["Glacier White"](https://a.co/d/6SwaUq4) controller.
Author
Owner

@Excrubulent commented on GitHub (May 20, 2024):

Having the same issue. I bought two original controllers from a reputable big box store in Australia years ago. I have a very hard time imagining how they could've been clones in any way. They're labelled as Sony products and I really doubt they're knock-offs.

@Excrubulent commented on GitHub (May 20, 2024): Having the same issue. I bought two original controllers from a reputable big box store in Australia years ago. I have a very hard time imagining how they could've been clones in any way. They're labelled as Sony products and I really doubt they're knock-offs.
Author
Owner

@preston176 commented on GitHub (May 23, 2024):

same issue yet im having original controller old one from 2015

@preston176 commented on GitHub (May 23, 2024): same issue yet im having original controller old one from 2015
Author
Owner

@NanoPi commented on GitHub (May 24, 2024):

Were any of you using a Bluetooth connection at the time?

Using a Bluetooth connection is how I get the clone message on an original controller.
I don't get the clone message when the controller is connected by USB. Have done stick calibration over USB several weeks ago. (JDM-055, FW from 2017)

On Bluetooth, device.receiveFeatureReport(0x81) on line 112 results in running the catch block with e containing "Failed to receive the feature report".

@NanoPi commented on GitHub (May 24, 2024): Were any of you using a Bluetooth connection at the time? Using a Bluetooth connection is how I get the clone message on an original controller. I don't get the clone message when the controller is connected by USB. Have done stick calibration over USB several weeks ago. (JDM-055, FW from 2017) On Bluetooth, [device.receiveFeatureReport(0x81) on line 112](https://github.com/dualshock-tools/dualshock-tools.github.io/blob/20075c4552f70bc0b8aa296ca12efe531d263788/core.js#L112) results in running the catch block with e containing "Failed to receive the feature report".
Author
Owner

@e3ndr commented on GitHub (May 24, 2024):

Were any of you using a Bluetooth connection at the time?

Using a Bluetooth connection is how I get the clone message on an original controller.

I don't get the clone message when the controller is connected by USB. Have done stick calibration over USB several weeks ago. (JDM-055, FW from 2017)

On Bluetooth, device.receiveFeatureReport(0x81) on line 112 results in running the catch block with e containing "Failed to receive the feature report".

I was, yeah. Does the web tool work over USB or would I need to use the Python version?

@e3ndr commented on GitHub (May 24, 2024): > Were any of you using a Bluetooth connection at the time? > > > > Using a Bluetooth connection is how I get the clone message on an original controller. > > I don't get the clone message when the controller is connected by USB. Have done stick calibration over USB several weeks ago. (JDM-055, FW from 2017) > > > > On Bluetooth, [device.receiveFeatureReport(0x81) on line 112](https://github.com/dualshock-tools/dualshock-tools.github.io/blob/20075c4552f70bc0b8aa296ca12efe531d263788/core.js#L112) results in running the catch block with e containing "Failed to receive the feature report". I was, yeah. Does the web tool work over USB or would I need to use the Python version?
Author
Owner

@NanoPi commented on GitHub (May 24, 2024):

I was, yeah. Does the web tool work over USB or would I need to use the Python version?

Web version worked for me over USB. Chromium, Windows 10.

@NanoPi commented on GitHub (May 24, 2024): > I was, yeah. Does the web tool work over USB or would I need to use the Python version? Web version worked for me over USB. Chromium, Windows 10.
Author
Owner

@Excrubulent commented on GitHub (May 24, 2024):

Okay, USB fixed the issue for me, I had indeed been using BT, thanks so much. It might be an idea to add this solution to the error message.

@Excrubulent commented on GitHub (May 24, 2024): Okay, USB fixed the issue for me, I had indeed been using BT, thanks so much. It might be an idea to add this solution to the error message.
Author
Owner

@Doyle4 commented on GitHub (May 30, 2024):

When using USB it uses the data lines to connect to the controller board which is what allows it be flashed etc.
Using bluetooth will show connected but not have access to write to the section thats needed.
Although it says clone, pretty good that its stops anything from been flashed as it could cause issues or even brick the controller.

@Doyle4 commented on GitHub (May 30, 2024): When using USB it uses the data lines to connect to the controller board which is what allows it be flashed etc. Using bluetooth will show connected but not have access to write to the section thats needed. Although it says clone, pretty good that its stops anything from been flashed as it could cause issues or even brick the controller.
Author
Owner

@dualshock-tools commented on GitHub (May 30, 2024):

With the latest version, the website should warn if the controller is connected via Bluetooth instead of USB. Let me know if that works!

@dualshock-tools commented on GitHub (May 30, 2024): With the latest version, the website should warn if the controller is connected via Bluetooth instead of USB. Let me know if that works!
Author
Owner

@e3ndr commented on GitHub (May 30, 2024):

Can confirm that using USB fixed the issue for me! Thanks for the hard work @dualshock-tools. I'll check the bluetooth warning in a couple of days. Feel free to close this :)

@e3ndr commented on GitHub (May 30, 2024): Can confirm that using USB fixed the issue for me! Thanks for the hard work @dualshock-tools. I'll check the bluetooth warning in a couple of days. Feel free to close this :)
Author
Owner

@Excrubulent commented on GitHub (May 30, 2024):

Just checked the BT message, and I got "Please connect the device using a USB cable." Nice work!

@Excrubulent commented on GitHub (May 30, 2024): Just checked the BT message, and I got "Please connect the device using a USB cable." Nice work!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dualshock-tools/dualshock-tools.github.io#3