You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Curious to see the results of this..Update...
Dropped my car off at the service center and reproduced the issue I noted before with both devices. They then attempted with a Galaxy S10+ (Android 10) and it worked fine. I gave them time stamps of when I had issues so they could look through error logs and left with a loaner.
A few hours later I got a text stating:
"Upon further diagnostics technician determined that the car computer on your Tesla needs to be replaced."
I then received an email stating the following part had been ordered:
TLA,CAR.COMP,NA,HW3.0,M3 - PROVISIONED
Part #: 1462554-S0-I
I'm hoping this will fix the issue for me but also hoping this isn't a major issue that will plague everyone else.
I have had this issue for about 4 weeks like most of you. A click sound during a call then all sound dead for a period of time.
I booked a service with Tesla and logged some times when it occurred. A tech called me 2 days ago for more info and I advised lots of people are complaining about this on the forums. He advised I'm the only one.
New tech called me today (not the halfwit) that called before. This guy was knowledgeable and said it was a software bug that appeared 2 versions ago and should be fixed in 2020.24.x. I asked if he could push the update to my car and he advised no. There's my 2 cents worth
My service center refuse to replace anything and claim it's FW issue.Updated #2...
Picked up my car this morning and have not had any issues no matter how many different ways I've tried to replicate the issue. So it appears to be fixed. When talking with the service center they really had no idea what the issue was just that they were able to verify the issue and their next steps were to replace the computer.
The new computer was updated to the current 2020.20.12 software but with the previous version of navigation data.
Not sure if that is good news or bad news for everyone else having the issue.
Has anyone been experiencing this issue or seen that it has been fixed while on the new update (2020.24.6.1) that's rolling out?