-
-
Notifications
You must be signed in to change notification settings - Fork 134
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
Comments
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. Sorry for the troubles. I think some DS4 controllers must be sending strange packets that the switch doesn't like, causing it to abort. |
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 |
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. |
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 |
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. |
Thanks for trying to fix the issue. |
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? |
@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. |
@ndeadly Yes, I created this log during the crash. I will also post atmosphere crash log once I clean old logs. |
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. |
Got the same issue and this build solved my problem too. Thanks |
This build also seems to work properly for me, no crashes after a full charge. |
Sounds good. Can we close this issue then? |
I think we can @ndeadly . |
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?
The text was updated successfully, but these errors were encountered: