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. motorolanews.com/motorola-th…

We're aware there's 5 ETH sitting in smart contract with fee revenue from a token someone made. We'll see if we can claim the money safely without a software wallet. If we can't, we'll simply wait until we've moved on to a new multisig hardware wallet setup. It might be years.

We use hardware wallets with split seeds to receive cryptocurrency donations. We aren't sure if we can even claim the money you're talking about. We're not going to gather seed phrases in 1 location, feed it into an Ethereum software wallet and hook it up to some smart contract.

GrapheneOS is freely available to everyone. It's a non-profit open source privacy project. Donations don't come with any personal rewards. The purpose of donating to GrapheneOS is making it better for everyone. GrapheneOS Foundation is non-profit. No one is getting rich from it.

Vanadium version 154.0.8037.57.0 released: github.com/GrapheneOS/Vanadi… 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: discuss.grapheneos.org/d/422… #GrapheneOS #privacy #security #browser

GrapheneOS Messaging version 14 released: github.com/GrapheneOS/Messag… 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: discuss.grapheneos.org/d/422… #GrapheneOS #privacy #security #android

GrapheneOS only uses devices where radio is isolated and unprivileged. Cellular works similarly to Wi-Fi, Bluetooth, GNSS, NFC and UWB. Those run on isolated processors without access to the application processor or OS. Only memory that's explicitly shared is accessible to those.

GmsCompatConfig version 175 released: github.com/GrapheneOS/platfo… 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: discuss.grapheneos.org/d/422… #GrapheneOS #privacy #security #gmscompat

GrapheneOS version 2026091900 released: grapheneos.org/releases#2026… See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread: discuss.grapheneos.org/d/421… #GrapheneOS #privacy #security

Vanadium version 153.0.8010.52.0 released: github.com/GrapheneOS/Vanadi… 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: discuss.grapheneos.org/d/421… #GrapheneOS #privacy #security #browser

GrapheneOS version 2026091700 released: grapheneos.org/releases#2026… See the linked release notes for a summary of the improvements over the previous release. Forum discussion thread: discuss.grapheneos.org/d/420… #GrapheneOS #privacy #security

The account we responded to at nitter.net/GrapheneOS/status/2100… is clearly using an LLM to masquerade as an expert and make inaccurate attacks on GrapheneOS. Our account was blocked alongside their clearly AI generated reply. They should be enabling the "Made with AI" content disclosure.

No, that's not accurate. The cellular baseband is an unprivileged component isolated from the application process and OS. It does not have control over the device. It's similar to Wi-Fi/Bluetooth and the other radios which are all isolated. The OS on the device definitely does matter for containing an exploit to the isolated component. The OS can also reduce attack surface for the cellular baseband which is part of the GrapheneOS feature set. Components having vulnerabilities is nothing new and that's why systemic security protections including isolation, attack surface reduction and exploit protections are important. A firmware patch for this vulnerability is available and currently being tested by GrapheneOS prior to release today.

It's patched in the latest cellular firmware. That will be included in today's GrapheneOS release. We completed a port to Android 17 QPR1 prior to it being released. We were prepared to ship it on launch day with all the Pixel driver/firmware updates. Android 17 QPR1 wasn't pushed to AOSP and we don't currently have permission to ship it without an AOSP release. That means we couldn't ship what we prepared and need to make backports. We posted a thread about it: nitter.net/GrapheneOS/status/2100…

GrapheneOS is partnered with Motorola Mobility which is Lenovo's mobile division. Motorola Solutions is an entirely different company from the one working with GrapheneOS. These companies aren't part of the same business and don't have the same ownership. In 2011, Motorola was split into Motorola Mobility and Motorola Solutions. Google acquired Motorola Mobility in 2012 and sold it to Lenovo in 2014. Motorola Mobility is the company selling smartphones and tablets. Motorola Solutions is a separate company. It's the continuation of the government contract side of Motorola selling radios, cameras and now drones. Both share the same brand for historical reasons but are entirely different things. People regularly get the companies mixed up due to both using the Motorola brand. It's Motorola Solutions making surveillance cameras, not Motorola Mobility. We're only working with Motorola Mobility. We're working with Motorola Mobility on upcoming devices meeting all of our requirements for updates and security protections. These devices will provide official support for GrapheneOS and we'll be provided with everything we need to provide proper updates. The first device with GrapheneOS support will be a very high end flagship but it will expand further from there.