[TheNightman]

Have these folks done any sort of actual audit on the Android code base to ensure they’ve removed _all_ of the “phoning home”? Not so much doubting their claims, more so just curious to see what they found. Is it possible google has baked in some tracking features deep in the OS, outside of gapps? Things you wouldn’t see with a mitm proxy? I’d be interested to know

[_rdvw]

They literally include Google Widevine DRM and Google EUICC:

https://gitlab.e.foundation/e/devices/android_device_fairpho...

https://gitlab.e.foundation/e/devices/android_device_fairpho...

microG itself connects directly to Google: https://github.com/microg/GmsCore/wiki/Google-Network-Connec...

and /e/OS default enables those connections: https://gitlab.e.foundation/e/os/android_prebuilts_prebuilta...

including the default download and running of the proprietary Google SafetyNet binaries: https://gitlab.e.foundation/e/os/android_prebuilts_prebuilta...

Kuketz covered the connections made in full at the very end here: https://www.kuketz-blog.de/e-datenschutzfreundlich-bedeutet-...

[Qwertious]

microG itself connects directly to Google: https://github.com/microg/GmsCore/wiki/Google-Network-Connec...

No shit, of course they do.

>In general, we obviously try to minimize the connections to Google, but some services strictly rely on them and would just not work without.

What exactly do you think they should do instead?

[_rdvw]

Be opt-in like the other systems, not opt-out.