This is an interesting review of #GrapheneOS

https://lwn.net/SubscriberLink/1030004/898017c7953c0946/

Essentially, the reviewer says that it's great. But modern life pretty much requires proprietary software, which weakens the system.

For me, I'm willing to put up with the tradeoffs. So, for example, I use a bunch of Google Apps. But I'm doing so knowing that overall I'm in a better position than if I was using stock #Android.

Last updated: 9 June 2025, I will just leave this here!

https://eylenburg.github.io/android_comparison.htm

If you think anything is factually incorrect, please let him know.

#Privacy#Security#Android#GrapheneOS#CalyxOS#EOS#LineageOS#Android

I’m running CalyxOS on my old Fairphone4, not because it’s a bad choice, but precisely to observe how incredibly behind this OS is on security updates.

My primary device today is a Pixel 9a running GrapheneOS, not this outdated, insecure, and privacy-compromised Fairphone 4.

This Fairphone never became my daily driver once I realized just how far behind it is on security and privacy. I used it from October 2022 until I switched to my Pixel 6a running GrapheneOS in early May 2023, and only recently upgraded to the 9a (see links below):

https://social.linux.pizza/@midtsveen/114785407166445792

https://social.linux.pizza/@midtsveen/114801787891495911

https://social.linux.pizza/@midtsveen/114840637379788570

Now, heading into August 2025, and the Fairphone is on Android 15 with vendor and firmware updates on CalyxOS stuck at versions from March 5 for vendor, and June 1 Platform and June 5 for kenel updates, months behind in a critical security landscape. 😐

#Fairphone4#CalyxOS#GrapheneOS#Android

ok, well, flashed the Keltec v3 to #Meshcore, no problemo. But on my #grapheneos phone I can't get the meshcore app without using Aurora Store to grab it from Google Play. So did that, and then paired the device with my phone, but the app doesn't detect the device so I'm stuck with just no way to talk to it.

At some point companies bullshit should be made public. This is what #grapheneos is doing.

I'm french, I used Mandrake. But when Gael makes advertisement for his /e/ project telling it's not Android and other bullshit. I'm not happy. I loose trust.

We had Qwant bullshit and /e/ is on the same road.
They have to reach a critical mass to exist. I feel Tesla is their marketing model.

Hvis du bor i Norge og bruker BankID på GrapheneOS, kan du gi tilbakemelding til utviklerne direkte fra appen ved å trykke på profil bilde øverst til høyre, deretter velge Hjelp og tilbakemelding > Gi oss tilbakemelding!. Dette tar deg til et nettsted hvor du kan sende inn tilbakemeldingen din.

Du kan gjøre det samme for Vipps, gi tilbakemelding til utviklerne direkte fra appen ved å klikke på Meg til høyre > deretter velge Hjelp og støtte > Send oss tilbakemelding!. Dette tar deg også til et nettsted hvor du kan sende inn tilbakemeldingen din.

Hver tredje måned sender jeg inn tilbakemelding der, med en lenke til GrapheneOS sin veiledning om attestation compatibility, og forklarer hvordan GrapheneOS fungerer og hvorfor støtte er viktig.

https://grapheneos.org/articles/attestation-compatibility-guide

Hvis du også er avhengig av BankID og Vipps, samt bruker GrapheneOS, anbefaler jeg sterkt at du gir tilbakemelding der og gjør det samme.

#NorskTut#Norge#Bergen#Oslo#Trondheim#Stavanger#Tromsø #Kristiansand#Drammen#Fredrikstad#Sandnes#Ålesund#Bodø#Porsgrunn#Hamar#Skien #Vipps#DNB#SPV#SparebankenNorge#SparebankenVest#BankID#BankIDpåMobil #Nordea #Sbanken#DanskeBank#SpareBank1#BNBank#StorebrandBank#KLP#Handelsbanken#HelgelandSparebank#FanaSparebank#Eika#OBOSbanken#Swedbank#GrapheneOS#Android

I have a travel question for those using Pixel phones... Have you been singled out by US customs/border security?

I read the recent story here in Spain about Pixel users being targeted due to the popularity of GrapheneOS and I haven't been to the US yet with the current regime in place, so not sure what to expect. Just wondering if even the sight of the phone is a red flag for them.

Boost please!

#grapheneOS #graphene#Pixel#Surveillance #security #privacy

Support for #keepassDX in progress 🌱 https://github.com/Kunzisoft/KeePassDX/issues/1421

GrapheneOS just dropped stable Android 16 support for Pixel devices! 🚀🔒 Despite new hurdles from Google, the team’s update includes the TapTrap vulnerability fix and under-the-hood improvements. No flashy features, all about security! #GrapheneOS#Android16#Pixel #privacy #security

🔗 https://www.heise.de/en/news/GrapheneOS-releases-Android-16-in-the-stable-channel-10484215.html

Shortlink: https://heise.de/-10484215

Oh, the #grapheneos pixel fold I have has updated to Android 16... Was sure indeed about it being early testing not even that long ago... Impressive.

I've noticed many tiny ui changes? Good and bad i guess.

Police in Spain have reportedly started profiling people carrying Google Pixel devices operating on #GrapheneOS

#privacy #security#OS#androidAlternative#FOSS

https://www.androidauthority.com/why-i-use-grapheneos-on-pixel-3575477/

If you think GrapheneOS isn’t private and secure, check out this comparison chart covering GrapheneOS, CalyxOS, IodéOS, /e/os, LineageOS, and Stock Android.

https://eylenburg.github.io/android_comparison.htm

It shows how much more GrapheneOS focuses on security and privacy compared to the others!

Edit: GrapheneOS only supports Pixel devices because they meet the project’s security requirements, offering hardware features like memory tagging (MTE), StrongBox keystore, hardware key attestation, pKVM, hardened malloc, and more: https://grapheneos.org/faq#future-devices

#GrapheneOS#CalyxOS#IodéOS#EOS#LineageOS#Android