tiyn/wiki
1
0
Fork 0
mirror of https://github.com/tiyn/wiki.git synced 2026-09-13 10:31:36 +02:00
Code Issues Projects Releases Wiki Activity

GrapheneOS: Restructured the Google Play Services section

Browse Source
This commit is contained in:
Marten
2026-09-11 23:38:30 +02:00
parent eb263466fd
commit 9744ffe326
1 changed files with 26 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

31
wiki/android/grapheneos.md
View File

@@ -24,7 +24,24 @@ A general overview of this was given in a
Another recommendation on settings for GrapheneOS can be found in Another recommendation on settings for GrapheneOS can be found in
[a post by ventral digital](https://ventral.digital/posts/2024/12/9/practical-grapheneos-for-the-paranoid/). [a post by ventral digital](https://ventral.digital/posts/2024/12/9/practical-grapheneos-for-the-paranoid/).
#### Location Services #### Google Play Services
For normal use of Sandboxed Google Play, Google Play Services does not need the `Phone` or `SMS`
permissions.
They can therefore generally be set to `Don't allow`.
These permissions should only be granted when a specific feature requires them.
For example, RCS with Google Messages may require Google Play Services to have the `Phone`
permission, while ordinary push notifications and most Google Play APIs do not require either
`Phone` or `SMS`.
The `Notification` permission is only needed for notifications directly from the Google Play
Services application.
Location-related permissions and settings for Google Play Services are covered in the
[Location Services section](#location-services).
##### Location Services
It is recommended to enable `Network location` under `Location` and `Location services` in the It is recommended to enable `Network location` under `Location` and `Location services` in the
settings and select `GrapheneOS Apple proxy`. settings and select `GrapheneOS Apple proxy`.
@@ -38,13 +55,17 @@ implementation instead.
With location request rerouting enabled, Google Play Services usually does not need the `Location` With location request rerouting enabled, Google Play Services usually does not need the `Location`
permission for normal application location requests. permission for normal application location requests.
Its location permission can therefore generally be set to `Don't allow`. Its location permission can therefore generally be set to `Don't allow`.
Some Google-specific features, such as certain location-sharing functions, may still require
Google Play Services to have location access. Some Google-specific features, such as certain location-sharing functions, may still require Google
Play Services to have location access.
##### Wi-Fi and Bluetooth Scanning
If network location is unreliable while Wi-Fi itself is disabled, `Wi-Fi scanning` can optionally If network location is unreliable while Wi-Fi itself is disabled, `Wi-Fi scanning` can optionally
be enabled. be enabled.
If Wi-Fi is already enabled, `Wi-Fi scanning` is generally not required for network-based location. If Wi-Fi is already enabled, `Wi-Fi scanning` is generally not required for network-based location
From a privacy standpoint it can otherwise remain disabled. and can otherwise remain disabled from a privacy standpoint.
`Bluetooth scanning` is generally not required for GrapheneOS Network Location and can remain `Bluetooth scanning` is generally not required for GrapheneOS Network Location and can remain
disabled unless another feature specifically depends on it. disabled unless another feature specifically depends on it.