Every car forum has threads devoted to broken infotainment systems. As vehicles pile on the tech controlled through infotainment systems, it's inevitable that every automaker will get its time in the spotlight — or the courts — to deal with the innumerable traps hidden in ginormous amounts of code found in the average modern car. Now it's Mazda's turn, but only for certain Mazdas from the 2014 to 2017 model years, and only those in the Seattle area able to pick up National Public Radio station KUOW.
A piece in the Seattle Times explains that something in the HD Radio signal KUOW sends is nearly bricking the infotainment systems in these vehicles. The common thread is that after the inciting incident, the radio will only play KUOW. And, since the screen will only play the Mazda wake-up animation repeatedly, owners have lost access to their navigation, Bluetooth, reversing camera and vehicle information.
No one believes it's an NPR conspiracy. Yet. The Seattle Times spoke to a few owners, a couple of dealers, Mazda and Xperi, a company making the software HD radio runs on. Mazda fingered the culprit as the station transmitting image files without an extension, say for an album cover, that Mazda's media software tries and fails to process, with tragic results. Mazda didn't say why this issue is only happening on the model years at issue, nor why this specific software can't work around a file extension error, which have existed as long as there have been files.
The story is one of those that might make you shake your head and offer a tragic chuckle for the unfortunate, then look at your car outside and wonder, "How long until you do me like this?" The little snafus seem likelier every day, given that we weren't joking about the amount of software in today's cars. Way back in 2009, the Institute of Electrical and Electronics Engineers wrote, "It takes dozens of microprocessors running 100 million lines of code to get a premium car out of the driveway, and this software is only going to get more complex." That's about four times the amount of code needed to operate the Lockheed Martin F-35 Joint Strike Fighter, almost 70% more than all of the code that runs Facebook. This was before the all-out race for driver convenience features, vehicles becoming digital nodes and the industry's quest to catch up to consumer electronics software cycles. Imagine how many more lines have been compiled in 13 years, and how many more are to come (Level 3 autonomy, anyone?).
Before you do that, though, check out the Seattle Times story. And kudos to Mazda for stepping up take care of affected vehicles while everyone tries to figure out what's happening.
Not long after purchasing my first car with parking sensors, after a few delighted first days marveling at how they helped me park in the tightest of spots, I found myself in some situation where they were beeping incessantly, so I turned them off. A half-hour later, I listened for beeping that never came as I backed into a wall, bruising my ego and the bumper skin. In a New York Times op-ed over the weekend, psychiatrist Vatsal G. Thakkar tells a similar story in which he placed blind reliance on proximity sensors — in a car that didn't have them.
He cites the National Highway Traffic Safety Administration, who says, "Many drivers are not aware of the limitations" of driver-assist technologies, while one in five drivers have had an accident or near miss because they too fully relied on these systems.
Thakkar points out something we often say at Autoblog: Driver-assistance technologies can be useful, but they require increased attentiveness, not less. It's not even a trust-but-verify situation — if you have these technologies, don't trust. Ever. Do have a thorough understanding of how they work, how they can be fooled, and be prepared to override them at a second's notice.
One might ask: If I have to be so attentive operating these technologies, then why have them in the first place? Why not just ... be attentive? Good question. I think we all have a pretty good sense that the impetus for lane-keeping, adaptive cruise and various other systems, in part or in full, is driver distraction brought on primarily by smartphones and infotainment screens. Driver distraction is undoubtedly a big factor in our alarming trend of traffic fatalities. But as Thakkar asks, "Could technology designed to save us from our lapses in attention actually make us even less attentive?"
In his concise piece, Thakkar makes the case that over-reliance on technology can be blamed for recent Tesla crashes, medical errors and even the recent crashes of Boeing 737 Max 8 jetliners.
But his solution is one after our own hearts, and why we suggest you read his piece. The answer to all of the above is simple, engaging and beautiful — it's the manual transmission. When your brain and all four limbs are fully engaged in the driving experience, who needs beeps?