The Pixel 10 has barely landed on doorsteps, and some early adopters are already hitting a roadblock with Android Auto. 9to5Google reports that complaints about Google’s latest flagship struggling to maintain a reliable connection with in-car infotainment systems are piling up on Google’s support forums and Reddit threads.

What the bug looks like

If you see it, you’ll know, and there’s no fix yet

Car dashboard display showing the Android Auto interface with various app icons and a navigation map, overlaid by a large Android Auto logo.

Source: Lucas Gouveia/Android Police | kungfu01/Shutterstock

The bug shows up the same way for unlucky users. Plug in a Pixel 10 and the car recognizes the device, but the dashboard display never gets past a blank screen stamped with the Android Auto logo. Audio still routes correctly — music, phone calls, and Assistant commands come through just fine — but the interface itself either doesn’t appear or takes several minutes to load. Even then, multiple reports say the UI is so sluggish it may as well not be functional, updating at a glacial pace of one frame every few minutes.

Affected users have tried the usual bag of tricks like clearing cache, reinstalling the Android Auto app, factory-resetting head units, and swapping cables. So far, none of it seems to help. The problem affects both wired and wireless connections across a wide range of vehicles, from late-model Chevrolets and Nissans to newer Audis. A handful of users report normal performance, particularly with third-party wireless dongles, but the majority of stories so far point to major stability issues.

Flagship launches, surprisingly, have a history of Android Auto hiccups. Last year’s Pixel 9 series saw a similar rash of complaints, and Samsung’s Galaxy S25 had its own round of compatibility bugs earlier this year. In those cases, Google rolled out fixes within the first month or two via software updates.

For now, if you just unboxed a shiny Pixel 10 and rely on Android Auto for your commute, you may be stuck waiting for a patch. Google hasn’t acknowledged the issue yet, but given the volume of reports, it seems inevitable a fix is in the pipeline.