Google ignores seven-month vpn kill switch in android 16

Seven months of silence. That is how long Google has left millions of android 16 users naked on public Wi-Fi after a kernel-level bug quietly murders their VPN tunnel the moment the app updates. No pop-up, no log entry, no red bar—just the sudden, ghostly return of your real IP address while the little key icon still glows in the status bar.

The vanishing act no one at mountain view will claim

Proton, Mullvad, WireGuard and TunnelBear all filed trackers before Christmas. Each received the same templated shrug: “We don’t see anything unusual.” Yet the stack trace is reproducible on a Pixel 7, a 6a, a Pixel 10 Pro and Samsung’s fresh Galaxy S25 Ultra. Update any VPN client while it is active and the netd daemon corrupts its routing table. From the outside you look connected; inside, packets leak like a sieve.

I watched it happen in the TechBloom lab. We flashed a Pixel 8 to android 16 QPR1, fired up Proton 5.7.63, then side-loaded 5.7.64. The handshake completed, the key icon appeared, and ten seconds later our traffic egressed from a Bell Canada IP in Toronto—1,200 km from the “Zurich” server we had selected. No kill-switch triggered, no reconnect loop. Just pure, unmasked data.

Google’s own Pixel VPN is not immune. android 16 beta 3.1 bricks the system-level client on first toggle. The irony? Google One subscribers pay for that tunnel.

A workaround that feels like 2008

Uninstall, reboot, reinstall. That is the ceremonial dance engineers are preaching in Reddit threads and support tickets. Some users swear a simple restart suffices; others need to clear com.android.networkstack cache from ADB. Neither fix survives the next app update, so set your Play Store to manual if your life depends on staying masked.

The broader picture is uglier. android 16’s quarterly platform release also freezes the Pixel lock screen, bricks NFC on some Moto units and halves refresh rate on certain Samsung panels. But the VPN rupture is the only flaw that exposes user traffic to every Starbucks packet sniffer, and Google’s comms team keeps stonewalling.

I asked a senior Android PM at MWC Barcelona why the ticket remains unassigned. He laughed: “VPNs are a rounding error in telemetry.” The numbers say otherwise—Proton alone counted 1.3 million failed connections last month. Multiply that across the ecosystem and you are looking at an entire privacy layer evaporating overnight.

Until a patch drops, treat Android 16 like a café you do not trust. Disable auto-updates for every VPN app, download server configs manually and keep a second device running Android 15 for anything that matters. Google will eventually ship the fix—probably bundled inside a bloated Feature Drop that also redesigns emoji. By then the forensic logs will already be sitting in somebody’s data lake, stamped with your real coordinates.