There’s more from the GrapheneOS folks here: https://grapheneos.social/@GrapheneOS/117645038299496084
what happened to Google’s Don’t be Evil motto? :O
That’s more dead than my hopes and dreams
This is why my next phone will be running Nura. I have been saying for years that Google was going to attack AOSP based projects, and here it is.
deleted by creator
Does this affect devices with graphene already on them or just the ability to put it on a new device? (I am new)
I’m pretty confident it would just be newer device releases. They might be able to start locking bootloaders on older devices via updates (I think it’s possible), but something already running graphene would be fine.
Lol but that was the only reason to buy a Pixel in the first place. Hacker’s Dev phone.
If they stop selling Dev phones, we’ll stop buying them
The only reason for you and me, but not for most people. Most just wanted a stock android phone that’s similar to iphones in terms of integration.
I mean that’s true but like 95% of pixel owners don’t know what a bootloader is
The market share of hacker devs is going to be too small to be relevant.
Locked bootloaders should be illegal.
Sloppy use of terms in the article. Locked down bootloaders should be illegal.
All new phones come with a locked bootloader, but unlocking codes are delivered on (a few) maker’s website by IMEI. Then the user unlocks it, installs a new OS, some of which can re-lock the bootloader with a new signature, re-enabling verified boot = secure boot, which stops malware from making itself reboot-resistant, and blocks evil maid attacks through the USB port.
The problem with the codes being on the website is that it gives the company control over who can unlock the bootloader
Eh. It’s a bit more complicated than that. Most of the carrier phones are locked because they are given to customers on a financed plan. Unless and until the phone is paid off and all other contract terms are satisfied, then the customer doesn’t actually “own” the device. It sucks, but it does make sense in the context. If you don’t like it, then don’t enter into such agreement. Either buy your device outright or use alternative means of financing which do not impose such restrictions.
They are illegal in Canada.
You should call your representative.
Source?
Bad news: “An unlocked phone works with any carrier’s SIM card. A locked phone only works with the carrier that sold it.”
It means it can’t be locked to a specific phone carrier, not that it can’t be OS locked.
That’s only for SIM locking. Totally different than having an unlockable bootloader.
make non-spyware alternative OS
target hardware is made by same company as spyware OS
What could go wrong?
I remember a conversation from a while back where it was discussed that the graphene devs were asked why they didn’t go all in on a Linux OS instead.
I wonder how much regret they have over making their choice.
Nobody would use it if they used a Linux OS because the whole point of GOS is that it’s a drop-in replacement for Android. Using a Linux phone even in 2026 is a huge commitment.
Yeah, and that’s a fair criticism, but the point is, if they had been working on it all this time, then it may not be such a commitment anymore.
didn’t go all in on a Linux OS instead
This is extremely difficult to do without open hardware or support from major chip manufacturers. You can’t make an open source operating system if you don’t have drivers for the hardware that the operating system is supposed to run on.
You can install non-android Linux on quite a few phones… assuming you don’t need it to work like an actual phone. Things like the modems (the hardware that communicates with cell towers) won’t work without drivers. If they do work, they are usually binary blobs - something akin to black boxes.
Yeah, I agree, the hardware is not there yet.
Hopefully this new bullshit from Google will create a large enough market that it’ll be viable.
What exactly would a Linux phone do better for them? The two main problems for the GOS project are 1. Finding hardware that is up to their security standards, and 2. Google putting increasingly more restrictions into their “security” APIs.
-
On the hardware side, the OS doesn’t matter at all. The main hurdle was their overly strict requirement for security. Whether that standpoint is reasonable or not is not the point here, cause it doesn’t change with the OS.
-
On a Linux OS they would’ve been hit even harder by safety net and hardware attestation checks. They certainly could get basic functionality like calls and SMS to work, but 99.5% of users want to use apps, not just have a dumb phone. Since there is absolutely no marked for Linux phone apps, even with the entire GOS crowd added to the userbase, the only viable solution would be running everything in an emulator like waydroid. Other Linux phone projects already do this, but its worse in security, privacy and usability than even a fairly plain AOSP implementation.
I get the wish for a Linux phone, but AOSP is a fully functional OS even without the Google shit tacked on. There is nothing wrong with using it as a base. The main problem with it is that google stopped adding new features and instead keeps them proprietary. But that doesn’t matter since a Linux phone wouldn’t have these features either, so the development would have to be done either way.
Yeah, I understand the decision that they made and why they made it. I’m just saying hindsight is 20-20, and we would all be in a better place if they had chosen Linux back then.
-

I use Graphene OS and have donated to them, but feel like the Graphene main dev (Daniel/thestinger) is the boy who cried wolf at this point. I don’t doubt that Google may want to diminish or end Graphene, but claiming there is a campaign to interrogate OEMs and warn them against supporting Graphene is something else.
I’ve read the news story and the Graphene forums threads and once again can’t see a single shred of evidence.
A screenshot, an attributed quote… Nothing. Just all the claims of one person, again.
Ah, the classic american pasttime of giving mega corporations that have already proven to screw over their user base over and over again the benefit of the doubt.
Literally said right in my comment that I don’t doubt Google’s may have such motives, I don’t see how that is possibly “giving them the benefit of the doubt”. All I asked for was proof.
If your whole response to someone asking for proof is to attack their character then you really don’t have much to add, especially as you can’t even do it right (I’m not American).
The problem is that if you have proof of Google trying to fuck you over, it’s already too late. I’m saying we prevent said fucking by killing google with anti-trust. Google doesn’t need any defence.
They’re saying that they expect Google to lock Pixel bootloaders, not that they have hard evidence of it.
If you’re going to make claims as to what they’ve said, at least read the article.

Where’s all the evidence that they’ve been reaching out to OEMs? Zero so far.
The terms are true, and they say that an OEM will lose GMS if they sell Android phones without it.
I’d feel bad for Graphene but they were the ones adamant that “pixel phones were the only phones we could support”.
how’s that working out for you guys?
not so good, huh? guess you stomped on your corpodaddy’s balls a bit too hard and they cut you off.
diversify or die.
It was about having that unlocked bootloader and the specific security requirements.
Motorola.
It’s hard for an open source project to maintain multiple hardware lines without maintainers.
I’m honestly not sure this is Google’s plan, regardless. One segment of the company is complaining, while another is supportive. We’ll have to wait till it gets to legal.
They didn’t just choose the Pixel. It was the only phone that met their requirements. You sure sound like a fool.
They chose to create requirements in which the only option was the Google Pixel. Its completely their choice. They could have had different the requirements, but they didn’t.
I don’t know why the language surrounding this debate always gets twisted. GrapheneOS wants to continue following their own requirements which point to Google Pixels only, more than they want to open up and support other platforms, some more ethical/moral, open, and not crafted by a company directly opposed to their goals.
They chose to create requirements in which the only option was the Google Pixel. Its completely their choice. They could have had different the requirements, but they didn’t.
Yes, like airplane manufacturers could have less stringent requirements for the materials with which they build their planes, doesn’t make it a good idea.
I don’t know why the language surrounding this debate always gets twisted. GrapheneOS wants to continue following their own requirements which point to Google Pixels only, more than they want to open up and support other platforms, some more ethical/moral, open, and not crafted by a company directly opposed to their goals.
So your argument is to lower security requirements so they can provide a less secure system in favour of more phone options.
To what end ? Their whole schtick is maximum security possible, there are plenty of alternatives if you want less security (for a given idea of security).
Lowering their security requirements is also directly opposed to their goals, so what is it that you are suggesting as a solution?
It sounds like you know the answer so stop complaining around it and just tell us.
So your argument is to lower security requirements…
I made no such argument. My comment plainly explains my issue with the language around this discussion. It doesn’t take a side nor propose a solution.
I’m so glad Linux phones are becoming a thing. The day my GrapheneOS device dies, I want to keep the same level of control over my phone’s settings, the software that runs on it and what on it is allowed to access the internet or not.
Stock android phones are nothing but thoroughly locked down, enshittified tracking and data mining devices that use your own battery power and data plan to constantly upload data about you and sometimes allows you to use them as smartphones.
We absolutely need non android competitors, preferably multiple different ones.
I’d like to see hard forks of android as well.
Shoes going to pay for it? Even Linux is paid for by IBM and others, we just get the benefits.
Shoes going to pay for it?
No, probably not shoes, but there’s likely a corp that’d be interested in funding something like that.
preferably multiple different ones.
Multiple devices/OEMs: Yes. Fragmented choices of operating systems and app stores: Hell, no
People who would install different OSs on their phone don’t need “app stores”. Monopolistic companies that want to control the OS on your phone need them.
I still remember how hard it was to find and install software on a Mac for the 25 years before Apple made an App Store.
...
Not hard at all. Not even a little bit.
It’s still easier to install software on a Mac without using the app store. But now Apple charges developers even if they’re not using the app store.
It’s still easier to install software on a Mac without using the app store. But now Apple charges developers even if they’re not using the app store.
But running unsigned and unverified apps on macOS requires jumping through hoops.
You can run signed and verified apps easier without the app store. Developers have to pay to get rid of the unnecessary hoops.
Your logic seems hobbled by a rosy bias toward “app stores”, NGL. 😅
People who would install different OSs on their phone don’t need “app stores”.
People who would buy a preconfigured phone that happens to run something else than Android or iOS (like Jolla) wouldn’t be the ones installing a different OS.
i know you specified “stock rom” but let me highlight lineageOS and similar projects may be an alternative for your device: https://wiki.lineageos.org/devices/
Fortunately that’s illegal in Canada, so I guess there will be a lot of US folks buying pixels from Canada in the future
Really?
I cannot wait to get rid of the steaming lump of shit known as the pixel 9, perhaps this will increase its saleability or resale value?
Edit I was very curious about what you said about it’s illegality so I did some research and as far as I can see, there’s nothing illegal about their plans. And they said out right they’re going to roll this shit out in January in Canada 🙃
Oh, apparently that law refers to carrier locking, which isn’t the same thing as bootloader locking.
Oh no, there goes my last reason to buy a Pixel as my next upgrade. Hello Moto!
Google just can’t stop shitting the bed, can they? At this point you might as well buy an iPhone…
If you don’t like Google you are definitely not going to like iphones
Yeah, I’m familiar with iOS/MacOS and definitely prefer Android/Linux, but Google keeps taking away the things that make Android what it is: We’re nearing the point where the distinctions are becoming fewer and fewer.
Android with a locked bootloader and developer verification is still way more open than iOS.
For now.
As if Apple isn’t moving to become even more draconian since years.
Enshittification olympics.
That seems to be true, unfortunately.
Ios macos are 2 completely different things.
Not exactly. iOS and Mac OS are both based on the Darwin core.
Yup, well, mostly different anyways but not completely: They’re part of the same ecosystem and both kinda based on BSD.
they are enforcing thier verification in Janaurary so im not surprised.
knock knock oem its the google inquisition are you hiding any grapheneos here

















