Android Auto update breaks media and navigation ‘Quick Controls’ for some users

Android Auto

Android Auto 15.2 is now rolling out more widely, but several users have discovered that one of its older features — “Quick Controls” — is no longer functioning as expected. The feature, accessible through the Android Auto settings menu, allowed users to control music playback or view navigation directions while using other apps. Although its importance declined after Google introduced the modern dashboard interface, “Quick Controls” remained a useful option for those who preferred the traditional taskbar-based experience.

According to multiple posts on Reddit and Google’s support forums, the feature appears to have stopped working on screens where the Android Auto taskbar is displayed vertically. Previously, enabling “Quick Controls” would automatically reposition the taskbar to the bottom of the display, restoring horizontal functionality. Now, however, toggling the setting has no visible effect — the taskbar stays fixed in place, and the shortcut controls never appear.

Early signs of this issue emerged in late September, coinciding with Android Auto 15.2’s transition to the stable release track. As the update continues to roll out to more vehicles and head units this week, reports of broken “Quick Controls” have grown significantly.

It is still uncertain whether this is a temporary software bug or an intentional move by Google. While the company has yet to make any official statement, some users have noted that “Quick Controls” still function normally on certain display orientations and screen configurations, suggesting the removal may not be by design.

Android Auto has undergone major UI restructuring over the past year, with Google gradually shifting away from redundant features in favour of a cleaner, dashboard-first interface. This change aligns with the company’s broader goal of simplifying in-car navigation and entertainment controls. However, given the current inconsistency across devices, it’s possible that the broken functionality could be the result of an incomplete rollout or a compatibility glitch.

Until Google addresses the issue, affected users can only wait for a potential fix in an upcoming version.