How will Graphene OS survive with google ending open sourced pixel ?

llama420

Pretty sure this has been mentioned already, just can't find anything about it. In a joint move, google seems to have ended open source development of pixel device trees and drivers at the same time they announced that no non-verified apps will be supported. No coincidence this comes at the same time that ID checks are becoming commonplace online. Very disturbing trend, likely tied to governmental pressure about surveillance coupled with their own desire to control what gets to be put on the devices we soon will no longer own.

How will Graphene survive this? Might have to go to a Linux phone at this point, or just not have a phone at all. I refuse to go along with this shit.

Some sources:
https://www.androidauthority.com/google-not-killing-aosp-3566882/
https://mashable.com/article/google-android-sideloading-apps-security/

mrket

llama420 How will Graphene survive this?

It already has, you say you didn't find anything about it, but with the huge number of posts on this subject at this point I doubt you did even basic research before posting...

mrket

llama420 Regarding verification of developer identities,
https://discuss.grapheneos.org/d/25543-developers-identity-outon-the-playstore

This post is currently on the front page of the forum, note how the first reply in that thread links two previous threads about this

llama420

mrket

wuseman

mrket

My bad. Didn't do much research admittedly. Been trying to remove this post. Looks like I can't for some reason.

wuseman

This is up literally every week. Can you please use the search feature?

ErnestThornhill

llama420 . Been trying to remove this post. Looks like I can't for some reason.

Well, yeah...It's been over two hours.

dc32f0cfe84def651e0e

GrapheneOS won't survive if Google stops issuing bootloader unlock codes. Sad but true.

llama420

dc32f0cfe84def651e0e Yeah, true. But at that point, they'd just become a worse iPhone. Everything would have to go to Linux if anyone wanted true tech freedom. Basically how the current PC market works.

Probably9857

dc32f0cfe84def651e0e GrapheneOS won't survive if Google stops issuing bootloader unlock codes. Sad but true.

Wrong.

Just to get it out of the way, there is no actual evidence that Google plans to do this. But, for the sake of argument, let's say they do.

1a. Google just released a new series of devices that allow bootloader unlocking, which in itself is evidence that they have no immediate plans to stop allowing it.

If they stopped allowing bootloader unlock for devices purchased with that as an option, they would likely face lawsuits.
Let's assume they aren't bothered about lawsuits. Not great. But every Pixel that already has GrapheneOS can keep using it. For the newest models, that's 7 years. 7 years is a long time to figure out a solution. In the meantime, used devices already running GrapheneOS would command premium prices.
If they only prevent unlocking new devices, that's even better.
GrapheneOS is already negotiating with an OEM to manufacture devices meeting GrapheneOS standards. Google would have no say in unlocking these devices.
Even if the OEM deal fails to work out, there are other OEMs.
If no OEM is willing to cooperate, do you think the project would just pack up and call it a day? This may be considered blasphemy, but I suspect the project would then consider loosening the hardware requirements. They have to be reasonable, after all, and requirements that no phone actually meets cannot be considered reasonable. The requirements have increased in the past as available hardware has improved. It's reasonable that they would relax if available hardware became worse. They aren't set in stone. It is a choice. In different circumstances, a different choice could be made.

MetropleX

This topic is becoming a recurring theme. For further information please search out a pre-existing thread that is still open to continue the discussion I believe everything has been addressed enough here for now.