Nostr notes by AmberFinal

It sounds stereotypical but if I had the time and learning ...

2026-10-28T18:56:25Z

In reply to nevent1q…f052
_________________________

It sounds stereotypical but if I had the time and learning resources then it would probably be a wallet app I personally worked on instead. I don't like most of them. App marketplace is oversaturated for it though...

I don't consider giving feedback on an app to be ...

2026-10-28T18:49:51Z

In reply to nevent1q…rahz
_________________________

I don't consider giving feedback on an app to be collaboration, none of us develop a messaging app and it's just me who provided that feedback.

Thanks! Updating this myself.

2026-10-28T09:00:13Z

In reply to nevent1q…5yd2
_________________________

Thanks! Updating this myself.

I am strongly for more native apps for Android made with Kotlin ...

2026-10-28T08:59:54Z

In reply to nevent1q…05m8
_________________________

I am strongly for more native apps for Android made with Kotlin and Compose being developed. You get the best compatibility with our security hardening and generally the best performance.

You shouldn't consider what I talk about to be a direct recommendation of what you should use to communicate with someone. GrapheneOS doesn't have any apps bundled for a reason, it's down to the user to choose what's right for them.

Had a discussion with the @nprofile…radp team about how they ...

2026-10-28T08:55:12Z

Had a discussion with the White Noise (nprofile…radp) team about how they could improve especially in a security and privacy standpoint. The post and article below discuss a small part of the efforts made. These provide substantial security improvements while having no added overhead or friction to the user.

If your application handles media, it's important that functionality is sandboxed and designed in a memory safe language. White Noise currently isolates image decoding in this way but now this has also been expanded to animated images as well. You can find out more below.

Memory tagging (MTE), a ARM hardware exploit protection used heavily by GrapheneOS and latest generation iPhones are now opted in the app manifest. This makes it unable to be disabled in GrapheneOS and also enables it for capable phones enrolled in Android's Advanced Protection.

The issue tracker also now tracks working on a few improvements, including adding this sandbox for other types of attachments too. I've also discussed on a improving accessibility features.

quoting
nevent1q…dxvx
White Noise for Android 2026.10.27 decodes GIF and WebP animation in a permissionless worker, away from account data and group keys, and requests native heap memory tagging checks on MTE-capable phones, so a malicious animated image has far less of your private data within reach. Thank you to AmberFinal (npub1hxx…g75y) for the conversations that inspired this hardening.

naddr1qq…ws0c

For those who don't read articles, USB was what was exploited ...

2026-10-28T08:36:11Z

In reply to nevent1q…dv90
_________________________

For those who don't read articles, USB was what was exploited here. Stock Android only blocks through software, so there is still the USB stack attack surface to exploit there.

Another win for our hardware USB-C port control feature. In the ...

2026-10-28T08:33:52Z

Another win for our hardware USB-C port control feature. In the highest setting, the device cannot charge unless it is powered off.

From Anthropic: "Claude wrote an exploit that let an attacker extract photos and other personal information from a stolen Android phone without unlocking it"
https://www.anthropic.com/research/discovering-vulnerabilities-with-claude

I hate talking about general security and privacy advice on ...

2026-10-26T21:32:01Z

I hate talking about general security and privacy advice on social media. It's a common tactic by charlatans to make them appear trustworthy for saying basic things. But, this has to be said.

An often overlooked detail of wallet company data breaches is the collateral damage to the customer. Your compromised information can be used to target you in additional breaches, such as for phishing emails or even credential stuffing.

Everyone talks about the risk of real world harm but it's also your cyber health at stake. Never reuse your credentials and keep information you provide non-attributable where there is no consequence to do so.

If you are running a business involved in decentralised finance, whether it be as a product or accepting a mode of payment, you must understand you will have a target on your back, all the time, with threat actors who work more hours than you do and also more likely to be held unaccountable should they succeed with their goals. You have to assume you WILL get a data breach eventually. No organisation is perfect. If you aren't ready to continuously put in an effort to security, quit while you can to protect your customers.

Basic mistakes are the most overlooked, and often the most dangerous. There is never a wrong time to review your posture. Don't let your impacts be amplified by technical failures you only were able to discover after the breach happened.

0 days without a wallet company data breach. #nevent1q…48fz

2026-10-26T07:52:14Z

0 days without a wallet company data breach.

quoting
nevent1q…48fz
0 days without a wallet company data breach.

Keystone

2026-10-25T20:28:18Z

In reply to nevent1q…eg3y
_________________________

Keystone

Unsure what could cause this other than an app issue. Do you use ...

2026-10-25T18:41:11Z

In reply to nevent1q…praz
_________________________

Unsure what could cause this other than an app issue. Do you use sandboxed Play Services in the original profile? Some apps poorly handle being without it, Signal in the past was one with a battery drain issue.

Nostr event nevent1qqsqqqqp5lz033t9eghgzsx6zg9qelgll54glsl4wupl7negvevp08szyzucmm2vat4zq7gdhjeux9qqdysqn56v07vj0s5xsddfnd6grfwzyrukgm8

2026-10-25T18:39:18Z

0 days without a wallet company data breach.

I could just edit it? Sure, but supposedly Wikipedia has ...

2026-10-25T18:34:19Z

In reply to nevent1q…4223
_________________________

I could just edit it? Sure, but supposedly Wikipedia has stringent 'confluct of interest' policies on editing articles about oneself or what you're associated with, so not worth the hassle.

Even Wikipedia appeared to get this wrong... > accused a man ...

2026-10-25T18:33:35Z

Even Wikipedia appeared to get this wrong...

> accused a man of destruction of evidence after he gave his screen lock duress pin to an officer during a border search.

Was not evidence, rather destruction of property to prevent seizure.

https://en.wikipedia.org/wiki/GrapheneOS

quoting
nevent1q…93v4
To say someone is 'suspected of' something is not an indictment or even a credible accusation. The suspect has NEVER been indicted on any other charge except destruction of property to prevent a seizure. Their defence are arguing this to be thrown out given this seizure was done without respect to the suspect's legal rights.

I'm not interested in changing my position unless there is a claim with evidence and there is not. You are innocent until proven guilty.

Good, it's a security improvement

2026-10-25T04:21:14Z

In reply to nevent1q…ukfw
_________________________

Good, it's a security improvement

@nprofile…radp committed memory tagging (MTE) enabled in their ...

2026-10-24T03:52:12Z

White Noise (nprofile…radp) committed memory tagging (MTE) enabled in their app manifest. This means in a future version of the app, you get MTE used in a very limited scope of non-GrapheneOS Android devices. For #GrapheneOS it means the exploit protections cannot be disabled.

https://github.com/marmot-protocol/whitenoise-android/commit/9f39a21709c9ec20ff3f4d2c12e8398b88ec91ce

To say someone is 'suspected of' something is not an ...

2026-10-20T17:36:21Z

In reply to nevent1q…v43h
_________________________

To say someone is 'suspected of' something is not an indictment or even a credible accusation. The suspect has NEVER been indicted on any other charge except destruction of property to prevent a seizure. Their defence are arguing this to be thrown out given this seizure was done without respect to the suspect's legal rights.

I'm not interested in changing my position unless there is a claim with evidence and there is not. You are innocent until proven guilty.

I was right. DHS Said They Searched Man Who Wiped #GrapheneOS ...

2026-10-20T17:30:59Z

I was right.

DHS Said They Searched Man Who Wiped #GrapheneOS Phone for Child Abuse Material. **They Lied.**

https://www.404media.co/dhs-said-they-searched-man-who-wiped-grapheneos-phone-for-child-abuse-material-they-lied/

quoting
nevent1q…4u9q
According to the defendant's motion to suppress in this case, the authorities refused to read him his rights and also made extreme, unfounded accusations such as checking for CSAM (which was never implicated to be under their possession nor was the defendant ever indicted for it, it is not in any court docs) to try and coerce them into unlocking their phone. It appears he chose the Duress knowing he was not given his rights. I would be interested to see how this case develops.

Authorities CAN and WILL lie to you to try and incriminate you even if you have done nothing wrong. Do not talk to them, do not discuss your day and if you are in a questioning then exercise your right to remain silent and get a lawyer.

Likely because this will be their approach in the future to try ...

2026-10-18T11:54:07Z

In reply to nevent1q…6x0t
_________________________

Likely because this will be their approach in the future to try and exploit device extraction now that USB is becoming more protected. Looks like someone over there hates the hardware port control feature we have (We also have a shutdown timer for Bluetooth).

They still were not able to exploit modern iPhones using memory tagging and the article appears to explain how this could have been patched.

I was sent this article showing what appears to be a document by ...

2026-10-18T11:40:14Z

I was sent this article showing what appears to be a document by Cellebrite that was marked as confidential describing a recent Advanced Unlocks capability. The document is a few months old. This capability allegedly uses a dedicated appliance with a stated range of about 8 metres. Given the range they suspect it is to do with Bluetooth.

There is no mention of iPhones with MIE (hardware memory tagging, iPhone 17, Air and later) and it is not on the latest iOS version, which could suggest a patch.

Take a look for yourself:

https://justin.sh/blog/2026/10/cellebrite-advanced-unlocks/

It would make sense that Cellebrite would choose to have capabilities like this one under development. When devices increase their security against physical attacks, the exploit developers will move towards a path of least resistance to exploit other components or circumvent the security measures that prevent the extraction, as we see with their automatic reboot cancelling exploits for iPhones. Since forensics labs contain devices in isolation to prevent network access and remote wiping, it is possible to make simulated / dummy network environments inside those containers where advanced labs can attempt exploit delivery without the risks.

The full document is available on request so it needs to be looked at further. While I do not intend to make discussion threads on this site regularly I think this is in a public interest.

Latest #GrapheneOS update moves the launcher grid options and ...

2026-10-17T21:36:58Z

Latest #GrapheneOS update moves the launcher grid options and icon sizes to the Stock OS. You should have an extra row for the apps at the top you didn't have before.

This is the last post about startup animations,I swear.

2026-10-17T21:15:03Z

In reply to nevent1q…a98z
_________________________

This is the last post about startup animations,I swear.

This is the new #GrapheneOS boot animation in the latest release ...

2026-10-17T19:13:02Z

This is the new #GrapheneOS boot animation in the latest release available now. 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.

I assume it's a future build or something. Windows can't ...

2026-10-14T07:05:19Z

In reply to nevent1q…9mjc
_________________________

I assume it's a future build or something. Windows can't in the second version.

Interesting new software from the Ibis Paint guys. Extremely fast ...

2026-10-13T03:14:57Z

Interesting new software from the Ibis Paint guys. Extremely fast office suite.

https://github.com/ibisjp/ibis-office

This one is intentional, as when you update the OS you recompile ...

2026-10-09T19:49:11Z

In reply to nevent1q…6r5e
_________________________

This one is intentional, as when you update the OS you recompile apps that have been changed at runtime. This would usually be done just-in-time but it is ahead of time in GrapheneOS for security purposes.

For those wondering. Boot animations can be split to an intro, a ...

2026-10-09T19:47:58Z

In reply to nevent1q…v60z
_________________________

For those wondering. Boot animations can be split to an intro, a loop, and an outro. What you're seeing is an intro and the loop artificially repeated a few times. Once the OS is ready to start, that loop will be interrupted, so you do not need to worry about boot speed.

Updaters: have you noticed it? 👀 #nevent1q…0r0a

2026-10-08T21:37:14Z

Updaters: have you noticed it? 👀

quoting
nevent1q…0r0a
You should see an OS performance increase in our latest update. In upcoming releases there will be much more too including a way to possibly decrease memory usage from our secure app spawning feature.

nevent1q…0mze

You should see an OS performance increase in our latest update. ...

2026-10-08T05:54:34Z

You should see an OS performance increase in our latest update. In upcoming releases there will be much more too including a way to possibly decrease memory usage from our secure app spawning feature.

quoting
nevent1q…0mze
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

No and we have strict disallowing on it and clear usage of AI ...

2026-10-07T04:50:12Z

In reply to nevent1q…seys
_________________________

No and we have strict disallowing on it and clear usage of AI generated writing/media. Frontier AI models across many providers are mostly used for reviewing human authored code for issues.

Nostr event nevent1qqsqqqqznqh0ndxc6r8ytnlh63u6lpmh9ryufw3s8ukvkg7ux0sfecczyzucmm2vat4zq7gdhjeux9qqdysqn56v07vj0s5xsddfnd6grfwzycx6luf

2026-10-07T04:38:49Z

Well it looks like I have Mythos 5.1 now. Sweet.

We won't be implementing other messengers/protocols to keep ...

2026-10-06T22:18:32Z

In reply to nevent1q…cv64
_________________________

We won't be implementing other messengers/protocols to keep the platform agnostic for whatever users choose to use. RCS is just to be closer to the Stock OS in capability but we wouldn't recommend people to use that for sensitive communications, hence the warning when you first open Messaging.

Shouldn't be much of an issue after release 2026100200, ...

2026-10-04T11:36:54Z

In reply to nevent1q…55pl
_________________________

Shouldn't be much of an issue after release 2026100200, although Pixels aren't the best phones for this either.

Android 17 QPR1 was released for Pixels on September 15. It has a ...

2026-10-04T11:02:59Z

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 now we fixed it ourselves.

Google is taking increasingly long to implement and ship fixes for major issues in Android. We're having to expand our workload to include handling basic updates, testing and quality control for the entire operating system. We have rapidly growing resources and we'll handle it.

Pixel 11 series received a bug fix release near the start of September 2026 with the 2026-09-01 patch level. That update wasn't Android 17 QPR1 and also doesn't include the September 2026 Pixel firmware/driver security patches. Perhaps they noticed this issue and cancelled it.

Standard Android and Pixel updates have a severe issue with delays. It usually takes 2-3 months for Google to ship fixes for both severe regressions and security issues. They often get the issues fixed in days but the release engineering and testing process is completely broken.

Major Android releases including Android 17 QPR1 go through a long public testing period. It typically takes Google at least around 4 to 6 weeks to ship fixes for even the most severe issues. They either cancel the release (Pixel 11) or ship a broken release (everything else).

Here's our fix for the awful Android 17 QPR1 regression causing lag, stuttering and freezes:

https://gitlab.com/grapheneos/kernel_pixel_6.6/-/commit/ed5a9b87d99b45618fa55b3d6b53094cbd784b9f

It's so severe that it's causing processes to be killed for stalls. It's unclear when Google will ship a fix for the issue. December 2026 wouldn't be a surprise.

Due to this major Android 17 QPR1 regression, we've been looking into reducing memory usage. We found a way to eliminate most extra memory use from our secure spawning feature without any significant downsides. We'll try to get that huge improvement shipped before November 2026.

Nope, the sole developer has other priorities they want to work ...

2026-10-04T09:35:32Z

In reply to nevent1q…qstr
_________________________

Nope, the sole developer has other priorities they want to work on before renovating the user facing app. They also work on changes in different branches of the repo, so all the latest changes do not go to `main` branch until production.

See their blog from a couple of days ago:

https://accrescent.app/blog/posts/a-tale-of-too-many-protocols/

Most of their work is building a delta updates library and backend server for app submissions.

https://github.com/accrescent/server

https://github.com/accrescent/ina

I'm tired boss

2026-10-02T06:33:16Z

In reply to nevent1q…w6eg
_________________________

I'm tired boss

Big number that I don't care to count anymore vulnerabilities ...

2026-10-02T06:32:32Z

Big number that I don't care to count anymore vulnerabilities in Debian just update your OS or whatever

https://lwn.net/Articles/1097401

quoting
nevent1q…cfc2
848 Linux kernel CVEs published yesterday BTW

https://app.opencve.io/cve/?q=vendor%3Alinux+AND+product%3Alinux_kernel+AND+created%3D2026-08-15

nevent1q…huw8

It's a brand new feature. Just a couple updates ago. Paste ...

2026-09-29T00:58:49Z

In reply to nevent1q…kgh3
_________________________

It's a brand new feature. Just a couple updates ago. Paste Only is not the default setting for compatibility. You already get alerts for if an app used the clipboard anyhow so you know which ones misbehave.

RCS is a replacement for SMS/MMS all the modern smartphones are ...

2026-09-27T19:31:42Z

In reply to nevent1q…lc2w
_________________________

RCS is a replacement for SMS/MMS all the modern smartphones are incorporating that has end to end encryption of message contents (note: see privacy issues with cellular providers overall). The issue is they're not as open as the predecessor.

if support for RCS begins with a Play Services requirement, then people who don't install RCS will only have SMS/MMS, it's that simple. We won't be bundling Google apps or services into GrapheneOS. They need to choose it.

@nprofile…radp exists as a messenger with MLS end-to-end ...

2026-09-27T19:26:03Z

In reply to nevent1q…3s3s
_________________________

White Noise (nprofile…radp) exists as a messenger with MLS end-to-end encryption with Nostr as an identity/network layer. These RCS services depend on carrier infrastructure too.

Our massive overhaul of the AOSP Messaging app has reached the ...

2026-09-27T19:10:51Z

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.

Full support for RCS with all of the additional features it brings including proper group chats, media, opt-in read receipts and much more is going to be the largest project. We'll also be adding RCS end-to-end encryption via Messaging Layer Security (MLS) compatible with Google Messages and iOS.

RCS support will be provided via an optional dependency on sandboxed Google Play for activation. In the longer term, we plan to make a fully standalone implementation requiring the carrier to support it. We probably won't make an alternate implementation of using Google's own system for this.

Finishing the user interface overhaul, resolving many minor issues and adding important features including search are going to be the priority before getting to RCS. In the meantime, Google Messages is already fully supported on GrapheneOS including RCS with E2EE via MLS:

https://grapheneos.org/usage#rcs

Side of Burritos released a video demonstrating a malicious app ...

2026-09-26T10:02:15Z

Side of Burritos released a video demonstrating a malicious app with no added permissions compared to stock Android collecting clipboard data automatically. Our new clipboard control features in GrapheneOS protects such a thing from happening.

https://youtube.com/watch?v=tGTwnru_9ZU

This update adds on many bug fixes and significantly improves the ...

2026-09-23T17:24:25Z

This update adds on many bug fixes and significantly improves the performance of our overhauled default SMS / MMS messaging app, most notably, large conversations (tested to 80k texts) now open 350x faster than before (~0.10 seconds from over 35 seconds).

quoting
nevent1q…s7j9
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

There are many security what-ifs that can be solved by answering ...

2026-09-23T16:51:50Z

There are many security what-ifs that can be solved by answering "POCs or GTFO" by the way.

The @nprofile…radp app transition to Kotlin and Jetpack Compose ...

2026-09-21T22:07:18Z

The White Noise (nprofile…radp) app transition to Kotlin and Jetpack Compose is really good. It's such a smooth, fast messenger. Even more so when I expect most apps relating to Nostr or BTC to be quite sluggish. There is a significant leap in usability for apps that are designed for a platform's native language and libraries.

Scroll down and it should be there. If its not, you likely ...

2026-09-19T21:06:57Z

In reply to nevent1q…yr3h
_________________________

Scroll down and it should be there. If its not, you likely don't have the latest update distributed and you should have it installed soon.

You can now control the clipboard access of applications ...

2026-09-19T14:52:24Z

You can now control the clipboard access of applications individually in #GrapheneOS. This makes apps only able to see data if the user manually pasted it, with exception of the clipboard item originating from the same app attempting to paste.

You can go into Settings -> Security and Privacy in Owner to control clipboard access globally.

You can also go into individual applications in any profile to control that individual app's access.

Secure paste has been merged into #GrapheneOS to provide a ...

2026-09-13T06:06:53Z

Secure paste has been merged into #GrapheneOS to provide a replacement for focused apps being able to read the clipboard:

https://github.com/GrapheneOS/platform_frameworks_base/pull/435

quoting
nevent1q…aav9
We've developed a secure paste feature replacing traditional clipboard APIs in #GrapheneOS. 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.

A small subset of apps including those written in Flutter implement their own text selection toolbar. We've worked around this by adding a Paste button to the default keyboard. We'll be replacing AOSP Keyboard with a much better keyboard and will carry over adding this feature to the new one too.

Android only permits the currently focused app and keyboard to read the clipboard. However, sensitive data often lingers around in the clipboard for a while and privacy invasive apps can read it. Android shows a notice for apps reading clipboard content set by other apps but by then it's too late.

Our approach is replacing the inherently problematic API-based clipboard access approach used by both desktop and mobile operating systems. It's another overhaul of the privacy model for apps similar to our Contact Scopes and Storage Scopes features. We have many of these privacy features planned.

The overhauled #GrapheneOS Messaging app is available in our App ...

2026-09-11T21:12:40Z

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.

We're going to be overhauling or replacing most AOSP apps in the near future: Calculator, Clock, Contacts, Gallery, Keyboard and Phone.

The apps we created will be overhauled too. PDF Viewer is done and Camera is next. Camera and PDF Viewer will be getting many new features too.

It's a massive overhaul and may need a few releases to reach the Stable channel. We're working on a version 14 release fixing issues with the predictive back animation, tapping contacts not always showing the right SIM with dual SIM and some outdated icons/colors we missed.

Messaging will be overhauled even more. We plan to add RCS support with Messaging Layer Security (MLS). That will provide E2EE with contacts using Google Messages or iOS. RCS with MLS can already be used on GrapheneOS via Google Messages but we want to avoid people needing it.

quoting
nevent1q…d7zt
#GrapheneOS messaging, our new redesign of the SMS/MMS messaging app, is now available in the GrapheneOS App Store in Alpha channel.

This is the first of many replacements of default apps we aim to work for. Check it out!!

#GrapheneOS messaging, our new redesign of the SMS/MMS messaging ...

2026-09-11T21:03:47Z

#GrapheneOS messaging, our new redesign of the SMS/MMS messaging app, is now available in the GrapheneOS App Store in Alpha channel.

This is the first of many replacements of default apps we aim to work for. Check it out!!

See what was talked about here: ...

2026-09-07T18:15:02Z

In reply to nevent1q…pyvp
_________________________

See what was talked about here:
https://discuss.grapheneos.org/d/5775-device-fingerprinting-test-results-concerns-and-questions/20 https://discuss.grapheneos.org/d/19692-vanadium-fingerprinting/4

Disabling the JS wouldn't actually stop it in practice, because you'd stand out incredibly by the lack of data being provided in comparison to almost everyone else on the planet. The service just isn't adapted to that scenario and it would be trivially easy to set up a library to do it. You should use web services that respect your privacy and don't do such nefarious things as a first priority. No browser's fingerprinting protection works well at all and is highly dependent on having a crowd. On most implementations it's randomizing data points and hoping that the service admin isn't smart enough to correlate or to track the points that do not change.

The more invasive a site is about fingerprinting then any resistance towards it is increasingly less possible, final boss being services requiring you to KYC to use it. This would apply even for browsers with strict settings that do not change. Take a look at your display size, locale, timezone, GPU, for example or even benchmarking the device performance. In reality the fingerprint suggests a GrapheneOS user of a certain device with a VPN and it tries to keep that as much as it can which goes under the radar for more naive services.

We've developed a secure paste feature replacing traditional ...

2026-09-06T19:41:30Z

We've developed a secure paste feature replacing traditional clipboard APIs in #GrapheneOS. 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.

A small subset of apps including those written in Flutter implement their own text selection toolbar. We've worked around this by adding a Paste button to the default keyboard. We'll be replacing AOSP Keyboard with a much better keyboard and will carry over adding this feature to the new one too.

Android only permits the currently focused app and keyboard to read the clipboard. However, sensitive data often lingers around in the clipboard for a while and privacy invasive apps can read it. Android shows a notice for apps reading clipboard content set by other apps but by then it's too late.

Our approach is replacing the inherently problematic API-based clipboard access approach used by both desktop and mobile operating systems. It's another overhaul of the privacy model for apps similar to our Contact Scopes and Storage Scopes features. We have many of these privacy features planned.

We're well into the process of converting the Messaging app ...

2026-09-06T19:41:07Z

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

In the longer term, we plan to add support for RCS including support for the standard end-to-end encryption (E2EE) via Messaging Layer Security (MLS). Currently, RCS including E2EE is available on GrapheneOS via Google Messages. We want to avoid the need to use Google Messages for RCS eventually.

RCS on Android is currently implemented with code across the OS, Google Messages and Google Play services. Our plan is to start by making an equivalent to the portion in Google Messages. It would initially require sandboxed Google Play for RCS activation, etc. but we plan to implement that too..

RCS isn't an open platform in practice. It isn't even as open as SMS/MMS. It heavily depends on proprietary Google and carrier infrastructure in practice. We can start by replicating Google's approach and then we can work on only using carrier services for carriers where it's actually supported.

We're also going to be overhauling or fully replacing the rest of the AOSP apps in the near future. AOSP Gallery is incredibly outdated and is being entirely replaced. AOSP Keyboard may be similar. We recently hired a bunch of new people and will be hiring more so our progress will be accelerating.

In the past, our focus was nearly entirely on the base OS rather than bundled apps with alternatives available. We've heavily ramped up the resources we're investing into the bundled apps. We'll also be scaling up our work on the base OS too. More donations will enable us to hire even more people.

Latest GrapheneOS release implements automatic call recording. ...

2026-09-06T11:50:23Z

Latest GrapheneOS release implements automatic call recording.

quoting
nevent1q…chwm
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've been testing performance of MTE on the Pixel 11 using ...

2026-09-02T04:41:12Z

We've been testing performance of MTE on the Pixel 11 using the Android 17 QPR2 Beta 4 release adding back firmware support for it. MTE in asymmetric mode only has around 5% overhead in the standard benchmarks and other tests we've done. That's more than good enough but we've done limited tests.

Android 17 QPR2 Beta 4 on the Pixel 11 force disables MTE for the OS from the firmware. Using it requires ignoring the arm64.nomte parameter being passed to the kernel. It still isn't clear why they're making the feature unavailable. SVE was also force disabled in Android 17 but not in QPR2 Beta 4.

Our initial testing indicates performance isn't substantially worse. The overhead may be higher but there was an incremental CPU performance with the Pixel 11 which should more than make up for it. However, MTE is unavailable with stable firmware and we're bypassing firmware disabling it for QPR2.

Multiple Google engineers we've contacted have said they aren't able to give us any information about this so we're left doing reverse engineering and relying on leaks. The leaks do not seem reliable and do not match what we see. Our concern is that MTE may actually be broken due to CPU errata.

quoting
nevent1q…z630
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.

Android 17 QPR2 Beta 4 was released on August 28th. It's the first Beta release with Pixel 11 support. MTE support is still completely disabled in the OS and arm64.nomte is unconditionally passed by the firmware to the kernel. The good news is the firmware itself had MTE support added back to it.

It's possible to enable reserving the tag memory for MTE via `fastboot oem mte on`, boot a non-stock kernel ignoring arm64.nomte and use MTE. We're in the process of determining whether it's fully functional and the performance characteristics. It's likely disabled due to performance being ruined.

We expect performance must be quite bad for Google to have decided to entirely strip out support for it in not only the software but also the firmware so that no would could even try to use it before Android 17 QPR2 Beta 4. That's a very strange thing to do. It's at least added back to firmware now.

We reached out to multiple people at Google asking about the MTE situation on the Pixel 11 prior to making our original thread and didn't receive any responses. We still don't know what's wrong with MTE on the Pixel 11. It isn't clear if there are serious CPU errata or it simply performs very badly.

If the issue is simply that MTE performance is poor, then we can support the Pixel 11 in #GrapheneOS with the major caveat that it will be a significant performance downgrade. Aside from MTE, Google downgraded the Pixel 11 series GPU compared to the Pixel 10 series in addition to reducing RAM for base Pro models.

Google has been increasingly silent in response to any communications since dropping Pixel support from AOSP with Android 16 in June 2025. They could have told us MTE performance was significantly reduced so they disabled it at launch but will add it back to firmware for QPR2. That's still unclear.

Android 17 QPR2 Beta 4 releases for the Pixel 11 series were only uploaded around 10 hours ago rather than with the initial release on August 28th so this hasn't been available for very long. It wasn't missed by us or people who looked into it after our initial thread but rather wasn't out yet.

We have good news about the Pixel 11. It still has at least bare ...

2026-09-01T06:12:54Z

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.

Android 17 QPR2 Beta 4 was released on August 28th. It's the first Beta release with Pixel 11 support. MTE support is still completely disabled in the OS and arm64.nomte is unconditionally passed by the firmware to the kernel. The good news is the firmware itself had MTE support added back to it.

It's possible to enable reserving the tag memory for MTE via `fastboot oem mte on`, boot a non-stock kernel ignoring arm64.nomte and use MTE. We're in the process of determining whether it's fully functional and the performance characteristics. It's likely disabled due to performance being ruined.

We expect performance must be quite bad for Google to have decided to entirely strip out support for it in not only the software but also the firmware so that no would could even try to use it before Android 17 QPR2 Beta 4. That's a very strange thing to do. It's at least added back to firmware now.

We reached out to multiple people at Google asking about the MTE situation on the Pixel 11 prior to making our original thread and didn't receive any responses. We still don't know what's wrong with MTE on the Pixel 11. It isn't clear if there are serious CPU errata or it simply performs very badly.

If the issue is simply that MTE performance is poor, then we can support the Pixel 11 in #GrapheneOS with the major caveat that it will be a significant performance downgrade. Aside from MTE, Google downgraded the Pixel 11 series GPU compared to the Pixel 10 series in addition to reducing RAM for base Pro models.

Google has been increasingly silent in response to any communications since dropping Pixel support from AOSP with Android 16 in June 2025. They could have told us MTE performance was significantly reduced so they disabled it at launch but will add it back to firmware for QPR2. That's still unclear.

Android 17 QPR2 Beta 4 releases for the Pixel 11 series were only uploaded around 10 hours ago rather than with the initial release on August 28th so this hasn't been available for very long. It wasn't missed by us or people who looked into it after our initial thread but rather wasn't out yet.

Searching 'MTE' on Twitter to see countless established ...

2026-08-30T21:57:47Z

Searching 'MTE' on Twitter to see countless established security researchers shocked at the Pixel 11. Clear example on how to alienate a community.

I use Bitrefill and get no crashes, although I see I enabled JIT ...

2026-08-30T20:23:06Z

In reply to nevent1q…n7ww
_________________________

I use Bitrefill and get no crashes, although I see I enabled JIT in the past. Would need to use it more. Will see if others can reproduce.

We are advising people to NOT buy the 11th Generation Pixels due ...

2026-08-29T18:56:31Z

We are advising people to NOT buy the 11th Generation Pixels due to removal of hardware memory tagging (MTE), a crucial security feature used in GrapheneOS since their introduction on the Pixel 8. Either use a previous generation or wait for the first Motorola devices with GrapheneOS. We have not determined what to do about this.

quoting
nevent1q…c5hy
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.

Not without some weird hacky method I don't know about. ...

2026-08-29T10:56:03Z

In reply to nevent1q…cusd
_________________________

Not without some weird hacky method I don't know about. It's a developer feature so you can consider it incomplete.

None of their phones have that. I know the ThinkPhone exists but ...

2026-08-24T20:58:56Z

In reply to nevent1q…r62a
_________________________

None of their phones have that. I know the ThinkPhone exists but that was just a typical smartphone for enterprises.

I very much appreciate the human (or strong effort to make it ...

2026-08-22T16:26:14Z

I very much appreciate the human (or strong effort to make it appear human) design of the upcoming Monero site.

I hate extremely vibe coded web sites more than apps themselves. The web site is your space to promote and document your software, so in my eyes it has to be written by you because it represents the authors.

https://beta.getmonero.org/

Initial focus for our partnership with Motorola is a regular ...

2026-08-22T08:27:55Z

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.

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.

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.

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.

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.

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.

Pixels have become much harder to support. AOSP 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.

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.

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.

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.

in another language where the protection is not present*

2026-08-16T12:09:43Z

In reply to nevent1q…0czc
_________________________

in another language where the protection is not present*

848 Linux kernel CVEs published yesterday BTW ...

2026-08-16T11:37:04Z

848 Linux kernel CVEs published yesterday BTW

https://app.opencve.io/cve/?q=vendor%3Alinux+AND+product%3Alinux_kernel+AND+created%3D2026-08-15

quoting
nevent1q…huw8
347 Linux kernel CVEs published yesterday BTW

The Xous distro that the Passport Prime uses has the right idea ...

2026-08-12T23:23:59Z

In reply to nevent1q…tfhc
_________________________

The Xous distro that the Passport Prime uses has the right idea from a design standpoint. Microkernel, memory safe languages used throughout, mandatory sandboxing for apps. Xous is mostly designed for embedded systems. Obviously implementation is a different thing to rate compared to just the design. I also haven't looked into the hardware as much. I would take it as one of the better offerings the HWW market has right now.

Secureblue has a server distro, hardened CoreOS. I would assume a lot of these bitcoin one-click server dashboard distros aren't as hardened to such an extent. Perhaps it's a room for improvement for these projects.

A lot of defence corps sell their own OSes with the above as marketing, 'STOP OS' by BAE Systems comes to mind. Good luck being able to copy of it yourself though.

I'll get heat for this but I don't believe in the David ...

2026-08-12T02:15:25Z

In reply to nevent1q…7ws2
_________________________

I'll get heat for this but I don't believe in the David vs. Goliath narrative people have for Linux as some sort of bastion against 'big tech'. It's one of the most used OS/kernels in the world, mostly by big tech and their employees motivate most of its development. It's only because it's open source.

I think if people cared enough about competition they'd invest it into improving things like Qubes OS, Secureblue (a novel hardened Linux distribution) or a jump to newer OSes like making Redox OS more available to people.

Nostr event nevent1qqsy35le0uj0vw6c0zkmeuaerylx609ye559fs5utjwydp60xs9xzdczyzucmm2vat4zq7gdhjeux9qqdysqn56v07vj0s5xsddfnd6grfwzyalmxaf

2026-08-11T19:51:34Z

347 Linux kernel CVEs published yesterday BTW

What content from me would you want to see? Some of us are ...

2026-08-09T20:26:18Z

What content from me would you want to see?

Some of us are GrapheneOS are working on longer form content, akin to a blog. You'll find more deeper dives about Android, Mobile security and GrapheneOS there... but what would you want to see from me separate to it?

This won't entirely replace human reviews yet. The high point ...

2026-08-06T20:01:57Z

In reply to nevent1q…yksy
_________________________

This won't entirely replace human reviews yet. The high point of an AI agent's capabilities is only slightly over the capability of it's user. Actual research orgs have vulnerability disclosures exponentially increase with AI while an average dev will mostly just close out simple security deficiencies. Creating a PoC for exploiting a vuln is also resourceful.

Serious vulnerabilities held under embargo on Android have increased massively. You can see our changelog on the security preview patches per release and see how the list gets bigger even when some vulnerabilities get removed from the list as they become part of AOSP.

We should call software less buzzwords. Something that's ...

2026-08-06T19:50:50Z

We should call software less buzzwords. Something that's 'Cypherpunk', 'sovereign' and 'freedom' actually tells me nothing about their properties.

Android / GrapheneOS have a cryptographically secure pseudorandom ...

2026-08-04T03:38:30Z

In reply to nevent1q…dqz7
_________________________

Android / GrapheneOS have a cryptographically secure pseudorandom number generator which apps can use: https://developer.android.com/reference/java/security/SecureRandom

You would use this to help create entropy.

In response to recent suggestions mentioning it: > If you need ...

2026-07-29T21:28:39Z

In response to recent suggestions mentioning it:

> If you need plausible deniability, you must not use VeraCrypt to encrypt any part of (or create encrypted containers on) a device (or file system) that utilizes a wear-leveling mechanism.

https://veracrypt.io/en/Wear-Leveling.html

The decoy profile concept many have suggested for years is far more flawed than this. It wouldn't hide the presence of other profiles and would be trivially identified. Basic forensic software on a laptop would identify it without exploits. It would also make exploits far easier.

According to the defendant's motion to suppress in this case, ...

2026-07-23T22:45:37Z

In reply to nevent1q…2dsc
_________________________

According to the defendant's motion to suppress in this case, the authorities refused to read him his rights and also made extreme, unfounded accusations such as checking for CSAM (which was never implicated to be under their possession nor was the defendant ever indicted for it, it is not in any court docs) to try and coerce them into unlocking their phone. It appears he chose the Duress knowing he was not given his rights. I would be interested to see how this case develops.

Authorities CAN and WILL lie to you to try and incriminate you even if you have done nothing wrong. Do not talk to them, do not discuss your day and if you are in a questioning then exercise your right to remain silent and get a lawyer.

The bookmarks? We have that: ...

2026-06-23T23:16:34Z

In reply to nevent1q…mute
_________________________

The bookmarks? We have that:

Molly (hardened Signal client) is building a Signal server ...

2026-06-06T19:27:53Z

Molly (hardened Signal client) is building a Signal server software called Flatline. This will allow creating Signal deployments with servers that aren't Signal's. They'll also be working on features such as supporting accounts without phone numbers.

quoting
nevent1q…w4tr
As some of you may know, we're building Flatline, a self‑hostable soft fork of the Signal Server. It lets you run a mostly Signal‑compatible server for research and private deployments.

We already run a Flatline server in Bahnhof cloud for internal development.

#Signal #mollyim #flatline

This week, we patched a VPN leak in Android that was reported to ...

2026-05-10T00:40:14Z

This week, we patched a VPN leak in Android that was reported to Google but was ignored. Here is some coverage about that:

https://cyberinsider.com/grapheneos-fixes-android-vpn-leak-google-refused-to-patch

Here is the original vulnerability report:

https://lowlevel.fun/posts/tiny-udp-cannon-android-vpn-bypass/

Bitcoin Racing x GrapheneOS. ...

2026-04-26T00:09:58Z

Bitcoin Racing x GrapheneOS.

Use the Telegram official app if you use Telegram. You're ...

2026-04-05T11:26:29Z

In reply to nevent1q…8nky
_________________________

Use the Telegram official app if you use Telegram. You're using Telegram anyway. There's not really a "hardened" alternative I recommend like Molly for Signal.

(updated post) The Nekogram telegram client contains code that ...

2026-04-05T10:39:57Z

(updated post) The Nekogram telegram client contains code that grabs your Telegram ID and phone number to send to their own bots, also some other OSINT bots mentioned. They admitted to it in their channel (@NekoUpdates) and are insulting users in the comments. Assume your number and user can be correlated at a worst case. Keep away from third party clients.

https://github.com/Nekogram/Nekogram/issues/336

https://github.com/RomashkaTea/nekogram-proof-of-logging

The licensing for either makes it incompatible for bundling into ...

2026-04-04T17:37:15Z

In reply to nevent1q…r7yg
_________________________

The licensing for either makes it incompatible for bundling into GrapheneOS unfortunately. We are trying to keep the license consistent with AOSP. We do know some great apps that can fit, but we also may look to building our own apps for some. We already have two new devs working on improvements including Messages.

More things like Messaging, Keyboard, Gallery, Dialer, the ...

2026-03-25T21:32:07Z

In reply to nevent1q…p4sg
_________________________

More things like Messaging, Keyboard, Gallery, Dialer, the prebuilt apps. Terminal is something we can look at as well but there's a lot of user experience improvements we want to make with the everyday apps.

We are hiring Android app software engineers to develop and take ...

2026-03-25T19:38:40Z

We are hiring Android app software engineers to develop and take ownership of maintaining new #GrapheneOS default applications. This is a fully remote, worldwide position.

If you have experience in Kotlin, Jetpack Compose and shipping production Android applications with commitment to security and privacy principles, come help fruit the next chapters of GrapheneOS.

Apply:

https://grapheneos.org/hiring#android-apps-software-engineer

GrapheneOS will remain usable by anyone around the world without ...

2026-03-20T12:26:16Z

GrapheneOS will remain usable by anyone around the world without requiring personal information, identification or an account. GrapheneOS and our online services will remain available internationally. If GrapheneOS devices can't be sold in a region due to their regulations, so be it.

Lightning support in Cake Wallet should be huge for XMR nostr ...

2026-03-04T20:36:08Z

Lightning support in Cake Wallet should be huge for XMR nostr users

An important announcement from us at the #GrapheneOS project: ...

2026-03-02T12:37:31Z

An important announcement from us at the #GrapheneOS project:

quoting
nevent1q…lea5
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.

https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/

We are happy to announce a long-term partnership with Motorola. ...

2026-03-02T05:03:29Z

We are happy to announce a long-term partnership with Motorola. Together, we will collaborate on new future devices that meet our stringent privacy and security standards.

https://motorolanews.com/motorola-three-new-b2b-solutions-at-mwc-2026/

#GrapheneOS

They will be announcing it, not us ☝️

2026-02-21T15:07:18Z

In reply to nevent1q…ktyg
_________________________

They will be announcing it, not us ☝️

This March we hope to officially announce our OEM partner whose ...

2026-02-21T11:11:01Z

This March we hope to officially announce our OEM partner whose future devices shall work to support GrapheneOS.

Seeing Proton get heat on social media for their marketing again ...

2026-01-25T14:23:50Z

Seeing Proton get heat on social media for their marketing again so lets repost this. Treat these email services for what they are: Alternatives to Gmail or Outlook with a security perspective and automated encryption features.

Yes, people on social media can't read, but IMO they should approach their service in a different way ("A reasonably secure email provider" is my suggestion) If they don't want people ratioing them all the time... Most of these people getting the wrong answer is because their site can be pretty ambiguous about the technical details without searching a few pages deep for it. Posteo is an email provider that does openly clarify they can be compelled to intercept incoming emails in a better way than how Proton says it.

Still doesn't mean these services are a bad thing though.

quoting
nevent1q…ltja
Regarding the recent situation with Proton Mail, I have nothing to comment that I haven't said countless times already. I would need to understand more context about what the users they suspended did, which is in the clouds of social media conflict right now. It is abnormal to suspend a researcher, so I personally would like to see a more formal response from Proton on their justifications -- especially since accounts were reinstated after the matter went public.

In the meantime, let us go through a refresher your need-to-know on encrypted email providers. If you are aware already on how Proton Mail works technically and as a business, it should be of no surprise to know the following:

- Email is not end-to-end encrypted. Proton Mail encrypts received emails from external domains when they arrive unencrypted. The only encryption is in the transit between the two email providers, NOT the individual users. In theory, a service provider could be legally compelled to intercept email traffic and keep the readable copy as they arrive. Only Proton to Proton emails are end-to-end encrypted.

- "Zero-access encryption" is NOT "end-to-end encryption".

- Providers suspend accounts on their own due diligence. Should be no surprise companies suspend accounts from reporting from sources like CERTs, ISACs, anti-spam registries etc. If an email provider can't read the mailbox, then this or email contents being reported is the most information they get. Don't act shocked when they aren't on your side.

- Don't think irrationally: Removal of service is not at all related to information disclosure.
Certain information you provide to the service cannot be encrypted in a way that is unreadable to the service, for example, email account recovery information. It wouldn't be possible to restore accounts using information they don't know. Understand what information you provide to a service provider.

Overall: Don't use email for personal highly sensitive communications you believe could be disrupted by a service provider. If there is no way around this, encrypt the email contents and attachments yourself and leave a generic non-sensitive subject line so neither providers can read it. The same applies to self-hosting your own email. Use end-to-end encrypted messaging apps for communication. Keep emails for accounts.

Mail providers with mailbox encryption like Proton and Tuta provide encryption as a protection mechanism against data breaches. Using such services are a reasonable choice for someone who needs an email provider with a focus on account security and requiring only the minimum amount of information required to function. But, they are not an opsec silver bullet.

We're developing our own implementations of text-to-speech ...

2025-12-27T01:34:36Z

We're developing our own implementations of text-to-speech and speech-to-text to use in #GrapheneOS which are entirely open source and avoid using so-called 'open' models without the training data available. Instead, we're making a truly open source implementation of both where all of the data used for it is open source. If you don't want to use our app for local text-to-speech and speech-to-text then you don't need to use it. Many people need this and want a better option.

We are working on TTS first then SST. The TTS training data is LJ Speech https://keithito.com/LJ-Speech-Dataset/ and the model used is our own fork of Matcha-TTS.

If people want they can fork it and add/remove/change the training data in any way they see fit. It's nothing like the so-called "open" models from OpenAI, Facebook, etc. where the only thing that's open are the neural network weights after training with no way to know what they used to train it and no way to reproduce that.

Many blind users asked us to include one of the existing open source TTS apps so they could use it to obtain a better app. None of the available open source apps meets our requirements for reasonable licensing, privacy, security or functionality. Therefore, we've developed our own text-to-speech which will be shipping soon, likely in January. We'll also be providing our own speech-to-text. We're using neural networks for both which we're making ourselves.

update: I'm an idiot and that is meant to be a Star of David ...

2025-12-24T01:36:00Z

update: I'm an idiot and that is meant to be a Star of David not a pentagram (why the fuck is it red?)

quoting
nevent1q…syxd
(at the satanist conference) Alright guys we made the mobile operating system now all we need to do is set up THE CLUES

Next #GrapheneOS update will remove the messy End Session button ...

2025-12-23T21:54:36Z

Next #GrapheneOS update will remove the messy End Session button in the lock screen of secondary users. You'll be able to end session within the power menu or the user profile switcher UI instead.

Placing in the power button menu also means you're able to choose to power off in the same place, which could be a valuable protective measure greater than ending the session of the current profile.

Desktop Mode doesn't work well on high resolutions yet.

2025-12-18T18:58:10Z

In reply to nevent1q…gk46
_________________________

Desktop Mode doesn't work well on high resolutions yet.

Couple of fans messaged and recommended me these as examples. ...

2025-12-12T02:11:31Z

In reply to nevent1q…ze3p
_________________________

Couple of fans messaged and recommended me these as examples. I've also been suggested Half-Life. Let me know of other suggestions.

Footage of highly experimental GUI Linux virtual machine (and ...

2025-12-12T02:09:51Z

Footage of highly experimental GUI Linux virtual machine (and video games) in highly experimental desktop mode in #GrapheneOS.

quoting
nevent1q…urx4
The home screen, YakiHonne and Cake on experimental Desktop Mode in #GrapheneOS.

nevent1q…ugym

The home screen, YakiHonne and Cake on experimental Desktop Mode ...

2025-12-10T20:03:59Z

The home screen, YakiHonne and Cake on experimental Desktop Mode in #GrapheneOS.

quoting
nevent1q…ugym
This is how the Desktop Mode looks in #GrapheneOS. Here you can see how some apps look. Below is a screenshot of me typing this post in Amethyst and two instances of Vanadium on different profiles (Private Spaces) demonstrating unique VPN connections to the same applications on the same workspace.

Here is how the apps resize.

This will continue to be improved in the Android 16 QPR2 based release of GrapheneOS on the way and possibly be available outside of a developer option in Android 17.

This is how the Desktop Mode looks in #GrapheneOS. Here you can ...

2025-12-09T17:50:15Z

This is how the Desktop Mode looks in #GrapheneOS. Here you can see how some apps look. Below is a screenshot of me typing this post in Amethyst and two instances of Vanadium on different profiles (Private Spaces) demonstrating unique VPN connections to the same applications on the same workspace.

Here is how the apps resize.

This will continue to be improved in the Android 16 QPR2 based release of GrapheneOS on the way and possibly be available outside of a developer option in Android 17.

Web hosting / low spec VPS providers that accept Lightning... Go ...

2025-12-02T20:23:18Z

Web hosting / low spec VPS providers that accept Lightning... Go

Bonus points for domain registrar.

Time to put some value back on some sats.

We now have experimental support for the Pixel 10, Pixel 10 Pro, ...

2025-11-26T02:02:30Z

We now have experimental support for the Pixel 10, Pixel 10 Pro, Pixel 10 Pro XL and Pixel 10 Pro Fold.

Our initial 2025112500 release for these is available through our web installer or releases page on our staging site. Download and test #GrapheneOS for your Pixel 10 at:

https://staging.grapheneos.org/install/web
https://staging.grapheneos.org/releases#devices