The accelerated development of Android Auto continues, as evidenced by the fact that last month we were talking about the launch of Android Auto 13, and now we are moving two versions to Android Auto 13.2. The good thing about so many consecutive versions coming out is that Google is working on a lot of new features, such as the arrival of new applications compatible with Android Auto, the possibility of using the radio in Android Auto, and much more. even more.
But these are not all advantages. When you step on the accelerator like that in app development, mistakes are inevitable; and when they arise, they can affect a large number of users who have no idea what is happening, because Google is not as transparent as it should be and does not report changes as it applies to Android Auto.
With the new Android Auto 13.2, we may see the effect of this policy. As usual, the new version arrived on Google Play without fanfare, and only users who tried the update realized that there is a new version; in the same way, Google has not detailed the news either of this version.
In theory, Android Auto 13.2 should lay the groundwork for recently announced new features, like Qualcomm and Google’s collaboration to bring AI to the car, and the latest Google Maps features that include a navigation mode with improved graphics and possibility of adding stops at interesting places on the route.
However, if you’re currently happy with Android Auto, you might be better off waiting for the next version, just in case. And just at the time of this new version, many complaints are coming from users who claim that an update stopped in-car callsmaking it completely unusable if you depend on this hands-free function.
Specifically, users report that when making a call with Android Auto, The sound comes out through the mobile speaker and not through the car speakers; This makes finding out what they are telling us much more difficult, if not impossible. The only thing these users can do is increase the volume of their cell phone to the maximum, because if they pick it up they could be distracted and cause an accident, or be fined by a DGT camera or a civil guard. Google Pixel mobile users seem to be the most affected so far.
It’s unclear if this latest version of Android Auto is causing the problem. For security reasons, users who are now using Android Auto and have no issues should probably wait for the next version, as there is no compelling reason to update. But if we suffer from this failure, the opposite might be better for us: install the update as soon as possiblejust in case Google fixed the “bug”.
