spl4tt

I'd just like to thank all developers, maintainers and all other involved in this project for such a wonderful experience installing and using GrapheneOS. Polished, thought-out, there is much to like.

My usecase is to become less dependent on Google. I'm using Google Play Store/services on GrapheneOS so I don't know how much it is improved exactly, but it has to be better than pure Google.

A word of warning for people wanting to install the OS and are dependent on Whatsapp; at the moment there is a flaw in the backup system of Whatsapp that won't let you restore a backup (see reddit thread concerning Whatsapp). I'm not dependent on it and it is a good excuse to just quit it and using Signal exclusively.
No fault of GrapheneOS, it's a fault in Whatsapp.

spl4tt What about the lockdown option in the powermenu? Isn't that doing what you want? Or does it not encrypt on enabling it?

No, it does not bring back storage to an encrypted state. It does not even shut down running apps. It just forces you to enter primary credentials again, fingerprint won't work. I tried it just now.

Top thanks for the explanations, as usual, well done to the GOS team for this update.

Stewart The new workarounds for apps banning GrapheneOS are always enabled. No need to enable them. There's a new Play Integrity API notification which tells you when apps use it. Apps can use it without using the result to ban using a non-stock OS so it doesn't imply anything is going to be broken when the notification is shown. There's a new per-app menu for configuring the Play Integrity API linked from that notification with the option to block it in case the service allows using it without giving a Play Integrity API result. Most services will require giving a result, but a small number of apps will likely become usable via blocking it based on the service not enforcing providing a result.

Revolut works again with the latest release that's currently available in the Alpha channel and will reach the Beta channel soon if no major issues are reported:

https://discuss.grapheneos.org/d/19436-grapheneos-version-2025012600-released

The changes made to work around Revolut banning GrapheneOS should also help with various other banking apps using the same awful SDKs. We also added a system intercepting Play Integrity API usage and showing a notification when it's used which links to a new per-app Play Integrity API configuration menu which includes the ability to block it on a per-app basis along with encouraging users to give feedback to developers via a shortcut to the Play Store page for leaving a review.

cdflasdkesalkjfkdfkjsdajfd Keep dreaming ;)

If the definition of "dreaming" includes something that has not yet happened but that might come to pass in the future, then sure, I'll keep "dreaming". You are free to keep repeatedly implying that it's never going to happen, but so far, I have not been convinced by any arguments in this thread.

cdflasdkesalkjfkdfkjsdajfd Nothing in life is forever ;)

Perhaps, but in this case it's clear that the workaround you are suggesting will only work within a very limited timeframe. Personally I don't see the point of trying to work around a block just to have the workaround stop functioning next month.

Personally, I'm hopeful that a legislative ban of this monopolistic system will be implemented in the end. At least in the EU, its history shows that they do not tend to shy away from regulating monopolistic business behaviour.

cdflasdkesalkjfkdfkjsdajfd GOS devels has the ability to remove these limitations, at least temporally, but it seems has decided to do not do anything, either optionally.

I believe the GrapheneOS official account has publicly stated multiple times that they are in discussion with at least one regulatory agency. Personally I would not describe that as "decided to do not do anything".

spl4tt It is not the service the problem but the strong and successful efforts to make it the only payment option (cashless sounds modern). I don't have a problem if others want to use this service but I don't want to be forced to use it.

IamZorro As written above logging in does not solve the problem you just fail a little later.

The provider did not yet reply to my bug report.

Tomelena Is it worth the hassle

So what hassle is that? a foolproof step by step guide to install GrapheneOS.
GrapheneOS, which is free of charge, works without issue out of the box, provides security beyond several Govt agencies capabilities, provides privacy on a level that shames Big tech...and best of all keeps G**gle out of my life.
If that is hassle... bring it on.

I have replaced the swollen battery on my Pixel 7 Pro second time in less than a year yesterday.
It bulged and caused the screen to separate from the body.

Since this happened twice already and I'm not looking to replace the battery twice a year I contacted Google support about this and they recommended to limit SoC between 20% and 80%, but on Graphene OS there is no such option in contrast to stock OS.

According to Google documentation limiting charging to 80% can be done using "Battery > Charging optimization" (missing on Graphene OS). My pattern of usage actually seems to match somewhat what they describe in the documentation under "Protecting your battery" (also missing on Graphene OS) on the same page (I keep my phone on wireless charger 90% of the time and it SoC rarely drops below 90% and only a few times a year below 80% unless I'm traveling).

It'd be great if Graphene OS could adopt the same/equivalent features of the stock OS.

I saw https://discuss.grapheneos.org/d/9017-how-can-i-limit-battery-charge-to-80 and there is https://github.com/GrapheneOS/os-issue-tracker/issues/3213 that has priority "none" at the moment.

Just wanted to share the experience of this feature being not only theoretically useful, but also practically (assuming Google's documentation is to be believed). I believe having less flexible variant of this to start would be better than none at all, though I understand potential technical debt.

@GrapheneOS

With the latest update, the stock OS now apparently supports a new Battery Bypass feature, which apparently allows to power the device directly and continuously from an external USB power supply only, without drawing power from the battery and without charging the battery (once the battery is charged to 80%):

1. https://www.androidauthority.com/pixel-bypass-charging-3507373/
2. https://www.androidauthority.com/google-pixel-bypass-charging-details-3508077/

Is this new Battery Bypass feature also available on GOS?

MrStreisand
Seems like you're referring to the system file picker. This is perfectly normal and Threema can't see anything beyond what you select with the file picker.

MrStreisand access to full dick

Has to be said, funny typo.

User2288 GrapheneOS doesn't support insecure devices, while /e/OS is highly insecure everywhere so it doesn't matter. It massively rolls back security compared to AOSP or the stock Pixel OS.

is security (even privacy)

It's a misconception that GrapheneOS is more focused on security than privacy, and it misses the fact that we provide a bunch of substantial privacy features.

@privacyisahumanright
GrapheneOS is in a different class on it's own. GrapheneOS is not really comparable to eOS since eOS is a a fork of LineageOS, it substaintially reduces security.
eOS also all mislead users into thinking they're getting all the important security patches despite not providing half the mandatory patches. An end-of-life device does not get many of those patches even with an alternate OS. It's still unpatched/insecure.

Hey all, new GrapheneOS user here!

I just installed GrapheneOS the other day on a Pixel 7 Pro (having a blast so far!) and I wanted to give some Google apps a go.

After reading the usage guide, I learned that it is not needed to install any of the 3 Google service apps (Google Play Services, Google Services Framework or Google Play Store) to use Google Camera. So I just downloaded Google Camera from the Aurora Store and it indeed works like a charm.

Then I was curious if I'd get the same results with Google Photos and even Google Maps.
And to my surprise I was able to install and use these as well without the need of installing any of the 3 Google service apps!

So far I have not found any features missing in these apps, which raises my question: why would I install Google Play Services, Google Services Framework or the Google Play Store when it comes to using Google Photos and Maps? I assume everything is still running sandboxed without any of the 3 Google service apps, so Google will have a hard time tracking me when using Photos/Maps?

Cheers!

Well, regardless, with this change, GrapheneOS won't differ in any way from how Stock OS handles this, and people can enable/disable the toggle as they see fit.

If people continue having issues, they'll need to wait for Google to address that. GrapheneOS has done its part.