Comment by rglover

Comment by rglover 9 hours ago

7 replies

I can't for the life of me understand why infotainment systems knock so many engineers for a loop. Is there a particular reason (industry/domain-specific) beyond just low-quality software development?

My Mazda 3 (2018) just had a class action lawsuit for its infotainment system which, completely at random after years of normal operation, starts clicking on menu items and scrolling about the settings (only to stop and not do it again for a couple of months). It can get so bad you just have to disconnect any devices and drive in silence/with the AM/FM radio.

rangestransform 2 hours ago

it's the consequence of not vertically integrating, having 20000 different ECUs each for a specific purpose and trying to nickel-and-dime suppliers on all of them, and the lack of urgency that traditional manufacturers and tier-1 suppliers have for adopting modern software development practices

jlokier 5 hours ago

I recently did some testing of Bluetooth connecting an Android phone to a reasonably new Mercedes. Being a "luxury" brand, you'd think the Mercedes would have good infotainment software, but I found at least 5 bugs in the GUI in about 1 hour of testing, and I wasn't particularly looking for bugs, just testing what I thought would be the happy paths for Bluetooth connection. The Android phone, on the other hand, did its job flawlessly.

I know software and embedded systems well enough to know all of the issues I found were preventable, if anyone cared.

The car seems well built in many other respects. It doesn't look like the problem is engineering ability.

(See also: Set-top box GUIs that are painfully slow to render menus, scroll, search etc. on hardware that I know can render 10-100x faster when programmed to.)

  • ryandrake 2 hours ago

    As you alluded to, the answer is they don't care. Car companies look at software like it's any other line item on the BOM. Like a bolt or a gasket: Source it as cheaply as possible and spoon it onto the product somewhere on the assembly line. I see fit-and-polish mistakes all the time in car infotainment. Text that can't handle unicode, icons that are misaligned by 1 or more pixels, connections dropping and coming back, audio mixing problems, things drawing outside their "windows." Nobody cares--they get to the drop dead date when the software needs to be on the assembly line, hand it over, and start flashing devices.

horns4lyfe an hour ago

They’re being cheap. None of it is vertically integrated and it’s all outsourced to the cheapest third world contractor they can find.

sleepybrett 9 hours ago

I worked at a company that did software for these connected infotainment system. They cost cut those things to the bone, minimal ram, minimal cpu, shit screens. Even in the high end models.

Gotta remember that the car radio has always been a cheap gimme.

  • CamperBob2 2 hours ago

    Gotta remember that the car radio has always been a cheap gimme.

    Not really. Some of the hardware that you could get in the 1950s-1970s timeframe was great. Heavy chrome knobs and bezels, permeability-tuned front ends with separate RF stages... electromechanical mechanisms that seemed like witchcraft when I took them apart as a kid, and would still be cool to play with today.

catigula 9 hours ago

You get a new device every year and teams of professionals are constantly churning updates for it.

With cars, you don't get to get a new device, it has to be consistent and keep working and you had better make it all work with a skeleton crew.