ndeadly
commented
1 year ago This seems to be an fs problem. Delete /config/MissionControl/controllers and try again. You could also try to fix your archive bits in hekate if that doesn't work.
Closed medic4085 closed 1 year ago
ndeadly
commented
1 year ago This seems to be an fs problem. Delete /config/MissionControl/controllers and try again. You could also try to fix your archive bits in hekate if that doesn't work.
medic4085
commented
1 year ago Did both steps as indicated. Arch bit was completed in hakate and did note "done, no changes needed". It did initially do the same thing. It shows "paired" however doesn't display the controller and then the screen goes black indicating the "crash". However, once i restarted the device, the controller was paired. I did try to replicate the issue. And now seems to be working as intended. I will report anything further if I come across it. Thanks again for your quick response!
Mxthislm
commented
1 year ago Hey how did you downgrade the xbox controller ?
medic4085
commented
1 year ago ndeadly
commented
1 year ago @Mxthislm
Official support page from Microsoft streamlines the process https://support.xbox.com/en-US/help/hardware-network/accessories/controller-firmware-reversion
Switch Firmware Version
Other (please specify in issue description)
Atmosphère Version
Other (please specify in issue description)
Mission Control Version
0.9.2 (Latest)
Boot Method
Fusée
Issue Description
Switch Firmware 16.0.3, Atmosphere 1.5.4 Downgraded the xbox controller firmware. Initially was not able to pair. However, after the downgrade, it now "pairs" however cannot use the controller. Also, when it pairs it then crashes atmosphere. I have posted a copy of the log for your records and troubleshooting. Just to reiterate, this was a non-LE BT controller, that had the firmware update to support the LE. I did the firmware rollback on the xbox accessories app. Thanks again for your efforts in this!
Error Report
report_16faeb85.zip
Additional Context
No response