One of Android Auto greatest highlights is its near integration with Google Assistant, but at the moment there seems to be an issue there. A “double beep” issue is recorded by many Android Auto users which sees Google Assistant not responding to failed commands.
With reports of this issue a thread on Google’s support forums has been rising over the past two months. Users of Android Auto note that either Google Assistant doesn’t open with a “double beep” sound when accessing Assistant, or the Assistant just doesn’t respond.
At this point, the more widespread of these two issues does not seem to be the “double beep” issue, but rather the fact that Google Assistant on Android Auto listens to commands but does not reply to them and does not execute the function requested.
In one reply, with Android Auto, Google recognizes the double beep issue, but the employee did not provide any fix. Users will have to wait until Google patches things up for now.
Unfortunately, the more frustrating issue Google hasn’t recognized is where Assistant on Android Auto is just not reply.
Many users–including a tipster at Android Police–have noted that Google’s “My Activity” page shows records of the assistant’s hearing and handling of their commands, but it doesn’t give an audible reply in the vehicle. Some commands, such as phone calls, seem to work for some users, but for many, the assistant is largely broken.
Whatever the cause of this issue, we hope that Google will be able to fix it sooner rather than later.
