Android 16 QPR3 Beta 2 tweaks a Pixel setting that can quietly reduce one of the most annoying mobile problems, Wi-Fi that looks connected but isn’t actually usable. Instead of a single Adaptive Connectivity on or off switch, this Android 16 test build breaks the feature into two controls, and both start enabled.
On the QPR2 stable release, Adaptive Connectivity lives under Settings, Network and internet, and it’s mostly a leap of faith. Turn it on and Google says Android will manage your connections to improve performance and extend battery life. In QPR3 Beta 2, the page gets more descriptive visuals and clearer labels that spell out what the feature is doing, and what it might cost.
It’s a small change on paper, but it gives you a cleaner way to decide when your phone should favor staying online versus squeezing out extra battery.
The mobile fallback is explicit
The first control is auto-switch to mobile network. When Wi-Fi is poor or unavailable, your Pixel can move to cellular to keep apps working, with a direct warning that data charges may apply. If you deal with weak Wi-Fi at home, in cafés, or in buildings where signals drop room to room, this is the switch that should cut down on stalls.
Because it’s separate now, you can keep the fallback behavior on without feeling like you’re also committing to every other part of the feature.
Battery tuning gets its own lane
The second control is optimize network for battery life. It keeps the original idea intact, Android automatically chooses what it thinks is the best connection to extend battery life. For most people, that’s the setting you’ll leave alone, since it’s designed to run quietly in the background.
The practical tradeoff is simpler with two switches. You can prioritize reliability and accept some extra cellular use, or you can limit cellular hopping while still letting Android optimize for battery.
A background update hints at more changes
Google also updated Adaptive Connectivity Services through System services, with version p.2026.01 landing within the past week or so. System services updates can adjust behavior without a full OS update, so the feature may keep evolving while the QPR3 beta continues.
If you’re testing this build, use your normal routine for a few days, then check mobile data usage to see whether the fallback is worth it. If you’re not on the beta, the takeaway is simple, Pixel’s connectivity tools are getting less all-or-nothing, and more transparent.
