MetropleX [GrapheneOS] ⚡🟣🟠

Freedom is the right of ALL sentient beings.
Privacy is your Responsibility & Obligation
Oversharing is not Caring
Priv/Acc
Human
GrapheneOS Advocate/Mod
#GrapheneOS

[Matrix]: @metroplex:grapheneos.org
Discord: https://grapheneos.org/discord
Matrix: https://matrix.to/#/#community:grapheneos.org

Personal Acct. Views Explicitly My Own
Likes and/or Boosts ≠ Endorsements

Public Key

npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c

NIP-05 Address

grapheneos.metroplex.bot

Profile Code

nprofile1qqsyxcm6xydptuwz2w6avpmc4d65ftrrnwywz688yf9fqr22gy5rrqcpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsxemgxv

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c

Show more details

Published at

2026-09-12T09:35:56Z

Kind type

0 Metadata

Event JSON

{ "id": "d470541dbf39330a3d184e5e3e16fc6f02a165e981d1ae3cdc8d66eaf82031bf", "pubkey": "43637a311a15f1c253b5d60778ab7544ac639b88e168e7224a900d4a41283183", "created_at": 1789205756, "kind": 0, "tags": [ [ "alt", "User profile for MetropleX [GrapheneOS] ⚡🟣" ], [ "name", "MetropleX [GrapheneOS] ⚡🟣🟠" ], [ "display_name", "MetropleX [GrapheneOS] ⚡🟣🟠" ], [ "picture", "https://grapheneos.social/system/accounts/headers/109/978/606/244/448/759/original/0af794da2de7c424.jpg" ], [ "banner", "https://grapheneos.social/system/accounts/headers/109/978/606/244/448/759/original/0af794da2de7c424.jpg" ], [ "website", "grapheneos.org" ], [ "about", "Freedom is the right of ALL sentient beings.\nPrivacy is your Responsibility \u0026 Obligation\nOversharing is not Caring\nPriv/Acc\nHuman\nGrapheneOS Advocate/Mod\n#GrapheneOS\n\n[Matrix]: @metroplex:grapheneos.org\nDiscord: https://grapheneos.org/discord\nMatrix: https://matrix.to/#/#community:grapheneos.org\n\nPersonal Acct. Views Explicitly My Own\nLikes and/or Boosts ≠ Endorsements" ], [ "nip05", "[email protected]" ], [ "lud16", "[email protected]" ], [ "client", "Amethyst" ], [ "pronouns", "Auto/Bot" ], [ "i", "twitter:Metr0pl3x", "1636139885613527047" ], [ "i", "mastodon:grapheneos.social/@metr0pl3x", "110056299484013759" ] ], "content": "{\"name\":\"MetropleX [GrapheneOS] ⚡🟣🟠\",\"username\":\"Metr0pl3x\",\"display_name\":\"MetropleX [GrapheneOS] ⚡🟣🟠\",\"displayName\":\"MetropleX [GrapheneOS] ⚡🟣\",\"picture\":\"https://grapheneos.social/system/accounts/headers/109/978/606/244/448/759/original/0af794da2de7c424.jpg\",\"banner\":\"https://grapheneos.social/system/accounts/headers/109/978/606/244/448/759/original/0af794da2de7c424.jpg\",\"website\":\"grapheneos.org\",\"about\":\"Freedom is the right of ALL sentient beings.\\nPrivacy is your Responsibility \u0026 Obligation\\nOversharing is not Caring\\nPriv/Acc\\nHuman\\nGrapheneOS Advocate/Mod\\n#GrapheneOS\\n\\n[Matrix]: @metroplex:grapheneos.org\\nDiscord: https://grapheneos.org/discord\\nMatrix: https://matrix.to/#/#community:grapheneos.org\\n\\nPersonal Acct. Views Explicitly My Own\\nLikes and/or Boosts ≠ Endorsements\",\"nip05\":\"[email protected]\",\"lud16\":\"[email protected]\",\"pronouns\":\"Auto/Bot\"}", "sig": "4517c48046bb353d13cee79b7c35a9f2b9b39a09031e64d5370459aa0f330aa77a82aa0dbbd3c62d76149926129621046ae00579f1a0608cbf7075872037c829" }

Last Notes

2026-10-04 09:34:17 GMT

- reply

No worries bud 😊

2026-10-04 09:30:48 GMT

- reply

No see the latest blog post:
https://accrescent.app/blog/posts/a-tale-of-too-many-protocols/

2026-10-04 06:15:08 GMT

- reply

They mean instead of whatabouttery actually provide and develop a proof of concept. Make it no longer a what-if question.

2026-09-27 19:54:52 GMT

If you have just or are planning on joining the global family of GrapheneOS users, you are doing so at a time of accelerated progress and change on a UI/UX basis. Great to have you along for the journey.
#ThingsAreHappening #GrapheneOS
#nevent1q…yq2v

2026-09-27 16:05:53 GMT

- reply

Yeah I know but I have a Zapraiser going lol 😁

2026-09-27 00:11:34 GMT

- reply

Not I...

2026-09-24 14:20:57 GMT

Almost half way to the Zapraiser target.
Nostr is dead 😜
#NostrIsDead
Thankyou everyone so far 🙏

2026-09-21 20:23:22 GMT

- reply

Misread me, I agree with your position, but despite FIAT digital non cash transactions having inherant issues people who may not have the knowledge or confidence to engage with it should be able to without issue or hinderance give their money to a non profit like GrapheneOS without issue. Them being KYCd should be fine as donating to us shouldn't be a mark against them etc.

2026-09-20 22:24:14 GMT

- reply

Part of freedom is allowing people the ability to choose for themselves. We offer what many would deem the better option, however it must be remembered donating to GrapheneOS is not and should not be considered an illicit activity.

2026-09-20 17:54:49 GMT

- reply

Not a fan myself but if people choose to use it and WISE they presumably understand the need for the request and are happy to provide the full non initialed name.

2026-09-20 16:14:15 GMT

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.
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.

2026-09-20 08:21:29 GMT

Almost 10% there in under 24 hours.
Target is approx 83k sats.
Thankyou Nostr 🤝🙏🚀💜
#nevent1q…s426

2026-09-19 21:29:03 GMT

"2026 DeGoogle Mobile Telemetry Study: 72-Hour Packet Capture Dataset
How much data does a phone secretly send to Google when you are not using it? Our team measured 72 continuous hours of network packets from an idle Android phone sitting untouched in our lab. Here is our raw dataset, our test setup, and what it means for your privacy."
https://www.praveentechworld.com/research/degoogle-telemetry-2026
https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/409ea1f846f5a5dc5cdfd51aca29812c0a2e3a0df19f3d72cfa6342061af690f.jpg

2026-09-19 21:16:47 GMT

- reply

82562 Approx

2026-09-19 20:59:47 GMT

- reply

Approx 82562

2026-09-19 20:24:09 GMT

GrapheneOS Zapraiser Challenge
I remember Nostr being that vibrant a Zapraiser like this wouldn't pose a problem.
Your challenge if you choose to accept it is to max the Zapraiser for which I also commit to matching the donation from my own funds. On making rhe target I will send on chain to the project and provide the proofs.
Good luck Nostr!
#nevent1q…2lqs

2026-09-19 18:10:36 GMT

- reply

Already available in the latest release. If on stable channel try Alpha/Beta.
https://grapheneos.org/releases#2026091700

2026-09-19 17:33:56 GMT

- reply

Thankyou for this literal explanation of a promotional post. 🫤

2026-09-19 17:27:48 GMT

What is that? Another pioneering privacy feature in your class leading privacy and security focused OS?
You CTRL-Clipboard.
#nevent1q…rdmu

2026-09-19 17:25:26 GMT

Quick App Review
Google Maps
Slow, delayed, no lane guidance on trunk roads, intentionally tries to destroy your clutches navigating you onto single track back roads in rural areas in the UK to save 2 minutes, in both cases self navigating on return journey was quicker and safer.
TLDR: Shit
I usually use Organic Maps or CoMaps however my co-pilot preferred GMaps, I use the past tense intentionally.

2026-09-17 20:06:35 GMT

- reply

I'm keeping 🤞 for that GrapheneOS x Moto Razr Flip I want.
Never did get over this... https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/dc9765de101be68c9fdd6aae212392745e30b9aa41cca88ff553d8d1c6858799.jpg

2026-09-17 19:59:39 GMT

Current state of play regards our continued research into possible support for 11th Gen Pixels and the MTE situation:
#nevent1q…sy6a

2026-09-17 19:58:06 GMT

- reply

This being said:
> 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 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 our 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'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. SME was also force disabled in Android 17 but not in QPR2 Beta 4.
> There have been multiple leaks from Google including info published on news sites indicating hardware related to MTE was cut. There have also been leaks indicating it has performance issues and that's why it was initially fully stripped out at a firmware level firmware and is force disabled in QPR2.
> 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.

2026-09-17 19:48:47 GMT

- reply

Should be updated soon, if not as part of the next release as we increase the patch level to match:
https://source.android.com/docs/security/bulletin/pixel/2026/2026-09-01
> "For Google devices, security patch levels of 2026-09-05 or later address all issues in this bulletin and all issues in the September 2026 Android Security Bulletin."

2026-09-17 18:08:45 GMT

- reply

I even managed to find a VHS but never found the one my Father came home with randomly one day. Unfortunately that one was sold during a house clearance I didn't manage to save it from.

2026-09-17 18:07:24 GMT

- reply

ME TOO! Do you know anywhere that has it available? Can only find the US one on YT for example.

2026-09-17 15:47:20 GMT

- reply

You remember it as the combined anime as released in the US with Major Chance or the European Goshogun unaltered English dub?

2026-09-17 11:54:26 GMT

Being that GrapheneOS had always shown Google up, enabling, providing cutting edge up to the minute patches & updates on Pixels, even before them. Their latest tactics are likely mitigations for that embarrassment, yet instead of them doing better they made everything worse for all, out of spite.

2026-09-17 11:51:45 GMT

GM Nostrland
https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/cbfa9298ae0158a340871f85bb14aca23673a15d2c32a656275aefa3f12517b3.mp4

2026-09-16 21:21:21 GMT

- reply

This nust be how he envisages Nostr, a veritable enchanted castle... https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/077c0927c873339dae5539d26ddd73ba6a4c0ce62011888d4211369986dd94b0.mp4

2026-09-16 20:44:11 GMT

- reply

It is, and we will continue to look into it.
https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/6e554526c2c7eb051f43942d30576d0dc2033fa531d0518b81126dc66ba39a77.mp4

2026-09-16 20:16:41 GMT

GrapheneOS continues to reveal Googles active hobbling of the ability of OEMs to protect their users in favour of market exclusivity/protection, and pushing ahead with monopolistic anti competitive abuse hand in glove with GPL violations.
Read below the break for the teams detailed analysis:
> Android 17 QPR1 is the first release since Android Honeycomb (3.x) adding new APIs for app developers without a release to the Android Open Source Project. The new APIs are currently exclusive to the Pixel OS and aren't available to other Android OEMs.
> https://developer.android.com/sdk/api_diff/37.1/changes
> Non-Google Android OEMs and AOSP-based projects can ship yearly and QPR2 releases. There are also security backports to those releases. Security preview access is needed to ship patches without months of delay. We've had that since before our Motorola partnership via another OEM.
> We already ported our code to Android 17 QPR1 since before it was released on September 15th but don't have permission to release it yet. We're working on backporting Pixel firmware, kernel drivers, userspace drivers and HALs from Android 17 QPR1 to Android 17 for now instead.
> Pixel Update Bulletin for September 2026 has additional patches to standard Android platform components used by non-Pixel devices. These patches are relevant to non-Pixel devices but haven't been made available via the September 2026 Android Security Bulletin or preview patches.
> Google should not be gatekeeping security patches to the standard Android platform code from Android OEMs but that's what they've started doing. Other OEMs will get these patches in December 2026 via Android 17 QPR2. We can ship them early by reverse engineering the code instead.
> It would be interesting to know if Google's legal team is aware they're giving Pixels months of early access to new Android features and bug fixes including certain important security patches. Pixels being given this competitive edge over Google's OEM partners is very dubious.
> 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.
> 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.
> 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.
> 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.

2026-09-16 19:58:35 GMT

GrapheneOS Pixel 11 Research results in Googles MTE removal continuong to emain a mystery...🕵️‍♂️
> 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.

2026-09-16 07:41:39 GMT

- reply

Google refused via this?
https://support.google.com/pixelphone/answer/15009955?hl=en-SE

2026-09-15 15:08:31 GMT

- reply

Dude you know they replace these screens free of charge right? Had mine and the OH screens done while-u-wait in my local repair centre.
Love my 8 still going strong no battery issues and I use it regularly plugged in for hotspot at 100% which many suggest is terrible abuse of a li-ion, li-po battery.
Performance can be meh but I dont game and use all GOS features without much overhead impact.
Pixels aren't refined sure but they are utilitarian.

2026-09-13 11:48:46 GMT

- reply

GM love the image, giving off Another World vibes..

2026-09-13 11:48:14 GMT

GrapheneOS doesn't ever stand still, if you think thibgs are quiet it's only ever because the project team are doing some heavy lifting in the background so that the OS comes out swinging and more robust than ever. Leaving no stone unturned.
We fight for the users, empower yourself...
#nevent1q…x7zr

2026-09-12 14:54:53 GMT

Of course it impacts your life, sharing anything tied to you as a person, on any platform you don't pay for or device corporations poll your daily habits freely from creates data sets of behaviour they & state can/will/do use for psychological manipulation more insidious than propaganda/agitprop.
They are right that the paranoid who believe themselves to be directly targeted is ridiculous as random individuals but the intention behind it is targeting broad swathes of society or society writ large. Their thread is very Belgian. Their prescription very theological. The state is not God.
https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/a0d59d6f7d8619951231bf8ae39e51c67b02e22117e90a0ca99d10f1fccb4edf.jpg

2026-09-11 21:04:31 GMT

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.
#nevent1q…g0mh

2026-09-11 08:49:08 GMT

- reply

#nevent1q…64qm

2026-09-11 08:45:57 GMT

This issue is not public, but based on this information we deem it unlikely that Google will do anything about it. GrapheneOS is aware of the issue and are working on a fix.
As always, it is most important to only install trusted apps on your device, and (if possible) use a security and privacy focused Android fork like GrapheneOS.
https://mullvad.net/blog/another-way-to-leak-traffic-on-android-has-been-discovered

2026-09-10 22:33:52 GMT

- reply

Ahh I do it the English way with my bitter, just sink it. 🤪🍻

2026-09-10 21:15:52 GMT

- reply

Just the ideological Fediverse cybersecurity experts who don't want people using AI to find exploits that hostile actors most certainly will be doing. Believing somehow using AI as a tertiary tool adding to and not subtracting from our existing framework and holistic approach to code standards, code review and testing is the same as media based generative AI trained on stolen work product and art work when no different than AI playing chess or go and operating in a pre-existing logic based system no different than learning a language.
They make the same gate keeping arguments you'd expect to find over the birth of the internet and giving away knowledge by using/scanning the written word, following on from what the printing press did too.
They think throwing their vitriolic metaphorical sabots at us is morally justified.
I mean, they literally want the power left in corporate and state hands and to walk around like this pretending by not using it we have something keeping us secure while the gaping holes are there for those using it for exploits expose and use them. https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/435bab7f43a78140f6379d1545ae49b341c5e0f2e39f2c2f608794c28ec7f1a3.mp4

2026-09-10 14:43:42 GMT

More progress is being made by companies understanding the drawbacks of Play Integrity API and the benefits of supporting genuinely secure and private alternate OS.
Quote:
> We have currently decided to allow GrapheneOS for use with the TK app, provided that the device's integrity check is successful. Google Play Services are still required to launch the TK app. Going forward, we would like to further reduce our reliance on them.
https://www.tk.de/techniker/versicherung/krankenkasse-anliegen-online-erledigen/tk-app/tk-app-geraeteauswahl-2023672#unterstuetzte-betriebssysteme-und-custom-roms

2026-09-10 11:43:54 GMT

The absolute hysterics over on the Fediverse...

2026-09-07 14:52:52 GMT

When you buy a vintage board game & come across gems like this that most Gen Z wouldn't even think of nor know about thanks to the capture of educational institutions refusing to impart knowledge of the dark side of the left. The tyrannical tools of state they only believe exist on the right. https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/9be06f8920d047bb8898c26b1e7765883562add7246848604ae524a04deddfed.jpg

2026-09-07 11:39:16 GMT

GM Nostr-nam https://npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c.blossom.band/7c7535fcea80370e50d5ab88a82cd0c34841d64b57b082a65165783bc9dc81e5.jpg

2025-09-11 22:16:02 GMT

As Freeborns OH has the issue some others may have noticed it too.
The official project response follows:
Google and carriers deployed changes to RCS which have been breaking it for many users on the stock OS including with certain carriers and in whole countries. The changes appear to have specifically impacted GrapheneOS users too. It's not related to our September 8th update. We're working on it.
You can find many recent threads about people having issues with RCS in Google Messages while using a stock OS with Google Mobile Services. There are articles about how some carriers and countries no longer have it. It still works for most people but the changes definitely regressed compatibility.
GrapheneOS users were impacted by these recent changes much more than other users. We don't know why yet but we're working on determining that and restoring compatibility with Google Messages for people who use it. We'll try to get compatibility with the new way it functions implemented very soon.
#nevent1q…f3yr

2025-09-11 22:14:50 GMT

- reply

Google and carriers deployed changes to RCS which have been breaking it for many users on the stock OS including with certain carriers and in whole countries. The changes appear to have specifically impacted GrapheneOS users too. It's not related to our September 8th update. We're working on it.
You can find many recent threads about people having issues with RCS in Google Messages while using a stock OS with Google Mobile Services. There are articles about how some carriers and countries no longer have it. It still works for most people but the changes definitely regressed compatibility.
GrapheneOS users were impacted by these recent changes much more than other users. We don't know why yet but we're working on determining that and restoring compatibility with Google Messages for people who use it. We'll try to get compatibility with the new way it functions implemented very soon.

2025-09-11 22:09:28 GMT

- reply

Had this asked in our testing room, so enabled it and plugged in, and it stopped at 83%. Going to leave it like this and continue over the weekend but on the very latest release I can't replicate on Pixel 8.

2024-04-06 18:40:06 GMT

- reply

Quad9.net

2024-04-02 23:52:46 GMT

- reply

GrapheneOS has been working on a duress PIN/password feature for a while, and as part of that we already implemented our own wipe-without-reboot system. We care a lot about doing things properly and the way this was done in existing apps and operating systems was highly insecure.
Can see the announcement of these being exploited in the wild at https://source.android.com/docs/security/bulletin/pixel/2024-04-01#Announcements.
In addition to them working on our proposal to implement wipe-without-reboot, we've spotted work on our other suggestions such as wiping key derivation results from memory after unlocking.

2024-04-02 23:49:12 GMT

April release of the Pixel boot chain firmware includes fixes for 2 vulnerabilities reported by GrapheneOS which are being actively exploited in the wild by forensic companies:
https://source.android.com/docs/security/bulletin/pixel/2024-04-01
https://source.android.com/docs/security/overview/acknowledgements
These are assigned CVE-2024-29745 and CVE-2024-29748.
source.android.com
Android Security Acknowledgements | Android Open Source Project
CVE-2024-29745 refers to a vulnerability in the fastboot firmware used to support unlocking/flashing/locking. Forensic companies are rebooting devices in After First Unlock state into fastboot mode on Pixels and other devices to exploit vulnerabilities there and then dump memory.
We proposed zeroing memory in firmware when rebooting to fastboot mode to wipe out the whole class of attacks. They implemented this by zeroing memory when booting fastboot mode. USB is only enabled by fastboot mode after zeroing the memory is completed, blocking these attacks.
GrapheneOS already implemented defenses against this attack before we became aware of it. After becoming aware of this attack against Pixels running the stock OS, we improved our existing defenses and added new ones alongside reporting the firmware weaknesses to get those fixed.
CVE-2024-29748 refers to a vulnerability providing the ability to interrupt a factory reset triggered by a device admin app. It appears they've implemented a partial solution in firmware. See https://twitter.com/GrapheneOS/status/1772616917611585809 about ongoing work we spotted on wipe-without-reboot support.
Google is publicly working on a fix for the factory reset vulnerability we reported:
https://android-review.googlesource.com/c/platform/frameworks/base/+/3008138
Currently, apps using device admin API to wipe do not provide any security against a local attacker since you can interrupt them. Forensic companies are aware of this.
Show more
GrapheneOS has been working on a duress PIN/password feature for a while, and as part of that we already implemented our own wipe-without-reboot system. We care a lot about doing things properly and the way this was done in existing apps and operating systems was highly insecure.

2024-03-22 12:52:02 GMT

When you level up your coffee game and the homebrew matches, note for note, the experience from the roastery. ☕💯😋 #DialedIn

2024-03-21 12:56:00 GMT

- reply

Not the only sketchy thing about that council...
"i approached five Labour councillors representing the Spinney Hills and North Evington wards, where many textile factories are located, about the situation. None of them responded."
https://inews.co.uk/news/leicester-sweatshop-scandal-one-year-on-exploitation-abuse-prosecutions-1134805

2024-03-18 13:46:10 GMT

- reply

Tested and confirmed also spoke with dev team, this is upstream with AOSP unfortunately.

2024-03-17 22:12:26 GMT

- reply

This popup DOES appear on GrapheneOS regardless of Play Services being installed or not. https://image.nostr.build/d4635136be82992fb6d48d941cb01377b04a07e38baf43ad018d703970256ab1.jpg

2024-03-15 18:06:54 GMT

- reply

This and on the cutting edge, be an Alpha 😜
#nevent1q…fuh0

2024-03-15 18:05:00 GMT

- reply

I know what you mean but you're approaching the question from the wrong perspective.
It works on any phone that supports it, just happens to be that Pixels are still the only ones that do. We're waiting and willing others to do the same. It's a damning indictment of the mobile device landscape that they haven't and don't.

2024-03-15 14:02:06 GMT

GrapheneOS Current Android QPR2 Bluetooth Compatibility statement:
Due to mainline modules, the Stock Pixel OS is currently using a much older release of the Bluetooth module than the current release in the Android Open Source Project without current security patches. We believe this is the reason for remaining issues not occurring for stock.
The remaining compatibility issues with a small number of devices such as the past couple generations of Galaxy Watch hardware appear to be the consequence of the March security patches and other changes in QPR2. There's a solid chance the Bluetooth devices are what's buggy.
GrapheneOS is on Bluetooth module version 990090000 from the Android 14 QPR2 release. Stock Pixel OS is still using 341313030, without tags available for that. Needs to be addressed even if simply by tagging the older Bluetooth module release being separately built/shipped.

2024-03-15 08:52:32 GMT

- reply

Menu>Settings>Wallet will allow you to use any NWC (Nostr Wallet Connect) enabled service (eg Alby).

2024-03-15 06:55:05 GMT

- reply

Don't use their wallet so all good 👍

2024-03-14 22:07:44 GMT

- reply

Change your Vanadium release channel to Alpha in the Apps app and ensure you are using the latest version.

2024-03-14 19:53:54 GMT

- reply

Vanadium is significantly more secure. It provides strict site isolation for the sandbox and type-based control flow integrity which are not normally available for mobile Chromium. It also disables JIT compilation by default, another setting not normally available on mobile.
See https://grapheneos.org/features#vanadium.
Brave currently has a more advanced content filtering engine with broader content filters due to supporting more syntax. It also has more complete state partitioning. Vanadium will be implementing more complete state partitioning in the near future.

2024-03-13 14:08:51 GMT

Android is moving towards completing one of the areas of verified boot which currently only works in GrapheneOS. They never fully adopted verifying out-of-band system APK updates with fs-verity and then disabled it. They're now moving towards using APK Signature Scheme v4.

2024-03-13 14:06:56 GMT

- reply

Said raids and harassment often involves CSAM and gore. We have members of our community across the age range.
https://m.primal.net/HkRW.png

2024-03-13 08:58:30 GMT

- reply

From a moderation view point and the fact the Matrix protocol suffers from state reset bugs that brick rooms, it makes perfect sense.

2024-03-09 18:26:35 GMT

- reply

Current face unlock support is much lower security than what was provided for Pixel 4 face unlock.
Pixel 4 had dual infrared cameras + dot projector + flood illuminator which provided a more secure approach than a fingerprint scanner. Pixel 7 > approach is far worse, 8 not massively better.
Pixel 4 was very expensive partly because they added all that fancy hardware for very secure face unlock along with a tiny radar on the front (Soli) for motion sense features. These have never been made the standard since.
Where additional functionality doesn't improve upon the existing options such as a random 6 digit pin with secure element throttling and fingerprint biometrics will mean it will always be triaged.

2024-03-08 23:47:52 GMT

- reply

I would suggest reading this thread:
https://x.com/GrapheneOS/status/1397952450108313600?s=20
If you haven't got X and can't find a nitter instance still running or alternate method let me know and I'll take the time tomorrow to paste the entirety.
Yes GrapheneOS is against persistent app accessible root access. As an open source project you are free to make whatever changes you wish to implement whatever options you desire. You can make debug builds etc as suggsted in the thread to determine the level of root you might desire and the method of it's operation.
It is your device, your prerogative and power to you.
Initial build instructions can be found here:
https://grapheneos.org/build
However as a privacy and security focused OS with clearly stated scope and high standards with many high risk individuals and organisations depending on it, it would be anathema to claim to be reducing attack surface while providing easily accessable tools and methods to do the exact opposite.
Good luck in your endeavours.

2024-03-08 23:23:32 GMT

- reply

I believe I have followed a Jack. yes.

2024-03-08 23:22:31 GMT

- reply

Not the PWA (Progressive Web App) but the actual Android app.

2024-03-08 23:01:45 GMT

Running #Primal native Android for a week. So far, so slick.

2024-03-05 17:05:29 GMT

GrapheneOS QPR2 Development Update:
Android 14 QPR2 is the first release following a new approach which means the changes are as large as Android 13 QPR3 to Android 14 were, resulting in a difficult port where there may be regressions to contend with.
As always donations for the project and the hard working development team are welcome at: https://grapheneos.org/donate
Read more below 👇
Official Project Release:
This month's Android release is the first one based on the new development model heavily centered around quarterly releases. It's essentially an early variant of Android 15 with many of the features disabled via feature flags. We're essentially doing a major yearly release port.
We were aware this was going to be the case, but it's still going to take a bit longer than usual. This port should be the hardest one since it's the first one. Future quarterly and yearly releases should be much smaller than this one. It should make the yearly ports much easier.
There's going to be a temporary disruption for us from moving to the first quarterly release under the new model. We didn't treat it as a yearly release with lots of preparation but we'll try to get it as done as quickly as the Android 14 release where we prepared for months.
Despite causing a lot of pain for us for this first migration, the new release model should be a substantial benefit to us. It will mean the changes are spread out throughout the year in quarterly releases and many will get shipped disabled via feature flags so we can port early.
In the very short term, this is a massive pain and disruption for us where we need to put in similar work this month as we did for the yearly Android 14 and Android 13 ports. Going forward, things should be easier. It may also help mitigate the issues caused by mainline modules.
Nearly all our changes are ported and we have builds running in the emulator. There's a lot of work remaining to fix regressions and get device support working. If we aren't done by the end of the day, we can do a security backport release. We'd prefer avoiding an extra release.
We're likely going to need to move the end-of-life Pixel 4a (5G) and Pixel 5 from extended support to legacy extended support. This is a major release with a similar level of changes as Android 13 QPR3 to Android 14, and we don't want to waste our resources on insecure devices.

2024-03-03 01:37:48 GMT

- reply

Spent hours with my siblings playing this on our AMIGA 500 growing up.
https://image.nostr.build/9210177a54a7088c1144ec65c6c18a2a792537332122c65729a821e347b11242.jpg

2024-03-01 20:21:26 GMT

- reply

I'll revisit been an #Amethyst loyalist up to now 😄

2024-03-01 16:39:35 GMT

It would be really useful if there was a way to stop boosts by followers of people you already follow not appearing in the main timeline. My thumb has RSI, Repetitive Scroll Injury.

2024-03-01 16:24:04 GMT

- reply

A good article on threat modelling:
https://privsec.dev/posts/knowledge/threat-modeling/
#nevent1q…atra

2024-02-26 21:30:40 GMT

- reply

https://image.nostr.build/f34a3d99f5bf37c76c0ca564f6f7add33c39a1ed43c1d728efb34895d7205bdf.jpg
#nevent1q…8wd8

2024-02-26 09:42:38 GMT

- reply

Can you raise this as an issue on the issue tracker if you haven't already done so?
https://github.com/GrapheneOS/os-issue-tracker/issues

2024-02-25 23:54:01 GMT

- reply

Try enabling exploit protection compatibility mode:
https://discuss.grapheneos.org/d/2610-chase-bank-mobile-app-wont-load-recent-issue

2024-02-25 23:45:50 GMT

- reply

Same...
https://image.nostr.build/24c5921750766025a451d24817835e4345ce1ed1fd4c859e4046d8f236a2bd8d.jpg

2024-02-24 17:21:00 GMT

- reply

Just be aware that the patch date is an editable string and LineageOS misleads by doing so. The patch date should only be updated like this when the full patches are applied and not just backports etc
Only devices on Android 14 have full security patch level and then only devices fully supported by the OEM for firmware and driver updates too.
I'm not informing you of this for any other reason other than you mentioning it and not wanting you to have a false sense of security, excuse the pun.
LineageOS do a fine job of maintaining older devices to breathe fresh life into them but it is neither private nor secure and should not be used for sensitive or mission critical data if this is important to you.

2024-02-24 13:56:11 GMT

- reply

Florisboard

2024-02-17 14:33:04 GMT

- reply

Need to find your carriers instructions. It's done carrier side.

2024-02-16 08:36:28 GMT

- reply

Sure I replied yesterday but apparently not?
Is the Pixel 5 using the same SIM/cellular plan? If not, even if the same carrier, dial *#*#4636#*#* and check the greyed out toggles for whether it is provisioned on the SIM in the 5.

2024-02-14 18:46:51 GMT

- reply

Qapla'!

2024-01-23 19:32:03 GMT

Latest OsmAnd+ update resolves memory corruption issue exposed by GrapheneOS' pioneering implementation of MTE.
https://github.com/organicmaps/organicmaps/pull/7229

2024-01-22 00:59:56 GMT

- reply

No problem, is there chance at all that Tesla offer extended test drives to allow you to put all this to the test?

2024-01-21 09:33:28 GMT

- reply

To emphasise however this isn't verifiable by me personally.

2024-01-21 09:32:21 GMT

- reply

I've asked around and the app should work fine and is known to. The only issue some have experienced is after a prolonged period the app might report a loss of network connection even with one present. Excluding it from Battery Optimisation may help but if not it requires toggling of Airplane mode on/off to reestablish connection.

2024-01-20 12:42:55 GMT

- reply

I'll pass the feedback along 😄

2024-01-20 01:26:38 GMT

- reply

AOSP
The Android Open Source Project (AOSP) includes individuals working in a variety of roles. Google is responsible for Android product management and the engineering process for the core framework and platform; however, AOSP considers contributions from any source, not just Google.
Contributors make contributions to the AOSP source code. Contributors can be employees of Google or other companies, as well as individual developers with no company affiliation. There is no distinction between contributors; they all use the same tools (git, Repo, and Gerrit), follow the same code review process, are subject to the same requirements on code style, and so on.
GrapheneOS makes a great many changes and while like all other Android OS derivatives it is based on AOSP it is not AOSP. GrapheneOS has and continues to be one of the contributing projects to AOSP itself.

2024-01-20 01:00:48 GMT

- reply

Welcome to the grid user! 🤝

2024-01-20 00:59:05 GMT

- reply

What are you wanting to know? I don't but can look to find out answers if I don't know them for you.

2024-01-16 09:10:31 GMT

- reply

It's available...
https://image.nostr.build/a63a7f71ebb97a8ba1f015a962ad94fcb2e46fea0bbdfded03bf01ff1db01b0d.jpg#m=image%2Fjpeg&dim=864x1920&alt=Aurora+Store+Play+Store+Front+End+Amethyst+Listing&blurhash=%5BG9%3F8%5Dxbs%3At61utRt8of%7C%7BofofkC7KWBj%3Fj%5B%3A%2BWBWCWVA%3DM%7BRjaerDRjV%40V%40I.V%40WBWBogNGRjoL&x=856fc1b29b5d2e8cd500ec41ea03c3b58d3907936d247cd4fa8ae1dd14f88a63

2024-01-15 21:49:02 GMT

- reply

What are they using on stock Android, I'm guessing they use Firebase Cloud Messaging for push to signal the app to sync?
If they were accommodating they could implement UnifiedPush or implement a good battery respecting websocket push.
They have options.

2024-01-15 12:05:19 GMT

- reply

Yes should work fine with sandboxed Play Services installed, then the stand app. However with various changes it could be that Google have made or make more functionality dependent on more privileged access resulting in lower charging speed.
Advise checking out our community channels (Matrix/Discord) and asking other members what their mileage is like, not owning one myself.

2024-01-14 22:37:43 GMT

- reply

If going GrapheneOS get 6th Gen or > do not get a Qualcomm based device, too close to End of Life.

2024-01-14 22:26:49 GMT

- reply

#nevent1q…9425

2024-01-13 18:42:50 GMT

- reply

Oh look another cycled npub. Nevermind honeypot, you're a timesink. You keep using that word FORCE too so lets get all Inigo Montoya...
https://image.nostr.build/d54275aa5f7f560a50fa91f7cca92d983a162536daac9061433b8f9ceb1c65d3.jpg#m=image%2Fjpeg&dim=537x464&alt=Inigo+Montoya+Meme&blurhash=%3BVD%2BuXf69tWWw%5Ds%3ANGj%5BfkMxayf%2Bayt6WBR*jZjZ_NWVs9s.R*WXWBoLjZbvayn%24f6RjayoLayj%40xvjtxafQflfQaebHRj-%3Bf6NGayRjoLoeWVWXV%40oLt7WVofoLjsWVR*%25Mf6aeazWBj%5BayWVjt&x=3e0af40376ee9f6d391ff0da96133f2667848b6aaeed0a126d0c586287576bb7