I just got an update notification over wifi. Was on 2.52.22 before....
17.4.14, updated tracker. Will take it out for a spin later this afternoon.
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 just got an update notification over wifi. Was on 2.52.22 before....
DittoGot 17.4.14 just now (HW1 car, was on 2.5.22). I was so excited to see what would show up... Minor bugfixes and improvements. Meh.
Ditto
Has anyone else noticed how the phone contact information is listed backwards? If I say "Call John Smith" his contact information comes up and the choice of phone numbers is listed backwards from how it is entered in my iPhone. I can never choose the first number that appears, and have to scroll down to the preferred number.
Just did. Thanks.That is an EXCELLENT point! I had noticed the need to scroll, but had not realized that the listings are actually reversed from how they are in my phone. How silly!
You should write this up for Tesla, and send it to [email protected].
Is your avatar really you?Not meaning to pick on you, but we don't need a lot of "me too" messages on this thread, unless you have some new observations on features, behavior, etc. It'd be great if you can update the firmware tracker (ev-fw.com) however.
Thanks!
Bruce.
Is your avatar really you?
am speculating that these are HW2 cars where the Enhanced AP option was not purchased.
Not sure how long this will last, but for the moment there appears to be a pattern to build numbers 17.x.yy.
If x is an even number (17.2.12, 17.4.14) then the build is going to HW1 and pre-Autopilot cars
If x is an odd number (17.3.2, 17.3.15) then the build is for HW2 cars. I know some cars are showing as not having AP, but I am speculating that these are HW2 cars where the Enhanced AP option was not purchased.
Previously, any build could go to any car. Given the significant change to the processing hardware with HW2, it makes sense to have major fork of the software streams and hence build numbers.
The test of the hypothesis will be if this pattern continues once we see 17.5.y and 17.6.y. Or just another fluke.
The second number xx (of 2.xx.yy) has been the release week for quite some time now (look back in 2016, matches very well). The first number has changed from generic "2" to the year "17" for releases this year.
So it is now year.week.zz, where zz is some incremental number.
Other theories?
The second number xx (of 2.xx.yy) has been the release week for quite some time now (look back in 2016, matches very well). The first number has changed from generic "2" to the year "17" for releases this year.
So it is now year.week.zz, where zz is some incremental number.
Other theories?
The idea may have merit if the year.week corresponds some engineering / testing release point for the build. Per data from the Firmware Tracker, initial observed deployment in the field appears to lag by a week or two:The second number xx (of 2.xx.yy) has been the release week for quite some time now (look back in 2016, matches very well). The first number has changed from generic "2" to the year "17" for releases this year.
So it is now year.week.zz, where zz is some incremental number.
Other theories?
Did they learn NOTHING from the Y2K fiasco? Kids these days...And the "17." also makes sense for year.
The idea may have merit if the year.week corresponds some engineering / testing release point for the build. Per data from the Firmware Tracker, initial observed deployment in the field appears to lag by a week or two:
17.4.14 first reported 1/29 (2017 week 5)
17.3.15 first reported 1/25 (2017 week 4)
17.3.2 first reported 1/21 (2017 week 3)
17.2.12 first reported 1/21 (2017 week 3)
2.52.120 first reported 1/14 (2017 week 2)
2.52.36 first reported 1/9 (2017 week 2)
Which invites speculation as to whether engineering is alternating weeks for releasing builds targeting HW1/PreAP or targeting HW2.