This has never happened to me before, but today all of a sudden my Stadia Controller’s A button pulls up the Stadia Menu instead. Pressing “A” behaves exactly the same way as pressing the Stadia button. It’s the same for the D Pad as well.
The issue only happens in-game. When I start up the Stadia and before I select a game, the “A” button is recognized just fine, but once a game is launched, the “A” starts pulling up the Stadia menu instead.
I am connected to my Chromecast Ultra.
I have tried resetting the Stadia controller and reconnecting the WiFi several times. Nothing helps.
Thanks in advance.
I just had the same issue after I ran out of battery on my controller, got an extension to charge it whilst playing and this happened. I eventually realised that if I turned the controller on whilst not connected to the usb cable, it worked fine again, then I could connect it to continue charging without issue.
So it looks like it goes into a different mode if connected to certain USB cables whilst powering on.
Hope that helps someone, no need to reset the controller etc.
Hi @Mykall
Sorry to hear about that, that must be really frustrating. I know you mentioned resetting the controller, I just wanted to check if you did a hardware reset or if you did a factory reset. I think a factory reset will hopefully fix it. Just in case, here is how you do a factory reset:
When you factory reset your Stadia Controller, all Wi-Fi login information is removed from it.
and Capture
buttons simultaneously for 6 seconds.
Note: After you perform a factory reset, you'll need to set up a Wi-Fi connection again in the Stadia app
to play wirelessly with your controller.
Hello,
Yes, that is exactly what I did: pressed Google Assistant and Capture buttons simultaneously. I reset the controller several times and the issue persisted.
I did some more research and there were a few threads that seemed to point to WiFi being the issue. I think it’s something to do with the WiFi range being spotty. I bought a WiFi range extender, reset both the Chromecast Ultra and the Stadia controller and moved them all to the same network.
Not exactly sure which of those steps corrected the issue, but it is fixed now. Hopefully this will help someone else with the same issue.
I just had the same issue after I ran out of battery on my controller, got an extension to charge it whilst playing and this happened. I eventually realised that if I turned the controller on whilst not connected to the usb cable, it worked fine again, then I could connect it to continue charging without issue.
So it looks like it goes into a different mode if connected to certain USB cables whilst powering on.
Hope that helps someone, no need to reset the controller etc.
This just happened to me, what you stated has fixed it... weird thing for a usb cable to do
Yep, this fixed it for me too. Should be top answer.