SkOmk4

Check out the first several posts of this topic:

Those 21(+/-1) seconds from Start to Audio playing is an eternity... But it also depends on the Audio source - if it's Phone or USB you should also add the time needed by the MiB to access that source. I found that it may vary A LOT between different engine starts. Radio should be the "benchmark" for such time comparisons. Do you reset the system once in a while? Usually it becomes a bit more responsive after reset.

I'm still trying to understand what's the car the OP has problems with... (probably I'm missing something)

Ok, that was actually my first question after reading your first post: Have you tried with a different phone? Check if your AA is up-to-date... Over the past 10 days, I've received 2 AA updates (on Android 14); 1st update made AA slightly unresponsive, 2nd one kind of fixed the issue.

This version of VAG PHEV is only able to charge at 3 kW max, and with the "reduced charging" option activated it will even go down to 1 kW. Indeed, the user should check the socket (and circuit) power rating, but without grounding it's a no-go...

That must be the reason. AFAIK the "home charger" needs a functional grounding circuit in order to work.

I have the very same engine and transmission on Formentor PHEV, and never had the feeling that the car goes into higher revs than what I was asking via the accelerator. It happened a few times that it went to higher revs than I was expecting, but it was exclusively my fault: I was in S and I was downshifting (manually); once I resumed the acceleration, I wasn't paying attention that the car stays in M. However, you can easily avoid the high revs using the paddle shifter - I do that sometimes. I only feel that for the "crawling" setting - I find it to be quite jerky sometimes, depending on traffic. When you're stuck in crowded traffic at very low pace, foot not even on the accelerator and the car barely moving, sometimes there's some "clunk-clunk" noise coming from the transmission (or the e-motor) that you can also feel in the car-body. I think that's caused by the car quickly oscillating between regen and traction - as it's unsure what to do at that slow moving pace. That could be surely optimized; I sometimes "force" the gearbox into M1 to avoid that behavior...

Ok, since it's available for Golf 8 for some time and I have it on my Formentor for about 2 months now, I was assuming it was also released for Octavia - though I never checked...

First of all, you need to specify what "latest software" you have. As far as I know 1969 is also released for Skoda too, so 1941 is no longer "the latest". Secondly,the restart of the Android Auto alone is sometimes related to the phone-infotainment connection problems or instability; but it's hard to say if it is exclusively the fault of the infotainment. I remember that on my Skoda, after the update to 1941, my AA was also restarting apparently) randomly while connected via cable. After several such occurrences I noticed a pattern: the AA restart was only happening when the phone battery was reaching 100% SoC (S21 Ultra). The fix I found was to unplug the cable before phone reached 100%, it would automatically go on wireless AA, and it was stable. In this case I blame the phone, not the MiB.

I was also looking forward to see what they've changed on the PHEV, but not a word about it. If you really need the bigger battery/range and you also need the volume of an estate, have a look at the new Superb - it has the new PHEV configuration (1.5 TSI) with the bigger battery and faster charging option, and IIRC two power versions. Sure, it's a bigger class, different price...

https://updateportal.skoda-auto.com/en-US

Here we go again... new Samsung flagship series => new problems (@VW, Skoda, Seat): https://www.sammobile.com/news/android-auto-issues-galaxy-s24-seat-skoda-volkswagen/

So, just trying to better understand: before this "new" MySkoda App you were using the MySkoda Essentials? And all the features for the PHEV (e.g. charging, pre-heating) were also available? I have the same (very annoying) bug as you, but on the Cupra Connect App - most likely the very same rationale behind both apps... When I'm trying to charge the last few percent of the battery (up to 100%) in the morning before I leave, the App is failing. It' either saying the car is "Not connected", or in most cases "something has gone wrong" - see picture. What's most annoying is that each time the charging request returns an error message, I am able to start the pre-heating - which means that Car-Server-App-and-return communication goes well. So what's the "secret" problem behind the charging failure? p.s. in the picture the HV battery is at 99%, so that might be used as an argument for the charging not starting. However, in most cases I'm trying to charge from 95 or 90% and it's always the same failure, and always successful pre-heating...

The TOTAL battery capacity is 13 kWh, but the "usable" one is 10 or 10.5 kWh. I never saw more than 11 kWh delivered by the charging station for a 0-100% charge (total indicated by the charging App), not even on cold weather when the charging efficiency is a bit lower.

Indeed, while in hybrid mode, even when the ICE is running there's some use of the HV battery - it will sometimes give some electric support for the acceleration. That happens when you keep the default settings of the hybrid drive. However, depending on your battery needs along the way, you can choose to preserve a certain amount of battery (or even charge while driving) for later use on your trip.