Google Maps speedometer is starting to appear for a small number of Android Auto users, but the useful news is not simply that it exists. The useful question is how to check a limited rollout without joining a beta programme or hunting for a setting that is not there. On July 19, 9to5Google documented the first sightings: at least two users in Canada saw the readout on their car displays with Google Maps 26.29.02.946673643, a beta build. That is not a Google changelog, not broad availability, and not proof that updating the app is enough to unlock it.
This is therefore a verification guide, not a recipe for forcing a server-side feature. Google’s Android Auto documentation explains that Android Auto brings compatible phone apps to the car display. Before blaming Maps, make sure the Android Auto connection is stable, the app is current and the car is exposing the display correctly. The remaining variable, in this case, is still the rollout.
First distinction: Android Auto is not Android Automotive OS
The report is about Android Auto, which projects a phone to a car display. It does not automatically apply to Google Maps running natively in a vehicle with Android Automotive OS. This is not pedantry: if the car runs Maps without the phone connected, you are looking at a different product and a different update channel.
Also confirm that Google Maps is the app navigating on the display. The reported speedometer is neither the vehicle’s own cluster readout nor a universal system indicator; it is a Maps interface element. If you use Waze, you are not waiting for the same feature: Waze has offered a speed readout in Android Auto for years, as the original report notes.
Checklist: verify it without turning beta software into a ritual
- Check the basic connection. Connect the phone by cable or wirelessly, open Maps on the car display and start navigation. If Android Auto disconnects, or Maps is missing from the launcher, the speedometer is not the first problem to solve.
- Record the Google Maps version. On the phone, open Settings > Apps > Maps, or check the app’s Play Store page. The documented sighting used beta build 26.29.02.946673643. It is not an official requirement or a magic threshold, but it is a useful comparison point.
- Install pending updates for both Android Auto and Google Maps. A server-side rollout may ignore the build number, but old apps make any comparison less meaningful.
- Look at the interface only while parked, or ask a passenger to check. Start a destination and look for the speed value in the navigation UI; do not tap through the display while driving. A car screen is not a debugging console, despite occasional evidence to the contrary.
- If it is absent, do not clear data or reinstall Maps. First save the car model, country, connection type, Maps version and Android Auto version. Those are evidence; a random reset turns them into a vague memory of having “tried something.”
What Play Store beta can and cannot do
The fact that the initial sighting came from a beta build is not an invitation to enrol. Play Store beta access can deliver newer code, but it cannot necessarily switch on a remote flag and it can bring regressions to an app used in the car. If Maps and Android Auto are stable today, moving to beta solely for an unconfirmed indicator is an unusually poor risk-to-benefit trade.
If you are already on the beta, update, restart the phone and test an ordinary navigation session. If you are not, wait for consistent reports in your country or an official update. Based on the information available, there is no reliable Maps or Android Auto toggle that enables this feature.
What actually changes
An integrated speed readout may reduce the need to move your eyes between the display and the instrument cluster, but it does not replace the car’s speedometer and should not be treated as a legal-speed instrument. Its practical value is interface design: if the number appears without covering maneuvers, lanes and ETA, it makes navigation easier to read. If it remains confined to a few beta builds, it is simply an experiment visible to a small group.
The important technical point is that Android Auto combines app version, phone, car, country and server-side configuration. That is why the better question is not “how do I enable it?” but “which link in the chain has received it?” Apply the same method when the issue is less cosmetic, such as AndroidLab’s related guide to wireless Android Auto, battery drain and Google Maps offline checks: isolate the context before touching settings.
Practical conclusion
Update Maps and Android Auto, confirm that you are using Android Auto projection, then check a navigation session safely while parked. If the speedometer is missing, the likely answer today is not a fault: your account, country or build is simply outside the rollout sample. Waiting for better evidence is less theatrical than beta-chasing, but much less likely to break a working setup.
In brief
- The first Maps speedometer sightings in Android Auto are from July 19 and a beta build, not a general rollout.
- Check whether you use Android Auto or Android Automotive OS; they do not necessarily receive the same features.
- Update Maps and Android Auto, but do not expect a visible toggle or a guarantee from beta access.
- Test while parked and keep the version, country and connection type if you want to compare results.
- The readout can help the interface, but the vehicle’s speedometer remains the reference.