Android Auto preferred phone number feature spotted in code
Calling a contact with more than one saved number through Android Auto has always meant one extra step: picking home, work, or mobile before the call actually connects. A teardown of a daily Android Auto build suggests that step might finally disappear, surfacing what's being described as an Android Auto preferred phone number feature buried in a set of unfinished code strings (Android Police, yesterday).
The strings turned up in Android Auto version 18.1.164344-release.daily, a build nowhere close to a public release. Google hasn't announced the feature, explained how it would work, or committed to a release window (Samsung Magazine, yesterday), and coverage of the find describes the underlying code as unfinished with no confirmed timeline (iHeartGeek, yesterday).
The problem this would fix is familiar to anyone with a chatty contact list. Telling the car to "call John" still triggers a secondary prompt to choose a number whenever John has more than one saved, and Gemini runs into the exact same wall handling the same request (Android Police, yesterday).
What the Android Auto Remember this choice strings actually show
The clearest piece of evidence in the teardown is a line of interface text: "Default set to %1$s. Click on contact to change." That phrasing points to a default contact number a driver could set once and revisit later, rather than a one-time override that resets on the next call (iHeartGeek, yesterday).
Alongside that string, the build contains a "Remember this choice" option that would reportedly surface during the call flow itself, letting a driver lock in a number the moment they place a call instead of digging through contact settings beforehand (Android Police, yesterday).
Compare that to how the app behaves right now: selecting a multi-number contact brings up the full list of saved numbers every single time, with no memory of what a driver picked on the last call (Android Police, yesterday).
What the strings don't settle is whether Gemini would inherit the same saved default. Android Police reports that once a driver sets the preference, "Gemini and Android Auto will assume you want to ring that specific number each time, until you tell it otherwise," though this detail still traces back to the same underlying teardown rather than independent confirmation from Google (Android Police, yesterday). A shared Gemini preferred phone number for contacts reads as the likely outcome here, not something anyone has verified hands-on.
The same build also contains strings for a Material 3 Expressive redesign of the Phone app's dial pad, swapping today's minimalist layout for larger, rounded buttons (Android Police, yesterday). That's a separate visual change found in the same code dump, not proof Google plans to bundle it with the calling fix, and it does nothing to change how multi-number contacts actually get dialed.
Who notices Android Auto calling multiple numbers less
The upside here is narrow by design. It only matters for contacts saved with more than one number, home, work, mobile, or some combination. Anyone whose contacts carry a single number already dials without interruption, so that group sees no change from this at all.
For everyone else, the friction repeats on a loop. Every call to a multi-number contact triggers the same manual selection screen today, a pattern Android Police calls small on its own but more consequential than its size suggests, especially for people who dial the same handful of contacts daily.
Voice-first drivers arguably have the most riding on this. Gemini's identical prompt means saying "call Mom" doesn't actually save a step over tapping a name on the screen, since the assistant still needs a follow-up answer about which number to dial. If the saved preference extends to Gemini, that group sees the biggest change in daily habit. If it doesn't, screen-based calling in Android Auto gets fixed while voice commands keep the old back-and-forth.
Eligibility is the other open question, and there isn't much to report yet. None of the coverage so far names which Android Auto versions, phone brands, regions, or beta channels might see this first. The only confirmed location remains a single daily build, not a public release track anyone can opt into today.
Why a daily-build teardown isn't a release date
APK teardowns work by digging through compiled app code for strings, icons, and layout files that haven't shipped to any user yet. They're useful for spotting what a company might be building, but they can't confirm a feature survives internal testing, clears regional review, or ever reaches a stable release. The safest read on this particular find: Android Auto appears to be exploring a way to remember a contact's preferred number, not that the feature is ready for anyone to use (iHeartGeek, yesterday).
That caveat matters here because basic implementation details are still missing. The teardown doesn't explain how a driver would actually set a default number in the first place, or where that preference would ultimately live. Even the outlets covering the find acknowledge the gap: the strings describe what the feature would do, not how it would work.
Coverage of the find spread fast, but it's worth being clear about where that coverage actually comes from. iHeartGeek's write-up is explicit that its report rests on Android Authority's original teardown rather than independent testing or a separate source inside Google, and it says plainly that the find "is not a confirmation of a public feature" (iHeartGeek, yesterday). Android Police's piece cites the same 18.1.164344-release.daily build. None of the outlets covering this have hands-on access to the feature working, because as far as the public record shows, it isn't working anywhere yet.
Real confirmation would look different from another teardown. It would mean the "Remember this choice" option, or a named default-number setting, showing up in a public Android Auto beta or stable release that anyone running that build could actually tap. It would also mean Google saying something about it directly, or independent testers confirming that calls placed through Gemini respect the same saved preference as calls placed through the standard Android Auto interface.
What Android Auto users should do now
There's no setting to hunt for in the current release of Android Auto, and nothing to toggle on or off. The preferred-number behavior described in the teardown exists only inside a daily build Google hasn't pushed to beta testers, let alone everyday drivers.
Anyone annoyed by the current multi-number prompt has one practical move: watch official Android Auto release notes for language naming a default number setting or a "Remember this choice" option, rather than assuming it's rolling out just because a teardown found the strings. Until that language appears in a build people can actually install, or Google confirms it directly, the Android Auto preferred phone number feature stays a plausible next step, not something drivers can count on yet.
Comments
Be the first, drop a comment!