Grapheneos with Google play services (sandboxed) only send 12 packets per hour, instead of around 350.
That’s great, but the sandboxed Google play services are by default set to normal in battery usage. Meaning it’s subject to dooze and other ways to artificially limit its background activity.
You neee to set the battery usage to unrestricted to reliably revive notification.
I wonder what the packet count would have been with unrestricted Google play services.
I'm less interested in the quantity, and more in the content of those packets. Do they contain my GPS movement history? A list of installed and opened apps? My contacts list, messaging text log, and list of visited websites?
The data I really care about protecting would fit into a few kilobytes, so knowing the phone sends, for example, a minuscule 2 MB/day, brings me no comfort.
This isn’t new. The disgraced Lunduke did this same test nearly a decade ago and observed the same results. Android is malware disguised as a consumer operating system.
Doesn't really work for me. It's just a site likely checking what the browser tells it any the system. Meanwhile I have a VPN blocking most connections and every Google app is either uninstalled or disabled.
Was there any TLS interception in place? Mind you, that can be detected and ignored...
Cause the (obviously AI generated) page is fairly ambiguous in this regard. In one section it claims certain pieces of info were sent outright. In others, it refers to them as "Privacy Threat Vector" items. Were they possibly sent or were they actually sent? Why is this left unclear? Why is transmission alone counted as evidence of later misuse? What data is technically necessary to send as part of a protocol?
I'm really quite tired of the run of the mill "privacy minded" folks thinking they're the hot shit because they can launch WireShark, and gawk at packets flying about. Like no, various corporate SNIs appearing in a chatty network log is not evidence for illegal or unethical corporate espionage/surveillance, especially not a clear one. Nor is the network log being chatty any evidence one way or another. Do you really think that surveillence is a more likely explanation for them than just regular enterprise sprawl?
If you're bringing receipts, bring them whole, disclaimers and limitations included. Any analysis that stops before decrypting the traffic is deeply unserious, and only serves to discredit actual research findings & real violations of privacy.
Soulless LLM-ese. The content is needlessly stretched to occupy space, paragraphs, and tables. Any actual insights could have been condensed and conveyed with 80% less text.
The "Complete 72-Hour Raw CSV Dataset" CSV contains 13 records. That incomplete data is formatted incorrectly: rows 6 and 11 are missing payload_bytes, so their description shows in the wrong column.
The "How DeGoogled Are You" section is mostly a separate issue from the test described in the article, and it has no place being at the top. The article is about how Android phones are passively phoning home. For example, switching from Chrome to Brave won't reduce idle phone-home, as Android users can't uninstall Chrome, and the idle activity was not related to Chrome. The same goes for most of the other recommendations in that widget.
of which: Nearby Wi-Fi Routers (Location Triangulation)
is 84.2 pings/hr
So a stock (idle!) pixel 8 is checking where you are more than once per second (without maps running, without asking for directions) and asking what you're doing almost five times a second.
Is there any slope at all? Like, does it ask more frequently in the beginning and less after an hour+ of idle, or is it fairly static?
Would be very curious to see what adding social media and voice assistants does to this, especially with a controls against a silent room and a room with a radio/movies/TV/pure music playing.
Does the voice assistant send more data in the conversational context? How much more? If it is indeed more, how much voice is theoretically being transmitted given the average words per bitrate?
It could also be interesting to see if the stock device transmits more in a conversational environment. Like, if the device is idle, why would it be transmitting more while sitting in an office instead of a quiet lab?
So i wanted to know what an Android phone actually transmits when you aren't touching it most articles say "Google collects a lot of data" but nobody knows to what extent and publishes some proof lets say some packet captures
Stock Android 16 averaged 348.4 requests/hour to Alphabet ASN 15169 endpoints turning off location and usage diagnostics in settings still left 194.2 requests/hour active mostly checkin.gstatic.com Wi-Fi BSSID surveys. Running GrapheneOS with Sandboxed Play Services dropped traffic to 12.1 requests/hour, while pure GrapheneOS registered zero.
That’s great, but the sandboxed Google play services are by default set to normal in battery usage. Meaning it’s subject to dooze and other ways to artificially limit its background activity.
You neee to set the battery usage to unrestricted to reliably revive notification.
I wonder what the packet count would have been with unrestricted Google play services.
The data I really care about protecting would fit into a few kilobytes, so knowing the phone sends, for example, a minuscule 2 MB/day, brings me no comfort.
Care to run the same experiment for an iPhone?
Cause the (obviously AI generated) page is fairly ambiguous in this regard. In one section it claims certain pieces of info were sent outright. In others, it refers to them as "Privacy Threat Vector" items. Were they possibly sent or were they actually sent? Why is this left unclear? Why is transmission alone counted as evidence of later misuse? What data is technically necessary to send as part of a protocol?
I'm really quite tired of the run of the mill "privacy minded" folks thinking they're the hot shit because they can launch WireShark, and gawk at packets flying about. Like no, various corporate SNIs appearing in a chatty network log is not evidence for illegal or unethical corporate espionage/surveillance, especially not a clear one. Nor is the network log being chatty any evidence one way or another. Do you really think that surveillence is a more likely explanation for them than just regular enterprise sprawl?
If you're bringing receipts, bring them whole, disclaimers and limitations included. Any analysis that stops before decrypting the traffic is deeply unserious, and only serves to discredit actual research findings & real violations of privacy.
The "Complete 72-Hour Raw CSV Dataset" CSV contains 13 records. That incomplete data is formatted incorrectly: rows 6 and 11 are missing payload_bytes, so their description shows in the wrong column.
The "How DeGoogled Are You" section is mostly a separate issue from the test described in the article, and it has no place being at the top. The article is about how Android phones are passively phoning home. For example, switching from Chrome to Brave won't reduce idle phone-home, as Android users can't uninstall Chrome, and the idle activity was not related to Chrome. The same goes for most of the other recommendations in that widget.
of which: Nearby Wi-Fi Routers (Location Triangulation) is 84.2 pings/hr
So a stock (idle!) pixel 8 is checking where you are more than once per second (without maps running, without asking for directions) and asking what you're doing almost five times a second.
Is there any slope at all? Like, does it ask more frequently in the beginning and less after an hour+ of idle, or is it fairly static?
Would be very curious to see what adding social media and voice assistants does to this, especially with a controls against a silent room and a room with a radio/movies/TV/pure music playing.
Does the voice assistant send more data in the conversational context? How much more? If it is indeed more, how much voice is theoretically being transmitted given the average words per bitrate?
It could also be interesting to see if the stock device transmits more in a conversational environment. Like, if the device is idle, why would it be transmitting more while sitting in an office instead of a quiet lab?
Stock Android 16 averaged 348.4 requests/hour to Alphabet ASN 15169 endpoints turning off location and usage diagnostics in settings still left 194.2 requests/hour active mostly checkin.gstatic.com Wi-Fi BSSID surveys. Running GrapheneOS with Sandboxed Play Services dropped traffic to 12.1 requests/hour, while pure GrapheneOS registered zero.
Data is uploaded here : https://doi.org/10.5281/zenodo.22848749
Also, anyone know if there are downsides to blocking checkin.static.com?