cancel
Showing results for 
Search instead for 
Did you mean: 

-Dementor-'s Posts

Looks like it's fixed
Who marked this as the best response lol
For like the past year or so, the Stadia Android app just randomly crashes for me after a few seconds when trying to navigate around the UI or do anything with it. Uninstalling and reinstallin... See more...
For like the past year or so, the Stadia Android app just randomly crashes for me after a few seconds when trying to navigate around the UI or do anything with it. Uninstalling and reinstalling the app temporarily resolves the continuous crashing, but not for long. This was happening on my Pixel 2 XL with Android 11 and still happens on my Pixel 6 Pro with Android 12. I think the issue might lie server-side, though, because right after the Android app crashes, if I try to open Stadia on the PWA, I get the following error message: This error 429 lasts for a few minutes, but once it's gone, the Android app also starts working for me again. But it's a continuous cycle when the Android app crashes again. Looking online, I've only seen like one or two posts on the Stadia community forum about an issue like this. Apparently, error 429 means that "the client application has surpassed its rate limit, or number of requests they can send in a given period of time," and one person said they resolved it by reducing the number of people on their friends list and I reduced mine from around 75 to 25 but am still experiencing the problem. Not sure what else I can try to get the Android app to work consistently. I've been resorting to just using the PWA on my phone, but the Android app still has some other features like notifications and controller setup.
The linked Stadia Pro deals section is empty
Update: Somehow, this is fixed now! Just tested it today and it connected with the laptop over Ethernet. Maybe a recent Google Wifi update resolved it?
Cross-posted from Reddit I use a Google Wifi mesh with the primary point in the living room and one point in my bedroom and the other in the kitchen. The primary point connects to a TP-Link switch a... See more...
Cross-posted from Reddit I use a Google Wifi mesh with the primary point in the living room and one point in my bedroom and the other in the kitchen. The primary point connects to a TP-Link switch and this switch is connected through the walls via Ethernet to the two other Wifi points. My Chromecast Ultra is in the living room and connected via Ethernet to the switch. I've had no issues with using the Stadia Controller wirelessly with the wired CCU. However, when I use my laptop in my bedroom, connect it via Ethernet to the wired Wifi point, and try to connect the Stadia Controller wirelessly, the controller buzzes as if it worked for a sec, then buzzes crazy and flashes yellow. Basically, it doesn't work. I am able to connect the controller when the laptop is on Wi-Fi. Also, a neat "fix" is to first connect the controller when the laptop is on Wi-Fi and then plug in the Ethernet to the laptop. This works, but sometimes the controller just ends up disconnecting mid-way through a game. Below is a list of what I've tried: Doesn't work: Laptop > Ethernet > Bedroom Wifi point > Ethernet > Bedroom wall port > Ethernet > Switch > Ethernet > Primary Wifi point Laptop > Ethernet > Bedroom wall port > Ethernet > Switch > Ethernet > Primary Wifi point Works: Laptop > Wi-Fi Laptop > Wi-Fi > Connect controller > Plug-in Ethernet Laptop > Ethernet > Switch > Ethernet > Primary Wifi point The last bullet above is what stumps me. I am able to get it to work when the laptop is wired directly to the living room switch but not in my bedroom. I'm guessing this is also why my CCU "just works." Edit: So I tested this method again with the laptop connected to the switch and now it doesn't work. Lol I've also tried testing where the laptop is connected via Ethernet in the bedroom and the controller is in the living room (connected to the primary Wifi point) and that doesn't work. But having the laptop over Wi-Fi in the bedroom and the controller over Wi-Fi to the primary point   does   connect. Anyways, sorry for the long post, I just wanted to provide ample amount of details for troubleshooting. Does anyone know where exactly the problem lies? Would it possibly be something wrong with the wall Ethernet?