[Update: Fixed] Moto X4 Android 8.1 update broke Android Auto compatibility, fix coming

Update (June 13):

Motorola has pushed out an update to fix the Android Auto compatibility glitch on Moto X4.

Update: The Moto X4 Android 8.1 update has apparently broken the USB connectivity in general, and Android Auto not working is just one of many consequences. See here and here.

Original story follows:

Of late, if your Android Auto head unit is refusing to recognize your Motorola Moto X4 smartphone, then you are not the only one trying to figure out what went wrong suddenly. There are many others reporting the same across different help forums, blaming the Android 8.1 update for breaking the device’s compatibility with AA.

Error: Connect a compatible device

Going by user reports, Moto X4 (both standard and Android One variants) are currently facing compatibility issues with Android Auto head units, wherein on plugging in the device (with the help of a USB), AA throws a notification stating connect a compatible device.

The problem is being widely reported. Not only is the official Android Auto User Community drenched (1,2,3,4,5,6,7) with complaints, the affected Moto X4 users are also chiming about the same on Project Fi (1,2,3,4) as well as Motorola/Lenovo help forums.

Even micro-blogging site Twitter portrays the same story (1,2,3,4).

Fix in works

Both Google and Motorola acknowledged the matter this past weekend. Some one from the Android Auto team (who is also a Community Specialist at the AA user community), said:

We’re currently investigating this issue.

And a senior motoagent (at Motorola/Lenovo help forum) updated those affected that a fix is being worked on which will roll out in a future update.

Our product team is working on a fix which will be included in a future update

Apparently, the problem lies at Motorola’s end, which they are working to fix. This may bring a breath of relief to those affected, but currently there’s no exact known time line for the problem to be cured. Meanwhile, the company suggested workaround is to disable the screen lock.

And like always, we are monitoring all possible spaces to catch hold of every development on the matter, and will update the story as and when the promised update gets live.

Stay connected with us on Twitter (@PiunikaWeb) to hear about all related developments as and when they occur