Yes, but those minor traces are easy enough to remove, especially if you don’t care about being “ceritified” by Google (i.e. are not planning to run the Google services).
Right but the topic was about google’s data harvesting and what I meant was that you can’t just grab any AOSP distribution if you want to minimize that, you need to pick one that replaces the parts that send data to google. LineageOS for example still phones google for quite a number of services.
As far as “easy to remove” goes, I think that’s kind of debatable if you want to do it in a way that’s sustainable long term considering the effort that goes into e.g. GrapheneOS or DivestOS.
Edit: here is a list of the kind of stuff you need to watch out for if you want to minimize the data sent to google
They want to harvest the data, without Google’s control, and give none to Google.
That can be easily done with AOSP, to my knowledge there’s no Google stuff in there. Which is exactly what they’re using right now
There still is some google stuff in there, like for example phoning google servers to check internet connectivity among other stuff.
Yes, but those minor traces are easy enough to remove, especially if you don’t care about being “ceritified” by Google (i.e. are not planning to run the Google services).
Right but the topic was about google’s data harvesting and what I meant was that you can’t just grab any AOSP distribution if you want to minimize that, you need to pick one that replaces the parts that send data to google. LineageOS for example still phones google for quite a number of services.
As far as “easy to remove” goes, I think that’s kind of debatable if you want to do it in a way that’s sustainable long term considering the effort that goes into e.g. GrapheneOS or DivestOS.
Edit: here is a list of the kind of stuff you need to watch out for if you want to minimize the data sent to google
https://divestos.org/pages/network_connections