Google Maps traffic lines disappeared from Android Auto: what's gone, what still works, and the one fix that helps

Google Maps traffic lines disappeared from Android Auto car screens this week, stripping away the green, orange, and red congestion markers drivers use to read road conditions at a glance. Every road shows gray. The same phone displays traffic correctly when unplugged from the vehicle, according to user reports compiled by Liberty Times Net this week. Google has not acknowledged the bug.

User reports point to a specific version pairing: Google Maps 26.28.03.942936911 running alongside Android Auto 17.2.662624. Some users on the Android Auto 17.3 beta say they aren't seeing the problem, though that observation is anecdotal and unconfirmed, Liberty Times Net reported. Cache clearing, reinstalling Android Auto, and full device reboots have all failed to restore the colors for affected users.

There is one workaround. Whether the bug touches anything beyond the visual layer is worth understanding before assuming the rest of navigation is intact.

The only confirmed fix for Google Maps traffic layer missing on Android Auto

Tapping the "North Up" button on the Android Auto map shifts the display to a top-down overview orientation and causes the traffic colors to reappear, Liberty Times Net reported this week. Do this before departure, while stationary. The fix is view-dependent and may not hold if the map mode shifts mid-drive.

Standard troubleshooting won't get you anywhere. Cache clearing, reinstalling Android Auto, and rebooting have all failed across affected devices, Liberty Times Net noted. User reports mention a Toyota RAV4 and a Subaru Forester among affected vehicles, which points to a software-level bug rather than anything tied to a specific head unit.

Outside speculation points to two possible causes: a conflict with Google's gradually rolling-out immersive navigation feature, or a rendering error introduced in the recent Maps update, Liberty Times Net reported. Neither has been confirmed. Keep automatic updates enabled for both apps; any fix will arrive through an update, and no local troubleshooting step has worked for any affected user.

What drivers actually lose and what probably still works

The traffic color overlay is not decorative. Green, orange, and red give drivers an immediate read of road conditions without needing to parse a route summary or wait for an audio cue. That two-second scan while merging or approaching a highway split is exactly what the overlay is designed for. No turn-by-turn prompt replaces it.

The more consequential question is how much the bug affects the navigation engine running underneath.

Google Maps builds its traffic picture from probe data: speed and position readings collected from vehicles running navigation apps, averaged across short road segments, then translated into color bands, School of Web explained earlier this year. Route calculation works like a transit planner picking the fastest combination of legs, using each segment's current travel time as the key variable, School of Web noted. ETAs blend real-time probe data with historical patterns, which is why an arrival estimate drifts up or down by a few minutes mid-drive as fresh readings come in.

The color overlay is a visual output of that system, not a separate input to it. When affected users see gray roads on the car screen but correct traffic on the unplugged phone, the display is the problem, not the underlying data feed. That's the most plausible interpretation of the behavior. The root cause hasn't been officially identified, though, and no one has independently confirmed whether congestion-based rerouting and ETA adjustments are fully intact for affected sessions. If route accuracy matters for a specific trip, cross-checking on the phone before driving is a reasonable precaution.

The short version: ETAs and route suggestions are probably still working. The ambient awareness you normally get from a glance at the map is gone.

Android Auto has been here before

The current bug follows a recognizable pattern for how Maps failures on Android Auto tend to go.

About 14 months ago, alternate routes stopped appearing in Google Maps for Android Auto users and stayed missing for weeks. Cache clearing, reinstalls, and reboots all failed, and Google never acknowledged the issue or offered a timeline, according to Android Police. The problem didn't appear to affect CarPlay users. The current situation rhymes closely: same platform, same silence, same ineffective troubleshooting cycle. That CarPlay was spared then suggests Android Auto's interface layer carries rendering vulnerabilities that the underlying Maps data backend doesn't share.

A separate glitch that same month falsely marked dozens of major German highways as closed during a holiday weekend. The false closures were resolved within hours, but Google described only its data sources in general terms and never explained what had actually gone wrong, Android Police reported.

The pattern matters for one practical reason. When something breaks on Android Auto, users get no status update, no scope confirmation, no fix timeline. They're left guessing whether the problem is local to their device, already addressed in a server-side patch, or weeks from resolution. For a feature people depend on while driving, that communication gap is its own kind of problem.

What comes next

Use North Up mode before setting off, keep auto-updates on for both apps, and treat your route suggestions as probably reliable while accepting the loss of at-a-glance road-condition awareness.

Three things would materially change this story: a Google acknowledgment confirming scope and cause, a fix landing in a stable release, or user reports showing that rerouting accuracy is visibly degraded. None of those have happened. Google is reportedly continuing to expand Android Auto's feature set, with widgets, broader audio app support, and large-screen interface improvements expected to roll out this year, Liberty Times Net noted. A rendering bug in the current stable release is an awkward backdrop for that roadmap, but it doesn't change the fix timeline, which remains unknown.

Until Google says something, the North Up workaround is all there is.