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.
Yep, current eCMP platform by stellantis e.g. runs Linux and containers per “application” (radio, nav, backup camera…) for their nav capable head unit. Those are made by Continental and are called NAC, current gen is WAVE4.
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.
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.
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?
Still requires overhead and a non-zero number of head units are built on, this may shock you, Android.
My experience has been that anything on QNX works fine, and anything else is hit or miss.
How do you find what platforms run on QNX? I’d prefer that on my car over other options.
You’d have to look it up for your make and model, but previous gen Hyundai Kia Genesis tend to run on QNX. Don’t know what the new gen runs on.
Apparently some head units even run Linux!
Yep, current eCMP platform by stellantis e.g. runs Linux and containers per “application” (radio, nav, backup camera…) for their nav capable head unit. Those are made by Continental and are called NAC, current gen is WAVE4.
Hyundai Mobis head units for Kia run on Android 11 from what I’ve seen. Unless they’ve changed to QNX
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.