-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Has anyone called Tesla asking for a rollback to V8?
- Thread starter Barry
- Start date
wraithnot
Model 3 VIN #2942 Model S VIN #5785
Lots of Model S owners are unhappy with v9. But so far I haven't heard of anyone being allowed to rollback to v8 (I was told it wasn't possible). The most encouraging information I was able to find is in this post: Petition to demand "camera on top, media player on bottom" be retained in UI
There is also a petition here: Sign the Petition
There is also a petition here: Sign the Petition
Tam
Well-Known Member
Historically, Tesla doesn't do a "rollback".
What it could do is to tell you to apply the next update to get what you lost currently.
That happened to Model S and X that used to have +12/-12db equalizer sliders.
That's when someone was really smart and noticed that Model 3 owners only had a maximum of +8/-8 equalizer sliders and none of Model 3 owners complained!
Ah hah! Satisfaction guaranteed: Tesla then matched that Model 3 feature to S and X and all equally got +8/-8 equalizer sliders.
A few of us then complained that we ain't no Model 3 so +12/-12db equalizer sliders feature was then restored to S and X at the next update.
Thus, Tesla has a history of takeaways for Model S and X if you don't watch them and don't complain of the loss.
So, please write to Tesla if there's any features were taken away (such as top-half/bottom-half independently user configuration).
Providing the ability to rollback to the last stable software release has been a feature I've been requesting (for years).
When a new release is installed, it's more than just updating the software on the console and dashboard processors - there are many processors in the system. And unless Tesla has designed the software and tested it to support rollback, it may be difficult for Tesla to do this (at least doing an OTA rollback or at a Service Center).
Supporting rollback to any arbitrary version would be extremely difficult due to the many vehicle configurations and prior versions. But they could pick a specific prior version - add support for rollback to that version - and then instruct their internal and small group of hand-picked external beta testers to test the rollback.
Since Tesla's internal and external beta testers often miss obvious bugs and design flaws in major releases, providing the rollback feature would give owners more control over the software in their vehicles - and if they objected enough to the contents of a new release, they would have the ability to get back to the previous software release.
As for rolling back V9 to V8 - seems highly unlikely. Like with previous major releases (V8, V7, …) - they will likely address major bugs and design flaws in subsequent updates - and it's better for them to focus their resources on doing that than figuring out how customers or the Service Centers could support rollbacks to V8.
When a new release is installed, it's more than just updating the software on the console and dashboard processors - there are many processors in the system. And unless Tesla has designed the software and tested it to support rollback, it may be difficult for Tesla to do this (at least doing an OTA rollback or at a Service Center).
Supporting rollback to any arbitrary version would be extremely difficult due to the many vehicle configurations and prior versions. But they could pick a specific prior version - add support for rollback to that version - and then instruct their internal and small group of hand-picked external beta testers to test the rollback.
Since Tesla's internal and external beta testers often miss obvious bugs and design flaws in major releases, providing the rollback feature would give owners more control over the software in their vehicles - and if they objected enough to the contents of a new release, they would have the ability to get back to the previous software release.
As for rolling back V9 to V8 - seems highly unlikely. Like with previous major releases (V8, V7, …) - they will likely address major bugs and design flaws in subsequent updates - and it's better for them to focus their resources on doing that than figuring out how customers or the Service Centers could support rollbacks to V8.
Instead of rollback, ask for an UI that is at least as flexible as the old was.
It's not going to happen. Primary reason why it won't is that if they were to do so, they'd have to fork the software and maintain multiple copies forever. You may say that you can live without any new features, but that's not the problem. If there are any safety issues, they have to be fixed and having to maintain multiple versions is hugely expensive.
By the way, are you still running Windows 95?
By the way, are you still running Windows 95?
If you do software design right, that doesn't have to be a huge task. You may unify the code base in the backend code, but have different GUI. You separate the logic and backend stuff from UI. This is not anything new. There's zillions of manufacturers etc that mantain different products with different looks.
For the premium you pay for a premium car you should have more bells and whistles.
And on a screen that has a completely different layout (portrait vs landscape) and a different position (low vs high), you HAVE to have different designs. Microsoft tried to force the tablet paradigm onto the desktop in Windows 8 and it failed miserably, and they had to backtrack and add a proper start menu again. Model S is not Model 3. A desktop PC is not a tablet.
No, I didn't have enough memory in my Commodore 64 for that upgrade.
whitex
Well-Known Member
No matter how you modularize, supporting older versions of software always creates a for which has to be maintained by fixing all found vulnerabilities and running each fork through a full release test. Then there is the fact that the old fork is no longer supported by open source of whoever sold you the libraries, so you either have to port the old software to use new kernel or libraries, or have to sift through vulnerability reports and have security experts try to assess whether the new found vulnerabilities affect the older, no longer supported by community, software.
While I really don't like v9, and neither does my wife, I know all to well what it takes to support such old forks. To give you an idea, I looked at some data for supporting some safety critical software recently from a vendor. It went something like this: 1 year was included, 2-3 years was ~$200K per year, years 4-7 were $1M per year, years 8-12 were $5M per year, 12-15 were estimate about $15M per year. The same company offered upgrades to latest version within the $200K per year support, so if you continue to upgrade, you can pay $200K per year forever.
It's not about supporting older software, but adapting different UI to different types of screens / products that work well with those products. It's STILL different UI today, it has to be because the cars are indeed different. But they're trying too hard to make it the same. It's not more work, it's not a technical limitation, it's a design decision.
Many people want to downgrade to 8 because of the bad UI, not because of the features in EAP etc. Again, not about supporting old legacy software, but rather have UI better adapted to the S/X models instead of a forced unification like Microsoft tried with Windows 8, which failed horribly.
Similar threads
- Question
