Only because this is the one family of the devices secure enough to even bother with software security.

It's not their fault (plus since 2027 we expect the first Motorola handset secure enough tu be supported by GOS)

And at least they don't cheat on patches :)

If there's one thing I've learned about the custom Android community (and to a lesser extent, the Android community) it's that "it actually works" isn't really important or convincing to them.

>Well, for one you can actually buy an /e/ device right now. Also, once you have it, it just works.

Does that not apply to GOS?

You get a device that still runs proprietary Google blobs in privileged processes (for Play Integrity), talks a lot with Google, gives certain Google applications (like Google Maps) higher privileges than normal Android apps (you can find the signing keys of apps that get elevated privileges in the source code of the /e/OS microG fork), uploads your speech to OpenAI for speech to text, uses a shady middleman (which they do not want to reveal the owner of) for installing F-Droid apps [1], and is hopelessly behind on Linux kernel versions, firmware blobs, and Android security patches (remember that Android Security Bulletins only have backports of high/critical patches).

I wouldn't recommend anyone to use /e/OS. Either they are very incompetent or they are very shady.

[1] https://info.cleanapk.org

Google could invest in Graphene as a hedge.

they're working on it. GrapheneOS has serious plans to get a phone made for them. even more serious now that Google has become openly hostile to their project by no longer publishing the Pixel device tree when new releases come out.

At the end of the cycle of a Pixel model, they are heavily discounted. So much that it's probably close to hardware + development cost. Google probably expects to make a profit from Google One subscriptions, Play purchases, and ads.

By installing GrapheneOS, you are giving them nothing.