News
Tesla FSD Beta 10.69.2 “looking good” for weekend release + 10.69.1.1 Reviews
Elon Musk shared that Tesla FSD Beta 10.69.2’s release is still set for this weekend.
Tesla initially planned to release v10.69.2 last week but delayed the update to polish it up more. The company rolled out v.10.69.1.1 to more Beta testers instead.
Tesla FSD Beta 10.69.1.1 Reviews
A few Tesla Beta testers who received v10.69.1.1 shared their observations and thoughts about the update with Teslarati. One of the common issues Beta Testers mentioned was phantom braking.
One 2021 Model S owner, Howard, noted that his Tesla vehicle still experienced phantom braking too much. He shared that his Model S drove like a 16-year-old. “Not smooth with the wheel, throttle, or brakes,” he said.
Howard also observed that his Tesla ignored some speed signs, even if they popped up on the display. The Tesla Model S owner added that his car “still fades right into turn lanes when there is not [a] turn to be done. It then swerves to go to the last [turn] it just left.”
Fellow FSD Beta tester, Michael, was “a bit disappointed” with the latest update. He noted experiencing some phantom braking along the Long Island Expressway.
“Can’t seem to figure out the somewhat irregular lines in the HOV lane, which is surprising to me. Oh well….hope for better next time. Still not there, but much better than first experiences,” Michael added.
Impressions from a longtime FSD Beta Tester
FSD Beta tester Les also shared his thoughts about v.10.69.1.1 with Teslarati. Les has been an Early Access software tester since 2018. He was kind enough to break down all his observations from testing FSD Beta 10.69.1.1.
Les mentioned seeing a few issues with FSD Beta that have been around since Fall 2021. Some of the issues are listed below.
- [The] car doesn’t always stay in [the] proper turn lane when using the outer lane of a left dual turn lane scenario; 8/10 times, mid-turn, it will cross over into the inner turn lane. It has done this for me with every FSD Beta build back to October 2021.
- Inconsistent lane selection: my car will still sometimes move[s] into lanes opposite to the next upcoming turn, sometimes when close to that upcoming turn, sometimes missing the turn itself.
- Late turn signals: this is a long-standing issue many testers have reported. The turn signals [usually] activate too late when they need to activate ahead of a turn lane to alert drivers behind us.
Despite the continuing issues he observed, Les seemed to have an overall good experience with the latest update. He specifically highlighted Tesla’s work with Chuck Cook Style’s unprotected left terms which were specifically mentioned in v10.69’s release notes. Listed below are all his good observations about FSD Beta v. 10.69.1.1.
- The improvement to “Chuck Cook style” unprotected left turns with multiple lanes and medians is incredible. The car utilizes the median space very well. [It] feels like more than an improvement. It really almost feels like a feature upgrade. It’s that significant and amazing to experience.
- The car has almost no more phantom braking events for me. I never had many to begin with, certainly not as many severe events as other friends report, but I did notice the ones I had and the places they occurred no longer occurred.
- Traffic turning across my car’s path no longer triggers a cautious braking event when there’s enough room ahead. The car better recognizes the crossing vehicle’s direction and speed, and my car maintains its speed. Very human-like behavior.
- More assertive and smooth acceleration out of turns, especially when entering a higher speed road. Related: improved acceleration from stops. I like this very much, as prior builds often took too long (for my taste anyway) to get up to speed. It still could get up to speed more quickly, but there is [a] notable improvement.
- The dashcam bug has been eliminated!! The prior build would routinely crash the dashcam after I parked and/or charged, requiring either a computer reboot or removal/reinsertion of [the] dashcam thumb drive to fix. No more problems!
In general, Tesla is steadily improving FSD Beta with each update. And Testers are actively experiencing those improvements. However, Tesla’s Full Self-Driving suite still needs more work before it rolls out to the public.
Are you an FSD Beta tester? I’d like to hear your thoughts on v10.69.2! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.
News
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
AT&T, Verizon and T-Mobile want 290 MHz cut from an FCC satellite plan before Thursday.
AT&T, Verizon and T-Mobile are asking the Federal Communications Commission to pull nearly 300 MHz of spectrum out of a proposal that would let satellite companies like SpaceX offer cell service directly to ordinary phones. The request lands one day before the agency votes on it.
The FCC will vote Thursday, October 29, on a notice of proposed rulemaking that would make an additional 482 MHz available for direct to device service, expanding the number of eligible bands from five to 13, according to the FCC fact sheet. It would also scrap the rule requiring a satellite operator to lease spectrum from carriers, replacing it with a certification that the operator has coexistence agreements in place or holds the terrestrial license itself.
That second path matters for SpaceX. As Teslarati reported earlier this month, SpaceX agreed to buy Grain Management’s nationwide 800 MHz portfolio to turn Starlink Mobile into a full US carrier, adding to the spectrum it already bought from EchoStar.
The carriers want two bands removed, 2.5 GHz and 3.45 GHz, which make up 290 MHz of the 482 MHz on the table. Through industry group CTIA, they argued that about 300 million users depend on those bands and that satellite operations in them are not technically feasible. T-Mobile, which calls 2.5 GHz the foundation of its Ultra Capacity 5G network, said in its own filing that satellite interference could wipe out up to 96% of a cell site’s uplink coverage area and cut uplink speeds by 88% to 99%.
Executives from all three carriers met with FCC staff on October 20, and T-Mobile CEO Srini Gopalan met separately with FCC Chairman Brendan Carr. T-Mobile’s role stands out because it is still SpaceX’s US launch partner for Starlink Mobile. The three carriers have also teamed up on their own satellite joint venture to pool spectrum, a move widely seen as a response to Starlink.
SpaceX is asking for the opposite. In an October 23 filing after meetings with FCC staff and commissioners’ offices, the company asked regulators to add the 902 to 928 MHz band to the proposal. “Doing so now saves time later,” SpaceX wrote. The company also asked the FCC to modernize interference rules and align satellite deployment requirements with those for terrestrial cell networks, saying the goal is to let satellite and ground networks work together so Americans stay connected wherever they are.
The carriers have not been shy about how they view SpaceX as a competitor. On Verizon’s third quarter earnings call Monday, its chief executive said Starlink Mobile “just can’t compete with a terrestrial network” and estimated SpaceX would need four to six years and $300 billion to $500 billion to build a full US carrier network.
Thursday’s vote will not settle which bands survive. Adopting the notice opens a public comment period, with final rules to come later in the proceeding. The FCC already considered and rejected 2.5 GHz for satellite coverage once, in 2024. SpaceX also is not the only satellite player watching: the FCC approved Amazon’s $11.6 billion acquisition of Globalstar on October 27, giving its planned direct to device fleet its own mobile satellite spectrum.
A Tesla Semi caught fire in Hayward, California, which caused both directions of traffic to shut down for hours before being completely reopened early on Wednesday, the California Highway Patrol said.
The fire occurred just after 5:30 local time in Hayward on Tuesday, as the Semi caught fire in the southbound lanes of I-880 before CHP officials made the decision to shut down both lanes of traffic due to potential risks from hazardous chemical smoke.
There were no injuries reported.
🚨 A Tesla Semi reportedly caught fire, with California Highway Patrol confirming. The Semi was on I-880 SB
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year
— TESLARATI (@Teslarati) October 28, 2026
The cause of the fire is currently unknown, as neither Tesla nor the CHP have not determined a cause.
However, some images taken before the Semi was completely destroyed by the fire seem to indicate this might have been an older unit, as it appears to be one of the designs that Tesla shipped as part of its pilot program, before revising it and starting mass production just a month ago.
@Tslachan From on of the videos looks like it’s an old Semi (not the refresh version that recently started production) https://t.co/KzwmR2kXow
— Area Under The Curve 🎗️ (@AreaUnderCurve) October 28, 2026
At the time of publication, CHP had not returned our request for a comment for additional details, including the Semi involved and any potential collaboration on an investigation between the CHP and Tesla. We will update this story when we hear back from them.
The southbound lanes were reopened at 3:30 a.m. on Wednesday, with the northbound lanes opening last night a few hours after the fire began. The CHP did state that the lithium batteries were “incredibly difficult to extinguish,” according to NBC Bay Area.
The truck’s driver said that the Semi caught fire, but he did not have an explanation.
An estimated 5,000 to 7,000 semi-truck and large commercial vehicle fires occur on U.S. roadways every year.
Tesla’s launch of the “Emergency Drive Away” function a few months back offered owners a safe option to evacuate an area if they were in reasonable danger. The function finally got its first use in the real world, but it appears it was by mistake.
A video shared by u/Joshalander in the r/TeslaLounge subreddit recorded the instance from his vehicle and said the incident took place in Austin this past weekend during the city’s F1 Race.
“Was charging around 6 AM this past Sunday in Austin before heading to the F1 race and heard a pop. Looked over and saw the new emergency drive-away feature in action. Genuinely felt bad for the dude when he got out and realized what happened, since he looked exhausted and only seemed to half-read the prompts.”
🚨 Here’s the first look at Tesla’s Emergency Drive Away function in action:
Apparently this driver accidentally enabled it and drove forward; you can see the Supercharger pull with the car.
Tesla said previously this would cost up to $25k if not used properly. https://t.co/B4qQRrsO6B
— TESLARATI (@Teslarati) October 28, 2026
Emergency Drive Away unlatches the Supercharger connector from the vehicle, but still causes damage to both the car and the Supercharger. Tesla has said that it will cost up to $25,000 in repairs to have everything fixed back to normal.
Additionally, the company said that if it were not used in an emergency situation, the driver of the vehicle who activated the Emergency Drive Away feature would be responsible for all repair costs.
Tesla constitutes the following situations as reasonable justifications for activating the feature:
- You face an immediate threat to your life or personal safety.
- You must leave the area immediately.
- Exiting the vehicle is unsafe.
- Unplugging the charge connector would unreasonably delay your departure or expose you to a risk to your personal safety.
After using the feature, Tesla requires the driver to schedule Service so the car can be inspected.
Verizon, AT&T and T-Mobile are trying to shut Starlink out before FCC vote
Tesla Semi catches fire in California: what we know
