dirkhh
Middle-aged Member
To reduce clutter and stretch the timeline... could you drop the 6.1 data? Or make this user selectable as well?
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
Bugs in firmware 6.2
- Thread starter onasj
- Start date
SeminoleFSU
Voluntaryist
Sorry, short term memory, couldn't remember from the walk from the car. .136 . I tried starting from scratch a couple of times without success. First time in 2+ years I've had a BT problem that lasted more than a few minutes.
dirkhh
Middle-aged Member
Looking at this data and playing with the knobs, I see:
1. 124 was generally released ~3/26; issues were found and addressed relatively quickly (by 4/02)
2. 136 was generally released ~4/02; issues were found and addressed relatively quickly (by 4/10)
3. 153 was generally released ~4/10; they might choose to drop a new release on 4/17ish as a general rhythm thing
4. All of the "late" 124s (post 3/26) were non-Perf (i.e. uncheck P85 P85+ P85D and they remain in the chart).
5. Only 2 reports of non-Tech-package in the data.
6. No reports of P85D or 85D getting 136.
Someone more attuned to release management could probably draw some decent conclusions about branches/forks from that data.
dirkhh
Middle-aged Member
Haven't seen that one. So you click on the little 'x' that you don't want and route to your next meeting and it comes back? Right away? Or while you are driving? Is it the same meeting? Or the next one?
I don't think I've ever had it pop up after the first minute or so of driving...
I dismiss the whole pop up, by clicking the X in the upper left corner of the pop up.... Sometimes after selecting a meeting, sometimes without selecting anything. The pop up returns shortly afterwards, or at some random times... Have not tracked that yet, since I'm usually driving and need to dismiss it. Happens soon after starting, rather than many miles down the road.
dirkhh
Middle-aged Member
So this sounds almost like something that I've seen. If the calendar is open and you dismiss it right as you start the car, then maybe a minute later I sometimes get the dialog for the next meeting which I then have to dismiss again.
But not "at random times" - only within the first minute, actually, I'd say the first 45 seconds of driving. And I don't recall ever having to dismiss the same alert twice, so if the alert came up while the calendar was open and I dismissed it, then it doesn't pop up again.
NigelM
Recovering Member
Returning to the auto-mute discussion: I rec'd .153 a couple days ago and now if I turn off the audio completely before exiting the car it automatically starts playing when any door (incl trunk) is opened. Auto-mute has mutated to auto-play!
Edit: yesterday this was reproducible, my wife tells me that today it didn't happen.
Last edited:
I think my S behaved that way before I got V6.2 two days ago.
Or perhaps I do not understand what you mean by "turn off the audio completely "?
One bug I noticed today: when driving in moderate to heavy rain, the blind spot warning chimes every time I change lanes. Even though there is never a car there. I think the sonar is mistaking raindrops for a car. Funny thing is that the white blind spot indicator isn't lit, but the warning sound (along with RED indicator lines) appear as soon as the car starts moving over.
NigelM
Recovering Member
I meant when you click the left scroll wheel so that audio volume is completely off. Pre v6.2 the volume resumed where it was previously, so off meant off until you increased volume again.
OK, I'm calling this a bug!
This clocks on console and dash displays both have a gratuitous "0" zero in the tens of hours digit, when it should be blank.
This is not military time, otherwise, I'd understand.
Before 6.2 the time would display like this, 8:32 am <<<----- MUCH PREFERRED TESLA!!
Now, with 6.2, time displays in both places like this, 08:32 am <<<---- semi-military style... kinda dumb for human drivers
It's the first thing my son noticed after the upgrade yesterday, "Why is there a zero in the time now?"
There shouldn't be.
It actually takes my eyes slightly longer to read time and have to filter out the first 0.
Hope this bug is taken out soon.
This clocks on console and dash displays both have a gratuitous "0" zero in the tens of hours digit, when it should be blank.
This is not military time, otherwise, I'd understand.
Before 6.2 the time would display like this, 8:32 am <<<----- MUCH PREFERRED TESLA!!
Now, with 6.2, time displays in both places like this, 08:32 am <<<---- semi-military style... kinda dumb for human drivers
It's the first thing my son noticed after the upgrade yesterday, "Why is there a zero in the time now?"
There shouldn't be.
It actually takes my eyes slightly longer to read time and have to filter out the first 0.
Hope this bug is taken out soon.
Last edited:
dirkhh
Middle-aged Member
It sometimes rains here in Oregon. I've had this happen a couple of times, but definitely not EVERY time I change lanes.
Yup...same here.
And it would be so easy to fix. 2 possible ways :
1) If AM/PM is selected, and 0 is the far left digit, only display the 3 right digits.
0r
2) If AM/PM is selected and 0 is the far left digit, color the far left digit to be grey (the same color as the bar, so we can't see it).
There's no mystery for fixing a bug like the clock display leading zero.
Tesla doesn't have to fake anything out, they own the code, and had it right pre-6.2.
Simply don't include a pre-pended zero in the display string, make it a space.
If offering a display setting option to the user for 12hr/24hr clock choice... then, having a leading zero on 24hr display is proper "military style" to show and pronounce leading zero for hours < 10:00 (which is always a.m. on a 24 clock).
If Tesla wants to stick with military style then they should also drop the "a.m." "p.m." thing on the end if a user has made the setting selection for 24 clock.
Right now, time display straddles the two styles. MAYBE clock is now displaying "Tesla Time" or "Elon Time" (things run slower than expected).
Someone mixed something up in the code.
Put it back to the way it was please!
Tesla doesn't have to fake anything out, they own the code, and had it right pre-6.2.
Simply don't include a pre-pended zero in the display string, make it a space.
If offering a display setting option to the user for 12hr/24hr clock choice... then, having a leading zero on 24hr display is proper "military style" to show and pronounce leading zero for hours < 10:00 (which is always a.m. on a 24 clock).
If Tesla wants to stick with military style then they should also drop the "a.m." "p.m." thing on the end if a user has made the setting selection for 24 clock.
Right now, time display straddles the two styles. MAYBE clock is now displaying "Tesla Time" or "Elon Time" (things run slower than expected).
Someone mixed something up in the code.
Put it back to the way it was please!
NigelM
Recovering Member
This should be around #53 on the priority list. Sure correct it, but it's beyond a #firstworldproblem.
Similar threads
