Photo: autoevolution
Samsung Galaxy S20 is one of the best phones of the South Korean company that money can buy right now, but as we’ve already told you not a long time ago, it doesn’t necessarily mean that everything’s running smoothly.
And Android Auto users know this best, as more and more users complain that the app no longer works after they upgraded to the Galaxy S20.
More specifically, Android Auto disconnects all of a sudden on Galaxy S20, and in the last few days, I’ve seen an increasing number of reports from users complaining that in many cases, AA isn’t even detected by the car when plugging in the phone.
In other words, Android Auto fails to launch despite the Galaxy S20 actually charging, which means that the phone itself is connected to the car.
Some say the Galaxy S20 is no longer recognized and is acting just like a device that’s not compatible with Android Auto. In some cases, it can actually play audio via Bluetooth, but Android Auto itself fails to launch no matter what.
Galaxy S20 buyers explain here and here on Google’s forums that trying out different cables doesn’t make any difference – as a matter of fact, the original Samsung cables are the most recommended for Android Auto, so you should stick with the one that comes with the phone for that.
In most of the cases, the aforementioned issues are experienced with the Galaxy S20 when paired with a factory-installed Android Auto-capable head unit, but there are users complaining that similar problems also exist with aftermarket radios.
Of course, the typical solutions don’t work, so you can try resetting Android Auto, clearing the cache, or removing the data, but this won’t fix anything for you. Neither Google nor Samsung confirmed that a fix is on its way, so for the time being, you’re all alone in your adventure to fix this.
We’ve reached out to both companies to ask for more details and will post a follow-up when an answer is offered.
More specifically, Android Auto disconnects all of a sudden on Galaxy S20, and in the last few days, I’ve seen an increasing number of reports from users complaining that in many cases, AA isn’t even detected by the car when plugging in the phone.
In other words, Android Auto fails to launch despite the Galaxy S20 actually charging, which means that the phone itself is connected to the car.
Some say the Galaxy S20 is no longer recognized and is acting just like a device that’s not compatible with Android Auto. In some cases, it can actually play audio via Bluetooth, but Android Auto itself fails to launch no matter what.
Galaxy S20 buyers explain here and here on Google’s forums that trying out different cables doesn’t make any difference – as a matter of fact, the original Samsung cables are the most recommended for Android Auto, so you should stick with the one that comes with the phone for that.
In most of the cases, the aforementioned issues are experienced with the Galaxy S20 when paired with a factory-installed Android Auto-capable head unit, but there are users complaining that similar problems also exist with aftermarket radios.
Of course, the typical solutions don’t work, so you can try resetting Android Auto, clearing the cache, or removing the data, but this won’t fix anything for you. Neither Google nor Samsung confirmed that a fix is on its way, so for the time being, you’re all alone in your adventure to fix this.
We’ve reached out to both companies to ask for more details and will post a follow-up when an answer is offered.
Google News