ou'll find similar statements on Leon 4 and
Formentor threads. I read one today
. I believe the software codes are interchangeable on the mib3 so whatever is said over there translates to what you have on your mib3.
Formentor thread here:
Hi everyone I took delivery of my
formentor vz2 in petroleum blue a month ago. I have had about six or seven problems with the infotainment screen in that short time. Most of the problems are around changing users. This really seems to be the screens biggest
problem. Sometimes it’s seem less...
www.seatcupra.net
I did elicit what the updates were for, here:
the infotainment has just said it needs an update . so it set if off and waited for bit but in the end i locked the car and came inside does it carry on in background or wait till i am in the car again? due to lockdown i wont be doing many miles .
www.seatcupra.net
So you could check yours against the release codes. You cant go above 16xx to 17xx. But you can get a better version as currently posted from your dealer if they apply an update.
16xx series doesnt have Android Auto wireless... that came in, in 17 series. This is why some people have it and others don't. 16xx without Android Auto, 17xx and 18xx with AA. East Yorkshire retrofit hope to be able to do that eg. Shift people to the higher "train"... although that's not a service they are currently offering.
There is an 18xx series which is above 17xx and you might be able to get to that if on 17xx.
Those fault lists came from "TPI" so dealers do know if they looked it up.
Do a cut and paste of
@Antera post since its so good... You might not have all the systems it's controlling in the car but blank screens do come up in people's posts across the MQB Evo platform here...
The post in question:
For 16Xx:
Institutions:
• The air conditioning controls on the radio navigation system screen are not displayed
displayed.
• Only with system language Danish:
− The text “SmartClimate” in the air conditioning menu is missing.
Display:
• Sometimes the radio navigation system switches itself off and on again (reset).
The screen of the radio navigation system remains black after switching on.
• The text message is continuously displayed on the screen of the radio navigation system:
− “Loading settings” is displayed, this means that the radio navigation system can no longer be used
served.
and/or
− “Radio/media not available at this time”
• Sometimes the radio navigation system shortcuts do not work.
• The image from the rear view camera is too dark.
audio:
• Sometimes the sound from the radio navigation system does not work.
• Sometimes a second language can be heard during the spoken navigation.
Navigation:
• The navigation database will be cleared automatically.
• Sometimes the navigation map is not displayed on the AID (Active Info display).
• When entering destinations via voice control, the navigation destination is not found/incorrect
recognized.
• The spoken display of the navigation is (sometimes) not intelligible.
• The navigation voice output is given in a language other than the one selected (country-specific).
• When entering the destination via voice command, the radio navigation system performs a reset automatically.
We Connect (online services):
• Sometimes the online search function “Alexa” does not work.
• If Apple Carplay is started via Bluetooth, the screen of the display and control element turns black.
• Creating a master user is not possible.
Driver assistance systems:
• After engaging reverse gear, the rear view camera image does not appear on the
screen of the display and operating element (screen remains black).
• The OPS (Optical Parking System):
− sometimes doesn't work.
− is optically shifted.
• Sometimes the tire pressure monitoring system button works on the display and
control element is not.
FOR 17XX:
Institutions:
• The mood lighting cannot be set in the menu of the radio navigation system.
Display:
• The displays in the Car menu are not correct.
audio:
• The sound settings of the radio navigation system are not saved.
• The audio playback via Bluetooth is interrupted every time.
• The length of the music title being played in media playback is not displayed correctly.
Navigation:
• The vehicle position in the radio navigation system is not displayed correctly.
We Connect (online services):
• Creating a master user is not possible.
----
Antera's post above says
16XX kan go to 1682
NOT TO 17XX or 18XX
17XX en 18XX can go to 1803
Assuming I haven't got the wrong end of the stick you should be asking your chief tech guy about 1682 if on 16xx and 1803 if on 17xx
. Probably putting the cat amongs the pigeons. They will probably say we don't do that on the
Ateca 2020 facelift... but suspect not. The mib3 firmware must be common across the brand as it is on mib2 high. You don't have different mib2 high releases by model within the Seat / Cupra brand. It will be the same for Mib3. Updated software is rolled out on new cars in the production life but unless you chase up for an update you won't be offered one free unless it's judged you really need it. That judgement might not be always right.
I don't have mib3.... I just read the posts
.
@dan555 on the Leon 4 thread knows his way around the screens and issues which I guess will be common although again the unit isn't addressing all the same systems.
The other thing is when it goes wrong, grab your camera phone and make a video of the fix to show to the chief tech guy as evidence. Concentrates minds. They should then run a
coding check and upgrade the firmware if you are not on the latest.
You are fortunate with the facelifted
Ateca you just got the mib3 issues not the more extended ones related to the re working of the systems on the MQB Evo platform. On all of this, firmware in systems should be updated if it isn't a hardware issue. Where you are reliant on good support from your dealer that knows their stuff.
Lastly just in case it is a boot up issue in the mib3 you can reboot it by the traditional long press on the power button until you see the logo welcome screen come up again... You just hang onto that button. You shouldn't need to do that all of the time, if so it likely requires a firmware update, known bug or not if it is not on the most recent firmware. The reboot trick you apply on mib when you get the odd issue... only had to do that on a mib2 standard once when the screen display moved by 1/2" off screen, it fixed it.
. At this rate I'll get a Tesla or of a Chinese MG when I go EV 
