• drekly@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    4
    ·
    9 months ago

    It’s more likely that auto manufacturers put the oldest shittest slowest chips in cars that crash constantly because they can’t handle any load at all.

    • andrew@lemmy.stuart.fun
      link
      fedilink
      English
      arrow-up
      9
      ·
      9 months ago

      Isn’t the whole point of android auto that it uses your phone and the display is just an external display when in that mode?

      • kingthrillgore@lemmy.ml
        link
        fedilink
        English
        arrow-up
        11
        ·
        9 months ago

        Still requires overhead and a non-zero number of head units are built on, this may shock you, Android.

      • Dave.@aussie.zone
        link
        fedilink
        English
        arrow-up
        4
        ·
        9 months ago

        I use android auto in numerous rental cars. Some head units are so slow to process taps or menu selections that it is pretty much unusable.

        The normal headunit UI is generally ok, so either there’s a whole lot of overhead for android auto, or some programmer simply dropped the base example implementation of it into the system and did zero work at optimising it.

        Personally, I’m betting that it’s the latter. “Supports Android Auto” box has been ticked on the feature sheet, send it.