Man, I’m glad Android Auto exists, I’m glad it’s finally appearing in more new cars with wireless connectivity (although MANY new cars still only have wireless carplay and wired Android), and I’m glad we’re finally getting the ability to open Google Maps on our phones while it’s also open on the car’s display.

But damn it still does some dumb shit.

I’ll just drop this one for now: I find it weird and dumb that Google Maps in Android Auto will let you send a progress share to a contact’s email address but not to their phone number as a text message with a link.

An email address might send a notification to somebody’s Google Maps app, but it’s certainly never happened on my partner’s iPhone. She just gets a link via email, and she is not the checking email sort — so I usually follow up with a text message telling her to check her email. 😑 (I wish she’d just get a Samsung…)

  • Takatakatakatakatak@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    2 years ago

    It seems like a lot of people have issues with the implementation in the cx-5. I suspect they have run too much cable between the deck and the USB port: a common cause of issues.

    As the years have rolled on, Android Auto has improved in leaps and bounds. Newer decks and vehicles don’t seem to suffer such issues. I use a Kenwood DMX820WS and a brand new phone and I don’t get any of those issues at all.

    My early experiences were much like yours.

    I really wish I’d waited another year to buy a deck with a wireless implementation.

    • Mike@lemmy.worldOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 years ago

      Yep. As a motoring journalist myself, I get to use wireless AA in a lot of new cars and it’s mostly fine now (if not perfect).