This Can't be good... screen issues with 2019.8.4

[ben1628]

Screen went "crazy". I did a soft reset and that fixed it.

Hopefully this won't happen again, as it seemed more like a software glitch than hardware issue.

Same here, version 2019.8.5, happened twice. Soft Reset twice, no alert to Tesla when I chat with them online. Chating on line is nice, feels like talking to my old self. lol

 

[Shopaholic]

Having similar screen freezing or complete blank and auto rebooting in the past week on 8.5 never in the past. Looks like 8.xx bug

 

[Skmetallica]

Had the same flickering screen happen to me twice in the past 24 hours. Anyone got anything official from Tesla yet? Or do we just wait on the next update? I am on 8.5.

 

[Tam]

...I haven’t seen anyone post this issue, but something is failing...

The first thing that I do is to do a hard reboot. If that doesn't solve the problem, I would call Tesla.

 

[OCR1]

One of our M3’s is also on 2019.8.5 and has been doing the exact same thing. It rebooted twice during our drive home one night while doing that. I wouldn’t bother going to the service center just yet. I’m pretty sure it’s an 8.5 bug.

Our other M3 is still on 2019.5.15. I’ve been a bit frustrated that it hasn’t been receiving updates, but after seeing the problems with 8.5 I think I’m glad I’m still on 5.15 until they sort this stuff out.

 

[PoitNarf]

Several people here have experienced the same thing, including myself. Seems to be a bug with 2019.8.5 and possibly some other versions of 2019.8.x. There’s a thread about this here somewhere. Just reboot and it should go away.

Edit: Found the other thread about this issue: This Can't be good... screen issues

 

[TD_alseT]

Thanks! Both of mine are on 2019.8.5, but only one has the problem so far... both have rebooted while driving though.

 

[Dante]

Have had similar issues, and above mentioned thread also documents others with problem. Also, now we all know where you live? Maybe? hahahaha.

 

[skitown]

Our Mobile Tech says it’s a known firmware bug. Reboot while driving clears it. I would expect a fix in the next release.

 

[boiler81]

Had that happen to my UI today for the first time. Rebooted and problem went away. I'm on 2019.8.5.

 

[turok3000]

Check out this thread: discussion (and similar videos) about the same thing:
This Can't be good... screen issues

 

[ronin]

8.5 on mine as well. Had this happen twice, once in the middle of driving then rebooted itself which freaked me out!

 

[beej666]

Has anybody here who has experienced this issue been updated to 2019.12.1? If so, your experience wrt this issue so far?

Thanks!

 

[turnem]

For what it's worth I had this issue today (my M3 is only 4 days old and has 249 miles on it). But unlike most of you I'm on firmware version 2019.7.105 (which is believed to be used for HW3 cars - still to be confirmed).

A soft reboot of the screen (while driving) solved it and I didn't see it again.

 

[RayK]

My one and only (so far) encounter with the screen flickering / artifacting was a couple of days ago. Weather has been a little warmer than before but nothing out of the ordinary for San Jose. I've been on 2019.8.5 since 4/4.

 

[ceekz]

I had a touchscreen failure a week ago, restored by a hard reboot. The next day, the screen was glitching like crazy, with sections of the map replaced by orange bars much like the examples given here. A reboot did nothing! The next day, screen operation was normal. I received the update to software version 12.11 last night, so we'll see if that helps.

I scheduled the update to run when I thought my car would be garaged, but it turns out I was parked on a city street but it uploaded anyway. I thought I had to be connected to wifi for updates? Also, it was a big jump from 8.5 to 12.11, a ton of notes that I haven't yet read.

 

[jthibault]

Mine does it all the time. It seems as if it's hacked as in It actually controls my screen. It removes my favorite, changes my volume, activates navigation, it's even open my glovebox. I've reported to tesla and they actually called me. Hard restart corrects it but not for good.