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.
I nearly got sucked into this trap on my most recent update. I could have sworn that the hill hold improved, but now I'm pretty sure it hasn't.Thanks for saying that.
I try to avoid falling into the trap of posting things about changed this or that unless I have pretty solid evidence, because I know what the patterns here have been. I really think this time Tesla has given us something to talk about!
I think that generally they have issues with the energy savings mode right now. If I use it, the 3G takes a very long time to recover after waking up. I've been advised not to use it unless I don't care about waiting for 3G for 10 mins or so.OK, I'm 99% sure I've figured out the car audio mute issue. There are two symptoms: 1) If you have energy savings mode turned "On", and you pause the audio before you leave the car, the car will NOT remember that it was paused, and next time you wake it up, it will resume playing audio at previous volume. 2) Also if you have energy savings mode turned "On", and you pause the audio before you leave car for long period, you may come back to completely different song.
It is really very simple error. When car goes into energy savings mode, it somehow does not correctly save the state of the audio pause/play button. Or, possibly, when it wakes up, it does not check prior state. Either way, it wakes up playing. If you've only parked a while, then it will resume same song it was previously playing. If you've parked a long time - say, overnight to charge - the car has been woken up overnight and resumed playing while it was awake (and you were asleep!). So, when you turn car back on, the audio progressed from the song you were playing when you left.
BTW, none of this happens if you have energy savings mode "off".
Though I never had it before 6.2, this error was reported widely several releases ago. Then it seemed to be fixed. Now it is back. Should be ultra-easy fix.
Anyone have a good channel to report to Tesla? "Bug report" in the car doesn't work with this much info. I used to send these things to "ownership@", but that's gone. Now the "service@" is there, but for the past year, it seems they just forward everything to the local Service Center, then you get a call from some well-meaning person who can't fix code. This really needs to get to the software engineers.
SC installed 2.4.213 on my classic P85+ yesterday. Tracker updated. It's curious that when the SC installs an update, the mirror reverse positions is not preserved. If I install the update OTA, all positions are preserved across the update. This is not the first time this has happened to me either.
SC installed 2.4.213 on my classic P85+ yesterday. Tracker updated. It's curious that when the SC installs an update, the mirror reverse positions is not preserved. If I install the update OTA, all positions are preserved across the update. This is not the first time this has happened to me either.
My mirror tilting was lost when I updated to 6.1 and it was an OTA update. Other people have reported losing the mirror sertings after OTA updates. But it doesn't happen on every update, and has only happened to me once. So I don't think it's a matter of SC vs. OTA, just something that is not rare but not consistent.
It may happen occasionally with OTA updates, but I believe the consensus here is that it happens 100% of the time with SC installed updates.
Does the SC maybe do a "reset" along with installs perhaps? It couldn't be a hard reset though or else you would lose your driver profiles and homelink too.
In over two years, I've only lost my mirror tilt settings once, and it was with an over-the-air update and not one of many that I've had installed during a service visit. What's interesting to me is just about every time my car's been in for service, they will report on the invoice that they installed the latest firmware. That seems to be one of the "standard" things they do at each visit. Anyone know if it's done via the SC's WiFi or whether they do it hard-wired?
Yes, the three times I got updates at the SC I always lost my mirror tilt setting. Don't recall losing it during any other upgradeNot sure, but I had .213 installed at the SC yesterday and, as expected, I lost my mirror settings again. It happens to me every time the SC does an update.
Yes, the three times I got updates at the SC I always lost my mirror tilt setting. Don't recall losing it during any other upgrade
OK, I'm 99% sure I've figured out the car audio mute issue. There are two symptoms: 1) If you have energy savings mode turned "On", and you pause the audio before you leave the car, the car will NOT remember that it was paused, and next time you wake it up, it will resume playing audio at previous volume. 2) Also if you have energy savings mode turned "On", and you pause the audio before you leave car for long period, you may come back to completely different song.
It is really very simple error. When car goes into energy savings mode, it somehow does not correctly save the state of the audio pause/play button. Or, possibly, when it wakes up, it does not check prior state. Either way, it wakes up playing. If you've only parked a while, then it will resume same song it was previously playing. If you've parked a long time - say, overnight to charge - the car has been woken up overnight and resumed playing while it was awake (and you were asleep!). So, when you turn car back on, the audio progressed from the song you were playing when you left.
BTW, none of this happens if you have energy savings mode "off".
Though I never had it before 6.2, this error was reported widely several releases ago. Then it seemed to be fixed. Now it is back. Should be ultra-easy fix.
Anyone have a good channel to report to Tesla? "Bug report" in the car doesn't work with this much info. I used to send these things to "ownership@", but that's gone. Now the "service@" is there, but for the past year, it seems they just forward everything to the local Service Center, then you get a call from some well-meaning person who can't fix code. This really needs to get to the software engineers.
You can't.