Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I have to admit at least Google handled the Stadia well in this regard. The money just got refunded to me without me taking any action at all.


Both were pretty lame tbh.

What would be ideal is to open up devices to be flashed with custom FW or OS installs and some rudimentary docs on doing so. That would be enough for the community to run with it if there is sufficient demand and value.


Stadia controllers got to be reflashed as standard Bluetooth controllers. I still use mine.


Refreshed before typing this because I realised someone might have beaten me to it! - But that's a big difference here - even though the service is gone, you got the refund and still a usable device as a controller out of it...

Spotify has taken something that could be used generically too, and just decided to brick it.

Insert something about product and consumers and how its all just some big money game or something somewhere :D


Spotify should have the ewaste generated by this decision accounted for when considering any ESG benefits or grants.


It's worth noting that for some reason there's a deadline for flashing the generic Bluetooth firmware onto a Stadia controller though, you have to get it done before the end of this year if you have one gathering dust.

https://stadia.google.com/controller/index_en_GB.html


Yes, but that's just when Google will stop hosting the tool that lets you reflash it. The tool works without Google's servers, and is already hosted elsewhere: https://github.com/luigimannoni/stadia-controller-flasher?ta...


Well, a community effort to reverse engineer the process and deobfuscate the javascript is keeping the tool alive. If they didn't step in to archive it, seemingly the cutoff would have been real.

It would have been a better testament to their commitment to prevent these controllers from becoming e-waste if Google just hosted an open source version of the flashing tool on their github from the start.


As far as I know, the reverse engineering/deobfuscation is only for the purpose of allowing third-party firmware to be flashed instead of the Google firmware for Bluetooth. If all you want to do is archive the tool for the latter, you merely have to copy the files from Google's site.


Oh right, I assumed it required Googles servers to sign the firmware for your specific unit or something.


To be fair, they've extended that deadline a few times already (and it's mirrored elsewhere, as another pointed out).

I know Google graveyards a lot of things, but in the Stadia case, they truly went above and beyond to make customers whole again. They refunded every software & hardware purchase automatically, in full, no matter when you bought it, and also provided save game exports. That means people got to play those games on Stadia for those few years, then got all their money back AND some free hardware (Bluetooth controllers). It was a failed Google experiment, but all us guinea pigs got some free entertainment and swag out of it. Kudos.


Probably just a deadline to kill the subdomain and resources.


My bad, that's pretty legit on Google's part!


> Both were pretty lame tbh.

Strongly disagree. While the arbitrary deadline on the bluetooth flasher tool that Google created is dumb, I ended up with 4 bluetooth controllers for free. Seems like a pretty great deal to me.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: