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

Dualshock 4 V2 first time pair was OK, second time crashes Switch. #39

Closed
ali-ee opened this issue Aug 31, 2020 · 14 comments
Closed

Dualshock 4 V2 first time pair was OK, second time crashes Switch. #39

ali-ee opened this issue Aug 31, 2020 · 14 comments

Comments

@ali-ee
Copy link

ali-ee commented Aug 31, 2020

Title was pretty explanatory.
I paired and used the controller without issues the first time.
Now, after a wake up of the console, everytime I try to pair crashes my Switch.
Tried disconnecting all controllers from menu, resync, restart.
Nothing worked.
What can I try more?

@ndeadly
Copy link
Owner

ndeadly commented Aug 31, 2020

Can you post the atmosphere fatal error report log here so I can see where it's crashing. Sorry I'm on mobile at the moment, but if you look in some of the other issues similar to this I've posted a build with debug logging enabled. Try running that and post your log here too.
You could also try resetting the controller itself if you haven't done that already.

Sorry for the troubles. I think some DS4 controllers must be sending strange packets that the switch doesn't like, causing it to abort.

@ali-ee
Copy link
Author

ali-ee commented Aug 31, 2020

01271121512_0100000000000013.log

01598876141_0100000000000020.log

are these enough?

by the way, after reading the other issues, I started thinking that mine also might be caused by battery level because I recently charged it

@ndeadly
Copy link
Owner

ndeadly commented Aug 31, 2020

Can you give me some more context? These are two separate crashes from two different modules (hid and nfc) that I don't directly interact with. These are definitely the logs relating to the errors you saw?

Do you have any other homebrew or anything running that might try to access controller functionally?

Again, you should try to run my debug logging build from the other thread and post the btdrv-mitm.log file so I can see what my module is actually trying to do.

The battery thing is something I still need to look into when I have time. It's possible that it's the cause of your problems too, but hard to say without seeing the log.

@Cruellest
Copy link

I also had this problem but in my case the bug happened because I had charged 100 percent of the control's battery before connecting it a second time so it crashed after reading all the articles in issues I thought it could be the battery bug that several other users reported, then I left the battery at about 70-80 percent (on ps4) so ​​I went to test it and it worked perfectly on the switch after that

@lirigoyenac
Copy link

I'm also having this problem. It only happens to me if I have an Xbox One controller and two Joy Con connected, and then try to pair the DS4. If I connect the DS4 first, or not connect the Xbox One controller at all, then no issues.

@ali-ee
Copy link
Author

ali-ee commented Sep 1, 2020

Thanks for trying to fix the issue.
Here is the log from debug version:
btdrv-mitm.log
Additional note:
I have sys-con and emuibo modules but they're off.

@ndeadly
Copy link
Owner

ndeadly commented Sep 1, 2020

Thanks for the info @Cruellest, the DS4 battery bug may very well be to blame here. I might try to fix that first before we dive too deep into this issue.

@ali-ee thanks for the log. I can't see anything that looks obviously wrong there. Did you experience the crash when making this log? I haven't heard any reports of sys-con causing problems, but since one of those other crash logs came from nfc it could have had something to do with emuiibo. Are these definitely new crashes since you installed MissionControl?

@ndeadly
Copy link
Owner

ndeadly commented Sep 1, 2020

@lirigoyenac could you make me logs of the two conditions you described? I have both controllers and have never seen any issues related to the order in which things are connected.

@ali-ee
Copy link
Author

ali-ee commented Sep 1, 2020

@ali-ee thanks for the log. I can't see anything that looks obviously wrong there. Did you experience the crash when making this log? I haven't heard any reports of sys-con causing problems, but since one of those other crash logs came from nfc it could have had something to do with emuiibo. Are these definitely new crashes since you installed MissionControl?

@ndeadly Yes, I created this log during the crash. I will also post atmosphere crash log once I clean old logs.

@ndeadly
Copy link
Owner

ndeadly commented Sep 1, 2020

Here's (hopefully) a fix for the battery related issues people have been seeing. Give this build a try and see if it resolves your issues or not.

MissionControl-0.1.0-ds4-battery-fix.zip

@uzumis
Copy link

uzumis commented Sep 2, 2020

Here's (hopefully) a fix for the battery related issues people have been seeing. Give this build a try and see if it resolves your issues or not.

MissionControl-0.1.0-ds4-battery-fix.zip

Got the same issue and this build solved my problem too. Thanks

@ali-ee
Copy link
Author

ali-ee commented Sep 4, 2020

Here's (hopefully) a fix for the battery related issues people have been seeing. Give this build a try and see if it resolves your issues or not.

MissionControl-0.1.0-ds4-battery-fix.zip

This build also seems to work properly for me, no crashes after a full charge.

@ndeadly
Copy link
Owner

ndeadly commented Sep 4, 2020

Sounds good. Can we close this issue then?

@ali-ee
Copy link
Author

ali-ee commented Sep 6, 2020

Sounds good. Can we close this issue then?

I think we can @ndeadly .
Thanks for the help.
Only thing left for this to be perfect is the rumble now :)

@ali-ee ali-ee closed this as completed Sep 6, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants