Autopilot interfering with phone calls?

[viper1619]

*If* the settings/power off button does work for a reset on MCU2, I found that since my screen was still responding to touches but not updating the image, I could tap the bottom left Controls area, tap where "Settings" would have normally popped up, and then gone through the menu to reset.

I'm fortunate that I had another owner on FaceTime showing me where to press in the screen. If anyone's interested (or it's a larger issue not solved by .12 or further software) I can take pictures and upload.

 

[viper1619]

@Phantom_Frog

Easy
method:

Screens froze while driving. Scroll button reset not Reset.

Power off vehicle from menu, hold scroll wheels, then press brake to wake vehicle up. Reset worked for me on MCU2

 

[Phantom_Frog]

I FINALLY got the update for the newest software scheduled to be downloaded and installed tonight. So hopefully this will fix my problem. But thank you Viper1619, I will let you know what happens tomorrow.

 

[Webfart]

My MCU2 X wouldn't reboot with the scroll wheels, so I called Tesla. They remotely reset my "gateway" and since then, the mcu reboots normally with the scroll wheels. As an added bonus, the wifi now works as well. I am on 2018.12

 

[Phantom_Frog]

OK so after my service visit today, I finally have fixed the problem. This is something good to know for all who have iPhone X's.

They were able to fix the problem by disconnecting my device, reconnecting it BUT without allowing the car to remember previous calls and contacts.

There was one technician who had figured out this "trick" and it worked.

I realized that there was a problem when i dropped my car off and they gave me a loaner Model S and I was experiencing the same problem on the way home.

So the problem is likely with my iPhone, and not the car. Other employees at the service center paired their phones to my car and there was no problem.

So I believe that it is an issue with my phone.

I just wanted to share since there seems to be a big problem with iPhone's and Tesla's.

 

[dgatwood]

So the problem is likely with my iPhone, and not the car. Other employees at the service center paired their phones to my car and there was no problem.

So I believe that it is an issue with my phone.

Uh, no. That's not the way standards work. If you build a device that is designed to work with other devices via Bluetooth and that other device sends you crap, and your device misbehaves in some minor way, such as not being able to see call history or not being able to make voice calls, then yes, you can blame it on the other device for sending bad data.

BUT... if another device sends you bad data and your device completely craps itself and stops working entirely, that's your fault for not validating input properly.

So what's happening here is that Tesla didn't test some edge case in their Bluetooth syncing implementation, and because of some data on your device (who knows what), the Tesla side of things is going berzerk whenever it momentarily silences the iPhone to play the autosteer chime. That's squarely a bug on the Tesla side of things, regardless of whether the data coming from the iPhone is bad. In fact, the phone shouldn't even be told when the car is doing that, and therefore, the code involved in phone syncing shouldn't even be doing anything at that point, which makes this a particularly bizarre bug on Tesla's side.

Moreover, just because it only happens with one device, that isn't sufficient cause to assume that the data is actually bad (as opposed to just unexpected). For example, your phone might be the only one that happens to have a single contact with more than 255 phone numbers for junk callers, or the only one with a contact that has a fax number, or the only one with a contact that received a call from someone who, thanks to different daylight saving time policies, had more than a 24-hour offset from your current time zone, or it might be the only one that got a phone call with a particular invalid caller ID value, such as 000-000-0000, or....

From a software engineer's perspective, Tesla is definitely at fault when this kind of bug happens. That doesn't necessarily mean that Apple might not also be at fault, of course (the exercise of determining whether the data that tickled Tesla's bug is valid or invalid is left as an exercise for the reader), but ultimately, any piece of software must be designed to cope with bad data. From a software security perspective, that's absolutely mandatory.