| is it de-googled? there is nothing about it in the features list, and the FAQ mentions the option of switching between using gooogle and graphene servers for things like the connectivity check, suggesting that people want to keep using google in order to "blend in". it is neither clear that these switches cover ALL ways that android has to send data to google, nor that there is any desire to remove all of them. the old FAQ apparently had this text (found that in a forum discussion): GrapheneOS leaves these set to the standard four URLs to blend into the crowd of billions of other Android devices with and without Google Mobile Services performing the same empty GET requests. For privacy reasons, it isn't desirable to stand out from the crowd and changing these URLs or even disabling the feature will likely reduce your privacy by giving your device a more unique fingerprint. GrapheneOS aims to appear like any other common mobile device on the network. that text has been replaced with: You can change the connectivity check URLs via the Settings Network & internet Advanced Internet connectivity check setting. At the moment, it can be toggled between the GrapheneOS server and the standard Google servers used by billions of other Android devices. This can be used to blend in with other Android devices, both with and without Play services. Changing this to the Standard (Google) mode will use the same URLs used by AOSP and the stock OS along with the vast majority of other devices there is more here:
https://forum.xda-developers.com/t/general-about-grapheneos.... a forum member claims that: Connections of android location services to get GPS constellations were shown before to send sim card imsi and connected cellular tower id to provider (qualcom/google) Graphene still allows those connections Android services make other weird connections. Example: AOSP dialler app is querying phone numbers against online database leaking all contacts to google. How was this taken care of in graphene? Are all AOSP services/apps security-verified to not leak any data? this suggests that while graphene developers do consider concerns about sending data to google, their goals are orthogonal to those of /e/OS, as Duval claims. |