Wondering, if we have the "opt-in" firmware, are we stuck with it until we get it? Seems we should have gotten something for us waiting in the middle of the 90's score.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Stuck in 2021.32.22?
- Thread starter bobby g
- Start date
Yea, I think it’s stuck until your score aligns with their roll out score criteria or you opt-out and update to the newest production software.
Which is weird because when we got rolled back from 10.3 due to a bug, we went to 36.5.1 and still had the safety score and the opt-in button on there.
Which is weird because when we got rolled back from 10.3 due to a bug, we went to 36.5.1 and still had the safety score and the opt-in button on there.
IronCoffee_Max
Member
Commuting 26 miles on I25 in Denver, and trying super hard to keep good follow distance and using NoA 99% of the time, still getting follow and fcw in the safety score of 8x, don’t think I’ll ever be in beta. So I’m going to opt out and hope I can get to a future update.
Lets see if I understand the firmware update situation as it currently stands now. If you have the firmware version that has the button to request the FSD, you must decline to get newer production releases? If you decline, requesting FSD beta at a future date is currently off the table? If you request the FSD beta firmware and do not have a good enough score to receive it or chose not to install it when you do, will you get firmware production updates that have new features?
Last edited:
I don’t think anyone knows how it really works lol. @AlexParker let us know if opting out will push you the latest production build.
opt out and leave it long enough for the safety score to disappear from your phone app - than can take several hours.
Then rejoin later and you will be rewarded with a zeroed out safety score.
Best strategy seems to be, opt out on Monday, opt back in on Wed/Thursday or enough so you can drive 100 miles by Friday.
Set the car on medium for FCW so you know when that has triggered.
If you think you've got unsafe following or a FCW trigger - pull over and reboot the car, that will clear out the current drive so it doesn't hit the score.
Keep it at 99 or 100 by Friday
FYI - unsafe follow is usually over 50mph, so stay below that before engaging NOA and slow down to <50 before disengaging.
However, as with all things FSD beta - YMMV
I'm also still stuck on 2021.32.22.
I opted out a few days ago. Had a 97 at the time. My safety score disappeared pretty quick from the app.
I opted out a few days ago. Had a 97 at the time. My safety score disappeared pretty quick from the app.
Are you opting back in or waiting for a production release update?
Some say opting back in, keeping score at 100 and driving 100 miles got them into beta.
Some say opting back in, keeping score at 100 and driving 100 miles got them into beta.
Similar to what I'm thinking. My shortest commute is 35 miles each way and often through one of the busiest interchanges in the states. Holding at 97 with little hope of getting higher.
I'm not planning to opt back in. I'd just like to get to 2021.36.5.1 (10.3 without FSD Beta), or later version.
And this will get me the beta FSD? I been on 92 safety score for a while but if this trick works that would be awesome.opt out and leave it long enough for the safety score to disappear from your phone app - than can take several hours.
Then rejoin later and you will be rewarded with a zeroed out safety score.
Best strategy seems to be, opt out on Monday, opt back in on Wed/Thursday or enough so you can drive 100 miles by Friday.
Set the car on medium for FCW so you know when that has triggered.
If you think you've got unsafe following or a FCW trigger - pull over and reboot the car, that will clear out the current drive so it doesn't hit the score.
Keep it at 99 or 100 by Friday
FYI - unsafe follow is usually over 50mph, so stay below that before engaging NOA and slow down to <50 before disengaging.
However, as with all things FSD beta - YMMV
That's what others have reported. It seems you need the min safety score and 100mi of driving. Elon originally also said 7 days, but there are lots of reports where it seems that's not the case. Like @Twiglett said, seems like opt out / back in around Monday, keep 100 score for the week, and you'll get it on/around the weekend.
My score was 98 and changed to 99 on this past sun, and I got in in yesterday's (Friday) wave. I never reset though.
Keep in mind there are also reports of people who have had 100/100 scores for a while and still don't have it even having never opted out/in. They seem to be in the minority though.
IronCoffee_Max
Member
Commuting 26 miles on I25 in Denver, and trying super hard to keep good follow distance and using NoA 99% of the time, still getting follow and fcw in the safety score of 8x, don’t think I’ll ever be in beta. So I’m going to opt out and hope I can get to a future update.
What I do wish is Tesla would not keep us on .22 and let us upgrade to .36.8 like my wife’s car. I’m the one of the two cars that could use the charging scheduling from the app.
I wasn't really not interested in FSD beta, just more curious what Tesla would consider my daily driving to be. I do want the new visualizations and eventually one stack NoA, but I don’t want the beta of those as they currently are. So now that I’ve seen that the driving score is completely useless for me and my commute, I’m fine waiting for FSD beta to improve.opt out and leave it long enough for the safety score to disappear from your phone app - than can take several hours.
Then rejoin later and you will be rewarded with a zeroed out safety score.
Best strategy seems to be, opt out on Monday, opt back in on Wed/Thursday or enough so you can drive 100 miles by Friday.
Set the car on medium for FCW so you know when that has triggered.
If you think you've got unsafe following or a FCW trigger - pull over and reboot the car, that will clear out the current drive so it doesn't hit the score.
Keep it at 99 or 100 by Friday
FYI - unsafe follow is usually over 50mph, so stay below that before engaging NOA and slow down to <50 before disengaging.
However, as with all things FSD beta - YMMV
What I do wish is Tesla would not keep us on .22 and let us upgrade to .36.8 like my wife’s car. I’m the one of the two cars that could use the charging scheduling from the app.
NJEV-Don
Member
Very annoying. Been stuck on this too for what seems like forever.
SalisburySam
Active Member
Just now installing v2021.32.30 from v2021.32.22. Pressing the FSD button on 32.22 but quickly went from 100 to 92, then opted out. Got this update three days after opting out but don’t know if there’s a correlation. Looks like I’ll get the opt-in button with 32.30 according to TeslaFi. 32.30 Release Notes
Similar threads
