There’s more from the GrapheneOS folks here: https://grapheneos.social/@GrapheneOS/117645038299496084
Shocking revelations!
deleted by creator
I was about to upgrade to a Pixel 10 because my Pixel 6 just stopped getting support. If I put Graphene on a Pixel 10 and Google drops support, what would happen? Bricked phone or just no more support?
No more support
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.
what happened to Google’s Don’t be Evil motto? :O
That’s more dead than my hopes and dreams
Locked bootloaders should be illegal.
Locking you out of a device that you have paid hundreds of dollars for 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.
My point is that those restrictions exist on a non-financed plan. Also, computers get sold financed all the time with an unlocked bootloader and it’s not a big problem, I don’t really see how the existence of financed plans justifies the practice.
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.
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
I mean that’s true but like 95% of pixel owners don’t know what a bootloader is
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.
The market share of hacker devs is going to be too small to be relevant.
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.
Linux phones are so behind in security that a hard fork of AOSP would make more sense. Security is the main point.
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’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/
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.
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.
Google has gone full evil now, they want 100% control of our apps and data.
Of course the only Motorola option is $1600, and not available on a $250 moto.
Only option for now but they have stated they will make other phones. I’m glad they are releasing it as there hasn’t been many high end tech phones for GrapheneOS.
Theres a significant hardware difference between $250 phones BTW and these $1600 flagships. Processor, cameras, the quality of the phone body. These features may not be appealing to you but I’m excited. Sort of getting tired of my Pixel 8A and def want the telescoping for birdwatching.
I’m in for one
You can install Lineage OS on quite a few Motorola devices including ones you can get used for dirt cheap.
Do keep in mind that Motorola makes you wait a while after setup to unlock the bootloader. They also have some crazy things in there terms including a clause supposedly preventing you from selling the device
Unenforceable terms are kinda pointless surely? If someone is buying, I can sell it
Technically they could take legal action against you
My guess is they don’t want eBay store fronts popping up with moto devices running alternative operating systems
A strong used market for a device raises the value of that same device. That’s not necessarily a bad thing for a company.
Used devices, especially with alternative OSes, can be bad if your goal is control over the user. In this mode the device is not the product but an infection vector. And you are the product.
mostly because I would buy the fuck out of one unless it was shipping from the 3rd world.
Sure, but they might not allow it to be activated on a different contract or network.
This isn’t news, or surprising.
It’s the first non-Pixel device to actually have the necessary hardware security that Graphene uses. And probably only because they’re working with the GrapheneOS team to have a non-Pixel alternative. Of course the first device with extra hardware will be a flagship.
Looking forward to buying them used in 4 years for $100
$1600 MSRP, which I doubt most will actually pay.
Linux phones are in my dreams. So ready.
You can get a jolla phone right now (or soon when theyve worked through their backlog anyway). It’s pretty great.
Smuggled one into canada, slowly getting it to functional parity. The lack of rcs is rough and the built in browser being so old their own forum reports it as too outdated is a touch silly.
I believe the main issue with RCS is that you need a backend provider, and for now the only option is Google, which the Sailfish devs do not want to use for good reasons.
If they wanted to support RCS they’d either have to spin up an RCS server themselves or find a different third party that can host one.
(this is all from things I’ve read on the forum, I’m not very well acquainted with RCS personally)
My takeaway from the several year old thread is that it’s technically a solvable problem (non-google provider) but requires building it yourself and convincing other providers (again, google) to talk to you at all. So… practically impossible, at least for awhile
Yeah I agree with the browser. There’s (I think) 2 different attempts to have a native up-to-date Firefox, but neither support extensions so I’m personally sticking with IronFox in AAS for now.
Looks cool. Backordered and still pretty expensive ($770 is better than $1600). I wonder if it would work with the corrupt-ass US service providers.
True, it is expensive compared to other phones with similar specs, but you have to consider they’re not ordering parts in nearly the same bulk-sizes as bigger manufacturers. Until Jolla themselves get big, they’re always going to be more expensive than the big brands.
According to their website, it is supposed to, but no specifics.
The Americans on the forum have all reported it did work IIRC, but if you want to be sure you should search here: https://forum.sailfishos.org/
Me too, unfortunately the phones don’t seem to be quite ready.
Yeah, I’ve tinkered on and off with pmOS over the last couple of years but the experience is still pretty rough. It seems like progress in that space is slowly accelerating though, so hopefully it won’t be too long before Linux phones are a little more viable as daily drivers.
There are always used phones, but at that price there won’t be many new ones to ever go on the used market.
Thankfully I’m not forced to buy day 1 or even new.
Pixel is $150-$200 used all day long
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 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.
That’s fair, you were just complaining about something for which you have no constructive input…
right up until you hit this part.
some more ethical/moral, open, and not crafted by a company directly opposed to their goals.
That’s a clear indication of a position, “more ethical” (correct or otherwise) implies an opinion on relative morality.
The general statement is a whole lot of speculation, but that’s the only part that veers in to actual sides.
Feel free to reply to any of the rest of the reply, or just continue to ignore it, that works as well.
That’s a clear indication of a position…
You should simply read my words rather than read something into them.
The general statement is a whole lot of speculation…
You are free to disprove my statements.
Feel free to reply to any of the rest of the reply…
When a significant portion of its merit relies on something I already replied to, then there is no need.
They would have to lower standards in order to support a different phone. That’s the whole point. They’re not sticking it to anyone. Just trying to provide as secure of an OS as possible.
They would have to lower standards…
Except that some context around security is threat model. There are people who view it as a significant security issue to be using Google hardware.
Security cannot so simply be boiled down to a one dimensional axis of more or less secure.
You’re not understanding. It has to do with specific hardware features not available elsewhere. The latest snapdragon SoC will support memory tagging and what-not. Previous generations did not. This isn’t some shitlib corpo looking to make a dollar.
Evidently it’s not for you. Move on.
so, if googledaddy makes changes that no longer allow Graphene to be installed on Pixels, what option do they have?
and if you seriously think that Motorola won’t roll over for a google contract, you’re just lying to yourself.
google has perceived Graphene and all ASOP forks as serious competition, that’s why they are locking boot down.
Does Debian consider Ubuntu to be a competitor?
This is a strange argument. I’m not sure where you’re wanting to go with it.
It’s a pretty big deal that the snapdragon SoC will meet the requirements for a reasonably secure OS.
so, if googledaddy makes changes that no longer allow Graphene to be installed on Pixels, what option do they have?
not much, that’s a large part of the original post…no ?
and if you seriously think that Motorola won’t roll over for a google contract, you’re just lying to yourself.
Oh , absolutely , motorola will capitulate at the slightest sniff of anything touching their bottom line.





















