As the world’s number one mobile navigation solution, Google Maps must undoubtedly offer the most stable, reliable, and flawless experience from the moment drivers jump behind the wheel to the one when they arrive at their destination. Starting recently, however, Google Maps is slowly turning into a major struggle behind the wheel, as for some reason, it no longer seems to feel at home on Android Auto. Google Maps, therefore, ended up hitting all kinds of bugs that made way too many people think of switching to an alternative. And as said, Waze is most often the first choice.
For example, Waze, which is owned by Google, is sometimes regarded as the runner-up since it is supported by excellent real-time traffic data, despite Google Maps now being the top navigation app for Android and Android Auto. Unfortunately, moving to Waze may soon be the only choice for people who use Google Maps for navigating. And it all boils down to the growing amount of bugs Google Maps is experiencing on Android Auto.
However, this doesn’t necessarily mean that everything in Google Maps is running properly on Android Auto. The satellite mode, which is one of the most popular layers that drivers enable when starting the navigation, has been broken for nearly a month, with the application freezing and eventually crashing on Android Auto.
Not a long time ago, it was discovered that Google Maps launched in the dark mode by default on Android Auto, therefore ignoring the user settings and other data such as the current position of the headlights. Using Google Maps with the dark mode during daytime is obviously pretty difficult, especially in direct sunlight, so it’s easy to see why people have been trying all kinds of workarounds in the last few weeks. Fortunately, Google has apparently become aware of this problem quite fast, and while it has remained tight-lipped on everything, it shipped a fix in the latest stable build of Google Maps.
It’s hard to say if Google Maps, Android Auto, or Google Assistant is the culprit this time, but I’ve seen users claiming that everything works properly with other navigation apps. This seems to suggest that Google Maps is the one to blame, but once again, Google is the one that should look into the problem and figure out what’s happening.
Fortunately, a workaround does exist this time, as disabling the satellite mode altogether does the trick and lets you use Google Maps in the default mode. It goes without saying it’s not the most convenient workaround, but with Google not saying a single word about a potential fix, this is pretty much the only option unless you’re ready to switch to Waze. Also a few weeks back, Android Auto users came across another problem with Google Maps, this time blocking the navigation from starting when the phone is locked. Google Assistant appears to understand the voice command correctly, but when it attempts to launch Google Maps and set up the navigation, the whole thing fails.
At the end of the day, what seems to be pushing some users from Google Maps to Waze is not only the plethora of bugs that are hitting the world’s number one mobile navigation app these days but also Google’s Apple-inspired secrecy. Without the search giant acknowledging bugs and promising fixes, users are left all alone in their struggles with Google Maps bugs, and more often than not, giving up on the app entirely is pretty much the most convenient way to go.