What's new
By:

Air Version 2.9.0

I'm scared to take my Air Pure out of the garage now and I have 2.9.0 but have not gotten notice yet for this 2.9.2 yet
 
mwscan said:
I agree people to make mistakes. I myself have made many. Just ask my wife. That said, Lucid has recent software errors that are way too famous. They really need to put as much extra time into testing before release as they need to make sure it’s smooth. It’s a matter of reputation at this point. Cliché apply. Haste makes waste. A stitch in time saves nine. I admire that they are jumping on this and handling it as quickly as they can. That’s to their credit. But they should not have had to do this in the first place. I’ve worked in Silicon Valley all my life. I know whereof I speak from very personal experience in premature software releases.
Click to expand...
Meta and their “move fast and break stuff” motto would like a word… :p
 
mwscan said:
I agree people to make mistakes. I myself have made many. Just ask my wife. That said, Lucid has recent software errors that are way too famous. They really need to put as much extra time into testing before release as they need to make sure it’s smooth. It’s a matter of reputation at this point. Cliché apply. Haste makes waste. A stitch in time saves nine. I admire that they are jumping on this and handling it as quickly as they can. That’s to their credit. But they should not have had to do this in the first place. I’ve worked in Silicon Valley all my life. I know whereof I speak from very personal experience in premature software releases.
Click to expand...
Hindsight is 20:20
 
Hi, everyone.

On Friday night we learned that a small subset of Lucid Air vehicles in the single-motor Pure configuration developed a fault after installing the most recent software update, version 2.9.2. We immediately pulled back this software release, and our engineering teams validated a resolution for affected vehicles that is currently being rolled out.
 
mwscan said:
I agree people to make mistakes. I myself have made many. Just ask my wife. That said, Lucid has recent software errors that are way too famous. They really need to put as much extra time into testing before release as they need to make sure it’s smooth. It’s a matter of reputation at this point. Cliché apply. Haste makes waste. A stitch in time saves nine. I admire that they are jumping on this and handling it as quickly as they can. That’s to their credit. But they should not have had to do this in the first place. I’ve worked in Silicon Valley all my life. I know whereof I speak from very personal experience in premature software releases.
Click to expand...
Working in Silicon Valley all your life then you of all people should know it’s completely unreasonable to think stuff like this won’t ever happen. All the QA and beta testing in the world can’t pick up everything. People should pay more attention to how quick a company is to act when something like this does happen.

To Lucid’s credit it seems they pulled it pretty quickly which shows the backend systems have been set up to handle an event like this and had a fixed version ready to deploy less than 24 hours later.

Also, have you seen the Rivian forums this week? Seems some owners experienced the exact same thing with cars getting bricked on the latest update also, so let’s not haul Lucid over the coals when this has happened with other companies as well.
 
marqie said:
Hi, everyone.

On Friday night we learned that a small subset of Lucid Air vehicles in the single-motor Pure configuration developed a fault after installing the most recent software update, version 2.9.2. We immediately pulled back this software release, and our engineering teams validated a resolution for affected vehicles that is currently being rolled out.
Click to expand...
Maybe for clarification it should be called 2.9.3?
 
HC_79 said:
Working in Silicon Valley all your life then you of all people should know it’s completely unreasonable to think stuff like this won’t ever happen. All the QA and beta testing in the world can’t pick up everything. People should pay more attention to how quick a company is to act when something like this does happen.

To Lucid’s credit it seems they pulled it pretty quickly which shows the backend systems have been set up to handle an event like this and had a fixed version ready to deploy less than 24 hours later.

Also, have you seen the Rivian forums this week? Seems some owners experienced the exact same thing with cars getting bricked on the latest update also, so let’s not haul Lucid over the coals when this has happened with other companies as well.
Click to expand...
Not hauling them over the coals. And I certainly know that these things happen. From very, very personal experience. I also know from personal experience what it can do to reputation and Lucid has recently has problems with the Gravity that became way too famous. Nothing in this world is perfect, and never will be, but as a matter of PR, it would be beneficial to say that a major release went out and everything went smooth as glass. Not perfect, but close.
 
Pure RWD owner here. I'm not a software engineer, but I play one on TV. ;) My other car (Mach-E) also has regular software updates. I tend to wait a bit before installing updates (unless labelled urgent to fix a major issue). All of the below can be true:
  • I absolutely love my Air, it's the best car I've ever owned.
  • Pushing a non-urgent update that renders my car undriveable is unacceptable, period. No amount of excuses or what-abouts change that.
  • I'm grateful that Lucid was able to correct the error so quickly.
FWIW--my Air is still on 2.8.30 and says its up-to-date.
 
HC_79 said:
Working in Silicon Valley all your life then you of all people should know it’s completely unreasonable to think stuff like this won’t ever happen. All the QA and beta testing in the world can’t pick up everything. People should pay more attention to how quick a company is to act when something like this does happen.

To Lucid’s credit it seems they pulled it pretty quickly which shows the backend systems have been set up to handle an event like this and had a fixed version ready to deploy less than 24 hours later.

Also, have you seen the Rivian forums this week? Seems some owners experienced the exact same thing with cars getting bricked on the latest update also, so let’s not haul Lucid over the coals when this has happened with other companies as well.
Click to expand...
And to be crystal clear, I very very much appreciate the quick response.
 
HC_79 said:
Working in Silicon Valley all your life then you of all people should know it’s completely unreasonable to think stuff like this won’t ever happen. All the QA and beta testing in the world can’t pick up everything. People should pay more attention to how quick a company is to act when something like this does happen.
Click to expand...
I can see both sides of this debate, but I have to align with the "should have done more homework before release" side - Lucid is under the microscope, especially where software is concerned, and needs to be extra, extra careful in every move. Also, it isn't like new software release problems haven't occurred with Lucid before - It isn't a matter of "won't ever happen." It has happened, more than once.

I applaud their responsiveness - pretty awesome, actually! But a couple things come to mind. First, what is it with Friday software releases? Is that the most appropriate time to have all hands on deck in case of emergency? Second, if I were headed out to my kid's school graduation or to go to see my dying parent and my car was bricked because of this mistake, I would have a hard time thinking "well, mistakes can happen."

Cars are commodities and, as such, we expect them to get us from point a to b whenever we want. OK, we may have to drive ourselves, with our own hands on the wheel or not have Dolby Atmos playing or complain about the windshield wipers not being perfectly timed - but, you can't brick the car. You just can't.

The customers and potential customers will write the rest of the story of Lucid - and I hope so very much for a long, long story - but the author seems to keep writing every chapter as if it might be the last.

I don't even have an Air, so I bow out of this particular software debate.

Dream Ahead!
 
Zinee said:
Pure RWD owner here. I'm not a software engineer, but I play one on TV. ;) My other car (Mach-E) also has regular software updates. I tend to wait a bit before installing updates (unless labelled urgent to fix a major issue). All of the below can be true:
  • I absolutely love my Air, it's the best car I've ever owned.
  • Pushing a non-urgent update that renders my car undriveable is unacceptable, period. No amount of excuses or what-abouts change that.
  • I'm grateful that Lucid was able to correct the error so quickly.
FWIW--my Air is still on 2.8.30 and says its up-to-date.
Click to expand...
So is mine.
 
IMG_2544.webp

Were these labels like “make a slight left” on the map pre 2.9.0? Or is this new? I know the voice guidance says it but haven’t noticed the label being that descriptive before 🤷‍♂️
 
Still waiting. I have a 2025 Air GT. Why haven't I been offered this update?
 
Bobby said:
I'd request that everybody here to remember something: people make mistakes. Lucid messed this one up, and I will not in any way justify or excuse that. That said, assuming the patch comes today, less than 24 hours later, on a weekend, we all need to stand up and acknowledge how well they handled the problem.
Click to expand...
They hyped this release extensively. The first documented instance I can see of this issue came on Thursday (per this thread), but they insisted on the release, to the point that when I installed it, and called to report the issue, they already had the pre-recorded message.

Not only that, rushing to a solution to unbrick the impacted cars, having a track record of unreliable software creates hesitance to trust the patch release on grounds of having other issues that may incur on safety concerns.

I cannot agree they handled this adequately. They bricked a substantial amount of cars for a couple days. Sure people make mistakes, but it is a bit insensitive to celebrate how they have “managed” the mishap ignoring how people were affected by this, and how were they left to hang dry. Furthermore, this is not an update of a phone or a tablet, that if it glitches there is no risk for the public safety. Regulation, development and validation of these releases seem more driven by hype and profit than stability and public safety concerns.
 
Lfcintron said:
They hyped this release extensively. The first documented instance I can see of this issue came on Thursday (per this thread), but they insisted on the release, to the point that when I installed it, and called to report the issue, they already had the pre-recorded message.

Not only that, rushing to a solution to unbrick the impacted cars, having a track record of unreliable software creates hesitance to trust the patch release on grounds of having other issues that may incur on safety concerns.

I cannot agree they handled this adequately. They bricked a substantial amount of cars for a couple days. Sure people make mistakes, but it is a bit insensitive to celebrate how they have “managed” the mishap ignoring how people were affected by this, and how were they left to hang dry. Furthermore, this is not an update of a phone or a tablet, that if it glitches there is no risk for the public safety. Regulation, development and validation of these releases seem more driven by hype and profit than stability and public safety concerns.
Click to expand...
Nobody is ignoring how people were affected.

But mistakes can and will happen. That is the definition of how accidents work.

The question then becomes, after doing all the work to minimize accidents wherever possible, how one responds to an emergent accident when it occurs.

There are many options, but “pull the release immediately and ship a fix less than 24 hours later on a weekend that works and unbricks all vehicles” is a pretty good choice.
 
borski said:
Nobody is ignoring how people were affected.

But mistakes can and will happen. That is the definition of how accidents work.

The question then becomes, after doing all the work to minimize accidents wherever possible, how one responds to an emergent accident when it occurs.

There are many options, but “pull the release immediately and ship a fix less than 24 hours later on a weekend that works and unbricks all vehicles” is a pretty good choice.
Click to expand...
Perhaps a good "recovery" under the circumstance. But that's hardly a good measure. It is like saying the firemen were brave. Yes, they were. But the fire should never have started in the first place.

Again, it shows Lucid not have a validation process and protocol. This could have and should have been caught in validation. I know hindsight is 20-20. Learn from it!

Yes, I know validation is brute force. Until we get a lot smarter, brute force at least give you another chance to catch what you (intellectually) missed!

Even AI needs validation! ;)
 
This issue makes me again wonder what happened to the “Insider Track” type communication we received a while ago? Some people want to try new features with risk accepted, maybe they have relatively easy access to another car. That could have gone a long way with this issue.
 
You must log in or register to reply here.
Back
Top