As depicted by various leaks, also covered in our previous articles, Android Auto is in the beta testing stage of its next generation. While reportedly different users who even not undergoing updates are facing an issue. As Android Auto has snapped non-touchscreen rotary controls, the case especially happens with Google Maps.
While the controls in Android Auto are mostly functional towards touchscreens. But at the same time, the platform also supports vehicles that do not support a touchscreen. Therefore vehicles from Mazda and BMW, that subsequently opt for rotary controls, here in this spinning dial are given for navigation. Hence in order to navigate through the car that works both Onboard OS as well as Android Auto respectively.
Although, it’s a system that sometimes proves to be a little tricky to get the hang of. While it works rather well, as rotating a dial focuses in on a specific UI element. Also, in Mazda cars, whereby pushing the dial selects and scrolling over the side can skip between UI sections. Also, it usually works well, but there seems to be a bug as a result. Some issues came into highlight this week.
Moving further by this news, only a few users on Reddit have to resound that the latest Android Auto updates seem to be non-functional in rotary controls partially. Whereas those who got affected either have limited or no control over Android Auto using a rotary dial. However, the problem does not seems common to all users or car models. While at the same time it comparatively to be widespread. One user experiencing the problem on his Mazda vehicle and claims that Android Auto impact when Maps is the “larger UI element.”
Going back to an older version of Google Maps for Android solves the issue
People who got affected, soon realises that the issue seems to track back to Google Maps. In the event of a forced stop, the app unlocks rotary controls in the car for a time. While some also found that going back to an older version of Google Maps for Android. That comes with version number 11.28.7 also going to solve the issue as well. On the other hand, Android Auto app versions did not prove to be the central cause of problems reported on v8.3 and v8.5.
Google has its turn to respond to the problem. But we are quite assured that the same issue will be going to certainly launch sooner or later.
