GrapheneOS Overhauled Default Apps and Secure Clipboard
Cider9986
246 points
185 comments
September 06, 2026
Related Discussions
Found 5 related stories in 54.7ms across 5,720 title embeddings via pgvector HNSW
- GrapheneOS protections against data extraction from locked devices Cider9986 · 401 pts · July 26, 2026 · 57% similar
- GrapheneOS recommended for domestic abuse victims aussieguy1234 · 62 pts · July 17, 2026 · 56% similar
- GrapheneOS Defends Data-Wiping Function That Blocked US Border Search pseudolus · 155 pts · July 28, 2026 · 56% similar
- A Journalist had his mobile phone seized. Did using GrapheneOS protect his data? rzk · 11 pts · July 23, 2026 · 55% similar
- GrapheneOS duress PIN could land a man in prison kitd · 18 pts · July 26, 2026 · 54% similar
Discussion Highlights (14 comments)
Cider9986
twitter versions have paragraphs not threads https://xcancel.com/GrapheneOS/status/2096677808424788256#m https://nitter.click/GrapheneOS/status/2096677808424788256#m https://bsky.app/profile/grapheneos.org/post/3muun5c4fdc2o Secure paste: https://xcancel.com/GrapheneOS/status/2096685327020933355#m https://nitter.click/GrapheneOS/status/2096685327020933355#m https://grapheneos.social/@GrapheneOS/117225731764489295 https://bsky.app/profile/grapheneos.org/post/3muupuvlfbs2v
IshKebab
Very good idea! Google abandoned these long ago. I don't really get why so many Americans want RCS to succeed though. Do you guys not remember when carriers charged 10p/text? Why on earth would you want to give any power at all back to those people?
kotaKat
"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." Except... what carriers still remain using their own RCS carrier services and haven't been pressured by Google to adopt Jive?
thinkp26
I'm happy todays update shipped auto call recording.
exceptione
> 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. What is the point of RCS though? It seems to be strictly inferior to Signal. It seems a Google product meant to serve Google. I wouldn't hate it if GrapheneOS would totally ignore RCS. I fail to see any value in it, but maybe I am lacking information(?)
goda90
I believe this is the planned gallery app. I've already been using it: https://github.com/IacobIonut01/ReFra
andrepd
There are excellent FOSS gallery apps already, like the Fossify suite. Why not use them I wonder?
lucb1e
Ctrl+f clipboard, no results. What does "Secure Clipboard" in the title refer to? The release seems to be only the SMS/RCS app, rest is future: > 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.
drnick1
Certainly, with Opus 5 and GPT-6, modernizing or even completely rewriting self-contained, non-critical tools seems like a Friday afternoon job now. I wonder however how important this is, in the grand scheme of things. I use GrapheneOS and the bundled messaging app is serviceable. It isn't pretty, but it gets the job done.
ravenstine
I hope they replace the AOSP keyboard with FUTO keyboard. I'm mostly fine with the other stock apps, but that keyboard was the one thing I absolutely had to end up replacing due to its jenky behavior.
pizzaiolo
Graphene is clearly bullish on Android, but I have no idea why. The writing is on the wall, Google is slowly asphyxiating AOSP.
cwillu
“We'll be making a new release later today with a completely overhauled user interface written in ‹whatever›” is something developers love, and users fear.
water-drummer
Funny reading those anti-LLM comments, lol
yellowapple
> 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. Hell yeah. Google Messages has worked reasonably well for RCS so far (after a long and frustrating period where it didn't on T-Mobile), but having a non-Google option will be huge.