pull down to refresh
Update for somehow anyone still seeing this: This is a pretty bad article, but for the sake of SN I am keeping it up. :)
This functionality will not be in GrapheneOS at all. If it is pushed into AOSP we will just take it out.
If Motorola chooses to in their stock operating system, it's a different thing unrelated to us.
Moto Analytics are unrelated Enterprise device management features for businesses with fleets of work mobile devices. They are announcing separate things in the same article and this will not be in GrapheneOS at all, this is including the builds for Motorola devices.
They can choose to make their own device management apps for this if they wanted, but it's a different thing and wouldn't be included in GrapheneOS. No one here should be Stacker News'ing on their work phone (I hope).
This tweet was about potential ideas for future devices. We haven't confirmed such a thing.
This site frequently releases sloppy articles. It's not the first time.
No idea why these articles always try and reference a criminal case to attempt to make us look bad and responsible, when the example is always someone caught red handed, arrested and being charged. We also can't know who any users are because it's an open source project anyone can change the code and run their own version of... Shocking! Doesn't sound like we are enabling any crime to me if theyre being caught. Maybe they should ask the same questions to the teams of Android, LLVM or Linux who make most of the code.
The moment police IT specialists tried to extract data from it, the device mysteriously reset itself.
There is no feature that just 'mysteriously' resets itself. The only feature is the duress password, which is an overt and well documented feature. This is not characteristic of GrapheneOS. If there is an app doing this, ANY Android device can do it.
“When this system is present on a mobile phone, it is a clear indicator of technical sophistication and an intent to conceal,”
Or that they are a important or at-risk individual with additional security needs other commercial off the shelf device and operating system setups aren't providing? Why do they make malicious assumptions?
Is enabling Lockdown Mode on your iPhone also an intent to conceal?
One distinctive feature of GrapheneOS: you can get it both on the darknet and on mainstream websites. Police have also detected specialized forums, darknet chat rooms, and unlisted YouTube channels that promote it.
Anyone getting GrapheneOS from "unlisted YouTube channels" and the "darknet" lacks reading comprehension. Whatever these are, they aren't by us and would be an infringement on our trademarks. We have a public chat bridged to many mainstream platforms and a surface web site... Not to mention we ban anybody suspected of being involved in anything universally considered criminal activity.
Note they kept talking about us like we are a business selling a product. We aren't a business and aren't selling anything.
The software can erase all data on the phone by displaying, for example, a fake Snapchat screen when a cyber-investigator tries to access its memory or decrypt it.
Not even a GrapheneOS feature. Completely made up attribution. If there's an app doing this, then again, any Android device applies.
We have contributors around the world as it is an open source project. GrapheneOS was founded by a Canadian and the non-profit GrapheneOS Foundation is registered in Canada.
You can see from our releases page that releases with the patches have their own separate channel. Versions ending in 01, 03, 05 [..] are security preview variants. Their changelogs are separate by listing the CVEs patched in that version.
I'm pretty sure this means Graphene security patches become not-open-source until about 3-4 months after they actually release them (correct me if I'm misunderstanding this).
These are strictly Android's upstream patches, not our patches or any code that we create. We only have access to these through a new OEM partnership. They're simply an opt-in for people who want to benefit getting all of these patches the moment they are made, rather than waiting for a quarterly release like every other Android OEM / distribution will do. If you don't want to run embargoed code, then you'll just wait like everyone else / how we used to wait for patches before this month.
Standard GrapheneOS is completely open source and reproducible. This is simply a separate addition to a standard GrapheneOS install and that's why the first boot will give you the choice to do so. We recommend security patches for obvious reasons.
We openly call out people to try and download our update packages to reverse engineer them and review any changes. People can make their own code which standard GrapheneOS and other Android distributions can get earlier. We have source code access but we cannot disclose it ourselves.
What we do and any additions we make are totally open source and will remain that way.
I am for having that stricter search from the past. Makes searching a post about a certain thing on a common word harder for me. Also made me take extra steps when I need to do help/support replies about GrapheneOS as I didn't always see who was discussing at first.
GrapheneOS is focused on privacy, the security benefit isn't mutually exclusive. There's a lot of privacy features for per-app privacy like Storage and Contact scopes, sensors and network permission toggle for apps and other features like per-connection WiFi MAC randomization for the OS. Unlike CalyxOS we also are not connecting to Google services by default, which they do for their connectivity check, DNS check, network time, hardware and DRM attestation services. Their MicroG service also runs with privileged access and isn't sandboxed.
Posted a link to a comparison table at: #1065801 that explains things, but there's a lot more to it.
OP should be aware CalyxOS development is officially halted and they no longer officially provide any instructions for new installs.
https://calyxos.org/news/2025/08/01/a-letter-to-our-community/
If they want a comparison, they can check out:
People employed at these organisations have been going to news organisations claiming that when they see a Pixel phone, they think it's a drug dealer (insane and ludicrous hyperbole) and that it is apparently our fault.
Since then, numerous news sites in different languages have been posting that, mainly repurposing the same talking points. It's just a news campaign trying to claim we are enablers of illicit activities.
In a swing of irony, here's an article from Citizen Lab on how the same Spanish government used exploits against political opponents in Catalonia:
Bear in mind that even police using these will almost entirely be using them against people not convicted of a crime based on suspicion. GrapheneOS would have been more likely to protect them.
I work for GrapheneOS but I'm not a developer, it would conflict with other stuff and I don't do any Kotlin app development. That may change soon. As it stands GrapheneOS has 10 developers, at least 7 of them work as full time developers who the Foundation pays. There's also GrapheneOS Foundation staff, OS support, and some volunteer community mods.
Usually I help the team with matters to do with support, or any discussion about forensic kits like Cellebrite. I also help proof the more technical posts like #774701 #670170 and #455267.
I may be partially to blame with their interest in posting on Nostr... but it needs to be done right.
I announced the device here:
nevent1qqsqqqqzgw787paa22nwu66m4m3cj8vxfy85u63ngcfwlpquu0cvg9qzt88gy
It's a very flagship smartphone. It has been mentioned on our social channels for a while that it will be the case. Leagues better processor, GPU, Display, Camera, almost everything from most of the supported Pixels overall.
Eventually other phones will be supported, and as these flagship processors become previous-gen stuff, you should hopefully see cheaper phones in the far future as well... this is not something guaranteed though, and there are still 'a' Series Pixels for people who don't want to open the pockets for this.