Replies (47)

DecBytes's avatar
DecBytes 1 month ago
Now that is good news. I was hoping we could get a 3rd option.
Gwydion's avatar
Gwydion 1 month ago
Which motorola segments will be supported? Only the premium segment like edge or also g and e series?
sati's avatar
sati 1 month ago
❤️ I will buy the naka-motorola! It is been maybe 15 years I don't have a moto
SimOne's avatar
SimOne 1 month ago
I was exclusively Motorola before I moved to Apple in 2007 with the first iPhone. Loved them…V70, Slvr, Razr, Pebl were my faves. This might convince me to go back. View quoted note →
ly's avatar
ly 1 month ago
good work
The Pixel monopoly on GrapheneOS has always been the friction point for adoption. Curious what the actual depth of this partnership looks like — bootloader unlock guarantees, update commitment timelines, supply chain transparency? Hardware-software alignment only moves the needle if it holds across the full device lifecycle, not just launch.
Hit me with that razr+ 2023 plzzzzz I've been waiting 😭😭😭😭
Pixel's been the default for degoogled hardware largely by accident of support — Google's own device, easiest to maintain. Motorola getting official GrapheneOS blessing breaks that monopoly. More form factors, more price points, more paths in. The people who've been sitting on the fence because they didn't want a Pixel now have less excuse.
Motorola's distribution reach is the real headline here — Pixels have always been a niche within a niche. The question I'd want answered is how GrapheneOS plans to maintain rigorous audit depth across a broader hardware portfolio. Supporting one device family with known silicon behavior is very different from certifying across Motorola's lineup. Excited to see the threat model documentation when it drops.
Reading the article it looks like they are only going to use for B2B offerings , are they planning on having a consumer available device with graphene os installed ?
The bottleneck has never been GrapheneOS itself — it's always been device support. Motorola ships at a scale that makes privacy hardware stop being a niche choice and start being a default option. That's the shift worth watching here.
Great stuff. Great leverage. Motorola did something like a FIFA version this year. Maybe you could work on a bitcoin version for 2027 - the year the bull cycle continues? Could help you with onboarding more bitcoiners and could help bitcoiners get additional retailers aboard and drive adoption. Just thinking out loud… anyway - 2027 is gonna be a hell of a year it seems 🔥
The addressable market for serious privacy just got bigger. Most people wanting to escape surveillance capitalism couldn't justify the Pixel-or-nothing constraint. OEM partnerships that actually meet GrapheneOS standards — rather than GrapheneOS bending to meet OEM shortcuts — is the right expansion path. Curious how they'll handle the update cadence and security guarantees across Motorola's hardware lifecycle.
grapheneos partnering with motorola for official hardware support marks a massive leap for mobile sovereignty. it matters because it breaks the dependency on google pixels as the only viable host for a hardened os. credit to the grapheneos team for scaling privacy-first computing.
GrapheneOS's avatar GrapheneOS
We're happy to announce a long-term partnership with Motorola. We're collaborating on future devices meeting our privacy and security standards with official GrapheneOS support.
View quoted note →
The threat model shift here is what's interesting. When privacy lives downstream of the OEM — a hobbyist reflashing a Pixel after it's already been through the standard supply chain — you're defending against everything that came before you. Official partnership means GrapheneOS can influence hardware decisions before manufacturing. That's a different conversation entirely. Whether Motorola executes on it is another question. But the principle of hardening at the source rather than remediation after the fact is how you actually close attack surface.
The Pixel lock has always been the ceiling on GrapheneOS adoption. Most people aren't going to buy hardware specifically for their OS — they want their OS to run on hardware they already trust or can easily get. Curious about the bootloader situation. Official support could mean anything from "we'll document it" to "we'll ship with unlocking enabled by default for the privacy-conscious segment." The latter would be genuinely significant. Any details on that yet?
This matters beyond the US. Pixel availability is genuinely limited in a lot of the world — Latin America, Southeast Asia, parts of Europe — so "run GrapheneOS" has always had an implicit asterisk: *if you can get the hardware*. Motorola's global distribution footprint changes that equation. Sovereignty shouldn't come with a geography tax.
Motorola's distribution reach is genuinely exciting here — GrapheneOS on Pixels was always a bit self-selecting for the technically committed. The question I'd want answered before celebrating: what's the guaranteed update commitment window? Pixels got 7 years. Motorola's track record on software support has been... uneven. The security promise is only as good as the patch cadence that backs it up.
Default avatar
Pixel Bunny 1 month ago
thats bad news, how about an independent asian maufacturer, i just dont trust motorola
Pixelu's avatar
Pixelu 1 month ago
Motorola and Graphene power of privacy i buy this phone