croman
Well-Known Member
Pin to drive is only to protect you aginst "honest" people. real thieves would just plug into in-car network and drive away.
You scare me. Like awe, not terror. But still damn...don't get near my car.
You can install our site as a web app on your iOS device by utilizing the Add to Home Screen feature in Safari. Please see this thread for more details on this.
Note: This feature may not be available in some browsers.
Pin to drive is only to protect you aginst "honest" people. real thieves would just plug into in-car network and drive away.
Tesla really, really, need to get some better software validation procedures in place before they unleash these dodgy updates on us all. Amazingly they've re-introduced the not being able to log in to Spotify bug again, that was only fixed in the last update and it's back, what the!!I'm also having to reboot my MCU1 every day now. Pin to drive keypad seems to move around the screen and no longer be central. I've also had it freeze. Bluetooth is a mess. Delays answering after I click answer call with the wheel button and the muted issue also for me. Web browser will actually load a web page for me now. But after viewing a few pages seems to crash and go blank.
Tesla MCU QA department deciding on release stability.They need a QA department, testing all hardware and software revisions. And I do mean actually testing it. not just sitting with a virtual machine or whatever in the office with top wifi connection.
This is pretty possible if not likely the case!Having done my emulator time this smelled like fish from the beginning. This deserves an incredible amount of attention. I wonder if they are subtly trying to gauge the backlash from MCU1 owners when real features start to be differentiated. For the record the Tegra2 platform is not as shitty and behind the times as many might think. In my opinion the UX could be radically improved from its current state.
Yea, I tried it again, it seems the app is fighting with the car what the setting should be, resulting in a completely undefined setting where the app and GUI and the actual controls are completely out of sync (e.g. app and big screen in the car shows steering heat wheel is on, but the steering wheel heat doesn't know that, so it really isn't). A true example how Tesla releases their software, slap something together which looks pretty, let the customers figure out what doesn't work. Honestly, really sad. I work with automotive companies and yes, they take their sweet time and it's frustrating sometimes, but at least they think about testing the stuff they release so it works for a large majority of users.It works for me. 2018 MS.
2) same here
3) They were fairly responsive. If you press and hold the driver's seat, all of them will go off. There's a communication via LTE, cloud services, and then the car, which has to send a response back that it has actually been done. There should be something that blocks the user from taking further action on one seat until the change is confirmed, if the button has been idle (not 2 consecutive presses).
4) Yeah it does nothing which is kinda sad.
6) Must be buggy software which doesn't account for lag in services, and the state is out of sync.
7) yup sync error.
I don't think the guys who code and verify the UI ever run it in a real car. Let me give you an example. In 2013, I submitted a bug about the fact that whenever I turn on my headlights automatically, when I try to get out of the car I get warning beeps and a message which says my range will be affected, which is not true because the headlight turn off as soon as I lift off the driver's seat. So, a few months later they fixed, it, the warning text was gone but the warning tones were still there! My best guess is, whoever got assigned the bug just suppressed the visual warning but they didn't even have a speaker connected to realize they only suppressed the display of the warning, not the full warning including the dings. About 3 years later the visual warning returned (someone noticed the hack in the code?), now is shows both the useless warning and the dings. The car trained me to ignore any warnings on exit - one time somehow the car didn't shift into park (maybe I didn't press hard enough on the stalk, I don't know) and as I was getting out it dinged at me to tell me that the car is still in drive, I plain ignored it because warning dings on exist are just normal with Tesla (on entry too, I get some warning which was not able to catch on the screen because it beeps and then goes away before I ca read it). Lucky the car automatically shifted to Park as I was getting out, but still, why have useless warnings?It works for me. 2018 MS.
They need a QA department, testing all hardware and software revisions. And I do mean actually testing it. not just sitting with a virtual machine or whatever in the office with top wifi connection.
I think you are wrong. This is the QA department:Tesla MCU QA department deciding on release stability.
4x4x4x4=256 possible choices. Don't forget repeated numbers.
Edit I guess with repeated numbers you would see less than 4 spots having fingerprints. So I'm not entirely correct either.
It would be 10,000 combinations. 10x10x10x10. 0-9 for each slot?
None that I have noticed.Does 2018.48.12.2 contain any noticeable fixes?
Yes, but only if you don't know the numbers. Here we're talking about seeing the smudges on 4 numbers so you have 4x3x2x1 combinations assuming no repeated numbers.
As do I and this is what kills me watching what Tesla do, I know the software validation procedures some of the other OEM's go through which does mean they are slower but the big difference at the moment is if they don't get it right first time then it could cost them money or risk losing a customer for life. This is because they require all owners to bring the car in to the dealer to get updates, just imagine as Tesla owners we didn't get over the air updates. So you'd waste your time going to the dealer to get a bug fixed only to have to return a month later to get another bug fixed that got introduced with the last update! And the cycle repeats. The problem is because Tesla don't need to do that there is less importance put on getting it right the first time because they can just deploy another over the air fix.Honestly, really sad. I work with automotive companies and yes, they take their sweet time and it's frustrating sometimes, but at least they think about testing the stuff they release so it works for a large majority of users.
As a followup to my own post, a reboot fixed this. A few others have reported similar with that version.Anyone else having their car not connecting to wifi with the latest versions? As of 2018.48.12.1 it has not once connected to wifi. It no longer even sees the wifi I have at home nor the wifi hotspot I've set up for remote locations...
Usually in a structured software team, for each bugfix, an effort is made to reproduce the error programmatically in an unit test. Then that unit test is one of many tests that is automatically executed for each version you do. That way old bugs don't find their way back unnoticed.To me it seems like they don't have a good system in place to ensure that fixed bugs don't reappear. I know not everyone has Spotify enabled vehicles but we've gone from a previous update where users could not log in to getting that fixed with an update to now with the last update we can't log in again, that stinks of the software team not doing thorough version control and someone has put some old code back in.