I'd just call it lawyer-baiting.Given that you don't have a new config Model S, I would find it inexcusable that Tesla is still holding you on 5.12. Call ownership and demand 6.0 - you must have fallen through a hole in their system.
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'd just call it lawyer-baiting.Given that you don't have a new config Model S, I would find it inexcusable that Tesla is still holding you on 5.12. Call ownership and demand 6.0 - you must have fallen through a hole in their system.
I downloaded 6.0 about 3 weeks ago, and yesterday my Model S displayed a message saying that there was software to be downloaded. I downloaded it when I got home in the evening, and this morning I was suprprised to see the download was... Firmware 6.0
I haven't had time to go through it in details, but the software release notes look exactly the same as when I downloaded it the first time 3 weeks ago.
I am wondering if the change could be the 1.67.43 between brackets, after v6.0 - see picture:
What do you guys have between brackets next to 6.0?
Has anyone else experienced this second download of Firmware 6.0?
My car now drives itself and can accelerate to 60 in 3.2 seconds due to this update. Tesla's really are amazing that they can be updated all the time via software updates! So future proof.
I'd just call it lawyer-baiting.
Something I noticed (I think) with 6 is that now when you indicate, the DRL on that side dims to about half brightness. On 5.X (as far as I noticed and also on the loaner I had recently) the DRL on that side would completely turn off until the indicator cancelled.
I downloaded 6.0 about 3 weeks ago, and yesterday my Model S displayed a message saying that there was software to be downloaded. I downloaded it when I got home in the evening, and this morning I was suprprised to see the download was... Firmware 6.0
I haven't had time to go through it in details, but the software release notes look exactly the same as when I downloaded it the first time 3 weeks ago.
I am wondering if the change could be the 1.67.43 between brackets, after v6.0 - see picture: View attachment 61533
What do you guys have between brackets next to 6.0?
Has anyone else experienced this second download of Firmware 6.0?
One new "feature" of 6.0 that I noticed the other day is that you cannot close the sunroof if driving on the freeway. It gives you an "unable to select this position at this speed. slow down" error if you try to close it at freeway speeds. It doesn't seem to have a problem going to the vent position so I'm not sure why they though it was bad to fully close at hight speeds.
With .15 I've had problems with the GPS freezing location. Controls and map still works just the GPS location doesn't move.
Also Slacker often pauses and does not resume when interrupted by Waze on iPhone 5 iOS 8.0.2 via Bluetooth.
Someone reports this every time there is a new build. It seems to be an artifact of the update process and you will be back to displaying something close to your previous rated range in a day or two.I updated to 1.67.43 this afternoon (from 1.67.28, I think). Had 204 rated miles when I started the update (charge limit was set to about 82%, and the car hadn't been driven in a few days). I came back a couple hours later, the update was complete and it had 215 miles of range.
Has anyone else seen a change in rated miles from this update?
Has anyone else seen a change in rated miles from this update?
Someone reports this every time there is a new build. It seems to be an artifact of the update process and you will be back to displaying something close to your previous rated range in a day or two.
Definitely have this. But I had it previously too. Took it in to service for it and they supposedly reset something, but still happens...seems like even more frequently since I got 6.0 (.15 variant). I just got an update notice today so will tr yet hat t onsite. Hopefully it addresses it. If not, I'll definitely take it in at some point. It's not a huge deal, but would like it resolved eventually...