MissionControl icon indicating copy to clipboard operation
MissionControl copied to clipboard

[Bug Report]: Xbox One S Disconnects When Docked

Open kpas0 opened this issue 4 years ago • 10 comments

Switch Firmware Version

Other (please specify in issue description)

Atmosphère Version

Other (please specify in issue description)

Mission Control Version

Other (please specify in issue description)

Boot Method

Hekate

Issue Description

HOS: 13.0.0 Atmosphére: 1.1.0 Mission Control: 0.6.0

Xbox One S controller pairs successfully to switch when in portable mode, but disconnects once docked. Once removed from dock, the controller pairs again.

Error Report

No response

Additional Context

No response

kpas0 avatar Sep 28 '21 00:09 kpas0

Thanks for the report. I haven't docked my Switch in quite a while, so this is admittedly something that hasn't really been tested. I will check it out later. Do you know whether this happens on previous firmwares or with any other controllers?

ndeadly avatar Sep 28 '21 09:09 ndeadly

I wasn't able to reproduce this on my console. The Xbox controller remained connected as I docked and undocked the console several times. Can you tell me anything else about your environment? Are you running any other custom sysmodules? Do you have other controllers connected when the disconnection happens? Is this happening in-game or anywhere specific? (I only tried on the home screen)

ndeadly avatar Sep 28 '21 11:09 ndeadly

I struggled to get the controller to pair at all on HOS 12.1.1/AMS 1.0.0/MC 0.5.1 but I'm leaning toward user error/appstore install issues on that front. I went with a clean install for my current environment and everything paired properly. I've got Emuiibo installed. The other controller connected to the console during the disconnection is a pair of joy-cons as a single controller which remains connected during the Xbox disconnect. I observed the issue in-game but I'll try it on the homescreen when I get the chance. Also worth mentioning is the controller also won't pair while the console is docked but the controller was already in the database. I'll try clearing the database and seeing if the controller will pair while docked as a new controller.

kpas0 avatar Sep 28 '21 15:09 kpas0

Just tried to pair while docked with all pairings removed and wasn’t able to get the controller to pair until I undocked it.

kpas0 avatar Sep 29 '21 00:09 kpas0

Can you clarify whether you actually mean pairing as in hitting the sync button on the Change Grip/Order screen, or just reconnecting the controller with the guide button? Many users use the terms interchangeably.

It might also be useful to know whether your console is an erista or a mariko unit, whether you have any kind of modchip installed etc. that could cause different docking behaviour.

ndeadly avatar Sep 29 '21 13:09 ndeadly

Sorry about that. Yes I mean pairing by hitting the sync button on the Change Grip/Order screen. I had previously cleared all device pairings. I don't think mine is Erista or Mariko, it's the original unpatched version purchased a few weeks after launch. There are no modchips installed.

kpas0 avatar Sep 29 '21 15:09 kpas0

I just tried on a clean freshly installed SD card with nothing but Mission control and the behavior is still present. How could I enable logging to see what's happening with the connection when the console is docked?

kpas0 avatar Oct 11 '21 18:10 kpas0

I don't include logging functionality in the release builds in order to limit resource consumption as much as possible (and because many issues these days require problem-specific data to be logged anyway). Logging can also create problems too due to being slow and messing with timing critical code.

You can try this debug build of 0.6.0 and post the log it creates here for me to take a look at. You can find the log in sdmc:/bluetooth-mitm.log. Note that the log is wiped and started over on every boot.

MissionControl-0.6.0-dbg-a3591fe.zip

ndeadly avatar Oct 11 '21 19:10 ndeadly

Thank you for that. Using another fresh SD card never previously booted and with nothing but the dbg build, my Xbox controller connected to my undocked console and my custom button mapping was present immediately after powering the controller on without having to pair it. It seems the controller sticks in the console's BT database. I'm not too sure what to make of the log, but I docked after connecting the controller and the controller disconnected. I then held the pairing button on the controller while the console was docked and on the Change Grip/Order screen but the controller never paired. I then removed the console from the dock and power cycled the controller and it did not reconnect to the console until I held the pairing button on the controller again while on the Change Grip/Order screen on the console. Once the controller paired with the console, I docked the console and the controller disconnected again.

bluetooth-mitm.log

kpas0 avatar Oct 11 '21 20:10 kpas0

Sorry I forgot to follow up on this. I can't really see anything suspicious in the log (though there are many lower level things I am not able to log). I have tried several times and still cannot replicate this issue with my Xbox controller. Can you check whether this is still an issue with the latest HOS/AMS/MC versions?

ndeadly avatar Nov 18 '21 12:11 ndeadly