I dunno about frequent, but I get it periodically. Mostly when it's been in deep sleep for more than a day, but it has happened a few times when the car was just driven a couple of hours ago.
My service advisor says that the problem stems from the car too often going immediately into "deep sleep." For me it can happen after literally two minutes of driving the car. I would *welcome* this behavior if the car intelligently went to deep sleep after a day or two of non-use. In fact, I'd love the option to immediately put the car into deep sleep when I know it is being left for an extended period. But this is just annoying.
Bizarrely, the car still works sometimes even when the screen is black. I can flick the stalk to R or D and just start heading out. Screen eventually turns on while I'm driving. Since I can drive, it doesn't overly bother me.
Yeah, it does *overly* bother me still. I rely on that backup camera to exit my garage safely, as the rear glass is too high to see what's directly behind me. The backup camera display doesn't work while booting, the music doesn't work while booting, my LTE doesn't work while booting, I can't begin navigation while booting... and my seat doesn't change to my programmed positions while booting. So eventually, The the memory position DOES finally attempt, usually something remains positioned wrong. So I have to flick between my wife's setting any my setting to get it back into sync. It's a bit more than an annoyance for me. But yeah, at least the car can drive. Mostly (sometimes it won't go into gear either, however).
Many energy optimizing s/w variables at play including learning your usage behavior, settings of your power saving features etc.
Is there some "setting of your power saving features" that I'm missing?
I think I will cancel my appointment. I read on another forum where engineering said the problem is due to a bug in firmware and they are working to get the black screen delay down to 10 seconds and then finally to squash the bug entirely. So hopefully it will get fixed at some point. It appears the bug causes a software panic when waking from a deep sleep.
Because we all have the same software, why do so many cars work correctly, while ours do not? My service manager is going to replace my computer on Thursday after running some deeper diagnostics than were run previously when my car was in for this same issue. If this were only software, we'd all be experiencing the problem, I'd think.
If the firmware mentioned is in the classical meaning where it is contained in a ROM, a computer board replacement might fix it. My car was manufactured in July. Probably should do a poll including that somehow.
I have three close friends near me with 3's.
- Built and delivered in June. RWD (duh). 6,000 miles. Never seen the blank screen
- Built and delivered in December 2017. RWD (duh #2). 8,000 miles. Had the blank screen regularly, six frustrating service visits, finally replaced computer in Feb. Been working great ever since.
- Built and delivered in September (the same day mine was delivered). AWD. 2,000 miles. Has never seen the blank screen
- My car. Built in Aug, Delivered in September. AWD. 2500 miles. Blank screen at least once per day EVERY day since taking delivery in September. One service visit with the response "we know about the problem and will eventually fix it with software." Then I contacted the service manager who fixed friend #2's car. And he's having me bring it in for the same fix.
