D&V

@Jim_363 And you don’t have the car in the Tesla app. That really knocks down 50%+ of the stuff that makes a Tesla nice.

@d_vwatts That’s the problem. It’s a rental obviously we’re not gonna pay for connectivity. I don’t even think we could.

I’ll never understand the anti-CarPlay crowd. We just picked up this Tesla while our car gets repaired, and the simple fact is we could’ve gotten in and had everything on our phones on the screen within seconds. Refusing to give the consumer an option just for the simple fact that they can keep all the information to sell and profit makes zero sense for the end user, except to be more of a hassle. And why the hell does the Tesla app want access to my health data?

@Jim_363 Wow, without the premium connectivity you can’t use anything accept bluetooth. You might be able to connect to you phone’s data via wifi but if you are doing that might as well stick with bluetooth and use your phone.

OK, that’s that. It’s stupid not to offer it—what harm does it do? Yay, we get to stream music through Bluetooth just like I did in my '09 Ford. I can’t use Apple Music because the car needs a connectivity package, which of course a rental isn't going to have. It’s a '22 Dual Motor, but we just took what we could get. They can take any data they want. We’ve already seen it with GM.

If you disengage FSD anywhere at anytime going highway speeds and you don’t know that you did it because you were asleep or distracted 4 seconds later it’s going to be bad. How do you even know FSD “gave up”? You don’t. I don’t. You know there was a crash and you have 4 seconds of video that was being “manually driven” because Elon said FSD was disengaged 4 seconds before the crash. That’s it. There is not gotcha.

Tesla fans using the “4-second disengagement” as a gotcha are missing the forest for the trees. Yes, the driver was technically in control of the vehicle at the moment of impact. But she was in control because FSD was already failing by driving too fast ahead of this sharp turn — it was heading straight into a concrete barrier at highway speed with no sign of correcting. Everyone who has frequently used FSD or Autopilot and paints this 4-second disengagement as a “gotcha” moment is being disengenous, and that includes Elon Musk. I have tens of thousands of miles on FSD, and I’ve experienced the system coming too fast into a turn at least half a dozen times. We’ve said this before and we’ll keep saying it: the problem with FSD isn’t what happens when the driver is paying attention and the system works. The problem is what happens when the system gives you every reason to trust it, and then suddenly doesn’t work. The driver has to recognize the failure, assess the situation, decide on a correction, and physically execute it, all in less time than the system needs to create the danger. Musk and Tesla’s propagandists can point to the logs all they want. The video shows what actually matters: FSD approaching a standard highway curve at full speed with zero indication it was going to navigate it. That’s the failure. Everything that happened after, including the panicked disengagement, is a consequence of that failure. The framing that this was “manual driving, not FSD” is technically true for the final 4 seconds and deeply dishonest about the full sequence of events. It’s exactly the kind of liability shell game that courts are increasingly rejecting, as that $243 million verdict makes clear. Tesla created the system, sold it as “Full Self-Driving,” and profits from the ambiguity. At some point, it has to own the consequences.

@dictionaryhill @dkhos @ZachBeenvvr @Rivian @RJScaringe @Uber Did Uber get a % of Rivian? This looks like a cap raise.

@dkhos @ZachBeenvvr @Rivian @RJScaringe @Uber They really are. I wish early Tesla investors understood what Rivian is building instead of constantly bashing them. $TSLA folks now generate the same FUD we fought in the early days when nobody believed in Tesla. Great job seeing the signal through the noise .@dkhos

Rivian is building something special: vehicle, compute, software, and manufacturing in the US all working together. Excited to partner with @Rivian and @RJScaringe to bring autonomous R2 robotaxis to @Uber.

@Mattlinn01 @Eric_L_Roe I think the word you were looking for was Safety, not liability. There is a lot Tesla does for safety, there is almost nothing they do just for the sake of liability.

@d_vwatts @Eric_L_Roe No conspiracy. I think the software as in any situation detects a situation it can’t recover from and reverts back to driver control.

Why do so many people think that the Cybertruck has base AP?

@Mattlinn01 @Eric_L_Roe I think it’s been proven that manufactures with ADAS functionality and cameras that do not record to a user accessible drive do so for liability purposes, maybe? Literally the most user data accessible cars on the planet and it’s a conspiracy to avoid liability. Ok.

@Eric_L_Roe I think it’s been widely proven that FSD/Autopilot automatically disengages right before any detected accident, for liability reasons maybe?

If only there was a history of people saying FSD did this or that and the media playing it up as a fact only to be proven it was the driver 3mo later, not FSD and nobody caring. Even the same version of FSD in the same vehicle will do it differently. The logs with driver input + overly of the video files are the only facts.

@JoNationLive @FoxNews So… in August of 2025, a Cybertruck would have been running on V13. Probably V13.2.x. Is it that hard to understand that an older version of FSD may have performed differently than his running V14.x?

.@FoxNews care to comment on this? If you actually did just a little investigative journalism, you would have been able to verify the Cybertruck owner wasn’t using FSD when the accident happened. FSD handles that road perfectly fine.

@LamarMK This poll is incomplete. Both.

Is your Tesla HW3 or HW4?

@TesCalendar1 Me too. I’ve only had about an hr total with CT and none since FSD was improved. All I’m saying is there are intangibles that don’t translate to paper and you don’t know until you’ve had the time to run into those.

@d_vwatts I’ll happily drive for weeks if you want to loan me one

Putting my Cybertruck review to the side for a bit as I want to get a little more time behind the wheel first and I felt compelled to write a different article… stay tuned 😎

Plus apparently ABRP was constantly changing his rout to save 5 min but would put him in charging limbo by going to chargers he could not trust and apparently would do so without his acknowledgement. I have not used ABRP for trips so I’m just going by all of the WTF is it doing/did it do/why am I on this road phone conversations. I know Ford nav and Apple nav have done this to me. I was surprised ABRP was no different.

I don’t think 10hrs is enough. You really need several days and multiple use cases. What keeps CT in the mix for me is FSD and the supercharger network. After driving to Florida and back I don’t know if I can do road trips without FSD and SC. BC/Supercruise are not the same. FSD and superchargers you just get in and go, not a thought or worry, just press a button. My brother did the same trip from Oklahoma in his new Lightning and ABRP sent him to two CCS chargers that were behind dealer locked gates at 3:00am and the hotel that was next to them had two broken L2 chargers. He had to get a room. On the way back ABRP sent him to a EA that had all the chargers covered in bags. There was a Ford dealer down the street and luckily there was a delivery guy that let him in (behind locked gates) but then made him leave 15min later when he was done with his delivery. The charger was rated at 170kw but only delivered 50kw. He had to drive at 40mph for 100mi to make it to the next charger at 1:00am. You don’t get that experience in 10hrs.

The ChatGPT moment was when everyone was using ChatGPT. Nobody is using any of those cars that he listed. He then said “in the future”, that’s not the ChatGPT moment is “now”. The only car you can get in press the button and have it drive you to your destination is a Tesla. That’s the ChatGPT moment right, now not Nvidia.

@niccruzpatane Have you noticed who hasn’t been able to find a single manufacturer to license their self-driving tech?

NVIDIA CEO Jensen Huang today: “The Chat-GPT moment for self-driving cars has arrived. NVIDIA announced that they’re now expanding their self-driving partnership to BYD, Nissan, Hyundai, and Geely. Their automotive partners: • GM • Toyota • Mercedes-Benz • Jaguar Land Rover • Volvo • Rivian • Hyundai • BYD • Geely • XPENG • Polestar • NIO • Lucid • Li Auto • Nissan • Isuzu • Zeekr • Xiaomi • Stellantis Additionally, NVIDIA and Uber are partnering to launch a global network of Level 4 autonomous robotaxis, beginning in LA and San Francisco in early 2027 before expanding to 28 cities by 2028. The robotaxi race is well underway.

@Mattlinn01 It looks so good! I think his is the only red one I’ve ever seen in person.

@d_vwatts Red is an underrated color on the Lightning.

“Ford’s software is so slow!” Ehh… seems fine to me. Could definitely be prettier.

@Mattlinn01 @bowefamilyEV I think he still has an appointment today.

@bowefamilyEV @d_vwatts Wouldn’t be a bad thing to get that checked out by the dealership.

Ford Lightning people. Anyone ever get this error. Getting it on both a Tesla SC with adapter and a Francis CCS. The truck is able to L2 charge.

@bowefamilyEV @Mattlinn01 , Ok, so looks like it was a pin alignment issue. After L2 charging for several hours he went back to try the CCS again and this time pushed in harder and moved the charge cable around while doing so and the pin latched and it started charging.

@d_vwatts Yeah I think best bet is going to be to bring it in just with its module history

@bowefamilyEV Yeah, 1yr BtoB and he bought a 3yr extended. It had a failure to charge over 50% and a battery module replaced. The dealer said they had DCFCd the day before.

The scanner can sometimes reset a code but often times it will come right back again. Disconnecting the battery for just a few minutes and then reconnecting. It will sometimes work some magic. If you start seeing repeated problems, then I would replace the 12 V. Since it was a buyback, did it come with any type of warranty or extended warranty? A lot of times when you buy a buyback, it will have some type of extra protection with it. Do you know the history of the buyback? Once you try the simple things like resetting and clearing codes if it’s still there, it’s unfortunately gonna be something more serious that the dealer will have to look at, and hopefully it’s covered under some type of warranty.

This is my brother’s truck. He just bought it. It was a buyback. I think he bought an OBD2 at walmart while it was on L2 but you can’t reset anything with just the scanner can you? He was thinking a 12V reset too. How long do you think it should it be off? Or not risk it and just stay on L2 for 4 hrs?

@d_vwatts Do you happen to have an OBD 2 scanner to see if it’s giving you a code? Other than a 12v reset hoping for a locked up module it’s likely you’ll have to bring it in to the dealer 🫤