A Chrome instance on a Thinkpad X1 Carbon Nano. Runs much better on Stadia than it does locally. Ironic really.
The tool for enabling Bluetooth is available now but has to be done before the end of 2023:
Just make sure you have a USB-C cable which supports data and you are using Chrome.
It’s not quite that straightforward.
The Chrome-based validation tool isn’t robust. The different controller types confuse it.
Got a White (normal) controller? - You’re good, it’ll work as instructed
Got a Wasabi Controller or a Founders Edition (Dark Blue)? - Then you need to ignore the validation tool and go into bootloader mode. Had me tearing my hair out until I realised each controller ‘colour’ is identified - and the big G hasn’t (yet) realised this.
Spent hours today trying to get the FE controller to switch, whereas my White controller switched on the first attempt.
Anyway, all Bluetoothed up now and the controllers live on.
RIP Stadia ![]()
I went through quite the experience to flash Bluetooth access to my FE controller. Good to know it’s not a widespread thing - maybe the tool has been updated? I can’t verify this until tomorrow as I’m overseas at the mo.
Last week I was able to enable Bluetooth on both of my controllers, one white and the other wasabi, without any issues at all. Very straightforward to get them to pair with my Pixel 6
The Stadia concept boomerangs once more