Photo: Google
It’s never quiet in the Android Auto world, and this time the thing that’s making some buzz is a glitch that pretty much causes the application to shut down automatically after only a few seconds.
In other words, Android Auto loads and starts correctly, but after 10 to 20 seconds, or even less, the application just disconnects.
Users posting in this thread on Google’s forums claim the whole thing happens with new-generation Android phones, as for some reason, Android Auto is just running flawlessly with an old device like a Samsung Galaxy S7.
But the moment they switch to a new phone running Android 10 or 11, Android Auto just can’t stay connected for more than a few seconds.
“Recently I tested it with my Samsung S21 Ultra, and the issue is the same. Just for fun I reconnected my S7 to the head unit again, and that works just fine. So it really suggests that it is related to newer version of Android on the mobile device,” one user explains.
The generic workarounds don’t seem to be making much of a difference, so in case you’re thinking of downgrading Android Auto to an earlier release or switching to a new cable, that won’t help.
At this point, it’s not really clear what’s causing the error, especially because at the first glance, Android Auto doesn’t seem to be the culprit given the app starts and runs correctly at first.
On the other hand, a random disconnect while running the app appears to suggest the cable or a loose connection could be the one to blame, but of course, given several other cords have already been tested by people struggling with the glitch, there’s a chance this isn’t the problem either.
Google is yet to acknowledge the glitch, and time will tell how widespread this error eventually becomes, especially as more people upgrade to new-generation Android phones.
Users posting in this thread on Google’s forums claim the whole thing happens with new-generation Android phones, as for some reason, Android Auto is just running flawlessly with an old device like a Samsung Galaxy S7.
But the moment they switch to a new phone running Android 10 or 11, Android Auto just can’t stay connected for more than a few seconds.
“Recently I tested it with my Samsung S21 Ultra, and the issue is the same. Just for fun I reconnected my S7 to the head unit again, and that works just fine. So it really suggests that it is related to newer version of Android on the mobile device,” one user explains.
The generic workarounds don’t seem to be making much of a difference, so in case you’re thinking of downgrading Android Auto to an earlier release or switching to a new cable, that won’t help.
At this point, it’s not really clear what’s causing the error, especially because at the first glance, Android Auto doesn’t seem to be the culprit given the app starts and runs correctly at first.
On the other hand, a random disconnect while running the app appears to suggest the cable or a loose connection could be the one to blame, but of course, given several other cords have already been tested by people struggling with the glitch, there’s a chance this isn’t the problem either.
Google is yet to acknowledge the glitch, and time will tell how widespread this error eventually becomes, especially as more people upgrade to new-generation Android phones.
Google News