gstatic.com (a google domain) Connections On Stock Graphene OS On Startup

llama420

GrapheneOS Here's a log of the android related Linux packages on my PC:
dpkg -l | grep -i 'android|sdk|ndk|adb|fastboot'
ii adb 1:34.0.4-1build3 amd64 Android Debug Bridge
ii android-libbase:amd64 1:34.0.4-1build3 amd64 Android base library
ii android-libboringssl:amd64 14.0.0+r11-4build1 amd64 Google's internal fork of OpenSSL for the Android SDK
ii android-libcutils:amd64 1:34.0.4-1build3 amd64 Android utils library for C
ii android-liblog:amd64 1:34.0.4-1build3 amd64 Android NDK logger interfaces
ii android-libziparchive:amd64 1:34.0.4-1build3 amd64 Library for ZIP archives
ii android-sdk-platform-tools-common 28.0.2+9 all Tools for interacting with an Android platform - Common files
ii libmfx1:amd64 22.5.4-1 amd64 Intel Media SDK -- shared library
ii mobile-broadband-provider-info 20230416-1 all database of mobile broadband service providers
ii python3-sentry-sdk 1.39.2-0.1 all New Python SDK for Sentry.io (Python 3)

llama420

GrapheneOS Not tied to ADB. gstatic connection triggered immediately upon connecting to the USB with ADB and related android tools removed. No idea what's causing it.

dpkg -l | grep -i 'android|sdk|ndk|adb|fastboot'
ii libmfx1:amd64 22.5.4-1 amd64 Intel Media SDK -- shared library
ii mobile-broadband-provider-info 20230416-1 all database of mobile broadband service providers
ii python3-sentry-sdk 1.39.2-0.1 all New Python SDK for Sentry.io (Python 3)

llama420

GrapheneOS Got these OpenSnitch logs one second before the gstatic connection was triggered on the phone:

2025-07-28 21:51:29.294590,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294490,unix:/local,deny,239.255.255.250 -> 3702,udp,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294463,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294432,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294409,unix:/local,deny,239.255.255.250 -> 3702,udp,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294385,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294363,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294317,unix:/local,deny,239.255.255.250 -> 3702,udp,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294287,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294233,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane
2025-07-28 21:51:29.294192,unix:/local,deny,ff02::c -> 3702,udp6,/usr/libexec/colord-sane,deny-always-simple-usr-libexec-colord-sane

Two previous comments still "Awaiting approval", if anyone's confused by this.

llama420

GrapheneOS Tied to a debugging connection only, plug in test without debugging returned no gstatic.

GrapheneOS

@llama420 Note adb remains running as a daemon on the computer where you used it. Uninstalling it won't stop the service. adb kill-server can be used to stop the service. It will automatically connect to plugged in devices, not just when you use the CLI tool.

llama420

GrapheneOS Noted, thank you. Reinstalled ADB, killed the server, removed again, rebooted the phone with USB debugging enabled, no gstatic when plugged in.

llama420

GrapheneOS Fresh ADB install showed no gstatic after using adb reboot to restart.

de0u

llama420 As the saying goes, "All's well that ends well".

« Previous Page