Jorgeminator

Let's hope they answer and you get it fixed. No reboots for me after upgrading to 1941. I still have to visit the dealer for the camera unit update (48S5) but that can wait until winter since it appears only when using the steering wheel heating.

That works only for Maps/Waze, and I think he's well aware of that already.

You need to go to the developer options in Android Auto. Not the Android system settings.

Since upgrading from 1889 to 1941, I can't shake the feeling that the DSG behavior has changed, I just don't know how that would be rational since common sense tells me there should be nothing connecting the gearbox to the infotainment software. I usually blame barely noticeable differences on placebo, but this is more than that. On 1889, at the beginning of the drive with a cold engine/gearbox, the gearbox would many times judder in 1st before shifting to 2nd, like dropping/easing the clutch rapidly at a pace of 5 Hz or something. The judder was most pronounced at half-throttle accelerations from traffic lights etc. Once warmed up there were no issues. With 1941 however, I haven't noticed it juddering like that yet, and the shifts going from 2nd->3rd and 3rd->4th feel a bit smoother in general. Has anyone else noticed anything similar? I can't find a logical explanation...

Only if you subscribe to the Connect service.

That's precisely what mine said. Installed fine today after being left alone for the night. I couldn't care less about the in-car manual, but the notification popping up at every start annoyed me.

Someone at the factory will be scratching their head wondering about the sudden surge of 1941 updated cars connecting to the servers 😁

Yes, you can go straight from 1896 to 1941. Ask @varooom for the link.

The manuals should install once it's made a deep cycle, it will fail each time if you just step out of the car for a few minutes. I learned that myself during the last two days. Let it sit overnight and try again tomorrow. Is it giving you the code saying "ERR_1601_DM_IN"?

A battery charger is great as an additional layer of protection, better safe than sorry. That applies especially to those with Start-Stop enabled, since I imagine their batteries will have a lower SOC on average. I always turn off Start-Stop, but I still connected a 4 amp charger as a precaution. @varooom Two drives after the update everything still seems perfect. The manual I mentioned was successfully installed today, I guess it did indeed need the deep cycle. The system feels just a tad snappier overall (less animation lag I feel), which could be placebo.

I'll add the Kingston DataTraveler 70 128GB to the list of working ones. Got it for 11€, preformatted to FAT32 out of the box. Quite a bargain if you can live with the slow random iops and write speed.

Might be a stupid question, but is the adapter properly seated in the USB-C port? I've had a couple of instances where the cable I use for Android Auto wasn't all the way in and AA would either not work at all or just sporadically. Needs a good push downwards.

I also got that update immediately after upgrading to 1941 by myself. Thanks @varooom! The update was successful and the reboots should be gone now. Now there's only one small annoyance with an update of the manuals failing. I can remember having the same problem before and the manual was then successfully installed a couple days later, I hope that's the case now as well. Looking at @djmartzian's post above, there's a fix for the manual, so maybe it just needs a full deep sleep cycle.

Since everyone is reporting success, I'll go ahead and ask for the link as well, @varooom. I won't bother with the dealer 😃

Here's 2065556/10. Changes from revision 9 in amber.

If it's indeed coming from the transmission, there's a problem. I've never heard that sound on mine.

Do people never ask follow-up questions? If the dealer said it's normal then he should be able to explain WHY it's normal and what's causing it. To me it sounds like a heat shield or something rattling underneath the car.

Forgot to turn off Bluetooth before getting into the car today, so the phone connected briefly to the car before I turned it off. Had two reboots in quick succession before it settled down. No reboots on my way back when Bluetooth was off.

Flight mode usually does not disable Bluetooth nor WiFi, that's why... It's basically just a toggle for the cellular radio.

This. On Monday I had the system reboot three times during a 10 minute drive. Since then, I've kept Bluetooth disabled on my phone when going close to and being in the car. No reboots since. EDIT: I had wireless Android Auto disabled while the reboots happened, so the problem is likely separate from AA.

That only applies for the navigation updates. You still get bug fixes and system updates without a subscription.

Indeed. Yesterday, I went to the settings menu and the moment I touched the WiFi menu, it registered the touch, the WiFi bar turned green and the whole system froze then rebooted.

No... The white indication has nothing to do with the sensor being dirty or otherwise impaired. Apparently this needs some clarification: Appears at most startups and goes away within 30 seconds. The front assist system is calibrating its detection and intervention points by scanning the area in front of the car. This is what pops up when the sensor is dirty and front assist becomes unavailable.

This sounds like just another case of PEBKAC. Where does it fail? Is it only the one-click apps not working? Unfortunately, a lot more information is needed to take your advice seriously. Most people have zero issues with OBDeleven. Have you tried clearing the app cache and doing a full scan of the car afterwards?

Do you get the amber warning light for the front assist or just the white one? The white symbol is completely normal while it calibrates the sensor during the first few metres of driving.