Connect with us
tesla-fsd-beta-10.69.3.1-defeat-device tesla-fsd-beta-10.69.3.1-defeat-device

News

Tesla FSD Beta 10.69.3.1 update reviews from Beta testers

Credit: teslaphotographer/Instagram

Published

on

Tesla Full Self-Driving (FSD) Beta 10.69.3.1 has been out for some time now, and Teslarati talked to a few beta testers about the update. 

Below are some notes and observations about v.10.69.3.1 from Tesla FSD Beta Testers. 

FSD Beta 10.69.3.1 and Lanes

Lane selection has been one of the issues that most FSD Beta testers bring up when they talk to Teslarati. Before 10.69.3.1, FSD Beta reportedly had trouble understanding when to switch lanes, which one to switch to, or when to remain in a lane. FSD Beta testers are still experiencing lane selection issues. 

“Not only has lane selection in anticipating a turn been a step back for me, lane selection whilst performing dual lane left-hand turns still suffer. The car doesn’t stay in its assigned lane but drifts. This does not happen on right turns,” said Les, a long-time FSD Beta tester.

“Lane selection still has issues. Most of the time it’s ok, but occasionally, it does strange things like changing into the right lane momentarily, then back to the left when there is an upcoming left-hand turn,” noted FSD Beta tester Sandy.

Turn Issues in FSD Beta 10.69.3.1 

Les and fellow FSD Beta tester Sandy mentioned other lane issues related to turns. Les noted that one of the biggest step back with FSD Beta 10.69.3.1 occurs when the car faces an upcoming turn. 

Advertisement
-

“On previous builds, the car would only occasionally move in the opposite lane direction of an upcoming turn. On this build, virtually every turn I had upcoming, when the car got within half a mile of said turn, it would signal and move into the lane of the opposite direction,” Les said.

“Virtually every right turn I’ve had upcoming, the car, inexplicably, signals and changes into the left-hand lane. Same for left-hand turns, within half a mile out the car signaled and changed into the right-hand lane. Confounding to say the least, to the point of comedy,” he added. 

Sandy noticed that his car requires interventions or disconnects at stop signs sometimes. In the past, other FSD Beta testers have mentioned that their vehicle experiences jerky movements or their signal lights turn off and on during intersections, traffic lights, and stop signs. It’s as if the car is deciding whether the driver wants to turn or not. 

“Following and lane changes seem smoother and more natural,” said Sandy. “However, it still has issues that require intervention/disconnects. When it creeps at stop signs, it can make jerky movements with steering wheel and, imo, it creeps to slowly and takes too long before proceeding.”

Mixed Reviews for 10.69.3.1

As with all of Tesla’s FSD Beta updates, there have been a few good reviews and bad ones. Beta testers tend to focus on the issues, as it is their responsibility to report them so Tesla can improve FSD. However, testers also report significant improvements they see during their drives. 

In the case of 10.69.3.1, it seems like FSD Beta received mixed reviews. Some testers believed that the update significantly improved the advanced driver assist software while others thought it was a step back. 

Advertisement
-

“I have tested the 10.69.3.1 build on my Model Y, and it’s a giant leap forward from builds prior to 10.69,” observed Tony, a Model Y owner and a member of the FSD Beta program. 

Tony noted that the biggest changes were improvements to acceleration, smoother turns, and less necessary steering wheel input. Sandy also observed more improvements with Tesla FSD Beta 10.69.3.1 rather than issues. 

On the other hand, Les believed that v.10.69.3.1 was a step back for FSD Beta. 

“These 10.69.3.1 step backs are the biggest in my FSD Beta testing experience to date. Previous builds have been much better for me. But again, I understand the process; updates are sometimes “2 steps forward and 1 step back.” I still enjoy testing. The product isn’t finished yet,” he said.

Tesla FSD Beta Wide Release

Tesla started the wide release of FSD Beta v.10.69.3.1 in late November. A day after its release, Tesla rolled out FSD Beta to cars with less than 100 Autopilot miles and Safety Scores lower than 80.

The EV maker rolled out FSD Beta V11 to a few testers already. FSD Beta V11 is Tesla’s single-stack update. However, update 10.69.3.1 seems to be rolling out to more testers. 

Advertisement
-

Tesla also made Full Self-Driving Beta available to anyone in North America who purchases it from their car screen. Now that Tesla has released FSD Beta to anyone in North America interested in trying it out, the company might want to streamline its performance. Based on Teslarati‘s interviews with FSD Beta Testers, the software performs differently based on location, driver, terrain, and other factors.

“Phantom braking on city streets (not highways) returned for me in one bizarre instance; it wasn’t the sudden hard kind of braking, rather this was a new braking behavior that was slow and gradual almost to a stop while I was going straight in the middle lane of a three-lane road. Not at a turn, wasn’t going through an intersection, and the road was clear,” described Les in one instance. 

“There were no cars around me so I let the car do its thing to see what it was doing; it literally started slowing from 40mph to 5mph before I disengaged and accelerated back up to speed. Very weird. I went back to that spot a couple days later and the car didn’t do it. It acted normal,” he explained. 

Tesla Full Self-Driving has not received regulatory approval yet. It still faces a lot of skepticism, especially in terms of safety. Delivering consistent, reliable performances in various driving situations might help it get regulatory approval. 

Are you an FSD Beta tester? Have you tried out V11? If you have, I’d like to hear from you! Contact me at maria@teslarati.com or via Twitter @Writer_01001101.

Maria--aka "M"-- is an experienced writer and book editor. She's written about several topics including health, tech, and politics. As a book editor, she's worked with authors who write Sci-Fi, Romance, and Dark Fantasy. M loves hearing from TESLARATI readers. If you have any tips or article ideas, contact her at maria@teslarati.com or via X, @Writer_01001101.

Advertisement
Comments

Elon Musk

Tesla may test customer-owned Robotaxis as early as next month, Musk says

Published

on

Credit: @AdanGuajardo/X

Elon Musk says that Tesla could test adding customer-owned vehicles to the Robotaxi platform as soon as December.

In a reply on X to an Austin-based Uber driver who uses a Model Y with Full Self-Driving and keeps only 49-63% of fares after the platform’s cut, Musk wrote:

“Coming soon. If things well, may start trials next month. Much better to manage a fleet of cars than have to drive just one car by yourself!”

The exchange highlights the appeal of passive income from an autonomous vehicle versus actively driving for rideshare platforms.

This potential December start is technically earlier than prior company guidance, but it also aligns with the currently-projected first delivery of the Tesla Cybercab, a vehicle that has no manual controls.

Nevertheless, Tesla planned to bring customer vehicles into the fleet later on. During Tesla’s Q3 earnings call, AI leadership had pointed to roughly the second quarter of 2027 for customer vehicles joining the network. Musk’s comment suggests an accelerated pilot, most likely beginning in Austin, where Tesla’s Robotaxi service has operated longest and where new features typically roll out first.

December is also the target month for the first customer deliveries of the Cybercab. In mid-November, Tesla began inviting select buyers to purchase the purpose-built, two-seat vehicle for personal use at $29,990 plus a required $299 monthly Autonomy Subscription, with estimated deliveries in Austin.

Tesla Cybercab goes on sale for $29,990, slated for December deliveries

Those initial private Cybercabs are restricted to personal use within existing Robotaxi zones and do not automatically include commercial network participation; the large majority of Cybercabs are expected to remain Tesla-owned fleet vehicles.

The coincidence of the two December milestones underscores Tesla’s parallel paths. Customer Model Ys already on the road with FSD hardware could rapidly enlarge the vehicle pool for unsupervised trials, while the Cybercab, which is void of a steering wheel or pedals and equipped with only dedicated Robotaxi hardware, arrives as a purpose-built platform.

Hardware differences, such as additional cameras or cleaning systems on company Robotaxis, may constrain which Model Ys are eligible at the outset. Regulatory approvals, insurance arrangements, and software readiness will also determine whether the “if things go well” condition is met.

For owners, successful trials would fulfill a vision Musk first sketched in Tesla’s 2016 Master Plan: vehicles that earn money while their owners sleep or work.

Combined with the arrival of privately owned Cybercabs in the same month, December could mark the transition from Tesla-controlled Robotaxi operations to a broader ecosystem in which both company fleets and customer vehicles contribute to the company’s autonomous ride-hailing platform, which continues expanding.

Continue Reading

Elon Musk

FAA turned down free Starlink offer before nationwide ground stop, Elon Musk says

Elon Musk says the FAA declined free Starlink terminals before last week’s nationwide ground stop.

Published

on

By

Elon Musk says the Federal Aviation Administration could have had Starlink backing up its air traffic communications for free, and he is pointing to last week’s nationwide ground stop as proof it was needed. “As I was saying … Free Starlinks for FAA were offered to Sec Duffy, but he said they were not needed. As it turns out, they were,” Musk wrote on X Monday.

Musk was quoting his own post from February 2025, when he wrote that “the ancient system that is rapidly declining in capability was made L3Harris,” while a newer replacement system from Verizon was “not yet operational.” The Department of Transportation has not responded publicly to Musk’s account of the offer.

The outage behind the post began at about 3:30 p.m. ET on Friday, November 13. According to the FAA’s own account, its legacy equipment became unstable when data began flooding its FAA Telecommunications Infrastructure network at a rate of 1,000 connection attempts every four to five seconds. The agency traced the flood to two locations, a radar site in Amarillo, Texas, and a radio communications site in El Dorado, Arkansas, where L3Harris had been installing a new router.

Instability spread across 17 of the FAA’s 22 Air Route Traffic Control Centers. The agency grounded departures nationwide while about 3,500 aircraft already in the air landed safely, and lifted the stop at 8:15 p.m. ET. Operators canceled roughly 12,462 flights that day, though the FAA notes not all of those were directly caused by the ground stop. L3Harris blocked the two sites to stabilize the network, and the FAA disabled the same router function on about 60 similar units. Officials found no sign of a cyberattack.

Transportation Secretary Sean Duffy has blamed prior administrations and dated systems, and has called on Congress to fund a $50 billion overhaul of the system.

Musk’s history with the FAA network goes back to early 2025, when he was leading the Department of Government Efficiency. He claimed on X that the system was failing and putting air travelers at risk, initially blaming Verizon before correcting himself to name L3Harris. The FAA confirmed at the time it was testing Starlink terminals, one at its Atlantic City, New Jersey facility and two at “non-safety critical sites” in Alaska. SpaceX said it was providing the kits at no cost and had no intent to take over any existing FAA contract.

Duffy described Starlink then as “part of a solution” rather than a replacement. By July 2025, the FAA told lawmakers it was not considering replacing its L3Harris and Verizon telecommunications contracts with Starlink.

Whether Starlink would have prevented Friday’s disruption is not clear. The FAA described a fault inside its terrestrial network rather than a loss of connectivity, and Musk did not explain how satellite links would have been used. His post does put SpaceX back in the conversation as Washington debates how to pay for the next air traffic control system. SpaceX already supplies Starlink to commercial airlines for inflight connectivity, and United’s rollout required FAA certification for each aircraft type.

Continue Reading

News

Tesla makes $3.3 billion Cybercab bet at Giga Berlin

Published

on

Credit: Tesla

It is no secret Tesla is prioritizing Cybercab production as it plans to launch a fleet of fully autonomous vehicles without steering wheels or pedals across the world. Today, it made a €3 billion bet to do so in Europe.

Tesla announced on November 16, that it will invest €3 billion (approximately $3.3 billion) to expand its Gigafactory in Grünheide near Berlin, its only vehicle manufacturing site in Europe.

The investment will fund a major new production building—roughly twice the size of the existing main hall—and supporting infrastructure, including an additional wastewater treatment plant. The new facility is designed to produce up to one million Cybercabs annually once fully scaled, alongside continued Model Y output.

Tesla plans to file the building permit application before the end of 2026, according to Tagesspiegel, drawing on a broader expansion application submitted in 2023 that targets one million vehicles per year overall. Construction is scheduled to begin in the first half of 2027, with Cybercab production starting in 2029.

The company is already recruiting several hundred workers for construction and production planning. The site currently employs about 12,600 people after recent hiring of roughly 2,000, and it is ramping Model Y production toward 7,500 vehicles per week (around 375,000 annually).

This vehicle expansion comes just days after plant manager André Thierig indicated at the Automobilwoche Congress on November 11 that full battery cell production at Grünheide is on track for mid-2027.

The factory already produces electrodes, which are currently shipped to Texas for cell assembly and returned; the goal is to complete 4680-format cells on site using Tesla’s dry-electrode process, targeting up to 18 GWh annually.

The cumulative investment in the cell operation approaches €1 billion and is expected to create more than 1,500 jobs. Once operational, Giga Berlin would become the first plant in Europe to produce everything from battery cells to finished vehicles under one roof, raising the European content of its Model Ys to roughly 90 percent.

For Tesla’s German operations, the twin moves deepen vertical integration and reduce dependence on transatlantic and Chinese supply chains.

They also contrast sharply with the broader German automotive industry, which faces high costs, weak demand, and job cuts; Brandenburg officials have welcomed the investment as a significant economic boost that creates hundreds of new positions and strengthens the region as a manufacturing hub.

Tesla’s expansion advances its strategic pivot toward autonomy and robotaxis. The Cybercab is intended to become a high-volume product; adding major European capacity diversifies production beyond the United States and supports Elon Musk’s vision of autonomous vehicles comprising the majority of Tesla’s future output.

Combined with localized 4680 cell production, the plans position Giga Berlin as a more self-sufficient, technologically advanced European base, enhancing competitiveness as regulatory and market conditions favor higher local content.

Continue Reading