Android
Mobilsfera Newsroom
Android

Android Auto shouldn't turn a working Galaxy S9 into dead weight

Google now asks for Android 11 even over a USB cable. A silent support-page edit is a poor way to retire phones that still work, and Google owes users a technical reason.

Published
November 10, 2026
Reading time
3 min
Categories
Android

AI-generated image

Is a phone that still makes calls, runs Google Maps and plays your music really too old to talk to a car screen? According to Google's updated requirements, yes. And the way it got there is the part that bothers us most.

What changed, and how little noise it made

Google updated its official support page. As telefonino.net reports, the service now needs an Android phone running Android 11 or later, plus an active data plan. Android Authority also reports that Google confirmed the new minimums, which means Android 9 and 10 are out. The change came without a formal announcement, and some drivers had already seen a warning on screen in October saying their phone would stop being supported.

The affected list includes popular models. Several outlets name the Galaxy S9 and Note 9, and others add the Galaxy A50, A80, Huawei P20 Lite and Xperia XZ2 Compact. SmartWorld frames the new floor as applying to wired Android Auto too, which is the detail that stings.

A cable shouldn't need a brand-new OS

Wireless projection is easy to defend as something that may lean on newer system features. A wired connection is a different matter. In our view, a phone plugged into a car is mostly sending a map and a media player to a bigger screen, and we can't point to a technical reason for needing Android 11. Google hasn't given one that we know of. Without one, the cutoff reads less like engineering and more like housekeeping.

That matters because the people left out are not exactly early adopters. They are probably the ones who kept a good phone for years and treat the car as the one place where it still earns its keep. For them, "buy a new phone" is a steep price for keeping a dashboard feature. And a phone that is still perfectly usable for everything else is the opposite of what the industry says it wants: less e-waste, longer device lives.

Fair point: this is a small group, and cutoffs are normal

To be fair, telefonino.net notes that these users are a small share of the total. And this is not the first cut: the same report says Google had already trimmed older versions in a decision announced in 2024 that took effect in 2025. Maintaining a projection stack for old OS versions surely has a cost, and no company supports everything forever.

Our objection is not that a cutoff exists. It's that it arrived as a documentation edit, after a warning some users stumbled across. There's an oddity too: according to telefonino.net, the latest Android Auto app, version 18.1, still lists compatibility with Android 10. So the app and the policy don't fully agree, and users are left guessing which one wins. That is exactly the kind of ambiguity a clear announcement would have avoided.

What we'd do, and what we'd ask of Google

If you have an Android 9 or 10 phone, check your setup now rather than on a motorway. A phone with Android 11 or newer is the safe route. The cheapest fix is probably a used or budget handset kept purely as a car phone, though that's our suggestion, not something the documentation offers.

From Google we'd ask for three things: a clear announcement with dates, an explanation of why wired projection needs Android 11, and a reasonable grace period. We think a feature that lives on a car's screen should be held to a higher standard than an ordinary app update, because cars tend to outlast phones by years. Retiring a working phone should take a reason, and so far Google hasn't offered one.

Debate topics

No topics yet: start the first one.

More stories