Google's latest software update for Pixel phones has introduced a significant problem for drivers: Pixel owners who installed the March 2026 update are unable to run Android Auto in their cars with a wired connection, apparently due to Advanced Protection Mode resetting USB Protection settings and blocking Android Auto from running.
The issue emerged shortly after the update began rolling out earlier this month. Previously, users could simply plug their phone into their car's USB port and Android Auto would launch automatically. Once users connect their smartphones to their cars to run Android Auto with a cable, nothing happens, and the only way to continue using Android Auto is to unlock the phone to start Android Auto on every connection.
The culprit appears to be a new security feature built into the update. Advanced Protection Mode was integrated into Android 16 to block unauthorised USB connections. However, users are frustrated because they have already designated their phones as trusted devices and enabled Android Auto to launch when locked. Despite these settings, the app no longer functions unless the screen is unlocked.
The scope of the problem remains unclear. The issue only affects Google Pixel phones, albeit not all users seem to be affected. Reports on Google's support forums mention the Pixel 9a and Pixel 8 Pro, though Samsung owners or people running Android Auto with another Android device brand don't seem to encounter this glitch.
That's not the only Android Auto problem emerging from the March update. Multiple users on Reddit are reporting broken Android Auto behaviour, with issues like control knob glitches where the highlighted button quickly stops moving or shows multiple selected buttons. These problems appear to be exclusive to non-touch Android Auto head units, and Mazda owners are most often affected as their cars are fitted with control knobs to interact with Android Auto.
For users experiencing the issue, options are limited. Clearing the Android Auto cache and data may help, though success is inconsistent. Some have reported partial improvement by manually updating to Android Auto 16.3, though a comprehensive fix doesn't appear to be available yet.
The problems highlight the complexity of keeping Android Auto functional across hundreds of vehicle models and infotainment systems. When Google pushes security or software changes, they can inadvertently break the careful balance of compatibility required for in-car functionality. Drivers frustrated by these issues now face the choice of reverting the update (if possible), avoiding wired connections, or simply unlocking their phones every time they get in the car—which rather defeats the purpose of a voice-activated in-car interface.
Google has not yet publicly announced a fix for either issue, though the Android Auto support community continues to log new reports from affected users.