this post was submitted on 22 Oct 2024
33 points (100.0% liked)
GrapheneOS [Unofficial]
26 readers
1 users here now
Welcome to the GrapheneOS (Unofficial) community
This feed is currently only used for announcements and news.
Official support available on our forum and matrix chat rooms
GrapheneOS is a privacy and security focused mobile OS with Android app compatibility.
Links
More Site links
Social Media
This is a community based around the GrapheneOS projects including the hardened Android Open Source Project fork, Auditor, AttestationServer, the hardened malloc implementation and other projects.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
GOS play services are sandboxed by default, it's how they implement it. The sandbox just keeps it from having full system root integration so its not in everything by default like normal android. It still is full play services though.
What I'm saying is that if you don't want that on your phone but you do want to use apps that rely on it then you can set up a secondary profile. On the second profile install play services and any apps that need it. That way its segregated from your main activity. Other profiles are essentially viewed as their own phone installation so they dont talk to each other.
Oh ok. But just to be clear (IIUC) if the app uses or requires Play Integrity api, it won't work in GOS even if I use a 2nd profile for play services?
Correct, if the profiles are separate. They only share key hardware aspects (like WiFi and Bluetooth settings). The profiles can not talk to each other.
So if the first profile does not have google services it can't run anything that relies on it even if a second profile has google services installed. For all intents, they are "separate phones".