Maybe I missed it, but assuming GrapheneOS doesn't adhere to this verification, or provides some OS-level way to disable it, what makes Graphene worse after this change?

▲

traverseda 3 days ago | parent [-]

GrapheneOS is only allowed to live because google lets it. This signals a wider ecosystem change that tells us that GrapheneOS is going to stop being usable when this generation of hardware dies. This generation or maybe the one after it.

▲

johnwayne666 3 days ago | parent | next [-]

But why start from scratch with a “Linux phone” when we can continue on the basis of GrapheneOS. The source is there and it works.

Apps that require Google Play Service or some form of attestation will not run on a Linux phone either.

▲

palata 3 days ago | parent | prev [-]

What do you mean with "Google lets it"? GrapheneOS is based on AOSP.

GrapheneOS only runs on the Google Pixels, and Google may decide to render future Pixels unusable for GrapheneOS (e.g. by preventing to unlock/relock the bootloader).

But another Android manufacturer could get to the point where GrapheneOS endorses them. It feels like it shouldn't be that hard for an Android manufacturer, and they would immediately get quite some attention. Maybe not mainstream attention, but largely profitable, I think.

▲

pdesi 3 days ago | parent [-]

GrapheneOS exists only because the Pixel's bootloader can be unlocked. Google could remove that option anytime, making it impossible to install GrapheneOS.

	▲	drnick1 3 days ago \| parent \| next [-]
		Graphene is in talks with an OEM to make compatible devices. AOSP is free software, the only issue here is finding devices where it can be installed.
	▲	palata 2 days ago \| parent \| prev [-]
		I'm confused... how is it different from what I said?