Air Version 2.9.2 - Pure RWD only

[Gener Tejero]

I updated about 2 hours ago to 2.9.2. The app informed me that the update was successful. When I tried to pull out of my driveway, it gave me a "Drive System Fault" and to call customer service. I tried to call and was on hold for 30 minutes. I had to give up and leave my telephone number to be called back. It is now 1.5 hours later and no call back yet. I suspect they customer service is bogged down by this failure.

 

[Hammerthyme]

There's a lot of discussion on Reddit (r/lucid) about this. Seems like 2.9.2 was created for Air Pure RWD. Looks like many people got the drive system fault error after the patch and can't drive it. Seems like they cancelled the rest of the rollout.

 

[LucidPea]

There's a lot of discussion on Reddit (r/lucid) about this. Seems like 2.9.2 was created for Air Pure RWD. Looks like many people got the drive system fault error after the patch and can't drive it. Seems like they cancelled the rest of the rollout.

yikes

 

[larrycpa]

I got 2.92 Pure RWD. Seems fine so far

 

[The_Don]

I'm wondering if some of these recent updates are similar to recent Gravity updates in that they incorporate an architectural overhaul.

 

[MiamiMiami]

I installed this 2.9.2 update last night while out (in another car). When I got home, it had finished up. I reset the car in abundance of caution. This morning I had no issues driving it. I had prior short-term lease for an Air Touring and just switched the first week of April to an Air Pure. So I'm used to the occasional software glitch. But this worked out fine, so far.

 

[nck]

Is 2.9.2 only for Pure? What was in the release notes?

 

[MiamiMiami]

Is 2.9.2 only for Pure? What was in the release notes?

I've read it's only for the Pure. Seems to be identical to the 2.9.0 release, perhaps it's just targeted for the Pure and is otherwise it's the same.

 

[tonybot]

Scouring forums, some are fine after 2.9.2, but many others have experienced a drive system fault. This update was presented for my 2024 Pure but pulled before I could update - which might have been a blessing. I was initially wondering how Lucid QA missed something obvious, but seeing reports from some folks without any issues, I could venture a guess about what they missed. However, what is worrisome is that such issues are happening with a smaller footprint compared to other manufacturers. I wonder what hardware differences are causing such “catastrophic” issues, such as the drive system fault, and I hope they figure out a solid testing regime before the midsize rollout to catch these much earlier in the cycle.

Software remains Lucid’s Achilles heel, and I do hope they figure this out sooner rather than later - as a Lucid lover, owner, and shareholder.

 

[BS8899]

Scouring forums, some are fine after 2.9.2, but many others have experienced a drive system fault. This update was presented for my 2024 Pure but pulled before I could update - which might have been a blessing. I was initially wondering how Lucid QA missed something obvious, but seeing reports from some folks without any issues, I could venture a guess about what they missed. However, what is worrisome is that such issues are happening with a smaller footprint compared to other manufacturers. I wonder what hardware differences are causing such “catastrophic” issues, such as the drive system fault, and I hope they figure out a solid testing regime before the midsize rollout to catch these much earlier in the cycle.

Software remains Lucid’s Achilles heel, and I do hope they figure this out sooner rather than later - as a Lucid lover, owner, and shareholder.

Honestly, if these reports of anomalies are true, this kind of SW update is illustrative of Lucid's ineptness in SW management. This is not the first-time things like that happen.

 

[Cabonzhp]

There must be some common thread of passes and failures. I’ve seen cars from 24 to 26 both pass and fail. Seems to me that everyone got the Low Battery message in the app after the update ‘completed’. I was plugged in to L1 for the update.

 

[BS8899]

There must be some common thread of passes and failures. I’ve seen cars from 24 to 26 both pass and fail. Seems to me that everyone got the Low Battery message in the app after the update ‘completed’. I was plugged in to L1 for the update.

One would think so. Lucid should have had records of all the HW/FW/SW iterations on each and every one of their vehicles manufactured.

If Lucid had done a thorough validation, toot-caused and archive the error codes, before they release their SW updates, they should have caught errors like this before they release the updates.

 

[MikeM.]

My 2025 Air Pure RWD is sitting in the driveway from an update performed last night. Cannot get it into drive because of the error. No reason to call as they added a message about the issue and that they are working on a resolution. Did do not receive any other errors or indications of an update issue until we tried to leave this morning for an errand.

We are vehicle-less due to a charge port failure on our Tesla MS and it is sitting in their shop until they have time to look at it.

 

[BS8899]

My 2025 Air Pure RWD is sitting in the driveway from an update performed last night. Cannot get it into drive because of the error. No reason to call as they added a message about the issue and that they are working on a resolution. Did do not receive any other errors or indications of an update issue until we tried to leave this morning for an errand.

We are vehicle-less due to a charge port failure on our Tesla MS and it is sitting in their shop until they have time to look at it

Sad, and quite unacceptable! This kind of lapses should be totally preventable. The emphasis is/was not there.

 

[MiamiMiami]

There must be some common thread of passes and failures. I’ve seen cars from 24 to 26 both pass and fail. Seems to me that everyone got the Low Battery message in the app after the update ‘completed’. I was plugged in to L1 for the update.

I actually didn’t receive a low battery message. It was stuck for a while on 95% updated and then was ready abruptly. I am supposed to have the relatively recent vintage 2026. Maybe that makes a difference.

 

[Buffalo Bob]

One would think so. Lucid should have had records of all the HW/FW/SW iterations on each and every one of their vehicles manufactured.

I have to wonder whether some pretty obvious steps take place...

For example, the software engineers should have ready access to the specific Lucid vehicles they are developing for. If a team is working on an update for the Air Pure RWD, give them access to that model in various years and configurations so they can test the software on their own over the development and testing phase. I'll wager a lot of Lucid employees get company cars. Part of the deal could be that they are assigned an assortment of years, models and options, and that the employees must agree to sometimes give their vehicle up for a while and use another vehicle from a small shared fleet while their specific vehicle is tested. Software being developed for a more general release would of course need a wider array of vehicles.

For a few days prior to the planned release, the update should be pushed to all targeted fleet vehicles.

Similarly, to BS8899's point, the vehicle's diagnostic system should already be able to at least report a significant issue right away. If they have a database including the manufacturing date, model, and the HW/FW/SW iterations, it should be easy to look for any common threads as problems are reported... Ideally in the pre-release testing phase, but certainly as soon as problems arise post release. If this is happening, then something about it is not happening correctly.

A more thorough testing protocol is warranted even if it leads to a further delayed release. People may grouse about how long it's been since the last update, but nothing like their fury when staring at a big red screen.

 

[tonybot]

I have to wonder whether some pretty obvious steps take place...

For example, the software engineers should have ready access to the specific Lucid vehicles they are developing for. If a team is working on an update for the Air Pure RWD, give them access to that model in various years and configurations so they can test the software on their own over the development and testing phase. I'll wager a lot of Lucid employees get company cars. Part of the deal could be that they are assigned a wide assortment of years, models and options, and that the employees must sometimes give their car up for a while and use another vehicle from a small shared fleet while their specific vehicle is tested. Software being developed for a more general release would of course need a wider array of vehicles.

Similarly, to BS8899's point, the vehicle's diagnostic system should already be able to at least report a significant issue right away. If they have a database including the manufacturing date, model, and the HW/FW/SW iterations, it should be easy to look for the common threads as problems are reported... Ideally in the pre-release testing phase, but certainly as soon as problems arise post release. If this is happening, then something about it is not happening correctly.

A more thorough testing protocol is warranted even if it leads to a further delayed release. People may grouse about how long it's been since the last update, but nothing like their fury when staring at a big red screen.

Agree! And super important for Lucid to get this absolutely right before midsize gets released.

 

[BS8899]

I have to wonder whether some pretty obvious steps take place...

For example, the software engineers should have ready access to the specific Lucid vehicles they are developing for. If a team is working on an update for the Air Pure RWD, give them access to that model in various years and configurations so they can test the software on their own over the development and testing phase. I'll wager a lot of Lucid employees get company cars. Part of the deal could be that they are assigned a wide assortment of years, models and options, and that the employees must sometimes give their car up for a while and use another vehicle from a small shared fleet while their specific vehicle is tested. Software being developed for a more general release would of course need a wider array of vehicles.

Similarly, to BS8899's point, the vehicle's diagnostic system should already be able to at least report a significant issue right away. If they have a database including the manufacturing date, model, and the HW/FW/SW iterations, it should be easy to look for the common threads as problems are reported... Ideally in the pre-release testing phase, but certainly as soon as problems arise post release. If this is happening, then something about it is not happening correctly.

A more thorough testing protocol is warranted even if it leads to a further delayed release. People may grouse about how long it's been since the last update, but nothing like their fury when staring at a big red screen.

We are not inventing new science or engineering here. When you are building a HW/FW/SW system (that's you, Lucid), many a times, these components (HW/FW/SW) are managed by different engineering entities and are updated "asynchronously". If there is not an oversight body (e.g., an integrator) that oversees the whole process, you are just courting disaster.

The interactions at the integrated system level are not really "deterministic" at our current state-of-art. Perhaps AI will one day get us closer to that.

System validation is a brute force effort. it won't catch everything. Nevertheless, it needs to be done. No one engineer is smart enough to anticipate all the system interactions when you change just "one item".

 

[MikeM.]

I am hoping that they are working the weekend to solve this. I keep checking to see if they have an update on the app. Wish we could rollback to previous version for now.

 

[MorganB]

on the 2.9.0 thread supposedly the update has been pulled and a new update for the bricked cars should go out in the next 3 or 4 hours.