Search results

Ancient thread but it seems people are still interested. I finally have a legal contact at Tesla and they asked requests for compliance with the GPL to be sent there... so if you happen to want access to the source of the Copyleft software running in your car, drop me a PM (I don't feel...

Odd... we have 73 reports for 2.32.100 - and two for 2.34.100. Normally I'd say "hu, typo". But two in a row? And one from @andrewket who has submitted more than 30 of these entries... Other than that, 2.28.19 still seems to be the last full rollout.

I have stopped reading the forum since the switch in forum software. For a while I still popped in once every few weeks, but I'm basically no longer engaged. The Tesla Firmware rollouts have so completely gone off plantation with random daily builds being thrown out to random cars, there is not...

So if I'm counting correctly we now have 47 different builds of 7.1 reported. 2.24.30 is the latest (there was no 2.23.xxx, just like there were no 2.21.xx and 2.19.xx). Nine builds in the last nine days, and none of them have received more than 20 reports, so I guess they are just doing broad...

One report of 2.22.15 - so we skipped 2.21 and continue the odd "multiples of 15" pattern. But one single report of a new version? Strange.

Passed 200 reports on 2.20.45 and reached 164 for 2.20.30. Call me cynical, but that sounds like more beta testing, in this case A/B - the sum of those two is about what we usually get for a full rollout... and a quick search seems to show no one got upgraded from .30 to .45

Hate to distract the entertaining sensory sensitivity conversation with boring firmware data... 170 reports of 2.20.45, low for a full roll-out after 4+ days but otherwise very broad, seemingly covering all the axis I usually look at (geo, models, batteries, VIN ranges).

So 2.20.30 seems to have a lot more problems with speed limits in Oregon again. The first couple of times I thought it was just bad luck, but when I had 5mph on I5 three times no I started to wonder... 85 in a 35 zone, 20 when it was 40. 5 bad readings in two days. Not cool.

So the 2.20.30 roll-out seems to be fading, replaced with 2.30.45 (again that jump of '15' like we had with the 2.17.x series). We have 137 2.20.30 reports, seemingly tapering off yesterday and already have 44 reports of 2.20.45. While I didn't see any 2.20.30 reports for Model X, quite a few of...

I actually occasionally ask people for "don't have it" posts - the tracker does really well to capture the positive statements. But the absence of the positive statements isn't as clear - so for example, we had 406 reports for 2.9.154, 417 for 2.16.17, but only 343 for 2.17.37 - did that mean...

Not sure why you think I hate this. Or what "this" is in this context. Actually, that's great information to see that some people are still on 2.16.17 I think that has been a question we've asked ourselves countless times :-) One thing that has worked for others is to call their service center...

A fair number of people got 2.20.30 - 95 as of this posting. Given the number the fact that all reports are from the US or Sweden seems interesting. At this point in the roll-out I would have expected broader coverage if this was a full release. Also, it's Model S only so far - but otherwise...

And after 141 reports for 2.18.77 (about a third of what I'd expect for a "full" roll-out - but both of my cars got that build) we just got the first two reports for 2.18.91

6.2 had a total of 23 releases that we got reports for (ignoring the unicorns that appear to be beta versions that people recorded). It used two middle digits (2.4 and 2.5). 7.1 so far has 32 builds with 10 middle digits 2.9 - 2.18. That does seem like a change. Is it significant? I don't know.

... and we have the first report of 2.18.18 (still calls itself 7.1 it seems). That's the 32nd build of 7.1 that we have reports for (ignoring betas). Overall the number of reports in the past 10 days has been quite slow - after the fairly complete roll-out of 2.17.37 (330 reports) only 2.17.95...

That one was initially Model X only, so I didn't post here about it, but we now have the first two reports from Model S owners. And yes, the new "count by 15" version number scheme is unusually charming...

You nailed it. They clearly don't do sufficient QA on these builds. How could they possibly do that. And if we are supposed to do the QA for them, we need to know what changed / what to test, and how to get our feedback to them. #FAIL

What's wrong with the water at Tesla? We now have 2.17.50, 2.17.65 and 2.17.80... all three with reports today. With all due respect - I'm supposed to believe that all of these builds went through reasonable testing and QA cycles?

And another random update... we're at 227 reports for 2.17.37 (keep them coming), and in a way more interestingly the first two reports for 2.17.65...

So just a couple of weeks after the broad roll-out of "Needs more cowbells" (2.16.17) the as of yet unnamed 2.17.37 appears to be pushed out to most cars as well - we have crossed 200 reported installs this morning, which means that something like half of the fleet should have gotten it (since...

58 updates to 2.17.37 reported so far with a truly impressive geographic coverage (Belgium, Canada, Switzerland, Germany, Great Britain, Hong Kong, Japan, Netherlands, United States have reports so far - that's a lot broader than we usually get in the first two days of a roll out). It will be...

The random walk down firmware revision lane continues. To recap: After a pretty complete roll out of 2.16.17 (almost 400 reports) we got 10 reports of 2.16.31 (mostly Europe and a few in the US), then 17 reports of 2.16.51 (another cross section of Europe plus US and Canada) and now in the last...

382 reports of 2.16.17 by now. Definitely a complete roll out. If you haven't received 2.16.17, yet, I think you are being left out. We have six reports of 2.16.31 (but none the last couple of days) and now the first report of 2.16.51 on a P85D after it received its ludicrous update at the...

You know me well, Andy - I think that's exactly what it boils down to.

Interesting. I have long given up on reporting things to Tesla. If a single one of my reports had lead to it actually being fixed I might have continued... but frankly I don't think they care one bit. If it's not useful to hype the stock it's not happening. And since there are clearly hundreds...

Interesting - after 321 reports for 2.16.17 we now have a first entry for 2.16.31 - andrewket in his Model X... Andrew, you get to name that one :-)

Sorry, I vehemently disagree. The whole reason the tracker was started was to remove the "I've got it" posts. They don't provide "voice", they provide "noise". No one is suggesting that people who have an observation or a useful (or funny) comment to make not do that. That would be their...

That's pretty massive That's plain weird. I have had my rated miles not drop for the first couple of miles driven, especially if a charge finished just as I unplugged, but I have never seen it go up (unless going downhill enough to add 3 rated miles). Very odd. That has been the case for me...

178 reported installs of 2.16.17, the highest number since the very broad roll-out of 2.12.126. reports from around the world, all batteries, models, types... this seems to be the next full 7.1 version...

I'm as always impressed with Tesla's focus on what its customers need the most... and apparently that psychedelic cow bells. :facepalm:

My P85D went from 2.12.126 to 2.16.17, skipping all the versions in between. The 90D is still on 2.14.66 So Tesla continues to give us a new middle digit at a surprising rate...

Well, I have stopped using TMC at all. I just come back to this thread with a direct link to it on my desktop machine when I see something interesting in the reports. Like I just did this morning... First report of 2.15.16! They are treating the middle number as if there was an unlimited...

2.14.66 continues to roll out in a rather odd pattern. 130 reports in 48 hours, but barely anything since then (3 or 4 a day). Normally a "full" roll out gets us 300-400 reports, we have only 146 total for 2.14.66 (and only one of my two cars has received it, yet). It feels like it was pushed...

Very good points. Yes, a prioritization for super charger enabled cars makes perfect sense. We now have one VIN 3xxx report and a couple reports from 60s, which apparently are both super charger enabled. Still no P85+ but at this point I'd say this is clearly a full on roll-out with possibly a...

Seems that my request for a clear sign of "this is the next one" was heard :-) We already have 67 reports for 2.14.66 installs (that's the most we had in one day in a long time) and the coverage seems truly broad. 9 countries (the most since 2.12.126), Model S&X, most battery sizes (40 and 60...

100% agree. We don't no one way or the other. I'll leave the beta testing to the people who signed up for it. Thankfully the firmware tracker makes this easy. Once I see a build with hundreds of installs I will wait for the next "new upgrade" notification on my phone and then upgrade. Until that...

See, as a former eleven green bar poster I think the new design solves my biggest problem with TMC. I was spending way too much time here. But thankfully the forum has now become as usable for me as the TelsaMotors forum. Which means I will simply stop wasting time here. I will continue to post...

No, we've never had anything even remotely close. As I said. Be careful out there. You are being used as testers for experimental software. I am now declining updates (again) on both of my cars.

I don't think this has anything to do with Model 3. Model 3 is several years out (yeah, yeah, 2017, yada yada, whatever. Model X was 2013 based on that.. moving on) I think they are chasing a lot of bugs across their increasingly complex and diverse hardware footprint. I hear from insiders that...

Thanks for doing that. The wheel of firmware releases continues to spin rather fast. In the last six days we have seen reports for six different builds: 2.13.{77,103,120,170} and 2.14.{17,50} (well, technically we also had a 2.12.126 report but that came so long after the bulk of them that I...

Nope, the new one doesn't beep at all when closing and when I asked my DS told me that that is a very recent change.

It seems that the inflation of middle digits is not correlated to actual progress (or even noticeable changes) on the firmware itself. And after 18 reports on pi day it seems we are not really seeing a push for 2.14.17, either. Yet more beta testing (with production cars) it seems.

Between the incredible waste of white space and the 20 posts per page this has dropped significantly in usefulness to me. At 100/page and with some greasemonkey the old design was reasonably dense and readable. This? Oh well, I guess it's time for my bi-annual break from TMC.

As many others have demonstrated in this thread - random failures, tried many times to post and can't quite tell if the posts went out. Database errors. S-L-O-O-O-O-O-W. And as wk057 said in another thread. The 20 posts per page things is terrible. Oh, and no tapatalk? Hmm.

15 reports of 2.14.17 Mostly in Europe. Apparently brings Summon in some countries there. The middle digit inflation continues. (and remember that 'digit' is used both for a number and a finger...)

We got only a coffee cup, two pens and an umbrella... but then the car was dirt cheap at 102k...

Great color :-) My wife approves And from your picture it seems that they moved to the new delivery facility a lot longer ago than I thought.

It has proven so exceptionally useful... I can't tell you how happy I am that you convinced me to go your route instead of mine - there's no way we'd get this much participation with a wiki. Well done. And right now it's showing us that apparently Tesla is doing an A/B test right now. Clearly...

Not a spreadsheet... a super fancy web application: Tesla Firmware Upgrade Tracker Web App

I think they've only had the bow since they moved to the new indoor delivery area a few weeks ago