To get into the beta your firmware level would have to be downgraded from 2022.4.5.16 to 2022.4.5.15. Since Tesla usually doesn’t downgrade cars you likely have to wait until FSD beta is released on a version higher than your current one.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Wiki FSD’s Earliest Adopters Still Waiting
- Thread starter Lowchrg
- Start date
Seattle Tom
Member
Exactly as Sigma pointed out above, Tesla as a general rule doesn’t roll back to earlier FW. It only goes forward, not back.
I’m happy to have an exception disprove the rule here, but I can’t recall an instance of that happening over years of owning a Tesla and watching FW releases.
But it can like when FSD Beta 10.3.1 (2021.36.5.3) went to about 2% already on 2021.36.5.5 and maybe even 1 vehicle on 2021.36.8:
2021.36.5.3 Official Tesla Software Update - Teslascope
The release notes and other metrics for the Tesla software update, 2021.36.5.3.
teslascope.com
And "downgrading" from say 2022.4.5.16 to 2022.4.5.15 could still include everything in the "larger" version as Tesla can allocate version numbers (especially the 4th number) however they want without strict dependencies on previous versions. Tesla knows they need a different version for merging in FSD Beta behavior, so .15 and .16 could have been created at the same time knowing both would have the same bug fixes.
If Tesla used 5 numbers for versions, FSD Beta 10.11 could have been 2022.4.5.16.1 instead to perhaps more clearly identify that the FSD Beta version should include everything from the "parent" version. I suppose why didn't Tesla version 2022.4.5.16 as 2022.4.6 instead so that FSD Beta could be 2022.4.6.1?
Maybe internally they have some special meaning for the 3rd number, but seeing how they picked 2021.44.25.* for the Holiday/Christmas update, it seems like it can be pretty arbitrary as well (whereas the first 2 numbers are date based).
Seattle Tom
Member
The 10.3.1 debacle is a good example of a rollback. But that was driven by major issues, not just “oh we should add these folks to the Beta because otherwise we are just complete assholes.”But it can like when FSD Beta 10.3.1 (2021.36.5.3) went to about 2% already on 2021.36.5.5 and maybe even 1 vehicle on 2021.36.8:
2021.36.5.3 Official Tesla Software Update - Teslascope
The release notes and other metrics for the Tesla software update, 2021.36.5.3.
And "downgrading" from say 2022.4.5.16 to 2022.4.5.15 could still include everything in the "larger" version as Tesla can allocate version numbers (especially the 4th number) however they want without strict dependencies on previous versions. Tesla knows they need a different version for merging in FSD Beta behavior, so .15 and .16 could have been created at the same time knowing both would have the same bug fixes.
If Tesla used 5 numbers for versions, FSD Beta 10.11 could have been 2022.4.5.16.1 instead to perhaps more clearly identify that the FSD Beta version should include everything from the "parent" version. I suppose why didn't Tesla version 2022.4.5.16 as 2022.4.6 instead so that FSD Beta could be 2022.4.6.1?
Your number schema explanation gives me a little hope, but only a little. I hope you are right!!!
tezlaMXUR17&24
Member
I’m on 97 right now thanks to stupid FCW and unavoidable hard braking I picked for my weekend long trip, should I reset my score and drive 100 more miles or just wait it out? I read Elon tweeted he may lower the SS score to 95?
backinthelab
Member
Well, it looks like now there's 2022.8.2 which is branching off of 2022.4.5.3 (version I'm currently on). Still don't have any update pushes to my vehicle, although I do have a service appt coming up. I hope they don't upgrade it to 5.16 when it's there.
How do you know that 2022.8.2 is branched from 2022.4.5.3?
It appears that 2022.8.2 is going to European cars only so far...
backinthelab
Member
Maybe "branched" is the wrong term, but all of the vehicles being updated to 8.2 were previously on 4.5.3.
hybridbear
Active Member
For now based on TeslaFi data it seems like that version is going to Europe. Only 1 USA car shows that it has it... that could change though.
HELLAWATTS
Member
From my own experience if you’re pushed a new update it will stay in your car’s queue. I don’t think a newer update will be pushed to your car until you download the older one. That’s just my observation but correct me if I’m wrong.
EVNow
Well-Known Member
They will first upgrade current testers before pushing to new testers, going by how they handled this so far.
So, if everything goes well, we should see a big push to current testers tonight. New testers would be added in a couple of days.
TeslaFi.com Firmware Tracker shows that there was a small ~40 rollout for 10.11 today going to mostly legacy S/X including a 2016 S.
Maybe there was a rollout misconfiguration yesterday accidentally excluding older S/X and today corrected it as the intention for FSD Beta 10.11 was to include all eligible vehicles including those with RCCB retrofit, so that does make it more likely that others here will be eligible to be added to FSD Beta with 10.11. (Also possible that Autopilot internal testing was still evaluating 10.11 on legacy S/X and only completed it today but didn't want to delay yesterday's initial rollout.)
Yeah I do see that 2016 Model S. Whoever it is has had FSD since the new years rollout though, so they aren’t new to the program. Good to see at least that a 2016 vehicle is getting 10.11 today though. Hopefully we’ll see some first timers added with 10.11. I’ve been waiting so long and am very optimistic about getting it this week
Similar threads
