gmorales
Member
Thanks Bruce. You got it right! Feeling a little bit better as I'm not alone is this use case...
Is there an email address or web form to report these types of situations to Tesla ?
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Thanks Bruce. You got it right! Feeling a little bit better as I'm not alone is this use case...
Is there an email address or web form to report these types of situations to Tesla ?
Alex D
Member
You can send email to [email protected], and they'll probably acknowledge it, but who knows if it'll actually get fixed.
Bruce.
If a bug bothers you, you should definitely do this. Number of customer complaints to customer service is definitely a key metric used in the industry to prioritize bug fixes and/or convince engineering to reconsider.
JenniferQ
Active Member
So it seems everyone except for 5 of us have gotten 2.40.21, according to firmware tracker. I am one of those 5. My "equalizer" resets to 0 now, except for bass, tg. I haven't been able to keep up, but is there a list somewhere of what was "fixed" in this iteration?
I guess I'm one of the 5 too?
Even went into service for a service appointment last week and still haven't gotten 2.40.21
Bet TSLA
Active Member
Hmm. I just picked my car up from the Palo Alto service center yesterday. It got 2.40.21 while it was there.Even went into service for a service appointment last week and still haven't gotten 2.40.21
Thanks for the heads up! 1 of 5 here too. Maybe I'll swing by the sales center sometime this week...
Just to look at some showroom Teslas... yeah that's it, just to look...
nothing to do with the hope that geo-fencing might work...
Bet TSLA
Active Member
Oh, you were serious? You're reading it wrong. That should be obvious from the fact that it says that 782 cars are reporting. Not much overlap between those who have gotten 2.36.108 and those on 2.41.21. If you look at the Full Data Extract table, you'll see that most US cars are still on the earlier version.
As I mentioned, I was updated yesterday at a service center, presumably because I had work done that required firmware. I suspect if I hadn't had such work they wouldn't have updated me to the latest. They seem to be being very conservative with this rollout.
Has anyone noticed if 8.0 is more prone to false FCW's?
In my entire 2+ years of having a Model S with the AP hardware I've never had a false FCW's. But, now with 8.0 I've had my first one in a situation where there was absolutely nothing it could have triggered off of. Perfect weather and the car it red flagged was at least 3-4 car lengths ahead.
Having one versus zero is obviously statistically irrelevant, but I'm curious what other people are experiencing to see if there have been any changes with it.
In my entire 2+ years of having a Model S with the AP hardware I've never had a false FCW's. But, now with 8.0 I've had my first one in a situation where there was absolutely nothing it could have triggered off of. Perfect weather and the car it red flagged was at least 3-4 car lengths ahead.
Having one versus zero is obviously statistically irrelevant, but I'm curious what other people are experiencing to see if there have been any changes with it.
My understanding is that Tesla has tied geofenced updates to cars that have service tickets now so i am very interested to hear how it works out for you.Thanks for the heads up! 1 of 5 here too. Maybe I'll swing by the sales center sometime this week...
Just to look at some showroom Teslas... yeah that's it, just to look...
nothing to do with the hope that geo-fencing might work...
Do we know that 2.40.21 is indeed an improvement / upgrade? From what I have been reading on this tread it seems to be a slightly different version for outside the US, but not necessarily an improvement as such. Did I misunderstand that?
BertL
Active Member
Some are reporting 2.40.21 includes USB as part of the newer Media Search function that first appeared with 2.36.108.
I can't confirm that as I'm still on 2.38.19 which my SvC installed on Tuesday (When I queried if I could get 2.40.21 as a few others in the US had received, their remark was I received the latest version available for my VIN. It's our guess as to if that meant forever or just temporarily.
)This is very impressive and amazing if they can pull it off by December.
I have the impression that many of the features will only be available for the new autonomous driving hardware, though. With the new sensor and camera hardware being so different, I am somewhat concerned that Tesla will start focusing on this new hardware and not address the issues for our current hardware let alone continue to improve features for "old" cars (mine is 3 months old).
Bet TSLA
Active Member
Today's Tesla coffee-and-cars social (Sunday, October 23), is about "giving you a deeper look into our newly released Software 8.0, our most substantial update to the touchscreen and its apps since we launched Model S over four years ago."
JenniferQ
Active Member
Hm. I'm confused then, because when I look at the tracker it shows almost 400 cars with 2.40.21. And about an equal number with the first version of 8.0. Are all of those outside the US?Some are reporting 2.40.21 includes USB as part of the newer Media Search function that first appeared with 2.36.108.
I can't confirm that as I'm still on 2.38.19 which my SvC installed on Tuesday (When I queried if I could get 2.40.21 as a few others in the US had received, their remark was I received the latest version available for my VIN. It's our guess as to if that meant forever or just temporarily.
BertL
Active Member
No, not all are outside the US, but to me it appears a large percentage are... Many other countries e.g. didn't get the first drop of 8.0 like say I (and only some MS) did here in the US. I don't try to understand the tracker info as much as some others, so I'll let them chime in to help your understanding.
My post was only trying to respond to @Wanderer's question about new functionality that 2.40.21 may have opposed to the two previous releases of 8.0 my MS has received. Some of us are above our eyeballs in 8.0 USB anomolies and workarounds, so I had a bit of POV on USB Search being reported by others as first entering the scene with 2.40.21 wherever that is being made available.
2.40.21 was the first version rolled out to Xs, as well as international folks.
I do indeed have USB in the voice or text search in my X.
MarcG
Active Member
Ok I've now tested the last scenario I described above, and the behavior isn't what I would expect. Here's how it went down:
1. AP engaged in a 50mph zone, max speed possible is 55mph - fine. TACC set to that speed.
2. 40mph zone ahead: as soon as the car passes the 40mph sign, the car slows down to 45mph - fine. Max speed I can set is 45mph, and as you know pushing the TACC stalk up no longer increases beyond max speed - not great, but can live with it.
3. 40mph zone is over, speed limit is now 50mph again. After the car passes the 50mph sign, which it recognized and updated the IC with the new speed limit, car still travels at 45mph - NOT fine. Max speed that was set to 45mph does not revert to 55mph.
Keep in mind that during this whole period there was ZERO input from the driver besides keeping hands on the wheel.
I would expect the car to resume max speed to 55mph after the 40mph zone is over. I mean, I was in a 50mph zone to begin with!
That's a significant change for the worse for me; I set the limit to 60 and the car adjusts up and down to the variable speed limits on my commute. With 8 it will only adjust down and require more user input.
