Photo: Bogdan Popa/autoevolution/Google
Android Auto not working correctly is no longer news, as the application tends to break down for the most insignificant reason.
However, you wouldn't expect Android Auto to misbehave in a brand-new 2023 car, especially as the integration on the vehicle side should already be more refined.
Well, getting a 100% reliable Android Auto experience is still a challenge, whether you drive an old or a new car. Living proof is a new round of complaints from 2023 SEAT customers who ended up struggling with Android Auto.
A reader who contacted me using the tips section explained that they tried running Android Auto before leaving the dealership. The car was brand new, so they expected the application to fire up instantly.
It didn't, so they asked the mechanics to investigate the problem. The response was concerning: you're not the first customer who can't run Android Auto, but the problem is on Google's side. In plain English, Google must fix Android Auto, as everything runs properly on the vehicle.
Several SEAT customers confirmed on the official Google forums that they encounter similar problems in their cars. Someone says they purchased a new 2023 Arona, trying to run Android Auto with a Samsung Galaxy S23 (this is one of Samsung's latest flagships). The device runs Android 14 and an up-to-date Android Auto version, but they still get an error when trying to launch the app.
"Sorry, your mobile device could not be connected," the message reads.
Several others confirmed the same behavior in other SEAT models, and I'm also seeing complaints from other 2023 car buyers, including BMW. It's unclear if there's a pattern here or if the connection problems happen due to sporadic issues, but Android Auto not working in a brand-new car certainly isn't the experience someone paying a small fortune on a vehicle expects when getting behind the wheel for the first time.
Google has so far remained tight-lipped on the bug, but on its forums, a community specialist requested additional bug details to forward them to the Android Auto team.
Users who encountered the problem claim they've tried everything to no avail. They uninstalled Android Auto updates, deleted the cache and the data, and even reset the infotainment system in the vehicle.
I believe the problem could be related to Android 14, so if you still have an Android 13 around, try to connect it and see if Android Auto launches. If it does, Google's new operating system is to blame. If it doesn't, your next step is downgrading to the oldest Android Auto version you can try, as this step should help you determine if the app is the culprit. If Android Auto doesn't launch with the oldest version, the problem might reside in the software running on the vehicle's infotainment unit.
Well, getting a 100% reliable Android Auto experience is still a challenge, whether you drive an old or a new car. Living proof is a new round of complaints from 2023 SEAT customers who ended up struggling with Android Auto.
A reader who contacted me using the tips section explained that they tried running Android Auto before leaving the dealership. The car was brand new, so they expected the application to fire up instantly.
It didn't, so they asked the mechanics to investigate the problem. The response was concerning: you're not the first customer who can't run Android Auto, but the problem is on Google's side. In plain English, Google must fix Android Auto, as everything runs properly on the vehicle.
Several SEAT customers confirmed on the official Google forums that they encounter similar problems in their cars. Someone says they purchased a new 2023 Arona, trying to run Android Auto with a Samsung Galaxy S23 (this is one of Samsung's latest flagships). The device runs Android 14 and an up-to-date Android Auto version, but they still get an error when trying to launch the app.
"Sorry, your mobile device could not be connected," the message reads.
Several others confirmed the same behavior in other SEAT models, and I'm also seeing complaints from other 2023 car buyers, including BMW. It's unclear if there's a pattern here or if the connection problems happen due to sporadic issues, but Android Auto not working in a brand-new car certainly isn't the experience someone paying a small fortune on a vehicle expects when getting behind the wheel for the first time.
Google has so far remained tight-lipped on the bug, but on its forums, a community specialist requested additional bug details to forward them to the Android Auto team.
Users who encountered the problem claim they've tried everything to no avail. They uninstalled Android Auto updates, deleted the cache and the data, and even reset the infotainment system in the vehicle.
I believe the problem could be related to Android 14, so if you still have an Android 13 around, try to connect it and see if Android Auto launches. If it does, Google's new operating system is to blame. If it doesn't, your next step is downgrading to the oldest Android Auto version you can try, as this step should help you determine if the app is the culprit. If Android Auto doesn't launch with the oldest version, the problem might reside in the software running on the vehicle's infotainment unit.
Google News