Android Auto now requires Android 11: what older phones lose

Google has quietly rewritten the rules for Android Auto. The company's support page now lists Android 11 as the minimum operating system required to use the service, a change that pushes both Android 9 and Android 10 out of official support (9to5Google, this week; Android Police, this week).

The shift affects drivers on older flagship phones that never received an Android 11 update, including the Samsung Galaxy S9 and Galaxy Note 9 (SamMobile, this week). But the rollout looks messy. Some Android 10 devices still connect without issue, others have reportedly stopped working entirely, and Google hasn't published a date for when enforcement becomes universal (Android Central, this week; Android Police, this week).

Here's what's confirmed, what's still unclear, and what to check on your own phone before you assume anything.

Android Auto's Android 11 minimum requirement: what Google changed

Google's updated support documentation now specifies that using Android Auto requires "Android 11.0 (Red Velvet Cake) or higher" along with an active data plan (9to5Google, this week). That replaces the previous Android 9 Pie floor, a requirement Google had announced two years ago but reportedly didn't start enforcing until last year (9to5Google, this week).

For anyone connecting wirelessly, there's an additional hardware requirement layered on top of the OS version: a phone also needs 5 GHz Wi-Fi support (BGR, this week). That's separate from the Android 11 floor and has been in place regardless of this latest change, but it's worth checking if your phone is older and you rely on wireless Android Auto rather than a USB cable.

Wired vs. wireless: reports disagree on how far the cutoff reaches

Pay close attention here, because outlets covering the change aren't telling the same story. Android Police describes the new Android 11 requirement as applying to both wired and wireless Android Auto connections (Android Police, this week). Android Central and SamMobile, by contrast, frame it specifically as a requirement for wired, USB-based connections (Android Central, this week; SamMobile, this week).

Google's own support page doesn't spell out a wired-only or wireless-only distinction in the reporting available, which leaves genuine ambiguity about scope. If you're deciding whether to buy a new phone purely to restore wireless Android Auto, don't take any single outlet's framing as the final word. Check Google's current support page directly before you spend money on a fix that might not address your specific setup.

Which phones have lost Android Auto support

The clearest confirmed casualties so far are the Samsung Galaxy S9 and Galaxy Note 9 series, which no longer work with wired Android Auto (SamMobile, this week). SamMobile reports the only fix for owners of those models is upgrading to a phone that ships with Android 11 or newer (SamMobile, this week).

That list almost certainly isn't exhaustive. Any phone that a manufacturer permanently capped at Android 9 or Android 10, regardless of brand or release year, now sits in the same boat for wired Android Auto. The practical move is to check your phone's final software update rather than assume your specific model is safe just because it's not named in current reporting.

Android Auto support for older phones is spotty right now

Despite the policy change, Android Auto version 18.1, the current release of the app, reportedly still works on some Android 10 phones (9to5Google, this week). That inconsistency suggests Google hasn't flipped a single global switch. Warnings started appearing for some Android 10 users last month, weeks before the public support documentation caught up this week (Android Central, this week).

Meanwhile, other users say the feature has already stopped working on their devices entirely, and Google hasn't given a date for when every affected phone will lose access (Android Police, this week). Whether that means a staged rollout, a server-side check that varies by account, or something else isn't confirmed anywhere in current reporting. Treat it as unresolved rather than assume a tidy explanation.

Workarounds don't look promising either. One Galaxy S9 owner tried rolling Android Auto back to versions as old as 1.0.x and still couldn't restore the connection (Android Central, this week). If your phone currently still connects, don't assume that's a sign the cutoff won't eventually reach it. And if it's already broken, downgrading the app isn't a dependable fix based on what's been reported so far.

Google has narrowed Android Auto's OS requirements before

This isn't the first time Google has trimmed the list of Android versions it supports for in-car use, though the exact history gets murky depending on the source. BGR reports that Android 8.0 Oreo became the minimum in 2022, followed by a bump to Android 9 Pie two years ago (BGR, this week). Android Central instead describes Google dropping support for Android 6 in 2022 and Android 8 two years ago (Android Central, this week).

The two accounts don't match on specifics, and neither cites Google's own version history directly, so the precise timeline isn't something this reporting resolves. What both agree on is the pattern: Google periodically raises the floor, and the jump to Android 11 continues a policy that's been underway for years rather than a one-off decision.

Scale-wise, Google's own distribution data from last month shows that 88.3% of active Android devices are already running Android 11 or later (BGR, this week). There's no Android Auto-specific breakdown of how many drivers that leaves out, and BGR is explicit that the actual number of affected users isn't known. In percentage terms the cutoff touches a minority of the Android install base, but that's cold comfort if you're one of the people whose otherwise functional flagship just lost in-car connectivity.

What to check before you assume your phone still works

Start with Settings > About phone and confirm your Android version. If you're on Android 9 or 10, don't assume today's working connection means tomorrow's will work too, given how inconsistently enforcement has rolled out so far.

Next, check whether your phone's manufacturer ever shipped an Android 11 update for your exact model, not just the general product line. Some variants of the same phone series received different final OS versions depending on region or carrier.

If you rely on wireless Android Auto specifically, hold off on buying a replacement phone until Google's support page gives clearer wired-versus-wireless language, since current reporting conflicts on whether the Android 11 floor applies to both connection types. And don't count on app downgrades as a fix: the one documented attempt to roll back to an older Android Auto version didn't restore access.

If Android Auto is essential to how you drive and your phone is permanently stuck on Android 10 or lower, treat continued access as something that could disappear without notice rather than a guarantee, and start budgeting for a phone that ships with Android 11 or newer.