Google Maps Gets Always-On Speed Display on Android Auto

Google Maps on Android Auto is moving to a specification that displays the speedometer even when no destination is set. Speed limits, traffic lights, and stop signs will likewise be subject to always-on display. According to reporting by Chandra Steele of Android Police, the policy was disclosed by Mishaal Rahman, Android community engagement manager. The feature is in the process of a gradual rollout.

Previously, driving-assistance displays such as the speedometer in Google Maps for Android Auto were limited to cases where a destination was set. When driving freely without setting a destination, the displays did not appear. That difference caused confusion last week. Now, that very premise is being changed, moving toward always-on display.

The speedometer on Android Auto in Google Maps is about to be a fixed destination.

This single sentence succinctly shows the direction of the change. It means the speedometer has entered a stage where it is treated as a resident instrument, rather than a temporary guidance display.

Shift to Always-On Display on Android Auto

The changes cover the speedometer, speed limits, traffic lights, and stop signs. All are driving-assistance information overlaid on the Google Maps screen. The difference from the past is that they are shown regardless of whether a destination is set. Even while driving freely, you can check your own vehicle position and regulatory information at the same time.

According to Rahman, this always-on display is still being rolled out. It is not immediately available in all user environments. Server-side switching and staged rollout are proceeding in parallel. Behavior may differ depending on the user’s device and app version.

Always-on display is close to an idea called persistent navigation. It is a form in which the map follows driving and continues to present regulatory information even without starting destination guidance. Some users had already encountered this form through trial rollout. This update is positioned as its formal expansion.

Making the display persistent has the effect of reducing eye movement while driving. It reduces the number of times drivers compare the instrument cluster with the map screen. Speed and the speed limit can be checked on the same screen. It is highly significant as support for safe driving.

Bug Reports Reveal the Reality of the

Specification Change

It started with bug reports that spread about a week ago. There was a series of reports that the speedometer, speed limits, and traffic light displays had disappeared from Google Maps. Some users suspected the feature had been removed or a failure had occurred. Discussion expanded, centered on Reddit.

Rahman responded to user inquiries on Reddit. In his response, he explained that the displays reported as missing were specified to appear only when a destination was set. In other words, it was behavior as specified, not a bug. At the same time, he indicated that a feature to show them even without a destination was being rolled out.

What fueled the confusion was the existence of trial rollout. Some users had already experienced persistent navigation. However, there were cases where clearing the app cache reverted the display to its previous behavior. The loss of the trial feature looked like a bug.

This sequence illustrates the difficulty of disclosure in staged rollouts. Behavior differs between the test group and the control group. To users, it looks like an overall specification change. If explanations from the provider lag behind, it turns into failure reports. The response on Reddit this time functioned as a retrospective clarification.

Limitations of the Speedometer Feature

Introduced in July

Google Maps for Android Auto gained a speedometer in late July. The introduction itself was welcomed. At the same time, the slowness of the rollout was also pointed out. The reason was comparison with competing navigation apps.

Waze had a speedometer since before Google’s acquisition in 2013. Even after coming under the same corporate group, the Google Maps side made no progress. Google Maps for Apple CarPlay had supported a speedometer for about two years. The delay of the Android Auto version became even more conspicuous.

The implementation as of July assumed that a destination was set. During guided driving, speed and the speed limit were displayed. During free driving, the display did not appear or was limited. The benefit was thin for users who do not use guidance for everyday travel. This always-on display resolves that constraint.

The significance of the speedometer lies in supporting compliance with regulations. Drivers can instantly grasp the difference between their own speed and the speed limit. Displays of traffic lights and stop signs also serve as alerts. The integration of maps and regulatory information is fundamental to driving assistance. Making it persistent can be evaluated as a change that returns to that foundation.

As technical background, there is speed calculation by the Global Positioning System. Speed is a pure calculation obtained by dividing distance by time. A vehicle-side speedometer includes mechanical factors and display margin. It is designed to fall within an industry-recognized accuracy range, but it may differ from the strict actual speed. This is why the map-side speed display serves as practical cross-check material.

How to Enable It on the Smartphone Side

Using the speedometer requires updating Google Maps and Android Auto. Keeping both up to date is a prerequisite. Then, change the settings in Google Maps on the smartphone side.

The procedure is to open Google Maps and select the account image at the top right. From Settings, select Navigation and proceed to Driving options. Enable the speedometer toggle. After setting, it will be reflected when connected to Android Auto.

The caveat is the impact of staged rollout. Even if the setting item exists, it may not be reflected on the in-car screen. In environments not covered by the rollout, the display will not appear. Operations such as clearing the cache may cause the loss of the trial state. It is safer to avoid casual initialization.

The relationship between the in-car display and the smartphone display also needs to be checked. Settings are retained on the smartphone side. The display appears on the map screen on the Android Auto side. A version mismatch between the two can cause inconsistency. After updating, reconnect and check the behavior.

Updates to Related Google Services

Google continues to update features around maps and in-vehicle areas. Refinement is also progressing in payments, photos, and video distribution. The in-car screen could become a point of contact for them. Making maps persistent will serve as the foundation for the overall in-car experience.

On the payments side, the direction shown by the Google Wallet customized ticket feature for Ticketmaster is a useful reference. Optimization of ticket-face display for each use case is progressing. On the in-car screen as well, information presentation tailored to destinations and reservations will become important. Persistent map display is the prerequisite.

In the photo and video editing area, the Google Photos UI refresh and Gemini video editing features are drawing attention. Simplification of the operation system and integration of generative AI are progressing. Simplification is also required for in-car operation systems. Visibility and reducing the number of operations are common challenges.

In terms of video display quality, there is the move shown by LG OLED evo, Creator Original picture mode with Prime Video. Display that preserves the creator’s intent is being emphasized. For in-car maps as well, visibility in day and night and under backlight is important. Crafting display quality is directly linked to safety.

Editorial Opinion

As a short-term impact, we expect use premised on display during free driving to spread over the next three to six months. Checking speed against the speed limit will become established even in daily driving without setting a destination. The confusion reported as bug reports will subside as explanations spread. Differences from staged rollout will remain, but we assess that inquiries will decrease as setup procedures become widely known.

From a long-term perspective, we expect resident-type maps to become the in-vehicle standard within one to three years. Persistent navigation, not delimited by starting guidance, will become the norm. Display of speed regulations and signs will become established as the foundation of driving assistance. Duplication with vehicle-side instruments will become common, with the map side potentially used as a reference for cross-checking.

As a question from the editorial team, the accuracy of displays and where responsibility lies are at issue. How should delays in updating speed-limit data be handled? How should overconfidence by users be prevented when traffic lights or stop signs are missing? We believe that the more map providers step into vehicle instrumentation, the more important the freshness of information and handling of erroneous displays will become.

References

• “Google Maps on Android Auto is finally getting a speedometer that’s always on”, by Chandra Steele — Android Police, 2026-09-14T19:53:54.000Z (ARR)
• Source URL: https://www.androidpolice.com/google-maps-on-android-auto-is-finally-getting-a-speedometer-thats-always-on/