There is. I posted about it just a few posts up, in post number 175. Here's the excerpt, from another thread:
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
New Equalizer In Version 8.0.2.50.114 - Please Share Settings
- Thread starter Andyw2100
- Start date
-
- Tags
- Model S User Interface
There is. I posted about it just a few posts up, in post number 175. Here's the excerpt, from another thread:
IMHO where the settings reset to really doesn't mean much, the fact is that the setting are unstable and that this is a bug that is well known and should be fixed ASAP. why a fix for this issue hasn't been pushed out should be the topic of discussion not these repetitive where my settings are posts.
thecloud
As rhythm raced inside, the ship came alive
I'd imagine the fix has probably been ready for some time but didn't merit its own release while everyone is focused on the AP2 update, which is already later than promised.
Funny thing: I was reading an article this morning about how the new Republican congress had their priorities changed by a Trump tweet. Then I remembered he has a tech adviser who has some experience in that area.
ArtInCT
Always Learning
I emailed service as soon as I got the update and noticed the bug. Received and email back from a specialist about 5 days ago indicating they are aware of the bug in the equalizer and it will be fixed in a future release of the firmware. I wonder if any of the more recent releases (>,112) contain the fix??
SabrToothSqrl
Active Member
George Jetson
Member
Is everyone on this thread still on the 2.50.114 update? I initially had the EQ reset thing going on, but after I reset my driver profile it has been rock stable. Sorry to say, I wasn't attentive when I posted; I have the 2.50.180 update, not the one in the subject line. My apologies.
f-stop
Active Member
FWIW I am on 2.50.114 since 12/22. No EQ resets at first. As I reported on 12/26, I saw the EQ settings get reset just once, just after I got a "Touchscreen unresponsive" message on the dash and did a reboot - immediately after that reboot all the EQ settings changed to +3.5.
The EQ settings have not reset by themselves since I changed them after that point [touch wood]
The EQ settings have not reset by themselves since I changed them after that point [touch wood]
Egg on my face, as they say....
I was wondering why no one else was reporting a "random resetting of the Fader control". I reported as such, along with the equalizer resetting, to Tesla.
Turns out that the random resetting of the fader was of my doing I opened up the equalizer/Fader window to adjust the equalizer and when finished I pressed the "X" in the upper left corner to close the screen (so I thought), but it seems that in attempting to hit the "X" I was also touching the fader screen and causing it to reset to the back-left of the car.
I wrote back to Tesla and made them aware. They probably will get a good laugh out of this.
Sometimes it really comes down to an ESO problem.... Equipment Superior to Operator!
I was wondering why no one else was reporting a "random resetting of the Fader control". I reported as such, along with the equalizer resetting, to Tesla.
Turns out that the random resetting of the fader was of my doing
I opened up the equalizer/Fader window to adjust the equalizer and when finished I pressed the "X" in the upper left corner to close the screen (so I thought), but it seems that in attempting to hit the "X" I was also touching the fader screen and causing it to reset to the back-left of the car. I wrote back to Tesla and made them aware. They probably will get a good laugh out of this.
Sometimes it really comes down to an ESO problem.... Equipment Superior to Operator!
hmmm
Member
So there may be hope sooner rather than later. Anyone else on 2.50.180? Also, is your fader/balance staying put now? (Assuming your car had that issue too...)
hmmm
Member
hmmm
Member
thecloud
As rhythm raced inside, the ship came alive
Yes, it would be, except 114 is higher than 27.
"2.50.114" is not a decimal-point number. It's three separate counters tacked together; presumably they represent something like a release train (2), version (50), and build (114). As long as the first two counters remain unchanged, each new build of that version would be expected to bump up the last number by one.
Or at least that's how it appears to work, given standard practices for software versioning and observing the pattern over the past few years.
Last edited:
I wonder if it's .270 but another "bug" is displaying it like a decimal number and dropping the last zero?
