Reflecting on this, likely given the poster, bait tweet, but a good discussion to be had: You should be free and able to use what you want. What's not valuable to somebody may be valuable to somebody else. I'm a complete nobody with a normal life and I use GrapheneOS, Monero, I2P, LUKS etc. like this picture says. However, there is a different conversation to be had that you could use this same image with. Many people treat software choices like a subculture purity test. Software choice is treated like Console Wars or sports teams. There are certain groups of people who use things simply to be performative rather than just being honest that it is a preference. It serves no relevance in their threat model to use what they have to (counterargument: threat model doesn't need to be your sole reasoning to use something anyway). Some like to believe you need to be part of a certain group and you need to follow the rest of the trends of that group to fit in. Used Linux? Now you got to use Firefox. It's fine to say GrapheneOS is superior to something (we say that a lot). What is not fine is believing you are a superior person for using it, same with any other software. Classical FSF bros, Reddit users, and performative activists stink up discussions like skunks with this attitude. Every major project has this problem. If I had to TLDR this, then: Don't be sheep. Use everything in your preference, not to just reflect looking like others. You shouldn't see all these and be like "I want to use all of this!!", because really, you likely do not. image
It isn't a usual happening when an alleged career criminal cries about how he was charged with premeditated murder on social media in your comments while, incorrectly and without a smidge of evidence, blaming us for it. Back to your scheduled #GrapheneOS WINNING. Keep your eyes open for GrapheneOS based on Android 16 QPR2. View quoted note →
GrapheneOS news boring tiday, here is an OpSec of the year 2025 late contender. This is an update of that guy who falsely claimed GrapheneOS was compromised by law enforcement. He posted a document showing a warrant for **premeditated murder** and claimed we were to blame despite zero evidence of a device being exploited or even data of ANY device being accessed. The content they post across social media regularly implicates themselves in crimes they supposedly commit. They're now claiming that despite previously claiming GrapheneOS is insecure, they were using it and blame it for supposedly being charged with premeditated murder. The whole thing appears to be a very badly run smear operation targeting GrapheneOS. They're trying to portray GrapheneOS as heavily used by criminals while also portraying it as insecure. Despite claiming it's insecure, they supposedly keep using it and getting caught due to it. In their new story, they claim to have fled Belgium due to premeditated murder charges. They blame GrapheneOS as they claim the only way they could have been caught is Threema messages on the device. They claim the duress PIN feature many people have tested didn't trigger. They've been making claims about GrapheneOS supposedly being compromised or insecure for a while. It's quite strange for them to now come out with the claim that they were relying on it to store incriminating messages for plotting a murder. Incredibly strange thing to admit on X. If all of what they're saying is taken at face value, then they appear to be a career criminal who scams for people for a living and has gotten themselves into something darker. They have atrocious legal representation. If what they've said is true, they should go back to Belgium and turn themselves in. They've made it pretty clear they have incriminating evidence on their phone they tried to wipe but misremembered the duress PIN. They ASSUME their phone was exploited to get it with no proof. They claim to have an active investigation into themselves for murder. They claim to have tried to destroy incriminating evidence and fled the country. If it's real, their opsec approach is extraordinary. We think it's someone investing many months into smearing us this way.
Bear in mind there are a few major tasks: Priority will be made to work on completing porting to Android 16 QPR2 and then further work on the Pixel 10 to get it out of experimental. Major version upgrade is the most important. View quoted note →
#GrapheneOS version 2025120400 released. - full 2025-12-01 security patch level (has already been fully provided by our security preview releases for at least a month and most of the patches since September) - add experimental support for the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold (there were 2 standalone experimental releases prior to this via 2025112500 and 2025113000 along with corresponding security preview releases for each) - Cell Broadcast Receiver: switch back to our modified text for the presidential alerts toggle - kernel (6.1): update to latest GKI LTS branch revision including update to 6.1.158 - kernel (6.6): update to latest GKI LTS branch revision including update to 6.6.116 - kernel (6.12): update to latest GKI LTS branch revision including update to 6.12.60 - Auditor: update to version 90 - Vanadium: update to version 143.0.7499.34.2 - GmsCompatConfig: update to version 165 All of the Android 16 security patches from the current January 2026, February 2026 and March 2026 Android Security Bulletins are included in the 2025120401 security preview release. List of additional fixed CVEs: - Critical: CVE-2025-48631, CVE-2026-0006 - High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2025-22420, CVE-2025-22432, CVE-2025-26447, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634, CVE-2026-0005, CVE-2026-0007, CVE-2026-0008
I must be the greatest Windows user to have ever lived because every single major breaking bug that shows up on tech news every week has never happened to me. I have never seen it, never heard of it. Keep in mind I use Windows pretty often on corp PCs...
final.st
Android 16 QPR2 is out upstream and is pushed to AOSP. Work will be made to port once all the remaining sources have been pushed. This will take time to fully port as we had just previously ported QPR1, another major version, which was delayed in release.