GrapheneOS is not based in the US and never has been. It was started in Canada back in 2014 and our main infrastructure is still in Canada. Our non-profit for funding and protecting the open source project was created in Canada too. There aren't any reasonably secure devices which aren't heavily using components from American companies including Qualcomm so it's not clear what people expect to do about that unless you want to move to nearly fully Chinese devices.

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.

> 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.

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

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.

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.

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.

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.

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

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.

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.

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.

It doesn't take long. You have some kind of issue with USB connectivity where it's not detecting the device again after reboot. This can be caused by another application interfering. You should try doing it from another device as an easy way to work around it rather than figuring out which software is interfering or what's wrong with the USB connectivity.

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.