Apr 14, 2015
hans I wish we had something like chrome-to-phone for the car (chrome-to-car?). This would be one of the very first apps I would write after Tesla releases the SDK for in car apps.�
Apr 14, 2015
Bugeater I've been talking about a Google Maps to Tesla xfer tool since we got our car in 2012!�
Apr 14, 2015
aronth5 Sounds like when I plan my bicycle route and download it to my Garmin GPS. Works great, except in my case never use the interstate:smile: Sorry for the tangent!�
Apr 14, 2015
dirkhh +1 for a solution that allows me to plan on a real browser with a real keyboard and then just pushes it to the car. Preferrably on Google Maps or something similarly powerful.�
Apr 14, 2015
rickgt +1 for the ability to plan on computer or phone maps and then send to the car navigation system�
Apr 14, 2015
smartypnz Like in my 2010 BMW�
Apr 14, 2015
mochouinard Had the issue again today when I routed myself to go to Drummondville SuperCharger... Had +50km range available to do it, but it gave me a very short distance destination... It made me go back to Montreal (120km detour). I disabled all the charge point and told me I would make it just fine !
I'll have to be careful when I plan route even more and check where it actually sending me.�
Apr 14, 2015
rickgt And my wife's MBZ 350E
�
Apr 14, 2015
voidptr Leaving Cape Canaveral today to go north, was probably right on the edge of comfort to push to St. Augustine without stopping at Port Orange first, but it wants me to stop there, so ok. Charge at Port Orange to 202 miles, way more than enough to get to St. Augustine. It started spinning on planning the next leg, so I cancelled and re-selected my destination (have seen this a few times), it wanted me to pull a u-turn and charge another 15 minutes at Port Orange! Tried to select the route again, same thing. Decided to drive up 95 and see what would happen, it kept re-planning a double back to Port Orange all the way to about 20 miles south of St. Augustine (40 miles past Port Orange) when I again cancelled navigation and this time it picked the right stop.�
Apr 14, 2015
Dien Kim Nguyen Since I got the update (.153), I could not able to make the sound effect of "balloon squeal" from my car (P85) by stepping on the pedal. Anyone experiences something similar? Hopefully it is gone for good after nearly 2.4 yrs. I can sense the throttle behavior is different but more driving is required before I can determine whether it is better. My standard package sound is sooooo munch better -- treble range is more crisp with much improve bass performance.�
Apr 15, 2015
Peter_M +1 but then we'll be hitting the 10 waypoint limit on Google Maps for some trips.�
Apr 15, 2015
Adrian You should be able to push several routes and store them imo.�
Apr 15, 2015
HankLloydRight I'm still waiting for more than 2 trip odometers... and ones you can name and toggle on/off as needed. It's so simple to do. But maybe we'll have to wait for the SDK/API and I'll just do it myself.�
Apr 15, 2015
Andyw2100 When people like you, who have the skills to do the programming, the knowledge of the car and exactly what we, the users, want, and the desire to get it done are actually allowed and enabled to give it to us, it will be a golden moment in Tesla's history. I don't have any idea what they are waiting for, or what could be taking Tesla this long, but the sooner that day comes, the better, at least as far as I'm concerned.�
Apr 15, 2015
dirkhh I'll admit that I cannot cannot cannot wait for the SDK to be released. And then two generations of us complaining and moaning that we don't get access to ${FOO}. And then, once we wear them down, the amazing insanely cool apps that we can build.
I understand that this isn't a very high priority for them. But as a geek... Oh boy oh boy oh boy...
- - - Updated - - -
Think about their priorities. First they need to get the stuff that matters for Joe the Customer to the cars. Better navigation being HIGH on that list. Very high. The trip planner is just one aspect of that. Then hopefully deal with some of the challenges in the media app. Then the auto pilot features. I can see quite clearly how those could be perceived as much higher priority than and SDK. And the thing is that an SDK is hard to do right. And once you release it you are stuck with the APIs you have created (within reason). And you need a very, very thorough security review of all this. A sandbox that people really cannot break out - any story that an app could impact the driving of the car would be a disaster... So yeah, it makes sense to take this slow. Yet... yeah, I want it yesterday
�
Apr 15, 2015
andrewket All true, but depending on how much access tesla provides, third party developers could offer a better media app, a better energy planning app, etc.�
Apr 15, 2015
HankLloydRight I just want to be able to use MAME on the touchscreen using the steering wheel buttons and wheels for the controls. Yeah, that's it: TeslaMAME
That huge touchscreen is perfect for stand-up arcade style games -- PACMAN, Frogger, Space Invaders, Tetris, Donkey Kong, Tempest!
Come on Tesla -- you've done enough damage to the NAV... just port MAME !�
Apr 15, 2015
dirkhh Umm. Err. OK. #6524955 on the priority list...�
Apr 15, 2015
reese9879 I received my 6.2 update a few days ago, I have now have it weird issue. I have a USB drive with music, and before I get out of the car in the evening I pause what I am listening to before locking the car. When I get in the car in the morning I open the door and the music is playing and the album I was listening to has advanced by 10 or so tracks (could be more) and I noticed that range has decreased by a few miles. When I got my car 3 weeks ago, I didn't have this issue (music play or range decreasing).
Has anyone else experience this?�
Apr 15, 2015
mknox I agree... the way OnStar allows you to.
I tried a couple of mock routes (i.e. to my daughter's place near Chicago) and it seemed to map me through Maumee which I've never needed to do, and to make more Supercharger stops than I believe I need. What I'm not sure of is whether it is doing some calculation around faster, but more frequent charging with a lower SOC on the battery. In the past, I would do an 80 or 90% charge when I did stop, but the time wasn't important because I'd try to plan around a meal break anyway.�
Apr 15, 2015
brianman TesS (Sig P85, Nov 2012 delivery, 45k miles).
With 6.1 firmware, my 90% rated rose from 221-223 miles to 235-237 miles.
With 6.2 (.153) firmware yesterday morning, 90% rated rose immediately to 240; overnight (next charge and presumably balancing) cycle the rated range is now 232 miles with the UI still showing 90%.
Car has been in park for ~5 days now, so no driving consumption involved.�
Apr 15, 2015
dirkhh The spike to 240 I'd call an oddity. Maybe that's just some default value for a Sig P85 (so basically straight from a table with no adjustment).
And the slightly lower value after the last nightly charge... well, they keep playing with (err, fine tuning) the algorithm, I bet.
When's the last time you took the car below 10% SOC?
With my 60 (produced about 6 months after your Sig) the 90% readings would go to lala land if I didn't run it down to <30 miles range every once in a while... I had the 90% down to as low as 165miles and was getting worried about degradation. Next time I charged after driving the car down to about 15 miles it was back up to 178-ish.�
Apr 15, 2015
mknox And for me, once again, not even a 1 mile change after 6.2 the other night. (still getting 218 miles @ 90%).�
Apr 15, 2015
brianman That's my read as well. It's the "lose the data, new firmware" set value that I get on probably 1 out of 3 firmware upgrades until a day or two of driving and/or balancing rebuilds some battery data on my actual battery.
- - - Updated - - -
I'd have to look through the logs. At least a month ago, I think.�
Apr 15, 2015
Klaus I updated Monday evening. Full charge overnight -> 201 mi, same as for past 1-1/2 years.�
Apr 15, 2015
Andyw2100 The music playing has been mentioned by others in the 6.2 bugs thread here: Bugs in firmware 6.2.
As for the range decreasing, I think you are probably just seeing typical vampire loss, and that you probably were seeing it before too. Or if the weather has changed, and it is warmer where you are now, and your car needs to cool the battery more than it did before, that could be causing more of a range decrease. But no one else, as far as I know, has noted any change in this behavior, and there has always been vampire loss, (search on that term to learn more), so I think you're probably just seeing normal Model S behavior.�
Apr 15, 2015
tomas :biggrin:ok I'll confess. I was driving your car and listening to your tunes. But really, grand funk railroad?�
Apr 15, 2015
yoyo I got new update notification this afternoon (it was in SC for next gen seats replacement), and just finished update, it shows 2.4.160
I could not tell any difference in release notes with 2.4.153
any one else got this new one? (normally I get updates the second or third day)�
Apr 15, 2015
MikeBur You appear to be the first!
Remember to log this at Tesla Firmware Upgrade Tracker Web App please�
Apr 15, 2015
Benjamin Brooks No, but go post it here since you're the first
Tesla Firmware Upgrade Tracker Web App
�
Apr 15, 2015
yoyo have been trying... but somehow very slow for me and got stuck at add vehicle... will try again
�
Apr 15, 2015
HankLloydRight It worked. Your car and update have been recorded.�
Apr 15, 2015
yoyo think I got the tracker updated now...
�
Apr 15, 2015
anxman My P885D is also getting next gen seats installed and I received a software update notification as well. Picking it up tomorrow. I'm assuming it's the same .160 build.�
Apr 15, 2015
dirkhh I'm so glad that when I'm busy at Tae Kwon Do class others are doing the good work to ask people to post to the Firmware Upgrade tracker.
Positive reputation going to MikeBur and Benjamin Brooks! Everyone, please post your updates to the tracker! So far we have one from today and (oddly) romp says his VIN-less P85+ got it 4/11... I'll follow up with him to verify that
Grrr: updated to say "positive rep going to Mike, Benjamin and yoyo once my reputation giving ability has recharged..." - I run out every day :-/�
Apr 15, 2015
krisg81 Service center updated my P85D to .160 as well today. Initial changes noted is car steers itself (took me straight to In n Out Burger), it finally puts out the rated 691HP / 515kW inverter power, adds a usable blind spot awareness system, TACC doesn't try to rear end cars who are starting to enter/exit lanes, and premium stereo now sounds... Premium
Well, I'm kidding of course.. I'll just patiently await those other items but honestly, .160 has no difference I've seen or felt.�
Apr 15, 2015
SteveW25561 I've noticed that Bluetooth audio playback seems to be automatically resuming when I get into the car without needing to manually switch to the Bluetooth media source -- I've been wishing for this. I've only had 6.2 for a day or so thus can't say if this is a reliable new behaviour.
Btw my phone is an iphone 6, iOS 8.3�
Apr 16, 2015
Mayhemm Surprised no one has commented on the first line of the .160 update:
"Your P85D can now perform high-speed passing maneuvers up to 155 mph (250km/hr) when battery energy, powertrain temperature, and road conditions allow."�
Apr 16, 2015
Dennis87 That line was added in the .153 update�
Apr 16, 2015
smartypnz Finally merged to the 6.2 area this morning with version 2.4.153 will add to the data.
Question: once you input a destination, how do you get it to list directions past the first SC?�
Apr 16, 2015
PaulusdB Running 6.2 / 2.4.136 for a few weeks now. The other day I used cruise control to maintain ~ 50 km/h (30+ mls/h).
Never before noticed this cc malfunction. The car feels like the energy pedal is pulsing, like delivering just a little too much power followed by just a little less.
Reminds me of 70-s diesel powered Mercedes Benzes with manual gear. They featured what was called the 'Bonanza' effect (or 'jig-saw' effect in other languages) when de- or accelerating.
Due to the rocking motion of those engines your foot kept overcompensating, only to worsen the rocking.
It's not THAT bad with this firmware version, so it would call it the 'Parkinson' effect.
Any other drivers experiencing the same effect and is it gone in more recent firmware versions?
Experiencing this with the Model S, of course.�
Apr 16, 2015
Gizmotoy Has anyone else had a complete failure of the navigation's Favorites system since their 6.2 upgrade? Mine is now completely non-functional. I've tried rebooting, deleting, and re-adding things. No matter what I do, any location I assign to Home/Work/Favorites is directed to a mangling of my former Home address (it swaps a West for an East to put it in the other part of town). Even if I assign Home to something else completely, all favorites still go to that mangled version of the address I had set as Home when I was running 6.1.
Anyone else with similar issues, or is it just me?�
Apr 16, 2015
dirkhh Nope, never had this. Is this an AP car? You didn't enter your firmware update into the tracker, so I can't just look up your car details�
Apr 16, 2015
PaulusdB I will, Dirk. And no, it's a Classic P+ VIN 21xxx (produced okt 2013), BTW.�
Apr 16, 2015
Duckjybe It could definitely be an interim useful function but in doing that Tesla would be admitting their software isn't good enough. The Volt has that option from the app for general navigation which I have used a couple of times but it requires too many steps. It is somewhat useful only because the nav interface is so bad on the Volt, especially once you are used to the Tesla. Tesla really needs to eventually give the onboard nav the same functionality as Google maps which I am sure they are striving for and then some. Like Elon said they are probably a little short on resources so personally I would rather they spend time on the in car nav functionality than integration with a PC's Google Maps.�
Apr 16, 2015
MrClown I have noticed this too, at least in the neighborhood of 30-35 mph. It's fairly subtle and doesn't happen all the time (or it's subtle enough that I don't notice it all the time). I'm on .153.
- - - Updated - - -
I think I've only noticed it when I'm locked on to another car, in which case maybe it's the other car doing it causing TACC to follow suit. I'll pay more attention.�
Apr 16, 2015
ohaq I got v 6.2(101.36.2) today, not able to update tracker. does not like the new version�
Apr 16, 2015
castor I'm on 6.2 (136) and just got a notice for a new update. I'll wait at least a couple weeks before installed. I'll wait for feedback from TMC. Did someone else get it and installed? Did you notice something different?�
Apr 16, 2015
dtich was on .153, got notice this am, i installed, now on 101.36.2.. huh? i'll go down and see what the release notes are....
edit: same notes as .153. don't notice anything new really. perhaps when clicking an address in a calendar entry it highlighted the destination on the map with a 'navigate' button, whereas before i think it just starting navigating..? but not sure of that. if this is just little bug fixes it's so odd to completely revamp the version numbers, no? maybe it's the beginning of forking fw for different hw versions.? i'm og p85, 2012.
anyway.�
Apr 16, 2015
apacheguy Weird so the version number jumped from 2.4.x to 101.36.x? Now I think they're just messing with us.�
Apr 16, 2015
dirkhh That can't be real.
Does anyone have a screenshot?
grasping at straws here... 36 is 0x24 -> 2.4 ?
No idea where the 101 would come from.�
Apr 16, 2015
bollar It's real. I got it today.�
Apr 16, 2015
dirkhh Sorry, I realized too late that this sounded like I was questioning the truthfulness of the posts... that wasn't my intention.
It's much more "Come on, Tesla, that can't be real..."
This looks like an offset into some table got messed up or something. There's no version number scheme known to mankind that jumps from 2.4.160 to 101.36.2...�
Apr 16, 2015
Kalud Its somewhat typical with software, probably just a new branch of code... I confirm that 101.36.2 is real and valid, being pushed today.�
Apr 16, 2015
dirkhh I've been doing software for 30 years and I can assure you that 2.4.160 to 101.36.2 is anything but "typical".�
Apr 16, 2015
NigelM This is the pattern so far:
�
Apr 16, 2015
dirkhh So that's very typical... we see increments in the sub-minor version for bug fixes, increments in the minor version for small improvements and then the odd switch to major number '2' in the middle of the 6.0 release.
But all in all this is what I would expect. Not a weird jump from 2.4.x to 101.36.y. This is as stupid as going from Windows 3 to Windows 95 - but there they at least had the year as an excuse...�
Apr 16, 2015
wk057 Perhaps it got reversed somehow and is actually 2.36.101? lol�
Apr 16, 2015
yobigd20 Ha I was thinking the same exact thing.�
Apr 16, 2015
dirkhh 2.4 to 2.36 would still be a crazy jump. But see the other thread where andrewket posted a picture of a 6.0 build that was 101.10.12�
Apr 16, 2015
wk057 Looks like the fiance's P85 has an update... installing now.�
Apr 16, 2015
dirkhh Let me guess, it's 6.2 builds 354.764.87�
Apr 16, 2015
scaesare Got the funkalicious build of 6.2 tonight:
�
Apr 16, 2015
Klaus 
�
Apr 16, 2015
MarcG Perhaps different models have branched off to different releases? So far it looks like S60 models are getting the funky versioning.�
Apr 16, 2015
pgiralt I remember when the P85D was introduced, they were spied having some above-100 release numbers as well. Seems like Tesla uses those for their development branches. I wonder if this was just a mistake where the release did not get properly numbered before release.�
Apr 16, 2015
rickgt yes, .153 is an improvement over.136�
Apr 16, 2015
Kipernicus On Tuesday I received the update to 2.4.153, and tonight I received 101.36.2
Can't tell any differences so far.�
Apr 16, 2015
Klaus The Visible Tesla screenshot above my picture says 85 as the badge.�
Apr 16, 2015
scaesare Yup, that's me. Have a 85, not a 60.�
Apr 16, 2015
Klaus Similar here. Monday evening (popped up after we got home from a hike on the coast), and today ready when I got in to drive home from work. Both times the download at least completed if not happened entirely on 3G although I have a dedicated WiFi at home. That WiFi connection is unreliable, though, as discussed by others before.
I hope it's improved software
BTW on Monday I got an iPhone notification, but none today.�
Apr 16, 2015
Ugliest1 Just installed the funkiness, on my old, slow, blind "that's so 2013" S85. The compile and install worked, have to wait until tomorrow for the execution testing�
Apr 16, 2015
Copyright :tongue:�
Apr 17, 2015
FairFrank My P85 also updated from 2.4.136 to 101.36.2 today.
It's a big jump. Now you can send via voice control commands to speed control officers to look the other way. Great!
It also introduces the mother in law ejection seat button. That's what we call... insane!�
Apr 17, 2015
J1mbo Doesn't this update also enable the original front "D" motors that were fitted to the front wheel hubs in classic Ps for superior torque vectoring?�
Apr 17, 2015
mibaro2 Looks like Tesla decided to change their software version labeling.
It happens with companies every so often. Intel had the 286 chip, then 386, 486, then Pentium. Changed the labelling of new versions.
Microsoft did it several times, most memorable going from Win 98 to Win NT.
It will be interesting to see the next release after 101.10.12 to see if it was an error or not.�
Apr 17, 2015
pgiralt Funny you mention this example because actually Microsoft has maintained a fairly consistent numbering scheme for the actual version numbers (not the marketing version names). Other than adding the name NT to the version names for the NT series, they still maintained consistent numbering. Windows 95 was actually Windows 4.0 (and NT 4.0 came out around the same time). 98 was 4.1 and Windows 2000 was 5.0. Vista, Windows 7, and Windows 8 were 6.0, 6.1, and 6.2 respectively.
I still think this is some kind of mistake where something didn't get renumbered properly or something was released when it shouldn't have been. If it was a mistake, the issue they might have now is the upgrade code might not allow for downgrades, so a car with a 101.x.x version might not be able to "downgrade" to a future 2.4.x version without a service center visit. Hopefully that's not the case.�
Apr 17, 2015
mochouinard It might just be to identified development release that is not considered stable released... Though they do seem to push it to a lot of people. Maybe they saw remotely issues from car running the 6.2 update and forcing it to them.
From the 14 car I track, only one have 101.36.1. 5 have 2.4.153, 5 have 2.4.136, 3 have 2.4.124.�
Apr 17, 2015
mibaro2 Ah, now Microsoft's numbering makes sense. I only knew the marketing names.
It's nice that Tesla keeps us guessing at these things, right? If it is a mistake, then I expect the role-out of this new release to stop. Let's see how many get it in the next few days.�
Apr 17, 2015
mochouinard I went to service today to fix a door handle, and they updated my car to 2.4.160�
Apr 17, 2015
brianman For math people yes, for people that see the "." as a simple "field delimiter" 4 -> 36 isn't that crazy.�
Apr 17, 2015
Coiled Very interesting. Maybe 2.4.160 is the public/release version number of 101.36.1, which is an experimental/development version number. Just a guess on my part.�
Apr 17, 2015
hans Very plausible. Either an engineering build escaped into the user base or they just forgot to rename it properly when it (hopefully) passed QA.�
Apr 17, 2015
Coiled Or it was deliberately released to a limited number of users as a beta test. The crazy stuff people are reporting with nav might warrant a rushed fix. QA? We don't need no stinking QA!�
Apr 17, 2015
zwede I have 101.36.2. Just updated the tracker. Haven't noticed any difference compared to the previous 6.2 (but haven't looked through all the menus either).�
Apr 17, 2015
Majerus
�
Apr 17, 2015
AmpedRealtor Maybe Tesla forked the code for the new P100D that will be announced on 4/30?
ha!�
Apr 17, 2015
HankLloydRight
One of my favorite "meme" images!
�
Apr 17, 2015
president_ltd Just got 6.2 (2.4.168). "Insane mode is now more insane! Your car accelerates even faster when in insane mode, improving 0-to-60-mph performance in this mode from 3.2 seconds to 3.1 seconds. The accelerator pedal is also more responsive in insane mode."
Thanks Teslati folks.
�
Apr 17, 2015
rickgt I have .153 and was pleased with some fixes... BUT, just went to use Valet mode, and that function disappeared. SAY WHAT?�
Apr 17, 2015
MarcG Whoa is that a real screenshot?!? Can you take a shot of the release number please?�
Apr 17, 2015
dirkhh They are just messing with us. The intro to the release notes were written by a twelve year old. And her little brother is now in charge of the version numbering...�
Apr 17, 2015
apacheguy Yeah, seriously.
Guys, didn't drag times already get the Vbox number for an earlier version of 6.2 pegged at 3.1 s? So possibly this update will bring it sub 3 sec with the proper SOC?�
Apr 17, 2015
Andyw2100 I don't believe the release notes had mentioned an improvement in the 0-60 time before. This may just be the documentation for the improvement already seen in the earlier firmware version.�
Apr 17, 2015
LVSP85D Documentation updates for 2hours? I believe there should be more to it, notice it says better throttle response as well.�
Apr 17, 2015
Andyw2100 You misunderstood me.
I think the current firmware update is a real update, with bug fixes and whatever else Tesla threw in, including possibly the stuff about more throttle response, since that has never been mentioned by anyone before or documented. My point was that just because Tesla was now documenting the increase from 3.2 to 3.1, we shouldn't expect 0-60 times faster than 3.1 because what was probably happening was they were just catching that part of the documentation up to the firmware update they had provided previously (in .136 and / or .153 I believe), which, according to many had already given us the 3.1 0-60 times.�
Apr 17, 2015
Kilowatt Make sure you aren't moving when trying to switch to valet.�
Apr 18, 2015
Todd Burch Aren't moving = in park.�
Apr 18, 2015
MarcG So has no one else received .168 yet?�
Apr 18, 2015
Cyclone There is the one poster here and one more in the Driving Dyanmics subforum. I haven't seen any other reports yet.
New updates P85D: Insane mode now more insane!�
Apr 18, 2015
Andyw2100 I received an update last night shortly after 8:00 PM Eastern time, as per the notification my wife received on her iPhone app (I'd have no idea, since I use the second-class, lowly, Android app), but I won't be able to install it and confirm that it is .168 until late tonight.�
Apr 18, 2015
fiksegts if this is real, expect a 2.9x 0-60 MPH time, I already got 3.04 from the previous 6.2 release....
�
Apr 18, 2015
Andyw2100 Unless, as I tried to say earlier, they already put the 0-60, 3.2 to 3.1 improvement in the last firmware update, but just hadn't documented it. In which case this firmware update, which updates other things, does not actually update the 0-60 time, but does catch-up the documentation on the 0-60 time improvement made in the last firmware update.
We have definitely seen Tesla document features and changes late in the past. I think this is more likely than that they updated the 0-60 times twice, in two different firmware versions, trying for a .1 second improvement.
I'd love to be wrong.�
Apr 18, 2015
In2oil
I must be in the DEAD zone, my tesla remains in .153 this is the latest update I receive!�
Apr 18, 2015
fiksegts they didn't.... my previous best on v6.1 was 3.07.......
�
Apr 18, 2015
wk057 Guess it's good that this is out after I did my drag runs yesterday. Means I can actually put it to the test later�
Apr 18, 2015
Larry I just received 6.2 101.36.2 yesterday. Whatever that is�
Apr 18, 2015
jweinstein 
�
Apr 18, 2015
Andyw2100 Thanks for posting the screenshots, jweinstein!
- - - Updated - - -
OK, good to know.
There had been some debate over that, as some claimed there was an improvement in the 0-60 times at the same time that they increased the max speed to 155 MPH. I actually thought your tests showed the improvement, but I must have been mistaken.�
Apr 18, 2015
president_ltd yes its a real screenshot. no, i don't need to post a screenshot of the release number as i typed what it was.
you can choose to believe me or not.�
Apr 18, 2015
dirkhh we have only one report in the tool�
Apr 18, 2015
jweinstein How do I view/access the tool?
Thanks!�
Apr 18, 2015
LVSP85D I also got the update. Throttle response is noticeably better in insane mode.�
Apr 18, 2015
Shew Just installed .168. I couldn't find the tool either.�
Apr 18, 2015
gpetti I think they are just messing with us.
I would.�
Apr 18, 2015
Klaus The "Tool":
Tesla Firmware Upgrade Tracker Web App�
Apr 18, 2015
rickgt Nope: absolutely in park...�
Apr 18, 2015
3s-a-charm DEAD zone = Canada? I'm on the same version as you are... Please, Tesla, give me this before my Sunday drive tomorrow morning!!!�
Apr 18, 2015
rickgt Yup, stuck at .153
sounds like at least three newer updates are out in the wild...�
Apr 18, 2015
dirkhh We have seen .155, .160, .168 and of course on some older cars 101.36.2
So I'd say there are likely four newer updates out there. And I saw someone report .124 today as well. I'd say this is a complete mess right now�
Không có nhận xét nào:
Đăng nhận xét