zlacker

[return to "Google Pixels are no longer the AOSP reference device"]
1. coffee+fm[view] [source] 2025-06-12 18:36:12
>>tripdo+(OP)
Judge me if you must, but the only reason I recently bought a Pixel was because of the intention on sticking GrapheneOS on it the second I got it out of the box. And it really worked great for me so far... Unless it's something to do with work, I don't (intentionally) touch anything that has to do with Google, as I dislike too many things about them.

And yes, they're not obligated to provide those binary blobs, but since they've been doing it for such a long while, not announcing it well in advance, like they do with the so many services they choose to discontinue, just adds to that list of things I dislike about them.

Yeah, yeah, it's a bit more work to publish those binaries and make sure they work. But they still kind of have to do that, for themselves. So I think it's fair to assume why they did it. Because they made a choice to take a small loss on the devices they would sell for the few GrapheneOS users, and cash in on the walled garden, data mining, ads serving, yada yada, whatever brings the extra money after the initial phone sale.

◧◩
2. baurui+kK1[view] [source] 2025-06-13 07:59:50
>>coffee+fm
I only had Nexus and Pixel phones since they existed. I've never cared what hardware they had the only thing I cared is what they have killed now.

This is the bigger disappointment than the 24 days (and counting) that they need to repair my Pixel 7 right now. I'm really glad I didn't buy a new Pixel 9 already.

[go to top]