The shape of things to come?
SiriusXM radio service pushed out an update that expected the infotainment system to be at version x.5. Or whatever. If it wasn't, it rolled back. And therein's the rub. Sirius was unable to revert to its former state, so it tried to download its newest image. Which wasn't compatible with the current state of the infotainment system. Reboot the infotainment system, rinse, repeat.
For some Audi owners, this went on for MONTHS.
I would be seriously pissed if this were to happen to me! Now, my Subaru is 10 years old, and I replaced the radio with a newer Kenwood to get some additional functionality out of Apple's Car Play, and I'm glad I did it. But if I had a newer car with a touchscreen, and it got borked like this? WOW. Very unhappy camper!
The problem was that there are people with car that, for whatever reason, were not running the latest version of their car's infotainment OS. Maybe they had a bad antenna, who knows. Then this APP update comes along and blows everything up. Once again, bad programming that was unable to fail safe and properly revert back to its previous state. I don't know anything about how these infotainment systems are programmed, but you'd think the first thing you'd do when pushing an update would be to read what version is out there - which you can presume is working properly - and write that version identifier off to a safe memory space that won't be overwritten. If your update fails, reload THAT saved version! Then figure out what happened.
*sigh*
https://www.thedrive.com/news/a-siriusxm-update-sent-some-audi-screens-into-a-forced-reboot-loop-for-months
https://tech.slashdot.org/story/25/10/23/003245/a-siriusxm-update-sent-some-audi-screens-into-a-forced-reboot-loop-for-months
SiriusXM radio service pushed out an update that expected the infotainment system to be at version x.5. Or whatever. If it wasn't, it rolled back. And therein's the rub. Sirius was unable to revert to its former state, so it tried to download its newest image. Which wasn't compatible with the current state of the infotainment system. Reboot the infotainment system, rinse, repeat.
For some Audi owners, this went on for MONTHS.
I would be seriously pissed if this were to happen to me! Now, my Subaru is 10 years old, and I replaced the radio with a newer Kenwood to get some additional functionality out of Apple's Car Play, and I'm glad I did it. But if I had a newer car with a touchscreen, and it got borked like this? WOW. Very unhappy camper!
The problem was that there are people with car that, for whatever reason, were not running the latest version of their car's infotainment OS. Maybe they had a bad antenna, who knows. Then this APP update comes along and blows everything up. Once again, bad programming that was unable to fail safe and properly revert back to its previous state. I don't know anything about how these infotainment systems are programmed, but you'd think the first thing you'd do when pushing an update would be to read what version is out there - which you can presume is working properly - and write that version identifier off to a safe memory space that won't be overwritten. If your update fails, reload THAT saved version! Then figure out what happened.
*sigh*
https://www.thedrive.com/news/a-siriusxm-update-sent-some-audi-screens-into-a-forced-reboot-loop-for-months
https://tech.slashdot.org/story/25/10/23/003245/a-siriusxm-update-sent-some-audi-screens-into-a-forced-reboot-loop-for-months