You can never solve a problem unless you first suspect unless you believe in pure luck to happen upon it by accident.
Unless you're a Tesla employee, you're not being asked to solve the problem. You and I are both spectators; we can speculate, but we don't have access to the code, nor are we being asked to solve the problem. Of course, Tesla might need to consider the possibility of a Trojan Horse, but
they have access to the source code, revision history, training data, etc., as well as the expertise to check all these things. Thus, Tesla can check to see what's triggering the problem and, in all probability, quickly rule the possibility of a Trojan Horse in or out. For the general public, shouting "Trojan Horse" at every bug is unjustified. Most bugs are simply that: bugs.
I first believe this is not a v10.3 FSD beta release bug. because there are too many non-beta testers who are experiencing the same issue that began only yesterday.
Second, it had to be date triggered because I've been on this version 32.22 since September 25th and never a FCW. In fact never had any FCW on either of my Teslas until yesterday when both began this trouble.
To clarify: Are you saying that you've been on 2021.32.22 continuously for a month, never had a problem before yesterday, and are now experiencing false-alarm FCW alerts? If so, that's the first I've seen such a report -- all the other reports of the excessive FCW alerts that I've seen have been with 2021.36.x. To be sure, there have been reports of
occasional FCW false alarms for a long time, but the sorts of reports of them happening frequently are new. If you're the only person experiencing this problem on 2021.32.22, then I'd chalk that up to coincidence; but if there are significant numbers of people on 2021.32.22 who suddenly began having this problem recently, then it could be something else -- perhaps date-triggered, but perhaps something else is going on. This might or might not be a Trojan Horse; for instance, it could be that falling temperatures or autumn colors on trees is confusing the FCW algorithms (although as you're in Florida, chances are those aren't factors for you).
Third, Tesla builds there software by modifying the prior version so if there is a time triggered trojan horse in the software from way back it can hide until something triggers it. The last time Tesla started fresh, so they claim, is when they stopped using radar and rewrote the base code.
The no-radar Tesla Vision builds are being pushed out even to the cars equipped with radar. I noticed this in the 2021.36.5.2 release notes, but it may have been pushed out before then. (I haven't been paying close attention to this issue.)
No software developer completely re-writes their software "from scratch" with every release. In fact, I expect that even the Tesla Vision version shares a
lot of code with previous versions. This isn't really a point in favor of your Trojan Horse hypothesis; it's just a part of how Trojan Horses in code work in general.
PS, don't place Hanlon's Razor as your plan to solve a problem.
It's not, because, as stated before, it's neither my nor your job to fix Tesla's buggy software. In this context, Hanlon's Razor is a useful heuristic for guiding discussions. Assuming that malice is at play is a good way to start a conspiracy theory, but it's not a good starting assumption for a rational public discussion of a problem. That's not to say that malice can be entirely ruled
out, either; but without further evidence, in this context, it's a poor starting assumption. Tesla has a lot more evidence on this issue than we do, and in fact they've already pushed out 2021.36.5.3. That fact is not evidence in favor either of a non-malicious bug or of a Trojan Horse; Tesla could have discovered and fixed either within the day and a half or so that the buggy version has been available to the general public.
. Its raining here but my Tesla likes to play in the rain so I Will report back later .
