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

nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz2mhwden5te0wfjkccte9ekxjcn9wfhx2apwv9c8qtm2w4kxjet594ax2mnfw35z66mfd3hsxncqnf

Publishing to

relay.mostr.pub

relay.libernet.app/juliet-zenith-kilo

Author Public Key

npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5

Show more details

Last Notes

2026-10-26 02:40:42 UTC

GrapheneOS TalkBack version 23 released:
https://github.com/GrapheneOS/TalkBack/releases/tag/23
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/43100-grapheneos-talkback-version-23-released
#GrapheneOS #privacy #security

2026-10-24 22:31:56 UTC

GrapheneOS Messaging version 17 released:
https://github.com/GrapheneOS/Messaging/releases/tag/17
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/43079-grapheneos-messaging-version-17-released
#GrapheneOS #privacy #security #android

2026-10-23 17:52:29 UTC

GmsCompatConfig version 178 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-178
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/43045-gmscompatconfig-version-178-released
#GrapheneOS #privacy #security #gmscompat

2026-10-22 21:21:32 UTC

Our latest OS release moved to using the Linux 6.18 LTS branch for both arm64 and x86_64 for the emulator, Cuttlefish and microdroid targets. We've made a highly experimental port of the Pixel kernel drivers to 6.18 and are planning on moving to it across all supported devices.

2026-10-22 21:17:46 UTC

Google made a change to their RCS service breaking using it for a small number of users. It's likely in the process of being rolled out and is gradually causing issues for more users. We're already working on resolving it. It isn't caused by the OS update about to move to Stable.

2026-10-22 10:14:16 UTC

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

2026-10-21 08:21:51 UTC

Our discussion forum is the only software we have using PHP. We've taken it down temporarily while waiting for the patches for https://www.php.net/archive/2026.php#2026-10-20-1 due to vulnerability details already being available and proof of concept exploits being developed. Don't want to take the risk.

2026-10-21 07:03:27 UTC

Vanadium version 156.0.8078.47.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/156.0.8078.47.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/42992-vanadium-version-15608078470-released
#GrapheneOS #privacy #security #browser

2026-10-20 21:15:03 UTC

@nprofile…8qru @nprofile…zlze This doesn't contradict anything. Motorola Trademark Holdings is a wholly owned subsidiary of Motorola Mobility, not Motorola Solutions. It's not Motorola Solutions which owns the trademarks but rather Motorola Mobility. Motorola Solutions has a limited license to use the trademarks in certain fields where they had existing products. Lenovo can freely use the trademarks for anything they want including fields where Motorola Solutions uses them. Read the linked SEC filing.

2026-10-20 00:49:21 UTC

GmsCompatConfig version 177 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-177
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/42964-gmscompatconfig-version-177-released
#GrapheneOS #privacy #security #gmscompat

2026-10-17 17:38:36 UTC

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

2026-10-16 07:07:03 UTC

Vanadium version 155.0.8059.84.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/155.0.8059.84.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/42852-vanadium-version-15508059840-released
#GrapheneOS #privacy #security #browser

2026-10-14 03:22:20 UTC

Vanadium version 155.0.8059.79.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/155.0.8059.79.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/42801-vanadium-version-15508059790-released
#GrapheneOS #privacy #security #browser

2026-10-08 21:45:57 UTC

Vanadium version 155.0.8059.39.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/155.0.8059.39.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/42679-vanadium-version-15508059390-released
#GrapheneOS #privacy #security #browser

2026-10-08 21:43:49 UTC

2026-10-07 20:35:19 UTC

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

2026-10-05 03:53:58 UTC

GmsCompatConfig version 176 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-176
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/42570-gmscompatconfig-version-176-released
#GrapheneOS #privacy #security #gmscompat

2026-10-04 15:56:34 UTC

Android Security Bulletins have been twisted into a way to mislead the public about security. Patches are only listed in the bulletins 2-6 months after they're disclosed to each Android OEM and allowed to be shipped. Patches listed in the September 2026 bulletin were available to ship for months.

2026-10-04 04:46:01 UTC

Vanadium version 154.0.8037.126.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/154.0.8037.126.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/42548-vanadium-version-154080371260-released
#GrapheneOS #privacy #security #browser

2026-10-03 03:48:19 UTC

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

2026-10-02 15:56:00 UTC

Android 17 QPR1 was released for Pixels on September 15. It has a regression in the Pixel kernel driver tree causing stuttering, lag and outright freezes under memory pressure. It impacts GrapheneOS too since we updated the firmware/drivers but we fixed it for our release today.

2026-10-02 01:29:06 UTC

Earlier today, ARIN fulfilled our request for an IPv4 /22 via their IPv4 Waiting List. We now own the following IP space:
2602:F4D9::/36
23.149.124.0/24
23.149.125.0/24
206.220.120.0/22
Our initial 2x IPv4 /24 were quickly obtained via NRPM 4.10 for our ns1 and ns2 anycast DNS.

2026-09-30 23:07:27 UTC

GrapheneOS Messaging version 16 released:
https://github.com/GrapheneOS/Messaging/releases/tag/16
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/42469-grapheneos-messaging-version-16-released
#GrapheneOS #privacy #security #android

2026-09-30 00:38:47 UTC

Vanadium version 154.0.8037.92.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/154.0.8037.92.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/42431-vanadium-version-15408037920-released
#GrapheneOS #privacy #security #browser

2026-09-27 18:46:11 UTC

Our massive overhaul of the AOSP Messaging app has reached the Stable channel in our App Store after 3 releases. It's well on the way to becoming our own high quality GrapheneOS Messaging app instead. There are still parts of the interface to overhaul including widgets and important features to add.

2026-09-27 00:31:10 UTC

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

2026-09-26 20:05:06 UTC

GrapheneOS Messaging version 15 released:
https://github.com/GrapheneOS/Messaging/releases/tag/15
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/42345-grapheneos-messaging-version-15-released
#GrapheneOS #privacy #security #android

2026-09-25 09:34:00 UTC

Vanadium version 154.0.8037.57.1 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/154.0.8037.57.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/42299-vanadium-version-15408037571-released
#GrapheneOS #privacy #security #browser

2026-09-23 20:50:05 UTC

Vanadium version 154.0.8037.57.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/154.0.8037.57.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/42260-vanadium-version-15408037570-released
#GrapheneOS #privacy #security #browser

2026-09-22 20:24:26 UTC

GrapheneOS Messaging version 14 released:
https://github.com/GrapheneOS/Messaging/releases/tag/14
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/42224-grapheneos-messaging-version-14-released
#GrapheneOS #privacy #security #android

2026-09-22 03:38:38 UTC

GmsCompatConfig version 175 released:
https://github.com/GrapheneOS/platform_packages_apps_GmsCompat/releases/tag/config-175
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/42201-gmscompatconfig-version-175-released
#GrapheneOS #privacy #security #gmscompat

2026-09-20 13:58:12 UTC

We need the person who recently sent a 1000 EUR donation via Wise to contact us via email with their full name so we can get Wise to unfreeze the payment. We regularly run into this issue with Wise but it's usually for small donations such as a 5 EUR one which got returned today.

2026-09-11 18:14:25 UTC

The overhauled GrapheneOS Messaging app is available in our App Store via the Alpha channel.
Our new app development team worked on this for months. It's now a far better app with much higher quality code. We'll make a new release based on feedback soon.
https://grapheneos.social/@GrapheneOS/117253697387837898

2026-09-11 17:57:15 UTC

GrapheneOS Messaging version 13 released:
https://github.com/GrapheneOS/Messaging/releases/tag/13
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/41906-grapheneos-messaging-version-13-released
#GrapheneOS #privacy #security #android

2026-09-11 11:51:59 UTC

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

2026-09-09 04:42:34 UTC

Vanadium version 153.0.8010.36.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/153.0.8010.36.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/41830-vanadium-version-15308010360-released
#GrapheneOS #privacy #security #browser

2026-09-08 03:34:14 UTC

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

2026-09-06 19:25:13 UTC

We've developed a secure paste feature replacing traditional clipboard APIs. Users will be able to take away clipboard access from apps to use this instead. It integrates into the standard selection toolbar, input methods, accessibility services and keyboard shortcuts. We plan to get it merged soon.

2026-09-06 18:35:10 UTC

We're well into the process of rewriting the Messaging app included in GrapheneOS into a modern app. We'll be making a new release of it later today with a completely overhauled user interface written in Android Compose. We've made a massive amount of other improvements and bug fixes to the app too.

2026-09-06 07:36:42 UTC

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

2026-09-05 06:46:34 UTC

GrapheneOS is partnered with Motorola Mobility which is Lenovo's mobile division.
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.

2026-09-05 06:26:31 UTC

Vanadium version 152.0.7977.84.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/152.0.7977.84.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/41725-vanadium-version-15207977840-released
#GrapheneOS #privacy #security #browser

2026-09-03 18:20:17 UTC

We're aware of claims spread on German social media about GrapheneOS being exploited. We looked into it in case there was substance behind it. OS and hardware security isn't actually much of a factor in the story. Instead, the central claim is disk encryption with a strong passphrase can be cracked.

2026-09-03 06:20:43 UTC

Our replacement 9950X3D from AMD arrived today and is working well. RMA process took a bit under 2 weeks. It was sent back on the same day they provided a prepaid shipping label. It's a common issue with Ryzen 9000 X3D chips and they simply accepted it without questions.
https://grapheneos.social/@GrapheneOS/117129561025135382

2026-09-02 02:31:26 UTC

Vanadium version 152.0.7977.75.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/152.0.7977.75.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/41660-vanadium-version-15207977750-released
#GrapheneOS #privacy #security #browser

2026-09-01 04:57:14 UTC

We have good news about the Pixel 11. It still has at least bare minimum support for MTE at a hardware level. We think they removed most of the hardware acceleration from the CPU cache to save money. They ruined the performance so it ended up being fully disabled in firmware. It may still be usable.

2026-08-30 19:49:09 UTC

Near the end of May 2026, Russia began filtering access to DataPacket IP space with an enforced domain allowlist for HTTP and TLS SNI. GrapheneOS services aren't on the allowlist so we had to switch from DataPacket Frankfurt to Cherry Servers Amsterdam for Russia. That's now getting filtered too.

2026-08-30 19:48:18 UTC

Near the end of May 2026, Russia began filtering access to DataPacket IP space with an enforced domain allowlist for HTTP and TLS SNI. GrapheneOS services aren't on the allowlist so we had to switch from DataPacket Frankfurt to Amsterdam Cherry Servers for Russia. That's now getting filtered too.

2026-08-29 14:19:30 UTC

We have a partial port of GrapheneOS to the Pixel 11 series after a week of work on it. We're unable to complete the port due to lack of support for ARM hardware memory tagging in software, firmware and near certainly hardware. It appears Google cut an important security feature to save money.

2026-08-25 10:24:50 UTC

- reply

As we said in the first paragraph, our initial focus is on a non-folding device. We haven't provided a timeline on when we'll be able to expand to folding devices. This thread was published to clarify people should expect a non-folding device first despite media speculation.

2026-08-24 18:08:52 UTC

AppCompatConfig version 8 released:
https://github.com/GrapheneOS/platform_packages_apps_AppCompatConfig/releases/tag/8
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/41432-appcompatconfig-version-8-released
#GrapheneOS #privacy #security

2026-08-23 18:59:18 UTC

- reply

@nprofile…s7qu That's likely the issue. We made it easier for companies to automatically add the new ones by adding a signed JSON file providing them.
https://grapheneos.org/articles/attestation-compatibility-guide

2026-08-23 16:07:32 UTC

- reply

@nprofile…s7qu Did you try the per-app exploit protection compatibility mode?

2026-08-22 23:29:40 UTC

- reply

@nprofile…p5t6 No, but a device implementing these requirements well would also implement any unlisted requirements in practice. We included requirements for all of the main disqualifying issues with non-Pixel devices in this list. Quality of implementation matters too but that's hard to put into a requirements list in an objective way.

2026-08-22 17:49:01 UTC

- reply

@nprofile…xawl The current generation Motorola devices don't meet our requirements. It's a subset of the next generation ones which will meet our requirements. We pointed to the Motorola Signature (2026), Razr Fold (2026) and Razr Ultra (2026) as an example of what's coming. The current Signature is the predecessor to the upcoming device we're working on them with and we should be able to support the horizontal and vertical folding flagships with very similar hardware to that afterwards.

2026-08-22 17:00:26 UTC

- reply

@nprofile…ledj @nprofile…86nn @nprofile…nqv0 Our users often import Pixels to other countries and in some of those they still have those features marked as disabled for most carriers. The features usually work when simply force enabled so we added a way to do it. It's not forced by default since it may not work and we don't want to have broken mobile data and calls by default. It works with most carriers without those already enabled and users can easily figure out if it works with basic testing.

2026-08-22 16:58:53 UTC

- reply

@nprofile…ledj @nprofile…86nn @nprofile…nqv0 It works well with it.
By default, GrapheneOS works with all of the carriers supported by the stock Pixel OS. GrapheneOS adds a carrier overrides feature usable to force the availability of 5G, VoLTE, VoNR, VoWiFi and cross-SIM calling. This means GrapheneOS can be used with those features on carriers in countries where Pixels aren't available and haven't done compatibility testing to mark those as available. It makes it work better globally.

2026-08-22 16:51:17 UTC

- reply

@nprofile…kj8p We want it to be possible to buy the regular variant of the devices and install GrapheneOS on those to avoid depending on the availability of devices sold with GrapheneOS. These details all need to be worked out once it's closer to ready.

2026-08-22 16:50:26 UTC

- reply

@nprofile…0hzt We plan to support it and also plan to make it possible to use their camera app similarly to how we support using Pixel Camera.

2026-08-22 16:45:52 UTC

- reply

@nprofile…ajc2 If you use a strong passphrase as the primary lock method then you don't depend on the secure element rate limiting. A secure element exploit cannot make disk encryption less secure than it would be without the secure element. It authenticates with the secure element with a hash of the key to obtain a token stored there which is used as an extra input to key derivation. It only adds security and it's crucial for most users.

2026-08-22 16:43:13 UTC

- reply

@nprofile…ajc2 The main benefit of the secure element is having aggressive rate limiting for encryption key derivation attempts. Only 20 unique attempts are permitted for each profile to derive the key encryption keys with rapidly increasing delays between those. This being implemented by the secure element means an OS exploit or tampering with the main SoC/memory cannot bypass it. The feature cannot reduce security due to how it's integrated.

2026-08-22 16:40:48 UTC

- reply

@nprofile…ajc2 The Linux kernel feeds in more entropy over time and doesn't stop. It's only during very early boot where miscalculating how much actual entropy was added can cause issues. By the time people get to the lockscreen, a massive amount of entropy has been generated. In practice it's only the early boot kASLR base, ASLR bases, stack canaries, heap canaries, etc. which could be poor. The firmware gives an early random seed though.

2026-08-22 16:39:23 UTC

- reply

@nprofile…ajc2 If COLDCARD had used the secure elements to get random data, it wouldn't have had the disaster it did. The Linux kernel provides the main CSPRNG on the devices we use and it uses as many randomness sources as it can to feed into the CSPRNG without trusting those sources. It uses cryptographic hashes for this so it doesn't matter if one of the sources is very poor. It generates a ton of the entropy itself via timing jitter, etc.

2026-08-22 02:55:20 UTC

Vanadium version 152.0.7977.54.1 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/152.0.7977.54.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/41371-vanadium-version-15207977541-released
#GrapheneOS #privacy #security #browser

2026-08-22 02:31:40 UTC

- reply

@nprofile…mxxt Used Pixel 8a and Pixel 9a are what we're recommending to people as budget devices. It's also possible there are cheap Pixel 8 devices available too. They've got tons of update support time remaining so we can keep recommending them for quite a while. We'll likely stop recommending them once they reach only 3 years of updates remaining but they're nowhere close to that yet.

2026-08-22 02:29:17 UTC

- reply

@nprofile…mxxt Pixel 'a' series devices get 7 years of updates from launch. Pixel 8a launched in May 2024 so it has updates until at least May 2031. Buying a used 'a' series Pixel can be as cheap as those but comes with proper updates and security protections.
Pixel 8 and later meet our full set of official security requirements including hardware memory tagging and a very good secure element with everything expected. That includes the Pixel 8a. 6th/7th gen Pixels aren't recommended anymore.

2026-08-22 02:04:54 UTC

- reply

@nprofile…mxxt Pixel 10a base price is $499 and it's often on sale for 15% off. It has the same 7 years of support from launch as the flagship devices. Older 'a' series devices are often available very cheaply on sale. It's not currently feasible to provide a competitive budget option with strong security. We'll still have Pixel support and for now those are the budget option via the 'a' series especially by getting used devices.

2026-08-22 02:03:25 UTC

- reply

@nprofile…mxxt Only once those can provide at least 5 years of proper updates, hardware memory tagging, proper secure element integration and the other requirements.
Qualcomm has the best security features and most modern code for the flagship chips. It takes time for it to trickle down to the lower end chips.
Non-Pixel OEMs also typically don't provide updates nearly as frequently or for nearly as much time for the lower end devices which would need to change for us to use those.

2026-08-22 01:48:27 UTC

- reply

Supporting a flip device with vertical folding would be a new form factor for GrapheneOS. The main use case for those is a tiny phone to use with one hand in the folded form factor. The tablet-style folding devices we already support are extremely useful for web browsing, reading, maps, etc.

2026-08-22 01:45:36 UTC

- reply

We do plan to support Motorola's Razr Fold and Razr Ultra (flip) devices in addition to a regular device. We already support the original Pixel Fold (Pixel 7) along with the Pixel 9 Pro Fold and Pixel 10 Pro Fold. We still plan to add support for 11th gen Pixels including the Pixel 11 Pro Fold too.

2026-08-22 01:33:38 UTC

- reply

@nprofile…86nn @nprofile…nqv0 T-Mobile will definitely work fine. We haven't heard of people having issues with this in the US though, only certain countries like Australia and Turkey.

2026-08-22 01:26:12 UTC

- reply

@nprofile…nqv0 @nprofile…86nn It's quite possible the successor to the Motorola Signature will be available in the US. If it wasn't then it could be imported. Many of our users are importing Pixels to countries where they aren't available via a package forwarding service in the US, EU or elsewhere. It's how we get phones to some of our developers too.

2026-08-22 01:11:02 UTC

- reply

@nprofile…y93v No, you can keep using it until end-of-life. We even plan to support the Pixel 11 devices.

2026-08-22 00:57:30 UTC

- reply

@nprofile…8yyh No, since we need the security improvements in the upcoming devices and will have our hands full supporting those.

2026-08-22 00:56:52 UTC

- reply

@nprofile…86nn Razr Fold (2026) and Razr Ultra (2026) are available in the US so hopefully the next generation ones are too. Motorola Signature (2026) wasn't available in the US but hopefully that changes.

2026-08-22 00:40:21 UTC

- reply

Motorola is doing a large portion of the work of porting GrapheneOS to their devices. They'll provide us with what we need for firmware/drivers in the form we need it and it will be far easier than Pixels. We'll be able to get issues in the firmware and drivers fixed through Motorola and Qualcomm.

2026-08-22 00:38:17 UTC

- reply

Pixels have become much harder to support. Android 16 removed support for Pixels and they became harder to properly support than many other devices rather than easier. It's crucial to keep up with the major OS updates to provide all the security patches and we do but it's much harder for us now.

2026-08-22 00:35:57 UTC

- reply

It's very realistic to provide better security than Pixels against remote attacks. It's far harder to provide a secure element as good as the Titan M2/M3. There will definitely be a decent secure element providing the current generation features including the Android 16 QPR2+ rate limiting design.

2026-08-22 00:33:43 UTC

- reply

These devices will meet or exceed of our official requirements including 7 years of proper updates, starting out with the Linux 6.18 LTS which can be upgraded to a new branch eventually, reset attack protection for firmware boot modes and everything else. There wasn't time to do it all for 2026.

2026-08-22 00:30:26 UTC

- reply

Next generation Snapdragon will have more mature support for MTE and greatly improved secure element support. It's still likely going to be a lot of work to get MTE fully deployed for the kernel and OS. We need all our hardware-based features including our USB-C port protection ported to it too.

2026-08-22 00:28:42 UTC

- reply

Tensor was a sidegrade or downgrade from Snapdragon in many ways. Tensor is paired with the fantastic Titan M2/M3 which was a huge security advantage. It also brought hardware memory tagging (MTE) with the Pixel 8. Snapdragon 8 Elite Gen 5 finally shipped MTE but it's broken on the non-Elite SoC.

2026-08-22 00:26:34 UTC

- reply

Flagship Snapdragon provides much better CPU and GPU performance and provide more of what's needed via isolated components on the SoC. That includes better cellular, Wi-Fi/Bluetooth and GNSS radios with solid security including good isolation. Snapdragon Pixels worked well for us and it will again.

2026-08-22 00:16:06 UTC

Initial focus for our partnership with Motorola is a regular non-folding device. Current generation Motorola Signature (2026), Razr Fold (2026) and Razr Ultra (2026) are very close to meeting our requirements but lack MTE, adequate secure element integration and other features being added for 2027.

2026-08-21 22:11:04 UTC

- reply

@nprofile…sklt ECC memory is rare and expensive. DDR5 has built-in ECC for single bit errors on the memory chips but doesn't cover the rest of the path or protect against bigger errors.
Ryzen 9950X3D supports ECC memory and is essentially the same chip as the EPYC 4585PX. We could use ECC memory with 9950X3D CPUs if we were willing to pay for it.
Hardware is not very reliable in general and not a substitute for testing. If we had more resources we could do every build twice and compare the outputs.

2026-08-21 02:30:20 UTC

- reply

@nprofile…370v What Google is doing is far harder than simply pushing the code. It's also far harder than an automated system for providing it upon request. They're choosing to do this to create harm through delays.
The intended target of that harm is probably not GrapheneOS but rather major companies forking Android. After all, they still provide first class support for alternative operating systems on Pixels at a hardware and firmware level but are making it awful for people to use because of this.

2026-08-21 02:27:35 UTC

- reply

@nprofile…370v Google is one of the largest tech companies in the world. It's an entirely negligible burden on them to quickly comply with these requests. They could have entirely automated it or at least made it automated after the initial request from an email. They chose to make it a manual process with a lot of friction and delays. They chose to go out of their way to go a lot of extra work for this. They have to package up source code this way and manually hand out access to those to people.

2026-08-21 02:26:25 UTC

- reply

@nprofile…370v We didn't say it was the fact they're doing it via Google Drive using Google Forms which makes it a GPL violation. It was stated after bringing up the massive delays and then we elaborated on the situation. We didn't consider it to be a GPL violation until they started taking weeks or more to handle our requests for the sources.
What matters is how things work in 2026 especially for the Android source code. It matters how Google shares it with partners, the impact of delays and more.

2026-08-21 00:22:39 UTC

- reply

@nprofile…370v
> the waiting time of a few weeks should be okay
No, it isn't. It's an artificial delay causing substantial harm through delayed security updates. That means we have to reverse engineer the code to get the patches. We can do that but it results in ongoing damages from Google's violation of the GPL license. They used to push it immediately and now there's a deliberate artificial delay to cause harm. What other reason is there for moving to a manual system with substantial delays?

2026-08-20 20:47:43 UTC

- reply

@nprofile…kc7k Our 9950X3D build has 2x 64GB DDR5 6400MHz. It was purchased for CA$461.99 (US$336.58 at the time) on 2025-06-22. The price is now CA$3,999.99 (US$2,899.91).
Hopefully we can get both the CPU and motherboard replaced under warranty relatively quickly.
It isn't really clear if the motherboard is also dead or physically damaged in addition to the CPU. Probably a good idea to get it replaced but a new one might be just as prone to killing a replacement 9950X3D.

2026-08-20 20:15:06 UTC

- reply

Both the CPU and motherboard should be covered by the warranties from AMD and ASRock. However, it's typically a hassle to get this dealt with and we need another build machine right away. We'll likely buy a new CPU and motherboard. Can upgrade the 5950X machine after the dead parts are replaced.

2026-08-20 20:09:04 UTC

- reply

We've had a lot of memory issues with the older AM5 7950X machine including it not working with high capacity DIMMs. i9-13900K machine had performance crippled by the updates stopping it bricking itself. The oldest 5950X machine predating DDR5 is the only one which hasn't had any significant issues.

2026-08-20 19:47:44 UTC

Most recently assembled of the 4 workstations used to build official GrapheneOS releases died today. 9950X3D CPU was likely killed by the ASRock B850 Pro RS motherboard. Many other ASRock customers with AM5 boards and X3D CPUs have experienced it. We were concerned about this so we didn't use PBO2.

2026-08-20 14:44:39 UTC

- reply

@nprofile…8q2x @nprofile…6saw It's highly unlikely these devices were running GrapheneOS. It's likely the devices were purchased from a company selling phony hardened devices to criminals. Those devices are often marketed as using GrapheneOS including devices sold by ANOM which was an FBI operation. A device being marketed as either using GrapheneOS or being based on it doesn't mean it's true. Conflating products not running GrapheneOS with GrapheneOS is common.
https://nitter.net/GrapheneOS/status/2090436537783644455

2026-08-20 14:41:49 UTC

- reply

@nprofile…8q2x @nprofile…6saw It's highly unlikely these devices were running GrapheneOS. It's likely the devices were purchased from a company selling phony hardened devices to criminals. Those devices are often marketed as using GrapheneOS including the devices sold by ANOM which was an FBI operation. A device being marketed as using GrapheneOS or being based on it doesn't mean that's true. That was the main basis for false claims about GrapheneOS in France.
https://nitter.net/GrapheneOS/status/2090436537783644455

2026-08-20 14:38:34 UTC

- reply

@nprofile…8q2x @nprofile…6saw https://nitter.net/GrapheneOS/status/2090436537783644455

2026-08-20 03:25:13 UTC

Vanadium version 152.0.7977.54.0 released:
https://github.com/GrapheneOS/Vanadium/releases/tag/152.0.7977.54.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/41312-vanadium-version-15207977540-released
#GrapheneOS #privacy #security #browser

2026-08-20 02:09:33 UTC

- reply

@nprofile…vkrd The Hacker News thread is based on us answering someone's question in a reply but we've provided the same information many times before through Mastodon and other platforms. It isn't really news that the devices will be in 2027. We've been saying late 2026 to before the end of 2027. We moved to saying 2027 many months ago after determining it would be the next generation of devices meeting our requirements rather than the current one.

2026-08-20 02:05:33 UTC

- reply

@nprofile…hd7u It's not about AOSP and has no impact on our partnership with Motorola.

2026-08-19 03:48:35 UTC

- reply

@nprofile…seap @nprofile…vtea Never said you were doing it. It's /e/ and Murena themselves doing that, not you.

2026-08-19 03:22:52 UTC

- reply

@nprofile…seap @nprofile…vtea /e/ and Murena repeatedly claim privacy/security hardened devices are mainly for criminals and pedophiles. They've also been falsely claiming GrapheneOS is mainly used by criminals for years alongside misleading people about what it provides. That's why we began providing our perspective in response. Fairphone gave a weasel worded media statement supporting Murena in this and other involvement.
https://nitter.net/GrapheneOS/status/2040887784253141142
https://www.clubic.com/actualite-604786-murena-e-os-interview.html
https://nitter.net/GrapheneOS/status/2081837057433915603