GrapheneOS

Open source privacy and security focused mobile OS with Android app compatibility.

Public Key

npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5

NIP-05 Address

GrapheneOS@grapheneos-social.mostr.pub

Profile Code

nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujuerfw36x7tnsw43qz9thwden5te0wfjkccte9ekk7um5wgh8qatzqyxhwumn8ghj7mn0wvhxcmmvqy2hwumn8ghj7erfw36x7tnsw43z7un9d3shjzm9tls

Publishing to

Author Public Key

npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5

Show more details

Last Notes

2026-01-19 00:07:16 UTC

- reply

@nprofile…2das @nprofile…lp27 @nprofile…9nfu Yes, meant 2026. Fixed it on this side with an edit now but that won't bridge to Nostr.

2026-01-18 23:00:37 UTC

- reply

@nprofile…lp27 @nprofile…9nfu We're partnered with a major Android OEM since June 2025 and they're working towards devices meeting all of our update and security requirements for 2027. There will be 7 years of support, hardware memory tagging and the rest of what we need. It wasn't possible to get it all done for 2027 but there will be an announcement about it in the near future.

2026-01-18 22:59:41 UTC

- reply

@nprofile…lp27 @nprofile…9nfu Here's a lot more information with links to third party sources:
https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private

2026-01-18 19:52:57 UTC

- reply

@nprofile…lp27 @nprofile…9nfu Fairphone is aligned against GrapheneOS through their close partnership with Murena. Murena sells phony privacy products with false marketing including many years of endless false claims about GrapheneOS. Murena is a for-profit owned and controlled by the same people who run /e/ which receives millions of euros in EU government funding to build products for Murena.

2026-01-18 19:50:16 UTC

- reply

@nprofile…lp27 @nprofile…9nfu Fairphones are regular low quality Android smartphones with very poor security at a hardware, firmware and driver level. Fairphone barely does any engineering themselves but rather their ODM partner in China designs and manufactures the devices to be sold under the Fairphone brand. Their hardware doesn't provide reasonable security and we have no interest in it.

2026-01-18 05:59:47 UTC

- reply

@nprofile…5wcy The vast majority of Android apps can be used on GrapheneOS. What makes you think that you can't use German banking apps?
https://privsec.dev/posts/android/banking-applications-compatibility-with-grapheneos/#germany

2026-01-18 00:06:21 UTC

Vanadium version 144.0.7559.76.1 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/144.0.7559.76.1
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/30839-vanadium-version-14407559761-released
#GrapheneOS #privacy #security #browser

2026-01-16 22:38:21 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na Telling people to use TorVPN instead of Orbot is not a recommendation to use Tor. We regularly recommend not routing all traffic in everyday usage profiles through Tor because many exit nodes are malicious. Our recommendation is that if people want to use Tor, they should use it in a secondary profile dedicated to it and use the TorVPN app instead of Orbot.

2026-01-16 22:36:06 UTC

- reply

@nprofile…g2g5 @nprofile…ndew @nprofile…n8na They're saying this because we've been telling people to replace Orbot (unofficial Tor VPN app) with TorVPN (recently launched official Tor VPN app) due to severe issues including security vulnerabilities in Orbot. We're not even recommending Tor as they claim but rather telling people how to use it properly on GrapheneOS when people mention Orbot or Tor.

2026-01-16 22:33:44 UTC

- reply

@nprofile…9q7y It was patched for the stock Pixel OS and GrapheneOS in December 2025.
GrapheneOS has hardware memory tagging (MTE) in userspace and the kernel, doesn't have the kASLR issue documented in the article and has other relevant protections. It's much stronger at defending against memory corruption bugs than the stock Pixel OS.

2026-01-16 13:06:26 UTC

- reply

@nprofile…74am You've lied about our team and participated in the harassment by joining in with the baseless claims of someone being insane, delusional, unhinged, etc. You made public attacks on us based on falsehoods and false narratives. If you had wanted to give constructive advice, you would have done it without the personal insults, lies and clear attempts at directing more hate towards our. It's clear your goal was harming us, not helping us, regardless of how you try to spin that now.

2026-01-16 13:05:16 UTC

- reply

@nprofile…d7qp @nprofile…74am They're absolutely not trying to help. They made a public post attacking our team with false claims and false narratives. They directly participated in the harassment towards our team branding us as unhinged, insane, delusional, etc. If they had wanted to help, they would have posted a non-abusive private message rather than this.
The fediverse is the worst platform for abuse towards our team and we have no issue blocking another couple dozen accounts supporting it.

2026-01-16 13:03:12 UTC

- reply

@nprofile…74am You're not welcome to contact us any further.

2026-01-16 13:02:54 UTC

- reply

@nprofile…74am
> because it's totally impractical to read
You're choosing to go out of the way to read replies rather than our main timeline.
> I'm agnostic about that, and I don't particularly care.
It was already clear you don't care about the well being of the GrapheneOS team and the abuse towards us without you stating it so explicitly. You're actively participating in the abuse in your post above.

2026-01-16 12:47:09 UTC

- reply

@nprofile…74am
> This behaviour makes you look unhinged, and people generally don't trust products made by unhinged people.
Pushing these false narratives and personal attacks on our team closely resembling the ongoing harassment isn't going to be tolerated. You can either quickly remove the post or we'll be permanently banning you from the project and community. It's easy to tell you didn't make the post in good faith as it's not a private message but rather a public attack with personal insults.

2026-01-16 12:37:11 UTC

- reply

@nprofile…74am Murena's products are legitimately scams and have been widely documented as such by actual privacy and security experts. Murena has genuinely engaged in years of misleading people about GrapheneOS. When we finally began countering it, they began attacking our team including engaging in absolutely vile libel, bullying and harassment including spreading Kiwi Farms content. That's a provable fact and we've provided a clear example in this thread. We can provide much more examples of it too.

2026-01-16 12:35:31 UTC

- reply

@nprofile…74am You've made a long public post with extraordinarily inaccurate attacks on our project and team. You may use GrapheneOS but you do not support the project or the team behind it. It makes the highly inaccurate claims you're making about it that much worse. It's you who is participating bullying towards the GrapheneOS team which engaging in typical DARVO tactics presenting an open source project defending themselves from relentless attacks as them being the aggressors. No, you are that.

2026-01-16 11:54:10 UTC

@nprofile…sdzc You created this thread by mentioning us in a post making false accusations towards our team. You many not support any specific alternative to Android but you've chosen to be explicitly against the GrapheneOS project and have attempted to cause harm to it.

2026-01-16 11:49:20 UTC

- reply

@nprofile…sdzc There aren't currently any non-Pixel smartphones providing proper alternate OS support and a reasonable level of security. That's why we've been working with a major Android OEM since June 2025 towards a subset of their future devices meeting our hardware requirements. They were unable to meet the requirements for their initial round of 2026 devices but are getting close and will be able to meet the requirements for 2027. We have a requirements list at https://grapheneos.org/faq#future-devices.

2026-01-16 11:46:24 UTC

- reply

@nprofile…sdzc Aside from that, strongly recommend you stop posting as if you're against neo-nazis when you support Duval who openly links to neo-nazi harassment content towards our team.
We've linked to this proof of it and can link far more, but it appears you'll simply ignore it:
https://archive.is/SWXPJ
https://archive.is/n4yTO
You even started participating it in yourself with direct personal attacks on our team with the typical baseless insults openly mimicking Kiwi Farms.

2026-01-16 11:44:15 UTC

- reply

@nprofile…sdzc Making personal attacks on our team and pushing false narratives about us is the standard approach from Murena and their supporters. We'll put more effort into informing people about their unsafe products in response to it.
Murena is selling products without the most basic privacy patches with false marketing portraying it as highly private. You should do due diligence and read what privacy and security experts have written about it. People are being blatantly scammed by Murena.

2026-01-16 11:39:41 UTC

- reply

@nprofile…sdzc We've provided links to Duval participating in libel, bullying and harassment. We can share far more examples of it happening.
GrapheneOS posts accurate information about Murena's fake privacy products in response to years of their misinformation about GrapheneOS misleading people into believing it isn't suited to them.
Murena is primarily focused on selling people insecure devices and /e/ primarily exists to build the products for Murena to sell. They're not helping people.

2026-01-16 11:37:16 UTC

- reply

@nprofile…sdzc Murena is doing the opposite of providing people with privacy and security. What they're doing is scamming people for profit by selling extraordinarily non-private and secure devices with false marketing. What we're doing is informing and protecting people from being misled into buying unsafe devices without the bare minimum for privacy and security. Posting accurate info about it is completely appropriate. What's not appropriate is misleading people into using an unsafe device.

2026-01-16 11:34:46 UTC

- reply

@nprofile…sdzc You're willfully blind to the many years of attacks they've made on our project and team. You're participating in those attacks both in your top level post and other replies pushing a false narrative about the GrapheneOS project and our team. You've chosen to ignore the links we've provided showing the founder of /e/ linking to harassment content based on fabrications on an overt neo-nazi conspiracy website. Perhaps you support the Kiwi Farms libel/harassment which Duval spreads.

2026-01-16 11:33:00 UTC

- reply

@nprofile…sdzc Security currently has a monetary cost. Most Android devices have atrocious security for the hardware, firmware and drivers regardless of which OS you use. /e/ makes this worse because it has extraordinarily poor privacy and security itself including not shipping standard updates for Android, Linux, the browser engine, drivers and firmware. /e/ is nearly the direct opposite of GrapheneOS, thoroughly destroying the privacy and security of the Android Open Source Project...

2026-01-16 11:22:33 UTC

- reply

@nprofile…sdzc Here's the founder of /e/ and Murena promoting blatant harassment content towards our founder on an overtly neo-nazi conspiracy website:
https://archive.is/SWXPJ
https://archive.is/n4yTO
He was doing this in the context of supporting French state attacks on the GrapheneOS project which has been ongoing due to their crackdown on end-to-end encryption and secure devices. Duval, /e/ and Murena make endless attacks on our project and team including libel, bullying and harassment.

2026-01-16 11:21:11 UTC

- reply

@nprofile…sdzc /e/ and Murena spent years misleading people about GrapheneOS with an enormous amount of false claims about it to promote their OS. We used to leave it up to others to debunk it and many people did including Divested Computing. /e/ targeted Divested Computing with harassment and are a major part of why DivestOS was discontinued. We stepped up to begin defending ourselves from them as their attacks increased and they've targeted our team with extreme harassment because of it.

2026-01-16 11:19:59 UTC

- reply

2026-01-16 11:14:17 UTC

- reply

@nprofile…sdzc It doesn't make sense for GrapheneOS to support insecure devices where it's not possible to properly protect users due to lack of important hardware-based security protections we use as part of our core feature set and driver/firmware patches. The purpose of GrapheneOS is not providing a sidegrade from the stock OS on devices people already have but rather a highly private and secure option. You're better off using an iPhone for privacy and security than other AOSP-based options.

2026-01-16 11:12:06 UTC

- reply

@nprofile…sdzc GrapheneOS faces an enormous amount of inaccurate attacks towards our project and team on this platform from your communites. We'll continue defending ourselves from it. Non-hardened operating systems failing to provide basic privacy/security protections are not competition for GrapheneOS. We wouldn't be talking about them if the project members and their supporters were not attacking us relentlessly. GrapheneOS is a Linux distribution and Linux does not mean systemd/glibc/GNOME.

2026-01-16 11:11:42 UTC

- reply

2026-01-16 00:02:26 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na You should this supposed spynet you claim we promoted instead of vaguely referring to it without naming it. Our interpretation is that you're talking about Tor or Signal, but you aren't being clear. We haven't promoted Tor but rather have told people to use their TorVPN app instead of Orbot because Orbot isn't a secure implementation and has severe issues.

2026-01-15 23:55:55 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na People donating to GrapheneOS receive nothing in return and there's no process of them identifying themselves to us or communicating with us as part of making a donation. Donations involve people unilaterally choosing to send money to us via one of the donation methods. We don't have a choice about who donates and which transactions we receive.

2026-01-15 23:40:58 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na GrapheneOS is already well into the process of a financial audit by an accounting firm which mainly involves verifying that the way the money has been spent matches our official records and that it has been spent appropriately.
All the official donation methods are publicly listed. Most money is donated via cryptocurrency, which is mostly publicly visible.

2026-01-15 23:36:28 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na GrapheneOS is currently only paying developers and has a small development team. Our team needs to be greatly expanded with a lot more experienced developers and also people to manage other aspects of the organization. We currently heavily rely on volunteers.
GrapheneOS is entirely funded by donations from our users/supporters. It has no grants, etc.

2026-01-15 23:34:25 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na Non-Pixel Android OEMs do not provide what's needed to provide competitive security with iPhones, let alone doing much better. Providing a much less secure alternative to an iPhone isn't something we're interested in doing.
Your claims about backdoors are completely unsubstantiated and you'll likely make similar claims about any OEM we work with anyway.

2026-01-15 23:32:59 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na Our hardware requirements are standard updates and security protections, not anything exotic or Pixel specific:
https://grapheneos.org/faq#future-devices
These hardware requirements are to have reasonably secure devices. These are not a list of requirements for an extremely secure hardened device. It's a list of basic standards to have competitive security with iPhones.

2026-01-15 23:24:01 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na GrapheneOS is a privacy and security hardened OS. It doesn't exist to simply provide an alternative option. In order to provide the protections it offers, it requires hardware, firmware and drivers providing the necessary base to build on. Most devices do not have security features we build our core defenses around including hardware memory tagging.

2026-01-15 23:22:49 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na You're bringing up other operating systems which are the opposite of privacy and security hardened. They do not provide standard privacy/security patches and protections let alone greatly improving privacy and security. They don't have hardware security requirements since they're the opposite of security projects and don't use even all standard protections.

2026-01-15 22:59:25 UTC

- reply

@nprofile…jz3q @nprofile…3h4n It does not use GrapheneOS and is not a reasonably private/secure device. It doesn't come anywhere close to meeting our hardware security requirements. It runs an outdated fork of the Android Open Source Project without remotely comparable privacy and security hardening to GrapheneOS. It's based on Android 15 so it doesn't have current standard Android privacy/security patches and protections let alone being hardened like GrapheneOS.

2026-01-15 10:08:52 UTC

- reply

@nprofile…v0s9 In order to have other devices we can support, we're working with a major Android OEM since June 2025 towards their devices in 2027 and later meeting our requirements and providing official GrapheneOS support. This is going well but there's a lot to do. Meeting the requirements means making major improvements over what any non-Pixel Android OEM provides. We aren't going to take the shortcut of using devices without important security features we use and important security patches.

2026-01-15 10:05:04 UTC

- reply

@nprofile…v0s9
1. Pixels are the only smartphones with competitive security with iPhones and the only ones meeting our official security requirements listed at https://grapheneos.org/faq#future-devices. Other devices lack important hardware security features driver/firmware updates needed to protect users.
2. Pixels provide official support for using another OS, full functionality for it and don't void the warranty. The vast majority of smartphones don't allow this.
3. It's the littlekernel-based bootloader logo.

2026-01-15 06:21:26 UTC

- reply

@nprofile…68ls @nprofile…2qq7 We're going to continue expanding the language approach we're using where additional blocklists are added when those languages are enabled. It fits with the overall anti-fingerprinting approach that's being taken by not adding more fingerprinting than the enabled languages for this purpose. We added EasyList Germany support that way but haven't yet expanded it to other languages. We can expand it to the rest of these lists:
https://easylist.to/pages/other-supplementary-filter-lists-and-easylist-variants.html

2026-01-15 05:35:15 UTC

- reply

@nprofile…2qq7
> Give people choices.
You have the choice to use another browser without the same focus as Vanadium which you're already doing. Vanadium is going to remain focused on privacy and security with the same approach as GrapheneOS of doing things correctly even if it takes much longer to add features that way. We're not going to take problematic shortcuts in our projects instead of implementing things properly. Providing improved ad blocking is planned and will be done right.

2026-01-15 05:33:18 UTC

- reply

@nprofile…2qq7
> I have no proof that it has an ad-blocker, and by proof, I mean real-world usage and practicality. Because right now, ads, they're everywhere.
It blocks the majority of ads. It uses EasyList+EasyPrivacy and the vast majority of the network filtering is supported. Which language are the sites you're talking about using?
> I get that you want to lock everything down
Vanadium isn't going to add a feature with a massive negative impact on overall privacy and security.

2026-01-15 03:43:05 UTC

- reply

@nprofile…2qq7 Vanadium already has built-in ad blocking which will continue to be improved. There are no plans to add extensions due to major privacy and security downsides.

2026-01-15 03:42:03 UTC

- reply

@nprofile…2qq7 Vanadium has built-in ad blocking.

2026-01-15 03:04:03 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na Late 2026 to late 2027 is the original timeline we gave for when the devices will be available. Our hardware partner is going to be announcing the partnership soon, so you won't need to wait nearly that long to see they're a huge company that's officially partnered with us and doing most of the work on this on their end. It's not being announced in 2027.

2026-01-14 21:54:59 UTC

Vanadium version 144.0.7559.76.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/144.0.7559.76.0
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/30717-vanadium-version-14407559760-released
#GrapheneOS #privacy #security #browser

2026-01-14 08:29:29 UTC

- reply

@nprofile…qz20 @nprofile…ndew @nprofile…n8na Neither of those provides the standard Android privacy/security patches or protections. They don't keep up with the latest releases and have severe known vulnerabilities unpatched. See https://eylenburg.github.io/android_comparison.htm for a third party comparison but we bear in mind it only covers a small fraction of the privacy/security features we add, and it groups huge sets of features into categories such as hardened libc.

2026-01-14 08:00:25 UTC

GrapheneOS version 2026011300 released:
https://grapheneos.org/releases#2026011300
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/30696-grapheneos-version-2026011300-released
#GrapheneOS #privacy #security

2026-01-14 03:01:09 UTC

- reply

@nprofile…5xuv @nprofile…scwc Nearly the same as the stock Pixel OS since it's based on the open source Android 16 QPR2. It doesn't have the Google features built such as circle to search and copying text from recent apps which aren't part of the Android Open Source Project it's based around.
Most bundled apps aren't currently very good due to being AOSP abandonware but can be easily replaced.

2026-01-14 01:50:30 UTC

- reply

@nprofile…262p @nprofile…4n3n @nprofile…vsjc @nprofile…3udh What's being worked on for the initial gen is the first real secure smartphone alternative to iPhones and Pixels. Doing better than those is possible but will require a lot more investment after proving the business case to them.

2026-01-14 01:49:13 UTC

- reply

@nprofile…262p @nprofile…4n3n @nprofile…vsjc @nprofile…3udh Our OEM partner is making something which hasn't been done before: a non-Pixel Android phone capable of providing a reasonable level of privacy and security through having proper updates and important hardware-based security features.

2026-01-14 01:48:19 UTC

- reply

@nprofile…262p @nprofile…4n3n @nprofile…vsjc @nprofile…3udh GrapheneOS supports all of the currently available devices where we can provide a reasonable level of privacy and security. People are better off with multi year old used iPhones than insecure Android phones with problematic AOSP forks.

2026-01-13 13:10:09 UTC

- reply

@nprofile…a4ar @nprofile…l5k5 @nprofile…e965 We only support devices where these radios are unprivileged and isolated from the rest of the devices. Airplane mode also works properly for cellular. It's not maybe.
That tech blog article openly admits it's based on a product being marketed. The claims are unsubstantiated.
We know older devices didn't provide a working airplane mode and that certain modern ones don't have a persistent airplane mode which applies from early boot, but many devices do.

2026-01-13 12:59:17 UTC

- reply

@nprofile…a4ar @nprofile…l5k5 @nprofile…e965 It works properly for GrapheneOS because it works properly on the devices we support.
Many people have the misconception that cellular is implemented in a significantly different way than other radios which is not the case. Wi-Fi, Bluetooth, GNSS, NFC, UWB and NFC are all implemented similarly whether it's a smartphone, tablet, laptop or desktop. They're implemented on a chip running a separate RTOS, often with multiple radios implemented together.

2026-01-13 12:56:55 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na The reason the devices in 2026 can't meet the requirements is because Qualcomm only finished hardware memory tagging support for the Snapdragon 8 Elite Gen 5 at the last minute but doesn't have it working for the non-Elite variants of the SoC. It's the first SoC they've made with official support for it and there are likely also many issues to resolve.

2026-01-13 12:54:18 UTC

- reply

@nprofile…l5k5 @nprofile…a4ar @nprofile…e965 The only devices supported by GrapheneOS have a working airplane mode which properly disables cellular radio transit/receive including during early boot. Most modern smartphones support doing it properly while booted so that part isn't at all unique to the devices we support. Whether it works properly in early boot varies and has been tested with the devices we support and others where some of the others appear not to implement it properly right now.

2026-01-13 12:51:12 UTC

- reply

@nprofile…ndew @nprofile…g2g5 @nprofile…n8na Our OEM partnership started in June 2025 and work towards meeting the requirements began several months later. We said from the very beginning that the expected launch date was late 2026 or in 2027. We can now be more specific about the date because we know the new Qualcomm SoC platform will come out in Q4 2026 and the devices come out months later.

2026-01-13 12:47:30 UTC

- reply

@nprofile…ndew @nprofile…n8na You're attacking us because we told people to avoid Orbot and use TorVPN instead which is not a recommendation to use Tor but rather steering people away from an insecure implementation. The reasoning you're giving for attacking us is that Tor previously received US greants, but yet you're promoting a project primarily funded by the EU. Unlike Tor, it's not a real non-profit but rather being made to enrich shareholders.

2026-01-12 23:46:25 UTC

- reply

@nprofile…ndew @nprofile…n8na Meanwhile, you're promoting an operating system that's openly supported and funded by the French government and the EU despite their stances against end-to-end encryption, disk encryption and secure devices.
https://www.projets-libres.org/en/podcast/e-os-a-degoogled-android-gael-duval-e-foundation-murena/
> The European Union has subsidized us to the tune of several million for this project.
They have close government ties which is how they obtain this money to enrich themselves via Murena.

2026-01-12 23:40:01 UTC

- reply

@nprofile…ndew @nprofile…n8na
> Just hope one day your suspicious financing runs out and so stops this bullshit.
GrapheneOS is fully funded by donations from our users and supporters. There's no suspicious funding. We haven't received any government grants and don't have business partnerships which are providing us money. We have a partnership with a major OEM where they're making devices meeting our requirements so they can sell more devices.

2026-01-12 23:35:34 UTC

- reply

@nprofile…ndew @nprofile…n8na
> That post shows the warning page.
There's no warning page. The post shows relevant text in the lengthy terms of service for the overall Murena services. Putting something into the terms of service few people read is not obtaining consent. Most awareness of them sending the data to OpenAI is due to the forum threads.
> spynet sponsored by the US government
What are you talking about? Is that a reference to Signal?

2026-01-12 22:53:16 UTC

- reply

@nprofile…ndew @nprofile…n8na
Here's a post from the /e/ forum on them sending sensitive user data to OpenAI without user consent:
https://community.e.foundation/t/voice-to-text-feature-using-open-ai/70509
https://eylenburg.github.io/android_comparison.htm provides an overview of the differences between AOSP-based OSes.
/e/ and LineageOS are forks of AOSP not preserving standard privacy or security. They're not in the same space as a hardened OS.
More info with links to high quality sources:
https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private

2026-01-12 22:48:27 UTC

- reply

@nprofile…g2g5 @nprofile…n8na @nprofile…ndew GrapheneOS does not receive any government funding and is not receiving funding from business partners. Our partnership with a major Android OEM does not involve them sending us money but rather having their engineering teams work on GrapheneOS support. They'll likely end up helping to improve GrapheneOS by publicly submitting improvements to it upstream.

2026-01-12 22:46:34 UTC

- reply

@nprofile…g2g5 @nprofile…n8na @nprofile…ndew GrapheneOS is entirely funded by donations from our userbase. Our userbase includes people like Vitalik Buterin who are providing significant donations. You should read our response:
https://grapheneos.social/@GrapheneOS/115884539052244771
https://grapheneos.social/@GrapheneOS/115884550027291115
/e/ is a non-profit based in France heavily funded by France and the EU despite their issues with secure devices and E2EE...

2026-01-12 22:45:04 UTC

- reply

@nprofile…ndew @nprofile…n8na
/e/ is based in a country where secure devices and end-to-end encryption aren't being tolerated. According to the founder, it's receiving millions of euros in EU funding:
https://www.projets-libres.org/en/podcast/e-os-a-degoogled-android-gael-duval-e-foundation-murena/
/e/ is run by the same people who own and run the for-profit Murena company. They have a non-profit heavily funded by government money which makes products for their for-profit to sell. The government funding is corruption.

2026-01-12 22:42:17 UTC

- reply

@nprofile…ndew @nprofile…n8na
/e/ and LineageOS aren't privacy or security hardened operating systems. Neither provides all the standard privacy/security patches or protections. Neither provides the major privacy and security improvements in GrapheneOS. They're less private and secure than the Android Open Source Project without their changes.
GrapheneOS is fully funded by donations from our userbase rather than grants or business partnerships.

2026-01-12 20:47:26 UTC

- reply

@nprofile…55kg @nprofile…uzlc /e/ and Fairphone don't provide proper updates to the kernel, drivers, firmware or AOSP. They lag years behind and it's not only on a small subset of the patches. Fairphone 4 and 5 are now on end-of-life kernel branches but Fairphone wasn't shipping Linux LTS revisions anyway. They lag behind on doing the absolute bare minimum of shipping Android Security Bulletin patches. In the case of /e/, it claims to have patches it doesn't..
https://discuss.grapheneos.org/d/24134-devices-lacking-standard-privacysecurity-patches-and-protections-arent-private has fair more info.

2026-01-12 20:39:15 UTC

- reply

@nprofile…edud There are upstream issues introduced in Android 16 QPR2 which appear to be causing this for a subset of people with very low storage space.
https://www.reddit.com/r/GooglePixel/comments/1q714rb/7_pro_stuck_in_bootloop/
https://www.reddit.com/r/GooglePixel/comments/1q99jsm/pixel_9_pro_crashes_at_boot/
https://www.reddit.com/r/GooglePixel/comments/1qaa8t9/pixel_8_stuck_on_weird_bootloop/
We're working on a fix for it but need to make special builds for users with the issues.

2026-01-11 23:04:59 UTC

- reply

@nprofile…fkln Each profile has separate VPN configuration rather than it being global. There are VPN service apps which provide support for DoT/DoH/DoQ without an actual VPN. VPN apps don't have to provide an actual VPN and have the ability to replace the system DNS without routing other traffic through themselves. VPN apps can do things like local filtering/monitoring of traffic with or without routing traffic through a VPN, where RethinkDNS is one example of that.

2026-01-11 19:15:42 UTC

- reply

@nprofile…fkln Yes, by disabling Private DNS and using an app for it instead. VPN service apps can provide another DNS implementation without intercepting other traffic to provide a VPN or filtering for that. We recommend setting Private DNS to Off if you use a VPN in any profile anyway. Android didn't properly consider profiles and VPNs when implementing it and it can be done in a more flexible way without it. It's a useful feature but it would be nice if it was per-profile and worked properly with VPNs.

2026-01-11 18:29:58 UTC

Vanadium version 144.0.7559.59.1 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/144.0.7559.59.1
See the linked release notes for a summary of the improvements over the previous release and a link to the full changelog.
Forum discussion thread:
https://discuss.grapheneos.org/d/30591-vanadium-version-14407559591-released
#GrapheneOS #privacy #security #browser

2026-01-11 17:36:30 UTC

- reply

@nprofile…n8na We're working with a major Android OEM. It's one of the top 10 Android OEMs by sales. It's a definitely company you know already. They're hard at work on developing GrapheneOS support for one of their upcoming 2026 devices but it won't be possible to meet the requirements until the next generation, likely in 2027. Snapdragon Elite 8 Gen 5 is currently the only SoC meeting our requirements for non-Pixel devices but that doesn't mean any device using it meets our requirements at all.

2026-01-11 17:34:47 UTC

- reply

@nprofile…n8na It uses a MediaTek Dimensity 7300 with an OS based on the initial yearly release of Android 15.
It doesn't have hardware memory tagging, pointer authentication, branch target identification and other CPU security features. It doesn't have a secure element. It's not going to have proper privacy/security updates. It doesn't come close to meeting our hardware requirements.
It's not running an operating system that's privacy and security hardened. Standard AOSP 16 QPR2 would be better.

2026-01-11 04:05:37 UTC

GrapheneOS version 2026011000 released:
https://grapheneos.org/releases#2026011000
See the linked release notes for a summary of the improvements over the previous release.
Forum discussion thread:
https://discuss.grapheneos.org/d/30465-grapheneos-version-2026011000-released
#GrapheneOS #privacy #security

2026-01-11 02:35:40 UTC

- reply

@nprofile…jc4r @nprofile…ayam Rossmann founded a for-profit T-Mobile MNVO (Phreeli) with the founder of Calyx, who was pushed out of Calyx. Calyx got sabotaged on his way out. It's very ironic considering that's a fake story both pushed about us about the Copperhead takeover attempt which directly led to the creation of CalyxOS by a former Copperhead dev working for them in 2018. CalyxOS users were left without updates and never got the 2025-06-05 patch level. They seem to not have the signing keys.

2026-01-11 02:32:56 UTC

- reply

@nprofile…jc4r @nprofile…ayam We didn't know Rossmann had started using Kiwi Farms, that his politics had wildly shifted and that he was working for a sketchy organization tied to people like Curtis Yarvin. We shared stuff with him we shouldn't have and from early on he was hostile towards our founder in particular and the rest of our team. He was using and supporting GrapheneOS as software. We don't need the $40k FUTO gave us and it doesn't make up for millions of dollars in damages.

2026-01-11 02:32:05 UTC

- reply

@nprofile…jc4r @nprofile…ayam We didn't know Rossmann had started using Kiwi Farms, that his politics had wildly shifted and that he was working for a sketchy organization tied to people like Curtis Yarvin. We shared stuff with him we shouldn't have and from early on he was hostile towards our founder in particular and the rest of our team. He was using and supporting GrapheneOS as software. We don't want the $40k they gave us and it doesn't make up for millions of dollars in damages.

2026-01-11 02:21:26 UTC

- reply

@nprofile…jc4r @nprofile…ayam He was angry we didn't make content with him, angry we didn't quickly accept money from FUTO and promote them but rather required that it be a no strings attached donation and other things. He has an existing issue with us from the start. We privately showed him the video with outrageously false claims clearly aimed at directing harassment towards us because we specifically asked about it due to seeing raids on our rooms, etc. His rooms even got raided for using it.

2026-01-11 02:18:17 UTC

- reply

@nprofile…jc4r @nprofile…ayam He was also clearly not scared to keep using GrapheneOS. He continued using it after all. He only switched to another OS many months later and he did it for perception reasons since people were complaining about him continuing to use it when he said he deleted it. What does he post in his video that you think is damning? He shows someone he has been tormenting with others in distress and trying to get him to stop. He actually got a ton of special treatment but wanted more.

2026-01-11 02:15:30 UTC

- reply

@nprofile…jc4r @nprofile…ayam The email thread he posted included Kiwi Farms being discussed in terms of them harassing friends of the lead developer (at the time) of GrapheneOS. Louis Rossmann was already using the site and consuming their content. He posted videos referencing it. He knew exactly what he was doing by leaking the specific things he did.
The concept of Rossmann being scared of us replying to things he posted about us and therefore feeling he has to go on the offense is nonsense.

2026-01-11 02:12:24 UTC

- reply

@nprofile…jc4r @nprofile…ayam Kiwi Farms became involved because Rossmann has strong support there and actively uses the site with an identity verified account. He made this content using their tactics and approach which caters to them. In it, he's leaking a private chat where he's clearly trolling and feigning ignorance while live streaming it and then doing a monologue lying about all of it. He leaks that the person he's targeting is autistic, leaks other personal info and posted private emails too.

2026-01-11 02:10:39 UTC

- reply

@nprofile…jc4r @nprofile…ayam He had made numerous public attacks in our chat rooms, his live streams and his videos prior to that video. His narrative that it had to do with him posting a comment on a video is nonsense. The video he's supporting very clearly extraordinarily fabricated harassment content, and that's from the person who orchestrated their community harassing us to the point of trying to kill the lead developer of GrapheneOS at the time. That was not Kiwi Farms, it was a small YouTuber.

2026-01-11 02:07:54 UTC

- reply

@nprofile…jc4r @nprofile…ayam After engaging in months of bullying and supporting another person orchestrating harassment towards the lead developer of GrapheneOS, Louis trolled them about the situation in a direct message while live streaming it. Nearly everything he claims is this video is a fabrication or misrepresentation. You should rewatch it and pay close attention to what he's claiming. He didn't even actually stop using it, his subscribers figured out was his daily driver for almost a year after.

2026-01-11 02:07:11 UTC

- reply

2026-01-10 22:55:00 UTC

- reply

@nprofile…4pdc Posting accurate technical information which people find inconvenient to their ideological goals and projects they support isn't toxic. It's not bullying or harassment either. We started off trying to get F-Droid to make major improvements and were met with disinterest and active pushback against it. A couple of their core devs have repeatedly told us they think sandboxing and a permission model including case-by-case consent are useless with open source so they don't care about it.

2026-01-10 22:51:39 UTC

- reply

@nprofile…4pdc Our community isn't targeting people with bullying and harassment. They're also not pervasively spreading inaccurate information about other projects to promote GrapheneOS. We hold people in our community to standards disallowing those things. That includes people criticism of F-Droid, which we expect to stick to accurate claims within our community platforms. We regularly make corrections to criticism of projects from our community members to guide people to stick to the facts.

2026-01-10 22:47:01 UTC

- reply

@nprofile…4pdc The screenshot from Telegram shows a time that core F-Droid developer posted that our founder is insane in a bunch of Telegram rooms. That specific example is from the Aurora Store off topic room. They've similarly spread the harassment content from Kiwi Farms and Rossmann all over the place. We're not blaming them for the actions of their community. The community is following the example set by them. It's easy for us to forgive the random kids trying to support them harassing us.

2026-01-10 22:44:07 UTC

- reply

@nprofile…4pdc
> from what I can tell, the KiwiFarms stuff was posted by a random user
Yes.
> and an F-Droid dev reacted to it without knowing what that is
They likely knew what it is and several of their developers have posted it elsewhere before to promote it.
> You seem to be lumping in the entire community with the dev team for some reason
The 1st example we showed above is one of the core devs calling our founder insane/schizo in 2 separate cases. They've repeatedly linked that video too.

2026-01-10 22:26:20 UTC

- reply

@nprofile…4pdc They've linked to our chat rooms and issue tracker in their chat rooms before and encouraged people to come brigade it with them. The same one posting the insults claiming our founder is schizophrenic, delusional, etc. because they disagree with what GrapheneOS posted about F-Droid security did that. Multiple F-Droid developers later made up a story about the thread we archived at https://archive.ph/j7qql claiming it was a raid on their issue tracker we orchestrated by our community.

2026-01-10 22:24:21 UTC

- reply

@nprofile…4pdc Multiple F-Droid developers have posted links to a Kiwi Farms thread targeting our founder and a similar harassment content on YouTube from 2 people clearly engaging in bullying based around fabricated stories and misrepresentations. The bigger of those two YouTubers is openly a Kiwi Farms user with an active account on the site. F-Droid developers have repeatedly posted this content and supported it. They've also made up fabricated stories about incidents such as what we linked above.

2026-01-10 22:20:48 UTC

- reply

@nprofile…4pdc Several of their developers have regularly posted links to harassment content themselves. Not all of them do it. It was one specific developer who showed up later and removed some of the worst of what was posted. He also acknowledged there was an issue, but choosing to fix it in a special cased way where the warning would be specifically kept on GrapheneOS but not shown on the stock OS anymore. We can detect F-Droid and hide OTHER_SENSORS from it to avoid the warning which is planned.

2026-01-10 22:19:15 UTC

- reply

@nprofile…4pdc You don't need to agree with our concerns about it, but we didn't make it up and what we've said isn't unfounded. We don't think F-Droid is maliciously targeting people right now. However, we don't trust a team with multiple members who regularly share links to harassment content targeting us including from Kiwi Farms along with posting their own personal insults and complete fabrications about things which have happened. The first link we posted is an example of that happening.

2026-01-10 22:17:16 UTC

- reply

@nprofile…4pdc There are several core members of the F-Droid project who we're particularly concerned about due to showing an extreme disregard for user security. There have been multiple cases of reintroducing already fixed vulnerabilities in apps by downgrading dependencies to have support for older build environments and older Android versions. We don't think their build servers are properly secured and they've been known to be running them on Debian oldoldstable and not using the modern tools.

2026-01-10 22:15:50 UTC

- reply

@nprofile…4pdc It was mostly GrapheneOS users making use of secondary profiles. Android added Private Space in Android 15 which is more convenient than secondary users or work profiles so many more people are using at least one secondary profile now.
In 2018, we stopped bundling F-Droid with our OS when we revived the project as part of no longer bundling 3rd party apps and growing concerns about security issues with F-Droid's client, repository system and especially the main repository.

2026-01-10 22:13:00 UTC

- reply

@nprofile…4pdc It happens for apps targeting an older API level where a new permission is assumed to be required and added or an existing permission split into multiple which now need to be requested separately.
We've repeatedly had the experience of F-Droid leaving things broken because it primarily impacts GrapheneOS users. For example, they wouldn't fix the main APK link on their site to use the latest version which causes an error in secondary profiles when a newer one is installed elsewhere.

2026-01-10 22:08:36 UTC

- reply

@nprofile…4pdc F-Droid contributors and community members were already posting abusive messages towards us there prior to us posting a detailed explanation. Once that was posted, it was ramped up. A link to Kiwi Farms style harassment content from a KF user was posted. One of their community members began posting a bunch of AI slop personal attacks clearly largely written with Grok (Elon's AI from x.com). F-Droid left most of the abusive messages up but did remove the link to the harassment content.

2026-01-10 22:04:11 UTC

- reply

@nprofile…4pdc In response to the detailed information which was posted, multiple F-Droid community/project members posted a whole bunch of abusive messages. One of their community members began posting a bunch of AI slop personal attacks clearly largely written with Grok (Elon's AI from x.com). Links to Kiwi Farms harassment content were posted. The abusive comments were not moderated by the core F-Droid team, who have been involved in similar abuse like the example above, which is from a core dev.