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.
2
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
i.e. maybe it passes that configuration to the baseband and it handles this, since it's tied to the mobile network. I think the carrier is definitely meant to be able to override the settings in AOSP which as far as I know are just a fallback configuration for this.
1
1
So, as far as I can tell, it might be necessary to test on a carrier where this actually gets used to see the connections. I'm not sure exactly how this works in practice. It's one of the open questions to be addressed along with the connectivity / captive portal checks.