All replies

This is something brand new issue. Can you tell me if logging out from the native multi-line settings completely solves the problem? By that I mean if you log out from Multi-line settings and just receive text messages to your primary SIM Card in the native SMS app, does Android Auto works for those messages?

If your answer yes, then I would say DIGITS may not be the issue. Android Auto being unaware of DIGITS functionality (as it is T-Mobile specific), may not work properly.

If your answer is no, then that is something to look into further.

Well my answer might seem counter-intuitive but it may be true. Please post your findings and tag me so that we can sort this out.

I can answer for him. It's neither. The native and app works in Android auto because it is design to. T-Mobile digits app is not. T-Mobile needs to step up and get it working in Android auto as well as Apple CarPlay. It is important to have a phone/messaging app to work with those two standards. It could be as important as saving lives in some cases.

I have not yet. I'll do it tonight when I get home and can easily send myself some test messages via my Google Voice account.

BTW I'm actually more concerned about 1 than 2. If it is just when DIGITS is enabled, then the DIGITS functionality is broken and it limits the usefulness of it. Even if it is using RCS, it still register that a text message was received.

debjitjdv So I logged out of Multi Line Settings and it still didn't work with Android Auto. I suspect that the DIGITS functionality is still enabled on the line as the texts were appearing in the DIGITS app on my tablet still.

Well by default its all DIGITS. I dont think you can disable it. All numbers are by default upgraded to DIGITS. Now this is something I cannot even test at my end. tmo_chrisevanmf can you shed some light on this?

So this is a bit of an odd one as there is no reason is should not be working anymore. The DIGITS app however will not integrate with Android Auto as it is not looking for a 3rd party app such as DIGITS when it receiving information from your phone. From what I have read, the voice services such as voice calls and sms are still handled via Bluetooth. Is receiving SMS the only issue you are having or are you also unable to send SMS and make/receive calls?

I did make one discovery today. I was driving back home today and I received a text from T-Mobile about a new area code in my area (Seattle) and the message came up with a notification in Android Auto.

When I look at the message details in the Samsung client, I see the following:

When I look at other messages, I see this:

Note how the T-Mobile message says that the type is "Text Message" and the other message says "Chat". The T-Mobile one was probably sent using SMS while for the other messages T-Mobile is using RCS. This is probably the same reason I see some of my text messages in Textra but not others. The ones which are sent as SMS appear in Textra. The ones which are sent via RCS don't. Android Auto most likely is only picking up the ones sent by SMS. This is a problem as DIGITS is primarily using RCS for text sending. It seems that the Samsung client should also be triggering the SMS received event for an RCS message.

I have the same issue, but it is new. I've had digits activated for several months and receiving texts on the native messaging app worked just fine. This problem where AA does see the incoming g texts just started in the last week or so.

I would like to chime in (found this while searching Google) - I have the exact same issue. And, I can say that the texts that do get notifications on Android Auto show up as "Text Message" under type, instead of "Chat". In fact, I had a duplicate message received - one came in as "Text Message" and one came in as "Chat". Only the "Text Message" fired off the notification.

Some Google Engineers were thinking that it may have to do with Samsung's chat app labeling messages it receives via RCS as Chats rather than Text Messages.

I've been on the T-Mobile Network since summer 2017. My (Brought over from ATT) S6 edge worked great with Android Auto. (Including receiving all SMS messages). I switched to a T-Mobile S7 a few days ago and I Android Auto will mostly miss SMSs messages (not all). The car's BT system will catch all(I get a notification from my car), but AA stays quiet. Even when I ask Google to read my messages, it says there are none. If I look at my phone I see unread SMS messages.

This isn't a solution for those of us actually using digits multiline as that won't work with Android messages. The reason that works is because you force all SMS and the issue, as I mentioned above is a known one for Android Auto, it won't handle RCS messages. As Google is a big RCS proponent this is truly absurd but it is a Google thing to fix, not a T-Mobile one.