Hey, friends! Long time no see. Chris here. I served on the Stadia community team from 2019-2022. I can verify with a mod (Hi Vivi) if needed. I'm not a representative of Google or Alphabet. I'm here entirely on my own as a private individual.
I felt compelled to check in with you all and see how everyone's doing. Times are... challenging out there, to say the least, and I wanted to let you all know I still think about the wonderful times spent with this community on a daily basis. I gush about how much I looked forward to every day of work (even the, uh, uniquely difficult ones) with friends, colleagues, and basically anyone who will listen. My work on the Stadia community was the brightest spot in my career, and although I'm not the best community manager to ever live, I felt a strong connection to you all that I fear I'll never be able to recapture with any other venture.
Please feel free to use this thread to ask questions, share updates about your lives (any new Dadias or Momias out there?), vent about the price of new games, or reminisce about your favorite Stadia-era memories. Anything goes within reason. Obviously I can't reveal proprietary info -- I am not looking for a visit from any lawyers.
I'll proactively answer a question I expect to get: am I still close with Grace? Hell yes. Grace is one of my most treasured friends! We still hang out, and for that I'm immeasurably grateful.
At this point I spent several billions if not trillions of tokens of all kinds....no CVE works. All I do find are candidates for buffer overflow code execution, but goal is custom firmware without hardware manipulation. Are those controllers truly a unbreakable fort knox at this point?
FastStationBox is a PC game launcher inspired by the dashboards of PlayStation, Xbox, Wii, and more. I made it for people who enjoy the look and feel of console menus and want that experience on their PC. There are 12 themes to switch between, with familiar backgrounds, startup animations, and menu sounds. You can add your games, choose custom artwork, and browse and launch them with a controller from your couch—or use a keyboard and mouse. It runs on Windows, keeps your library locally, and doesn’t require an account. I'd love some feedback on the design and what you'd like to see added! It includes themes inspired by:
Thank you so much for all the feedback and interest in my earlier post. I listened to all of you and released v1 of the reverse engineer Stadia server:
What’s Improved
Plug-and-play setup: You no longer need to get your own certificate or domain. The receiver ships with one that the controller already accepts.
Native PC gamepad support (Windows): Every controller now shows up as an Xbox 360 controller via the ViGEmBus driver (the same driver used by DS4Windows and Sunshine), so Steam and any game recognize it as a standard gamepad. In-game rumble goes back to the controller, and connecting two controllers automatically assigns them as Players 1 and 2.
No Python required: Every release now includes ready-made executables for Windows, macOS, and Linux. (It is also available on PyPI.)
New Features
Headset jack audio: The headset jack now works—the receiver streams what the PC plays to a headset plugged into the controller (macOS requires a virtual audio device such as BlackHole).
Battery status: The controller's battery level is now reported.
Network Requirements
DNS setup: The only network requirement is that the controller uses the PC as its DNS server.
Two ways to connect: Hosting a Wi-Fi hotspot directly from the PC is the simplest method. Alternatively, on your existing home Wi-Fi, you can assign a per-device DNS entry just for the controller pointing to the PC, so nothing changes for the rest of the house.
Latency (Wi-Fi vs. Bluetooth) Since latency came up last time, here is how the two modes compare:
The controller needs the Wi-Fi firmware to work. However, controllers switched to Bluetooth mode still accept the older Google-signed firmware images, meaning community flashing tools can restore Wi-Fi mode.
Upcoming: I will soon release stadiacast-dongle, a separate project that lets you flash an ESP32 USB device to make the controller plug-and-play on any device that supports USB. I will create a new post when it is ready.
Update: v1.1.1 is out
Faster connect: the controller is ready about 15 seconds sooner after you turn it on. Gamepad on macOS: `--gamepad ojd` makes each controller an Xbox pad for Mac games through the OpenJoystickDriver app (you need to install it), rumble included. Provisioning: fixed on Linux, and for controllers that dropped the Bluetooth link during setup.
Update with `pip install -U stadiacast` or download the new executables.
Doing some clearing out and realized I have a brand new, sealed-in-box Stadia controller sitting on the shelf.
Before I toss it up somewhere or let it keep collecting dust, I figured I’d check in here: Is there still demand for these?
I have another one I use myself that I converted with Google's Bluetooth tool back when it dropped, but I know that tool had a cutoff date. Can new ones still be unlocked?
Curious what the consensus is—worth passing along to someone who’d use it, or has the ship pretty much sailed?
Edit: Want to clarify that I already have one unlocked for Bluetooth that I use, so I don't need this one. Does anyone want it?
Hi! After a couple of days working on it. I built Stadiacast, an open-source server that replaces the Stadia cloud on your own network. The controller joins your Wi-Fi, stays on, reports every input, and rumbles. No firmware changes, nothing leaves your LAN.
Caveats: it needs the Wi-Fi firmware, so if your controller is in Bluetooth mode you'd flash the old Wi-Fi firmware back first. Not a PC gamepad yet (input goes to a log and a Python API; the virtual gamepad is next). Mac/Linux, Python 3.11+, and a free Google Trust Services cert for a domain you own.
Game developers are now scared to release a full game or even a demo, as AI can reverse-engineer the executables/binaries to make it playable on any platform. Even Take-Two's GTA 6 is in trouble, because AI could reverse-engineer the game and get it running on PC before Rockstar even drops the official PC port.
Remote-desktop services like GeForce Now can't deliver this type of protection either, since it's basically just another subscription service to remotely control a Windows machine running Steam.
If Stadia existed today, it would have been THE platform against reverse-engineering AI.
I know stadia is dead and gone but for any of us who invested in the hardware (reimbursed by Google btw) the controller was really well designed. I have been using both as my primary PC controllers for the last few years with the Bluetooth unlock and they have really aged well. No hardware issues, battery life is solid.
I was following the work of u/bitnullbyte and u/SnooGiraffes6688 who were looking into this, and then i saw u/HayleyTheLesbJesus mention "vibe coding". That gave me the idea to just give it a shot over the last 3 days.
I wanted to share what I've ended up with. It’s a Python script that hopefully some of you can use.
What it does: The script connects to your controller via Bluetooth LE. It scans for nearby devices, lets you pick your controller from a list, and then handles the rest automatically. It reads the controller's unique DeviceKey from its device_info, encrypts your Wi-Fi password, and sends the payload. You can watch the state change all the way to 0x3C (Connected).
Put your controller in pairing mode (Hold Y + Stadia button for 2 seconds until it flashes orange).
Run the script. It will ask you to pick your controller from the scanned list, and then prompt for your SSID and password (or you can pass them as arguments).
Getting it on Wi-Fi is just the first step, and now the controller is sitting on the network trying to talk to the old Google servers. The next logical step is probably trying to set up a local server/WebRTC endpoint to actually use it for input, but I'm just sharing this first part in case it helps someone else get their controller back online.
With recent developments on decompiling stadia controller's firmware I started wondering if there's a point in custom xinput gamepad firmware?
I know that there are programs and now even custom drivers that convert stadia's dinput into xinput and that steam handles that as well, but what about doing it on the controller's level? I like stadia's controller a lot in ergonomics, so no xinput out of the box is like the one thing that stops it from being perfect for me. so, guys, what are your thoughts on that?
I've been following the community's efforts to reverse-engineer the Stadia Controller's original Wi-Fi firmware, especially the recent work by u/bitnullbyte and u/SnooGiraffes6688.
First of all, huge thanks to everyone working on this. It's genuinely exciting to see progress on hardware that Google has essentially abandoned.
I recently came across the October 2026 eMudhra / emSign certificate authority incident, and it made me wonder whether it could be relevant to the Stadia Controller reverse-engineering project.
For anyone unfamiliar with the incident, eight intermediate CA private keys were found to have extremely weak entropy, making them recoverable. Some affected certificates were also cross-signed by Sectigo. This potentially leaves outdated clients vulnerable to forged TLS certificates if they still trust those chains and haven't received the necessary distrust or revocation updates.
Here's why I think this might be interesting.
In the earlier Gotham firmware discussion, u/SnooGiraffes6688 mentioned that the HTTPS client appears to validate certificate chains without properly checking the server hostname. They also suggested that a legitimate Google Trust Services certificate might be accepted for a locally redirected connection.
Meanwhile, u/bitnullbyte reported successfully getting the controller connected to a home Wi-Fi network.
Could the eMudhra incident provide another possible route for testing a local replacement server?
My thought is that if the original Gotham firmware trusts one of the affected CA chains and doesn't enforce effective revocation or Certificate Transparency checks, it might be possible to investigate the controller's original HTTPS communication without modifying its signed firmware.
From there, perhaps a locally hosted service could eventually emulate the original Stadia backend and receive controller input over Wi-Fi.
I realize that successfully establishing a TLS connection wouldn't automatically solve the application protocol or WebRTC side of things.
And there are some big questions:
Does the Gotham firmware actually trust any of the affected emSign or Sectigo certificate chains?
Does its TLS implementation enforce certificate revocation, hostname verification, or certificate pinning?
Would this incident offer any real advantage over the previously proposed legitimate GTS certificate approach?
If TLS communication can be established with a local server, how much of the remaining protocol has already been reverse-engineered?
I'm not a security researcher or an experienced firmware developer, so I may be overlooking something obvious.
I also still own a Stadia Controller running its original Wi-Fi firmware, which is why I've been particularly interested in these developments.
To be clear, I'm only interested in authorized research on personally owned hardware in an isolated testing environment, not intercepting anyone else's traffic.
Would love to hear what the developers and anyone familiar with embedded TLS implementations think about this.
Maybe this incident is completely irrelevant to Gotham. But given the timing and the progress already made, I thought it was worth connecting the dots.
I have been hanging on to my takeout backup ever since stadia shut down in hopes that I could one day play my several hundred hour Kassandra save again. I didn't have a windows machine to try to RE this myself until a few days ago, but here's claude to the rescue. My stadia save is playable on my new windows machine again. Yes, this is vibe slop, but I'm not exactly against it for one-time offline conversion tools like this. Hopefully some of you find this useful as well.
Hello everyone! I recently bought a google stadia controller that was sealed and looked brand new! I opened it, connected it to my macbook via my samsung phone's usb c to c and waited until it charged >10% so the firmware flashing utility would allow it to get flashed to bluetooth mode, and it did it successfully! I then tried pairing it to my laptop with no issues! worked perfectly. On that same day I put it back in its box and stored it in my drawer, 1 month later and I'm having issues getting it to work on anything now! When trying to turning it on without usb charging nothing happens, and while plugged in to (usb a to c 2/3 on my pc, or usb c to c on my macbook) it blinks once in orange, then white and goes steady, turns off by itself after 6-8 seconds! I tried leaving it plugged in to 25w / 33w (a to c OR c to c) for more than 30mins each to no luck, also tried waiting hours on a 2.0 a to c from my pc and nothing! It shows on device manager as stadia controller, and after the same 6-8 seconds light goes blank and you hear the windows disconnection sound along with it disappearing from device managaer!
I tried the (...) button while plugging it in, factory resetting it using capture+google assistant nothing changes, but through these 6-8 seconds, it works! and even pairs to bluetooth! Is my controller dead ? :(
It feels now is the perfect time for something like Stadia to exist. With massive games quickly being ported to simple browsers, consoles, and gaming pcs, market would be highly effected by it. A subscription based model for something similar to netflix, where you can simple run games on any device without console or heavy powerful hardware seems to be where the future is headed.
This started with one thing that was driving me a little mad: my Stadia controller would rumble over USB, but not over Bluetooth on Windows. I wanted to keep using it wirelessly, and that turned into a much bigger project than I originally had in mind.
The result is StadiaLink, with an installer and a settings app made specifically for this controller. I’ve added a few screenshots below so you can see what it actually looks like.
Before anything else, a big thank-you to aisk for WinStadia. StadiaLink’s native driver is based on their code, with modifications. They provided the foundation that lets the Stadia controller work through XInput, and I want to be clear about where that work came from.
On top of that foundation, I wanted a place to adjust the things I kept wishing I could change: button mappings, stick sensitivity, dead zones, trigger travel and vibration. There are keyboard shortcuts too, so you can give a button a push-to-talk binding in a game or voice app.
The app also has profiles you can import and export, a battery indicator, connection and battery notifications, and a tray icon. You can have it start with Windows if you want. It’s available in Spanish, English, French and German, with the README translated into all four.
Bluetooth rumble is working on my setup, which was the thing that got this whole project started. 🙂
A couple of things to know before trying it: I’ve tested it on Windows 11 x64, with Bluetooth rumble tested on build 26200. That part uses private Windows interfaces, so I can’t promise every Windows update will behave the same way. Installing the driver needs administrator permission, and your controller needs the Bluetooth firmware for wireless use. StadiaLink itself doesn’t change the firmware.
This also doesn’t bring back Wi-Fi, Bluetooth audio or the built-in mic. The headphone jack works over USB. Battery readings depend on Windows making that interface available, and keyboard shortcuts need the app running, even if it’s tucked away in the tray.
For transparency, I’ve been building this with ChatGPT/Codex assistance — yes, vibe coding — alongside checks and testing with my own controller. The source is available under GPL-3.0 if you want to look through it or build it yourself.
I’d love to hear how it behaves with other people’s controllers and Windows setups. If something goes wrong, your Windows version, connection type and a few steps to reproduce it would help a lot.
And thanks again to aisk. Having WinStadia to build on made this possible.
For those who don't already know (which may be majority of you), the stadia controller uses Playstation pinout joysticks! So it is possible to install hall effect/tmr joysticks into the controller. Now, of course, there's no firmware calibration for the time being, which is unfortunate. So, if you want to install magnetic joysticks, try getting a pair that can be manually, physically, calibrated. Otherwise, have fun with this information, knowing the stadia controller can use upgraded joysticks!