seatgraham

Active Member
Feb 14, 2012
525
79
Hello all

When I connected my iPhone to my 2019 Leon Cupra ST today, the car behaved as if it was seeing a new device. It showed a different circular-style menu instead of the usual grid, and then dropped into the setup wizard. After re‑pairing Bluetooth everything worked again, although disconnecting CarPlay caused Bluetooth to drop once more.

My phone later reported that it had updated its software, even though I hadn’t manually installed a new iOS version.

Has anyone else seen this? I’m wondering whether the infotainment had a momentary crash rather than any actual SEAT update.
It's still showing the different circular home screen, although stuff is working.
It lost all DAB station set up too...

Edit- I found the option in settings to change from Carousel menu to Grid. Still not sure why the system reset itself. Car is unlocking and starting fine.
 
Last edited:
The infotainment system isn’t capable of OTA updates
So maybe just the infotainment crashed?

It just seemed to lose temporary data such as stored radio presets, bluetooth pairing, and default settings such as menu options.
I noticed later it was an hour out because summer time was not ticked in the settings.
Since I reset stuff, it all seems to have been retained for now. Any ideas on why it went back to default settings - almost like a new unit?
 
Interestingly my 2018 FR 1.8 TSI DSG had a bit of a glitch on Monday. Time & date reset to 1.1.2013. I didn't have my phone with me so can't say if that went odd. Also my DAB stations stayed programmed. I stopped the car on my drive when I got back. Started again and date/time was then correct.
I'm set to update from GPS.
 
  • Like
Reactions: seatgraham
Possibly the hot weather messing up the infotainment system. There was a bug in some of the firmware over the British summer time / winter time thingy. Once connection was lost with the GPS they reverted to the wrong time. Why dealers were instructed to turn the auto time off to stop that on mib2 standards making it an manual affair. You fumble with it, off and on plus a reboot to correct that if you keep it on automatic and the issue arrivex. Gives you an arrival time an hour out. Only occurred on the mib2 standard units and possibly specific firmware releases. Had it a few time on our Arona. Comes out the garage on the wrong time since its lost GPS.

May be those pesky Russians jamming GPS these days causing issues on the GPS fault the cars were shipped with. Could be the one above. The latter mib2 standard units pick up a wide range of GPS providers from American, Russian and China. So the inter working of those could lead to issues. Not sure if they implemented the Galileo system in those. Mib2 high, least mine has a more limited access. America and Russia. Have tried restricting it in the past and playing with the constellation it was using.

Graham, I'd put yours down to a hot weather bug.
 
Possibly the hot weather messing up the infotainment system. There was a bug in some of the firmware over the British summer time / winter time thingy. Once connection was lost with the GPS they reverted to the wrong time. Why dealers were instructed to turn the auto time off to stop that on mib2 standards making it an manual affair. You fumble with it, off and on plus a reboot to correct that if you keep it on automatic and the issue arrivex. Gives you an arrival time an hour out. Only occurred on the mib2 standard units and possibly specific firmware releases. Had it a few time on our Arona. Comes out the garage on the wrong time since its lost GPS.

May be those pesky Russians jamming GPS these days causing issues on the GPS fault the cars were shipped with. Could be the one above. The latter mib2 standard units pick up a wide range of GPS providers from American, Russian and China. So the inter working of those could lead to issues. Not sure if they implemented the Galileo system in those. Mib2 high, least mine has a more limited access. America and Russia. Have tried restricting it in the past and playing with the constellation it was using.

Graham, I'd put yours down to a hot weather bug.
Thanks Tell. I'll put it down to the weather. Since I added DAB presets manually and reconnected to Bluetooth, I haven't spotted any glitches since.
The menu change has stuck too, so hopefully a one-off!
 
  • Like
Reactions: Tell
I should have mentioned the issue I had here:


Although trying to find my post and solution I found many posts across the net of rebooting mib2 standards. :eek: The issue I had was an over sized album art graphics somebody had embedded on a music file. You have this thing called memory over flow in programming where the code doesn't stay where its suppose to but writes into areas there it isn't suppose to since the program and operating system are pretty basic. Basically it zaps the system. Thats what this music file was doing.

I wonder whether you might have had something similar. A call to the program and off it does messing stuff up.

The example above could be repeated. Any other music file except that one. The IT help desk wasnt totally bemused at home with the partner. I normally produce music files from CDs using EAC and putting one file called cover.jpg in each folder no more than 512x512 not embedded in the mp3 file, use FLAC in anycase. SeatCupra board way of doing it that I learnt (other limits as well per the infotainment manual, number of files and directories). This one I'd handed over from one A.N.Other. Would have been some vinyl record that a hobbyist had added a scanned in cover of plus 1,000 x 1,000 or something. Deleted that embedded cover using the program mentioned in the link and all was fine.

Might have been something similar that the ropey program that behaves nearly 100% of the time (the infotainment system) went off on one or the hot weather 🔥. If it wasn't an other sized music file, it could have been some call to the program of plugging in the iPhone which sent it off on one of zapping the internal memory.

When the issue happened in the Arona I thought the infotainment system bad failed or the map card was corrupted. But no.