One of most useful features of Android Auto is the integration with third party apps. A large subset of popular apps can be accessed directly from Android Auto interface; no manual configuration is needed.

While driving, users can accomplish a number of tasks via voice commands. Sending replies via messaging apps, such as WhatsApp or Telegram is one of them.

Unfortunately, that particular feature is broken for a while for multiple users. Call it a coincidence: for most of them it actually started after upgrading to Android 9 Pie.

The exact syndrome of the bug has been described by an user in Google User Community:

When I say “Ok Google, WhatsApp message to <CONTACT>”, it replies, as it is supposed to with “What’s your message?” I dictate the message and wait for Google to re-read it to me and ask, if I want to send it or change it. I answer “send” and Google acknowledges it with “Message sent”.

But: The message will not be send. When I disconnect my phone and check my WhatsApp or Telegram app on the phone, I can see that no message has been sent.

Apparently other messaging apps, e.g. Hangouts or SMS are not affected.

It works well with Hangouts and SMS. Just WhatsApp and Telegram have this problem. It worked before the official release of Android 9.

Some users posted about the same issue on other platforms as well:

Sending text messages stopped working, despite AA saying "Message sent" (Pixel 2 XL, Android P) from AndroidAuto

WhatsApp messages not sending... from AndroidAuto

Factory resetting, upgrading the Android Auto and the affected apps to latest version or even a clean flash via fastboot did not help to resolve the glitch. However, the same configuration was reportedly working without any hiccups on Android 8.1 Oreo or Pie beta.

The bug is not limited to Google Pixel phones, as users experienced the same scenario on OnePlus or Huawei phones running Android Pie.

Also same problem for me on my brand new Oneplus 6T
This appears to be an Android Pie problem because my old Samsung S7 didn’t had this problem

(Source)

I tried on mine (P20 Pro), but still got the same issue

(Source)

The issue was quickly noticed and forwarded to the Android Auto team back in August 2018.

Hey Mario,

Thanks for the detailed feedback. We’ll forward this to the rest of the team. We’ll report back if we have more information to share.

(Source)

In December, someone from Android Team responded. They rolled out a new update, which should fix some cases. But they still needed more feedback from the users.

For the issue with replying to a message, our team rolled out a fix. Please let us know following info if you still experience the issue.

For the issue with starting a message, we are investigating with the Assistant team to address the issue, and it may need messaging app side update as well. We will keep you posted on this thread.

According to some users, the built-in battery saving mechanism of Android Pie aka the ‘Adaptive Battery‘ is behind all these shenanigans.

Now I did a change. Under android-setting – Akku – app start – whatsapp I turned the counter to “automatisch verwalten”.

Now I am able to start chats. Yippieh! 🙂

Is it possible, that the issue depends on the akku-setting? Perhaps android Auto isn’t able to wake whatsapp?

Could anyone of you try out a change in the settings?

(Source)

Although the solution was not foolproof.

I changed the settings accordingly on Pixel 3. Since then it worked a few times. Other times it didn’t work.
So unfortunately it’s not that easy.

(Source)

In February 2019, a Google Community Specialist has claimed that “Google Assistant team is actively working with partners to resolve this issue”.

android_auto_wa_tg_working_with_partners

For end users, it would be better to stick with old software if everything works with it.

I can’t try that as my PIXEL 2 XL has a defective Proximity Sensor and is currently in repair.
Now I have an old Samsung SM-A310F from 2016. This works fine, by the way with all the functions I want.

I opened this ticket in August 2018. That is a full 6 month now.

I am sure my next phone won’t be a Google Pixel….

(Source)

If it ain’t broke, don’t fix it.

PiunikaWeb is a unique initiative that mainly focuses on investigative journalism. This means we do a lot of hard work to come up with news stories that are either ‘exclusive,’ ‘breaking,’ or ‘curated’ in nature. Perhaps that’s the reason our work has been picked by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and more. Do take a tour of our website to get a feel of our work. And if you like what we do, stay connected with us on Twitter (@PiunikaWeb) and other social media channels to receive timely updates on stories we publish.

Kingshuk De
896 Posts

I came from a mixed background of Statistics and Computer Science. My research domains included embedded computer systems, mobile computing and delay tolerant networks in post-disaster scenarios. Apart from tinkering with gadgets or building hackintosh, I like to hop on various subreddits and forums like MyDigitalLife and XDA.

Next article View Article

Android Auto blank screen Google Maps issue & white bar on display top problem officially confirmed

Google's in-car infotainment system Android Auto (AA) is designed to make significant features from one's phone accessible through car's head unit on dashboard. All you need...
Apr 30, 2019 6 Min Read