And yet, this isn’t necessarily the case, and a glitch reported on Google’s forums earlier this week is the living proof in this regard.
While the whole thing doesn’t seem to be too widespread, and thank heaven for this, someone reports that Waze stops working only a few meters after launching the app and starting driving. In other words, they plug in the smartphone in the car, Android Auto shows up on the head unit, the app is started and then Waze runs, and approximately 100 meters later, the bug occurs. Waze stops working all of a sudden, and it’s believed it no longer receives GPS data.
On the other hand, Google Maps works just fine, and this means the problem doesn’t affect the phone itself, since GPS information is still available, but Waze and/or Android Auto.
The good news is a member of the Android Auto team has already responded in the linked thread and the problem is now being investigated by the dev group. But on the other hand, this obviously can’t be considered a guarantee a fix would be released, especially because at this point, the whole thing seems to be an isolated problem.
Similar issues have been around for a while, but in almost all cases, the GPS struggles were caused by the phone, which means other apps were broken down too. The glitch is different this time, so it’ll be interesting to see if others are also affected and how fast a fix is supposed to land.