This is still happening. Usually it'll reconnect but this time for me it would not reconnect to the Destiny game and then after three kills in my Crucible match it booted me. It seems to be getting worse and I've given feedback multiple times to Stadia but I've had no feedback or reply from Google.
More than a few times lately. Ive had my controller inputs start going super wonky (like locking into aim down sights on destiny2) that only corrects itself if i unplug the controller then plug it back into my chromebook.
Quick poll: Does the issue only affect Founders edition controllers?
I ask because I recently purchased a second controller (wasabi) and so far it has yet to experience the disconnect issue.
I just had this issue twice with the Premiere edition controller in destiny. I waited awhile, but the controls didn't start working again in game. I hadn't had this issue before.
I think my router is dual band.
A couple updates:
Per stadia support, I disabled all of my Google Wifi pucks except the main router one. The thinking here was the Stadia controller was trying to switch between the pucks, depending on which signal was stronger at any given time. No go...even with just one router puck active, the Stadia controller lost signal for 15 seconds then reconnected while playing Trials Rising. So much for that experiment!
The disconnect also occurred with my second controller (purchased later than my Founders edition controller), so it's not just one type of controller.
Yeah, I've had this issue through two different model of routers and through all games I've played consistently. When it happens I press the Stadia button (because that works) and shut everything down. Then start it up and it works.
My theory is that there's a port conflict. Since Stadia overlay menus work but the game isn't responsive it's like the game server uses the same port as the controller causing the controller to loose input to the actual game.