Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

launch dualshock 4 not pairing #101

Open
Sakitoshi opened this issue Apr 23, 2023 · 1 comment
Open

launch dualshock 4 not pairing #101

Sakitoshi opened this issue Apr 23, 2023 · 1 comment
Labels
bug Something isn't working

Comments

@Sakitoshi
Copy link

Hi.
I have a launch dualshock 4 (CUH-ZCT1U bundled with a launch "fat" ps4) that simply doesn't want to get paired, i've tried with aroma and tiramisu but nothing seems to work.
I also have a second dualshock 4 also v1 (blue, don't know the exact model number because half of the label isn't there anymore) that does pair and works without issues.
both identify as "Wireless Controller".

@Invictaz
Copy link

Invictaz commented Feb 24, 2024

You might want to submit a Bluetooth HCI snoop trace from Ubuntu.


How to use btmon to capture an HCI trace
The HCI trace is a snapshot of the communication between the Bluetooth host (software stack) and the Bluetooth controller (the chip). The ‘btmon’ tool can be used to capture such for both live debugging and saving it for later. Note that the HCI trace needs to be captured at the same time the Bluetooth issue occurs.

The ‘btmon’ executed without any parameters will offer live debugging which will print in a ‘tail -f’ fashion an ongoing exchange of the commands and events between the stack and the chip. It is possible however to make it save the data in the snoop format:

sudo btmon --write ~/hcitrace.snoop
Additionally, someone who would like to have a text version available for later too would execute it in a following way:

sudo btmon --write ~/hcitrace.snoop | tee ~/hcitrace.txt
The nice thing about btmon and how it works is that it is possible to have several versions of it executed simultaneously. This allows capturing logs as in the last example in one shell and viewing the live in another.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants