Nostr notes by GrapheneOS

The launcher grid layout was fixed in the same release including ...

2026-10-17T21:19:09Z

In reply to nevent1q…6ktm
_________________________

The launcher grid layout was fixed in the same release including the new boot animation.

https://grapheneos.social/@GrapheneOS/117457467257349333

quoting
note1yh8…xwvs

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

We could reduce the motion by reducing the radius it expands to ...

2026-10-17T20:32:58Z

In reply to nevent1q…ur0n
_________________________

We could reduce the motion by reducing the radius it expands to and extending the time for each loop but 4 seconds per rotation is already quite long. It already often doesn't have enough time to complete a single loop on current devices. Boot time will be getting significantly faster with our planned optimizations to secure spawning and also upcoming hardware. The upcoming Motorola flagship will be drastically faster than Pixels and may typically finish during the logo hold time.

No, it was created with a Python script using the Pillow image ...

2026-10-17T20:28:06Z

In reply to nevent1q…dxet
_________________________

No, it was created with a Python script using the Pillow image library. It's only a few hundred lines of Python code. It may have made sense to use a framework suited to generated animations but the way we did it works well and is very straightforward.

We initially tried using Blender to make a 3D animation. We decided 2D is a better fit for the minimalist aesthetics used by GrapheneOS. 3D is drastically more complex and it's a lot harder to make it feel high enough quality.

Intro 0.00-1.90: Atoms appear one-by-one and gather 1.90-2.70: ...

2026-10-17T19:13:00Z

In reply to nevent1q…c9ke
_________________________

Intro
0.00-1.90: Atoms appear one-by-one and gather
1.90-2.70: Bonds expand; name fades in from 2.20
2.70-3.50: Hold

Transition
0.00-1.20: Hold
0.00-0.80: Outer and split inner bonds retract; name fades
0.80-1.40: Ease into spin

Loop
0.00-4.00: One rotation from initial offset

This is the new GrapheneOS boot animation. It's generated ...

2026-10-17T19:10:29Z

This is the new GrapheneOS boot animation. It's generated frame-by-frame using a script. It has a minimum 3.5s total runtime for the intro including a small pause. The rest of the animation gets interrupted once the device is booted to avoid any delay so there can't be an outro.

GrapheneOS version 2026101600 released: ...

2026-10-17T17:38:36Z

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

Google apps and services can be installed on GrapheneOS as ...

2026-10-16T18:10:14Z

In reply to nevent1q…juak
_________________________

Google apps and services can be installed on GrapheneOS as regular sandboxed apps. You can test both with and without Google Mobile Services on GrapheneOS.

Devices without Google Mobiles Services are increasingly popular and apps should fully work without it. Many popular mainstream apps do including even the Facebook app suite.

There are alternatives to Google services. For example, apps can default to FCM when present while offering UnifiedPush as an alternative.

It was a poor repair. They likely either forgot to reconnect it ...

2026-10-16T17:08:36Z

In reply to nevent1q…q43j
_________________________

It was a poor repair. They likely either forgot to reconnect it or broke it.

Vanadium version 155.0.8059.84.0 released: ...

2026-10-16T07:07:03Z

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

Pairing with a specific Bluetooth devices doesn't require the ...

2026-10-14T23:01:38Z

In reply to nevent1q…f493
_________________________

Pairing with a specific Bluetooth devices doesn't require the Nearby Devices permission. Pairing uses a case-by-case consent system. The Nearby Devices permission doesn't allow pairing with arbitrary Bluetooth devices but rather scanning for them. See here for Bluetooth:

https://developer.android.com/develop/connectivity/bluetooth/bt-permissions

At a low level, the different parts of the Nearby Devices permission are split up and we could eventually expose separate control over those, but that would add complexity and more to maintain.

Can you provide more details on what's wrong?

2026-10-14T16:49:19Z

In reply to nevent1q…pl08
_________________________

Can you provide more details on what's wrong?

Try enabling the per-app exploit protection compatibility mode as ...

2026-10-14T16:47:05Z

In reply to nevent1q…whpm
_________________________

Try enabling the per-app exploit protection compatibility mode as an initial step. This works for most banking apps which don't work with the defauilts.

GrapheneOS isn't rooted and fully preserves the standard security model along with greatly improving it. You should report this to their customer support and leave a review about it on the Play Store too. Don't include a link in the review to avoid it being spam filtered. Give their customer support a link to https://grapheneos.org/articles/attestation-compatibility-guide.

Try enabling the per-app exploit protection compatibility mode as ...

2026-10-14T16:47:00Z

In reply to nevent1q…9zlc
_________________________

Try enabling the per-app exploit protection compatibility mode as an initial step. This works for most banking apps which don't work with the defauilts.

GrapheneOS isn't rooted and fully preserves the standard security model along with greatly improving it. You should report this to their customer support and leave a review about it on the Play Store too. Don't include a link in the review to avoid it being spam filtered. Give their customer support a link to https://grapheneos.org/articles/attestation-compatibility-guide.

Vanadium version 155.0.8059.79.0 released: ...

2026-10-14T03:22:20Z

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

Vanadium version 155.0.8059.39.0 released: ...

2026-10-08T21:45:57Z

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

GrapheneOS version 2026100600 released: ...

2026-10-07T20:35:19Z

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

It currently has to be supported by each app and there isn't ...

2026-10-06T16:51:13Z

In reply to nevent1q…yd9c
_________________________

It currently has to be supported by each app and there isn't a way to force apps to use another font beyond forking them.

There will likely be customization for this eventually, at least a choice between several fonts built into the OS.

Similarly to how most apps don't use the system there, a subset of apps don't use system fonts and wouldn't be impacted by changing the system fonts. It wouldn't be as widespread as the vast majority of 3rd party apps not using the system theme though.

This repository is too large for it to be uploaded to GitHub so ...

2026-10-02T16:41:26Z

In reply to nevent1q…k7ys
_________________________

This repository is too large for it to be uploaded to GitHub so we're using GitLab where we have a free Enterprise plan. It doesn't mean that we plan to migrate to GitLab. We'll likely start self-hosting our own primary mirrors for our Git repositories along with sticking to GitHub for receiving pull requests, issue reports, etc.

GrapheneOS version 2026092500 released: ...

2026-09-27T00:31:10Z

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

That's the udev rules step in the instructions. The web ...

2026-09-24T15:47:41Z

In reply to nevent1q…tnl3
_________________________

That's the udev rules step in the instructions. The web installer works across operating systems but we haven't dealt with making instructions on things like this for each one which is why there's an official list of supported operating systems. Those are just the ones where we have full instructions and regular testing.

Location Scopes is a planned feature as a per-app replacement for ...

2026-09-24T15:46:21Z

In reply to nevent1q…l85v
_________________________

Location Scopes is a planned feature as a per-app replacement for Android Mock Location. Android Mock Location is global and only available as a developer option via a Mock Location app.

We can add a new API for querying if it's enabled so apps banning Mock Location would work but would have the option to ban Location Scopes instead of banning GrapheneOS, which seems to be the best way to do it to maximize compatibility. It requires thought since avoiding app bans is important.

Vanadium version 154.0.8037.57.0 released: ...

2026-09-23T20:50:05Z

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

No, we don't have any timeline for it yet.

2026-09-22T22:19:18Z

In reply to nevent1q…vpg8
_________________________

No, we don't have any timeline for it yet.

GrapheneOS Messaging version 14 released: ...

2026-09-22T20:24:26Z

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

RCS is fully supported by GrapheneOS and works via Google ...

2026-09-22T17:07:55Z

In reply to nevent1q…pzum
_________________________

RCS is fully supported by GrapheneOS and works via Google Messages. Follow the official instructions and it will work. Google Messages is the only RCS client available for Android in practice and there's no timeline on when it will be added to our own Messaging app. It's planned for the future.

https://grapheneos.org/usage#rcs

Have you confirmed it works?

2026-09-22T13:45:15Z

In reply to nevent1q…n55p
_________________________

Have you confirmed it works?

GmsCompatConfig version 175 released: ...

2026-09-22T03:38:38Z

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

Using "Charging-only when locked" will enable connecting ...

2026-09-22T00:44:20Z

In reply to nevent1q…42kz
_________________________

Using "Charging-only when locked" will enable connecting audio accessories while unlocked. Those will continue to work after locking but new connections will be blocked, so non-audio USB peripherals and other USB functionality won't be possible to use after it's locked. You'll only need to unlock to continue using it if the USB connections is ended through it being disconnected.

We already accept cryptocurrency donations and receive the ...

2026-09-20T18:55:19Z

In reply to nevent1q…86yx
_________________________

We already accept cryptocurrency donations and receive the majority of our donations that way. We pay nearly all of our developers with cryptocurrency to avoid issues sending payments internationally.

https://grapheneos.org/donate

There's someone who keeps trying to donate 5 AUD and it keeps ...

2026-09-20T14:00:12Z

In reply to nevent1q…p3hf
_________________________

There's someone who keeps trying to donate 5 AUD and it keeps being returned since we don't have their full name to pass this review. It's likely mainly caused by sanctions enforcement. There are often name collisions especially in cases where the sending bank gives initials.

We need the person who recently sent a 1000 EUR donation via Wise ...

2026-09-20T13:58:12Z

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.

We'll support Pixels until end-of-life. Pixel 8 is one of the ...

2026-09-20T12:27:39Z

In reply to nevent1q…l060
_________________________

We'll support Pixels until end-of-life. Pixel 8 is one of the recommended devices and either a used Pixel 8 or Pixel 8a is a good budget device.

The initial Motorola device with GrapheneOS support in 2027 will be a flagship much higher end than a Pixel 11 Pro. It will take more time before we can add more devices. There will eventually be more budget devices but initially that's still going to be covered by Pixels. No point waiting to 2027 if you want a budget device to start.

GrapheneOS version 2026091900 released: ...

2026-09-19T23:07:31Z

GrapheneOS version 2026091900 released:

https://grapheneos.org/releases#2026091900

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://discuss.grapheneos.org/d/42142-grapheneos-version-2026091900-released

#GrapheneOS #privacy #security

Both browsers have their own internal memory management for tabs. ...

2026-09-19T20:26:53Z

In reply to nevent1q…5mpl
_________________________

Both browsers have their own internal memory management for tabs. There are also memory pressure signals from the OS with voluntary handling by apps.

The OS will kill background processes due to memory pressure but it prioritizes killing cached apps kept in memory to speed up startup over background processes.

Background processes which aren't currently supposed to be running are frozen and can't run but remain in memory unless there's memory pressure forcing outright killing.

Firefox is choosing to have it work that way as part of their own ...

2026-09-19T20:13:21Z

In reply to nevent1q…72px
_________________________

Firefox is choosing to have it work that way as part of their own memory management.

No, Firefox is choosing to have it work that way as part of their ...

2026-09-19T20:11:19Z

In reply to nevent1q…wzcc
_________________________

No, Firefox is choosing to have it work that way as part of their own memory management.

Vanadium version 153.0.8010.52.0 released: ...

2026-09-18T21:28:06Z

Vanadium version 153.0.8010.52.0 released:

https://github.com/GrapheneOS/Vanadium/releases/tag/153.0.8010.52.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/42105-vanadium-version-15308010520-released

#GrapheneOS #privacy #security #browser

GrapheneOS version 2026091700 released: ...

2026-09-18T12:35:24Z

GrapheneOS version 2026091700 released:

https://grapheneos.org/releases#2026091700

See the linked release notes for a summary of the improvements over the previous release.

Forum discussion thread:

https://discuss.grapheneos.org/d/42090-grapheneos-version-2026091700-released

#GrapheneOS #privacy #security

No, their devices have very poor updates and security features. ...

2026-09-18T12:05:44Z

In reply to nevent1q…ztar
_________________________

No, their devices have very poor updates and security features.

Fairphone 5 and earlier have end-of-life kernels without security support. Their newer devices will too. They lack proper firmware, driver and HAL updates too.

There's no proper secure element and many other missing security features.

Fairphones are designed and made by T2Mobile. Fairphone aren't the ones designing the devices and aren't in a position to make the massive improvements needed to meet our requirements.

No, their devices have very poor updates and security features. ...

2026-09-18T12:05:37Z

No, and we still plan to support the Pixel 11 series as long as ...

2026-09-16T20:07:03Z

In reply to nevent1q…xu4a
_________________________

No, and we still plan to support the Pixel 11 series as long as it gets fully functional MTE support.

Performance appears to be fine for MTE on the Pixel 11. We ...

2026-09-16T19:14:55Z

In reply to nevent1q…hrpm
_________________________

Performance appears to be fine for MTE on the Pixel 11. We don't know which it was completely removed from firmware and disabled at launch. It's added back to firmware but still disabled in Android 17 QPR2 Beta 4 which was released after our initial thread about it. We used that to enable it and test it. It passes all our tests and other standard tests. We benchmarked it and the performance is fine. There may be cases where it has higher overhead but the faster CPUs make up for it.

> With today's AI-powered rapid reverse-engineering, ...

2026-09-16T19:01:35Z

In reply to nevent1q…mk0k
_________________________

> With today's AI-powered rapid reverse-engineering, isn't releasing a security fix tantamount to disclosing the vulnerability to threat actors?

Yes, and we can reverse engineer it ourselves to ship it before December 2026 so it's not the end of the world.

It heavily draws into question what is supposed to be accomplished by the security preview system instead of simply allowing the patches to be shipped immediately as source code. It's hardly hidden by hiding that for months.

It will be far easier for us to support upcoming Motorola devices ...

2026-09-16T19:00:19Z

In reply to nevent1q…wjz7
_________________________

It will be far easier for us to support upcoming Motorola devices than Pixels. Qualcomm will hopefully expand MTE support beyond the highest end flagship SoC soon so we can expand to more than flagships. Pixel 11 didn't remove it from hardware, only firmware, so that's good news.

Pixels are now significantly harder to support than many other ...

2026-09-16T18:54:53Z

In reply to nevent1q…cw0j
_________________________

Pixels are now significantly harder to support than many other devices. One of the only advantages of Pixels is now a disadvantage instead. They're still the best fit for us due to the updates and security features but it burns time we want to spend on privacy and security work.

We could have shipped an Android 17 QPR1 update already since our ...

2026-09-16T18:54:45Z

In reply to nevent1q…5sqs
_________________________

We could have shipped an Android 17 QPR1 update already since our port was completed. Instead, we have to deal with ongoing pain until Android 17 QPR2 is released in December 2026. This will not be an issue for Motorola since we'll have official firmware and driver code provided.

Google is also once again failing to comply with our GPL source ...

2026-09-16T18:54:31Z

In reply to nevent1q…jx4k
_________________________

Google is also once again failing to comply with our GPL source requests for weeks. We requested CD1A.260905.001.A1 sources on September 1st and were only provided access today. The kernel build IDs are the same for 17 QPR1 Beta 9 and 17 QPR1 so we have that already at least.

GrapheneOS version 2026090500 released: ...

2026-09-06T07:36:42Z

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

We have a partial port of GrapheneOS to the Pixel 11 series after ...

2026-08-29T14:19:30Z

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.

Latest release of GrapheneOS finally shipped the long awaited ...

2024-06-02T14:28:05Z

Latest release of GrapheneOS finally shipped the long awaited duress PIN/password implementation. If you have a spare device, we recommend trying it out.

We've added initial documentation to the features page:

https://grapheneos.org/features#duress

It near instantly wipes and shuts down.

We mentioned Signal/WhatsApp because despite having end-to-end ...

2023-11-26T22:56:50Z

In reply to nevent1q…uhmx
_________________________

We mentioned Signal/WhatsApp because despite having end-to-end encryption, they both have a massive amount of remote attack surface, use tons of memory unsafe code for handling media, voice/video calls, etc. along with not using sandboxing. E2EE does no good if app is exploited.

We've also replaced the Linux kernel version on the Pixel 8 ...

2023-11-26T22:51:44Z

In reply to nevent1q…h33l
_________________________

We've also replaced the Linux kernel version on the Pixel 8 and Pixel 8 Pro. AOSP and the stock Pixel OS use 5.15.110 while GrapheneOS is now using 5.15.137 and will be closely following along with kernel.org LTS releases after they go through appropriate testing.

Everyone on GrapheneOS has hardened_malloc and our other baseline ...

2023-11-26T22:50:34Z

In reply to nevent1q…skzx
_________________________

Everyone on GrapheneOS has hardened_malloc and our other baseline exploit protections. hardened_malloc has great support for hardware memory tagging to provide a form of memory safety for memory unsafe code with a mix of deterministic guarantees and randomized general protection.

In the latest release of GrapheneOS, you can now enable hardware ...

2023-11-26T22:50:21Z

In the latest release of GrapheneOS, you can now enable hardware memory tagging for all user installed apps on the Pixel 8 and Pixel 8 Pro to make them substantially harder to exploit. This is particularly useful for apps like Signal and WhatsApp.

https://grapheneos.social/deck/@GrapheneOS/111479244810981775