SkOmk4

Before going to a dealership to pay for the upgrade to 1941 try the solution proposed by @Roman_K - switch to "Incognito mode" in User Settings: Otherwise, if it still doesn't fix the reboot problem, you can install 1941 by yourself. See the video posted yesterday on how to proceed.

I think the verdict should come after longer testing... That's because from my point of view there were two different behaviors of the infotainment: - one is restarting (sometimes in a loop of several/or many restarts) some time later after the start of the car. This one I don't recall ever happening to me, and it's the behavior described in the first few pages of this topic - let's call it the original fault; - the other one is the restart that occurs immediately after starting the engine (within 1-2 minutes), and it's usually a single reboot. This is the one that I also have, and it started manifesting itself after an OTA sometime in the second half of April. Between Oct.'22 an Apr.'23 I never had any reboot out of the blue - so that's a faulty update. My point is that for the second type of error, one might expect a single reboot (at the beginning of the trip) no-matter how long the trip is - assuming the car was not turned off during the trip. Two weekends ago I had a "record" of 10 consecutive trips (few of those were several hours long each) without infotainment reboot -> and I thought the solution was found: phone Wifi&BT turned Off. But the next weekend the reboot was back in the same conditions. Which type of reboot did you have on your car? Is it a 2023 Octavia and still you were experiencing infotainment reboot? ☹️

In my case it was crystal clear weather, no stress on the car (only crazy traffic), quasi-constant speed... So really hard to explain why that call would be initiated in such a context. AFAIK it's v.1941 that was mentioned on other forums to solve the infotainment restart problem. So if your RS-friend is on SW 1900, the problem is still there. Did he install on his own, or did he get the update at a dealership?

@Edela check the video I linked above - the guy with the Golf mk8 has H56, see minute 17m57s That's great news @Rainesh - it looks like there's some hope for all of us... Let's just hope that Skoda is not capable of releasing another OTA to crash an already functional/stable SW... (as it was the case for me at least)

A question for those of you brave enough to install the 1941 update: The update process - is it similar (or identical) to the one shown in the video below?

Today while driving for about half an hour and some 30 km, I suddenly realized the car was making a call!!! 😡 I was in heavy traffic, outside the city, AA was running Waze and Radio was on - when I noticed the Radio went Off. But I was so caught with people chaotically changing lanes in front of me that I didn't pay attention for a couple of seconds. When I checked the infotainment screen I had a nice surprise: "Breakdown Call" - it was ongoing, calling. I can't find a similar screen on the web to show you how it looked and I was not able to take a picture that quick. It was a full-screen call with some nice blue-ish picture as a background, with "Breakdown Call" as title, some text saying "Connecting..." to some service that I can't remember, and the red hang-up button at the bottom of the screen. Which I used to stop the call - since the car was fine. With the "Breakdown Call" stopped, the infotainment was back on the Home screen not on AA. I manually restarted AA an I realized that it actually disconnected, since Waze no longer knew my destination. Anyone else ever noticed a similar behavior? On a different note: there was no infotainment reboot.

Engine ON with Start-Stop OFF will be enough. I've done this on my previous car without any problems. It's true - the stress can be quite high through the process and during the several restarts of the system...

It's probably the sane and pragmatic approach... One of the main reasons for people buying brand-new cars is not that they love to spend a lot of money, but to have a hassle-free car at least for as long as the warranty extends. If the Skoda response to all those issues would be to take the faulty car and try to fix all the problems, while providing a courtesy car, some of the affected customers might accept the situation. (surely they don't have so many courtesy cars). But it's not the case... So yeah, going for another car seems reasonable as long as you do your homework properly and make sure you won't find other problems with a different producer.

Game Over!!! ☹️ This morning I had Wifi & BT Off on my phone while approaching the car. Started the engine an had an immediate reboot (accompanied by the message: "Maneuvering braking unavailable") 🙄 I moved the car for several meters while infotainment was rebooting (I was still in the underground parking), and it rebooted again several seconds after the first one. Therefore my first test is over... I embarked on a new adventure: testing with "not share my position" in User Settings, as @Roman_K suggested. So far I had 3 fresh engine starts today with this "undercover" user setting, while keeping the phone Wifi & BT ON, and there was no reboot. But as the previous test showed already, I won't trust a test with poor statistical significance.

The details they show are more or less relevant... Sometimes they just say "error fixes", other times you get more info. The pictures below are taken when the "update of death" arrived - the one that brought infotainment reboots at the start of the car (22nd of April)

Nice! How long have you been using the car without any reboots? (Sorry it sounds like a question at an AA meeting... "how long have you been sober???" 😂 ) Just asking to find out if it's a statistical effect, or if indeed it solves the problem. Mine was reboot free with the phone wifi-OFF, but it's testing over an entire weekend, for about 10 different drives - so statistical error ~30%... It's crazy when you think how many users encountered this problem (far more than those posting here), and how much time they must have spent surfing the web, looking for solutions, then testing those solutions on their cars, then reading some more, testing again... I wonder how many man-hours were ridiculously spent because of a faulty OTA update. I'm betting it's close to a year's work of a full-time employee. And the fault is probably something that Skoda might fix using a few SW-dev guys over a couple of days. So frustrating!!! It seems the fix is already out (not yet for Skoda) with v.1941, but should we expect receiving it OTA in the near future, or will it be an update requiring a service-trip?

You're right; I forgot to mention - I also unplugged the cable for that part of the test and there was no system reboot. But I was 10 or more minutes into the trip (after the engine start). I was wondering: is this infotainment restart occurring also for those using Apple CarPlay? I don't quite remember seeing such posts on this topic... I remember them having problems with Waze or GMaps displaying with strange colors or lines, even freezing, but no restarts...

As I was mentioning, I did try to see if the random reboots go away if I'm using AA with wifi & BTB off. (Just a reminder: in my case, the MiB reboot would occur immediately after the engine start - within the first 1-2 minutes) So as @Combi_NX5 mentioned, I turned off wifi and BT before approaching the car, started the engine and after that connected the phone via cable. The infotainment DIDN'T reboot in about 10 such tests over the weekend. Since I had several long trips, I took one step further and enabled the wifi on the phone while already being in AA for several minutes - an there was no restart! However, for each new trip I was approaching the car with wifi&BT off on the phone. Encouraged by the lack of MiB reboot, I also tried starting the car with phone wifi & BT ON - epic fail!!! In 2 out of 2 attempts the infotainment restarted... As @Combi_NX5 already indicated, the BT on the phone will be turned on after the cable is connected, and phone's BT will also connect to the car; but wifi stayed OFF on the phone, unless I decided to turn it ON during the trip. During all those tests I didn't touch the car's wifi and hotspot - it was always ON. To conclude, as Penguins of Madagascar were saying: "There's good news and bad news: the good news is we're landing! The bad news is we're crash-landing!" (scene at 1:20 in the link bellow for the original citation) And since the link is here - if any of you wants to know how I'm imagining the Skoda technicians are dealing with all the errors in MK4 - please have a look at the video between 0:45 and 1:20... ☹️ Later edit: King Julian seems to behave like the Skoda CEO 😉

This weekend I'll try the "no wireless" solution (if I'll remember to switch off BT&wifi when approaching the car). - the same test that @Combi_NX5 started... I'm just curious if the reboots will "magically" disappear.

I managed to take a picture of mine; not sure you're also interested in this one, since you mentioned version 1900 - which is not the case for me. Summary: car built @end of August '22, delivered end of Sept.'22 with SW 1896. I had several OTAs since, but the one around March or April this year made the infotainment reboot after the start of the car... Funny thing: I didn't have the key with me (I was parking my other car returning from work), but I decided to give it a try. So I opened the car via the Skoda App and tried to see if I can start the infotainment and furthermore the Engineering Menu. Surprise (at least for me): it works!!! @djmartzian once you get into the Engineering Menu (hold for about 3 seconds on the Menu button) you need to click "Software Update". I didn't take any picture, but it is the first option out of the three listed in that Menu. For those interested: check the video below - in order to access the Red Hidden Menu with the Software Train you need to click the first line (the one that the guy in the video is not clicking). The system will seem to reboot in some sort of "recovery mode" where you can choose to update or to see Software Info.

Actually, that might be a real thing... A guy from the dealership told me some time ago that one way to get rid of random restarts of the infotainment is to turn off all the wireless connections on the phone (bt &wifi) and use the cable. That was for the restarts occurring just after the engine start - as it is the case for my car. And a few minutes later after the car is started, one could use the wireless connection without infotainment restarting... I didn't have the time to test this hypothesis, and I didn't really trust the guy. That's because he mentioned as a second potential reason for the restarts, the presence of fingerprint grease on the power button of the infotainment. 🤨 That was a pill too hard to swallow for me. He insisted that cleaning the power button made the difference on his Cupra Formentor system that didn't restart on it's own afterwards - something I found very hard to believe. Probably there was some strange coincidence with a system update, or something else... BTW, I was wondering if the infotainment on other VAG cars (e.g. Formentor, Golf) has the same behavior with the random restarts, since it's basically the same system with different UI on top. I never had the curiosity to search their forums.

I don't have so much statistics as you guys, since mine isn't my daily drive, but as I posted before: my system was fine for several months, until one of the updates this spring was installed. Since then I'd say there's a 30-40% chance that the infotainment restarts right after the start of the engine. Yesterday I had a 100% record: 2 infotainment reboots for 2 engine starts. In some cases the infotainment reboot is accompanied by "Sound system error" on the dashboard; I don't remember seeing the "Error Park Distance" message.

The 1.6 is no longer offered, but you can still find a used one on Octavia 4. AFAIK the 1.6 had several technical issues (not sure if those were all addressed) - probably one of the reasons it's been discontinued. As owner of a 2.0 TDI (150hp) DSG, I can only: say go for it!!! Especially since you mentioned longer non-urban trips.

This weekend at a car show I was discussing with a Cupra country sales manager. Among other stuff I was asking why the PHEV's (of the VAG group in general) seem to be discontinued in Romania (e.g Octavia PHEV, Formentor PHEV, Golf GTE). He told me those were removed from the car-Configurators and orders were suspended for now, simply because there's an important components shortage for hybrids (not mild-hybrids, but the real ones). On a rather optimistic note, he was saying that they have high hopes they'll be able to accept PHEV orders before the end of this year.

yes, that's right. Why would you struggle with such a modification? Isn't if easier/faster to connect directly into the available positions of the Fuse-box? There you'll find both permanent and ignition-only power supply. On most dash cam's (if not all) you need both connections in order for the camera to know when to switch to parking mode and when to run continuously.

Indeed, 5 credits per day if I remember correctly, but this option was removed last summer.

You can read more about this "feature" (or bug) in the topic below. It only appears for a while when you change the info to be displayed on left or right side of the dash. Otherwise Waze directions will not normally show it the place of the clock (as your picture shows). What happened to me (described in the link) seems to have been a software bug - and it never happened again in the past 3-4 months...

After being used to sporadically get one or two errors (e.g. Lane Assist unavailable, Front Assist unavailable, Park Assist unavailable et al.) when starting the car in the beginning of the weekend, this weekend I noticed a new kind of behavior. The error was completely new - "Vehicle lightning" - and the warning light was on until I stopped the engine after several minutes. In all previous cases the errors that were showing up when starting the engine were vanishing in about 10-20 seconds. The error was gone when I restarted the engine, but had a new problem while exiting the parking place: I was parallel parked and had to reverse to get out - the camera image froze on the HU and the parking sensors beeping didn't change frequency as I was approaching the car behind me. So I stopped maneuvering waiting for the system to "wake up", immediately saw "Sound unavailable" on the screen for 1 second and then the HU restarted on it's own. Everything worked after that. After a ~200km trip the car was parked for ~3h. When I resumed the trip I had to reverse from the parking - same behavior: camera image frozen, HU rebooted... 😡

To add to the list of drivers that put the gearbox into Neutral at longer stops - I'm also doing that, but on the manual gearbox. And if there's a slight slope I'm usually using the handbrake, not only to relax the leg, but also because I hate bothering those behind me with the brake lights (especially in rainy weather). On the other hand, I keep the DSG in D/S at red-light and most of the time I'm using the Auto-hold while driving through urban traffic. (I know the brake lights will bother some of the rear drivers - I apologize, it's the system's fault, not mine). I also had a dual-clutch without Auto-hold (the Megane 4 GT EDC) and for longer stops I used to push the gear-lever to N and apply (electric) hand-brake when the road configuration required it.