Super popular app starts to act on Android Auto, bad update to blame


Google Play Music has long been the favorite service for Android Auto users, but now that Google has decided to go all out on YouTube Music, Spotify’s fan base has clearly improved.

And it’s no wonder why. Spotify is currently available in a total of 178 markets, providing access to an impressive collection of over 70 million tracks and over 3.2 million podcasts.

And one of the most important things about Spotify is that it feels right at home on Android Auto, with all the essential features right behind the wheel.

But like everything else on Android Auto, Spotify, to, o has all kinds of issues that no one can explain. And one issue that was discovered recently is just confirmation that sometimes it’s best to refrain from updating your apps if you don’t care a lot about the latest improvements.

The problem

Specifically, many users who turned to Google forum to point it out, state that Spotify no longer works with voice commands when running Android Auto on the screen.

In other words, Spotify works fine when playing music, but when it comes to switching to a specific track requested with a voice command, the app becomes unresponsive anymore.

Most people who experience this unexpected behavior claim that after repeating the command, Spotify ends up picking up the song that was already playing, thereby completely ignoring the request.

Others explain that Spotify acts differently in their cars. This time the app searches for the requested song but doesn’t play it automatically, so users just have to go to the search results manually and select the track to listen to.

In either case, however, the whole thing was introduced after a recent update, although at the moment it’s unclear exactly who is to blame for this issue.

The most recent stable version of Android Auto is 7.0, and it went live on the Google Play Store in early November. In the case of Spotify, the last update was released to the store on October 28, so both new versions ended up pushing Android devices almost at the same time.


In theory, if you’re certain that a recent version of Android Auto or Spotify is to blame for the aforementioned bug, the easiest workaround is to simply downgrade.

To do this, you need to manually remove the apps from your mobile device and then download the APK installers for the version you want to downgrade to. You can find the Spotify and Android Auto APKs on those pages here – just make sure you select the correct version when downloading them.

On the flip side, others have tried the generic workarounds, but these made little or no difference in almost all cases. Users claim that clearing cache, deleting data and even reinstalling Spotify does not restore voice commands to Android Auto.

So, at the moment, it’s pretty clear that a full patch from Google or Spotify is absolutely necessary to resolve the error on Android Auto.

The good news is that the Mountain View-based search giant has already confirmed that it is reviewing all of these reports, although at this time there is no ETA for a fix. In other words, the company is trying to figure out what is really going on and why Spotify is not playing well with voice commands anymore, and only then start work on the full fix.

In the meantime, Spotify has been completely low-key about the struggle with voice commands, so if the error occurs on its end, it might take even longer until it’s finally resolved.

Source link

Leave A Reply

Your email address will not be published.