Does GrapheneOS disable AGPS by default or send information to Google?
Conversation
Replying to
GrapheneOS doesn't include any supplementary location services and only has GPS-based location detection. Adding support for local supplementary location services is planned:
github.com/GrapheneOS/os_
It does include standard support for downloading GPS almanacs to improve GPS.
1
1
GPS almanacs are downloaded via HTTPS GET requests from xtrapath1.izatcloud.net/xtra3grc.bin, xtrapath2.izatcloud.net/xtra3grc.bin or xtrapath3.izatcloud.net/xtra3grc.bin. These are databases of satellite locations speeding up initial GPS lock. There are only a few other default connections, which are all important.
2
1
Replying to
It's configured that way in AOSP, but I don't think that's actually being used in practice. Let me know if I'm wrong about that since I want to make official documentation on the default connections along with planning out what GrapheneOS should be changing about it.
For example, it changes fallback DNS servers from Google DNS to Cloudflare since it has a better privacy policy. However, these aren't really used in practice, since the network almost always provides DNS servers. The user can set a preferred DNS-over-TLS server to override this.
1
1
I've considered hosting a server for the connectivity / captive portal checks but I'm not sure that switching them offers any actual privacy benefits and would identify GrapheneOS devices as such to networks even with the Updater app disabled. I don't feel that's a positive.
1
Replying to
Yeah, I noticed that and wondered the same thing. I'll try to verify if it does or not.
1
Replying to
I think the way it would work is that it sends the cell id to that server to fetch GPS almanac data, but I've never seen it make the connection in practice. It might be helpful to add logging to the AOSP code to figure out what it's actually doing. Could just be very low level.
1
1
Show replies