Gravity Bugs / Issues

Yes. It not only resets to "Zen", it also goes back to full brightness. It's just another one of the things we have to reset every time we get in the car (although only at night for this one) -- along with getting back to Tidal or Spotify because the car resets on Sirius, and adjusting the suspension height which stays on the last (usually low) setting although the drive mode resets to "Smooth", which should return the suspension height to standard.

I find this last one particularly annoying. I usually drive in Swift mode but manually adjust the suspension to low. But upon restart, the car has reverted to Smooth mode but the suspension remains set to low. That would be fine if it held that once I switched back to Swift mode to get underway. But as soon as I get underway the suspension starts raising itself, and I have to go back to the screen to lower it. I know that EPA regs require the car to default to the most efficient drive mode upon starting up, but I really wish Lucid would make "low" the default suspension height when going to Swift mode, as most drivers probably choose it for a bit more sporting drive where you would want a lower suspension setting.

But back to the ambient light issue: when we go back to the menu to turn the brightness down and change the color, the color will switch but the rotary brightness control does nothing. The only way we can get the brightness down is to turn the ambient lighting off and then back on, at which time it finally goes to both the color and brightness settings we had set it to earlier.

Getting underway in the Gravity is a royal pain. As frustrated as I am that it didn't even make to a finalist slot for Motor Trend's SUV of the Year, I can actually understand why. The ever evolving arrTotally with you. I’ve got the same problem, and service insists it’s not hardware-related. Hoping the next software update finally addresses it.ay of glitches just so dampen the driving experience.
Totally with you. I’ve got the same problem, and service center insists it’s not hardware related. Hoping the next software update finally addresses it.
 
I seriously doubt Lucid would ship flawed vehicles to Saudi buyers. Their QC process there must be far stricter than what early adopters here are experiencing.
So the Saudi’s get a bug free model and the US get the scraps? 😂. Highly doubt it!
 
So the Saudi’s get a bug-free model, and the US gets the scraps? 😂 Highly doubt it!
Let’s be real, Saudis are the feeding hand Lucid can’t afford to bite. Those cars have to go through extra‑rigorous QC because that market bankrolls the brand. Do you think Prince Sultan Bin Salman was driving around in a Gravity with "no key fob recognized" , a whistling noise over 60mph, or muffled audio on the other end of a call? 😂 Just to name a few.
 
I seriously doubt Lucid would ship flawed vehicles to Saudi buyers. Their QC process there must be far stricter than what early adopters here are experiencing.
So, the flaws that a different QC process at the KSA production facility reveals, would not be shared with the US production facility?

And the cars from US semi-knock down assembly for final assembly in KSA are corrected with that different QC process?

Come on now.
Nice joke.
 
Let’s be real, Saudis are the feeding hand Lucid can’t afford to bite. Those cars have to go through extra‑rigorous QC because that market bankrolls the brand. Do you think Prince Sultan Bin Salman was driving around in a Gravity with "no key fob recognized" , a whistling noise over 60mph, or muffled audio on the other end of a call? 😂 Just to name a few.
If Lucid knew how to fix the bugs they would. When the Saudi's realize the true state of the software more heads will roll.
 
Let’s be real, Saudis are the feeding hand Lucid can’t afford to bite. Those cars have to go through extra‑rigorous QC because that market bankrolls the brand. Do you think Prince Sultan Bin Salman was driving around in a Gravity with "no key fob recognized" , a whistling noise over 60mph, or muffled audio on the other end of a call? 😂 Just to name a few.
We'll never know because he's not gonna post it anywhere! 😀

Lucid sends the good cars to the KSA market and the PIF is ok with the others markets getting the leftovers.
 
I can't imagine the Saudi royalty would have much patience for bugs/issues. Same for the KSA customer base.

I see Lucid getting these bugs exterminated.

That’s the first and only time any Saudi Royalty will be driving themselves, or being driven in something that doesn’t say Rolls Royce on it. They’re investors and promoters but no way do they drive themselves around in an American made SUV.
 
Let’s be real, Saudis are the feeding hand Lucid can’t afford to bite. Those cars have to go through extra‑rigorous QC because that market bankrolls the brand. Do you think Prince Sultan Bin Salman was driving around in a Gravity with "no key fob recognized" , a whistling noise over 60mph, or muffled audio on the other end of a call? 😂 Just to name a few.
Let’s be real, heads have already rolled over Gravity woes. There’s no way the Prince got a perfect Gravity. He may have gotten one with minimal issues but no way did he get a flawless car.
 
If Lucid knew how to fix the bugs they would. When the Saudi's realize the true state of the software more heads will roll.
Something will happen or already is happening.
Heads rolling or something.

The PIF isn't funding Lucid simply to have good cars only in the KSA.
 
That’s the first and only time any Saudi Royalty will be driving themselves, or being driven in something that doesn’t say Rolls Royce on it. They’re investors and promoters but no way do they drive themselves around in an American made SUV.
Absolutely.
However, based on that one drive along with the sentiment of the KSA consumers, Lucid leadership will hear something.
 
So, the flaws that a different QC process at the KSA production facility reveals, would not be shared with the US production facility?

And the cars from US semi-knock down assembly for final assembly in KSA are corrected with that different QC process?

Come on now.
Nice joke.
You might want to do some research.
- US market: Cars are fully built at Lucid’s AMP‑1 facility in Casa Grande, Arizona.
- Saudi market: Lucid operates a facility in King Abdullah Economic City (KAEC) that currently does semi‑knockdown (SKD) assembly. That means partially built cars are shipped from the US and then finished in Saudi Arabia.

Because of that, the QC steps may look different, the Saudi assembly has to check both the imported components and the final assembly work

Beyond software bugs, I see some Gravity owners are dealing with major cosmetic defects too. These issues vary vehicle by vehicle, which points to inconsistent QC
 
Last edited:
So, the flaws that a different QC process at the KSA production facility reveals, would not be shared with the US production facility?

And the cars from US semi-knock down assembly for final assembly in KSA are corrected with that different QC process?

Come on now.
Nice joke.
BTW, I’m sure Gravity owners have already shared plenty of flaws with the US production facility. The real question, have they been fixed? From what I have seeing, the same issues keep surfacing car by car.

Perfect examples: the 5‑seater models still squeaking noise from the second row while driving and that horrible grinding sound from the seat tracks when moving has been called out repeatedly by reviewers on YouTube. These aren’t new complaints. They’ve been raised many times. So why are they still rolling off the line unfixed? I just got my Gravity delivered with those same defects, plus 12 more on my service list.

Do you still find it funny?
 
Last edited:
Yesterday I was washing my Gravity with the FOB on the front seat, it takes a while! Anyhow after around 30 minutes (guess) the car locked itself with the FOB inside. Not a problem as I was home and had the means to open the car. Struck me as odd that the car would do this with the FOB inside. I assume the FOB went to sleep and for security reasons the car locked itself. Do not recall this happening on other vehicles. Has anyone else seen this happen?
Simple enough ...
  • Lock the car when the fob isn't around (ie, you walked away)
So, the fob goes to sleep and the Gravity thinks you walked away, this would trigger the action.

Unfortunately, It is a typical software bug :confused: where state wasn't saved/considered.
  • Don't lock the car if the fob is inside.
  • Don't lock the car if the fob was inside and the doors have not opened.
Writing software is the easy part. Considering the edge-cases and error handling is where the real magic happens.

Working at Oracle, I've lost count how many times we flagged situations like this where management would say "No, that's not a marketing requirement" 🤬 .. When the "shituation hit the fan" at the customer's, it was ugly.
 
You might want to do some research.
- US market: Cars are fully built at Lucid’s AMP‑1 facility in Casa Grande, Arizona.
- Saudi market: Lucid operates a facility in King Abdullah Economic City (KAEC) that currently does semi‑knockdown (SKD) assembly. That means partially built cars are shipped from the US and then finished in Saudi Arabia.

Because of that, the QC steps may look different, the Saudi assembly has to check both the imported components and the final assembly work

Beyond software bugs, I see some Gravity owners are dealing with major cosmetic defects too. These issues vary vehicle by vehicle, which points to inconsistent QC
Nothing new to me in the info you stated.

"QC steps may look different". Speculation.
May not, but let's say they do.
Issues found during that QC process not shared with US? I doubt that.
 
BTW, I’m sure Gravity owners have already shared plenty of flaws with the US production facility. The real question, have they been fixed? From what I have seeing, the same issues keep surfacing car by car.

Perfect examples: the 5‑seater models still squeaking noise from the second row while driving and that horrible grinding sound from the seat tracks when moving has been called out repeatedly by reviewers on YouTube. These aren’t new complaints. They’ve been raised many times. So why are they still rolling off the line unfixed? I just got my Gravity delivered with those same defects, plus 12 more on my service list.

Do you still find it funny?
Yes I do.

Gravities were going to the KSA market before the US market.

My point: Info from KSA deliveries are being shared with US. Some of the examples you provide may or may not be limited to the US market. Unless data shows difference in quality of cars in the two markets, the assertion of diffences is speculation.

Speculation fills in until data are available.
Fun to speculate and assertions made can be funny. Maybe not to you, but to me.
 
Nothing new to me in the info you stated.

"QC steps may look different". Speculation.
May not, but let's say they do.
Issues found during the QC process that were not shared with the US? I doubt that.
It’s really just common sense. If cars are finished at KAEC, they must undergo QC there. From what I understand, Lucid checks US built cars in Casa Grande during production phase, then does another round of quality screening at the regional hub before the car goes to the local service.

That’s why I said QC steps may look different, SKD assembly naturally adds extra checkpoints compared to a single, integrated build at AMP‑1. We all hope defect information is being shared between the facilities. However, Lucid doesn’t publicly publish those internal QC procedures, so you can’t claim them as fact, only as very reasonable assumptions based on manufacturing norms.

For example, German cars feel different depending on whether they’re assembled in the US or Germany, most high end models are assembled in Germany first, then delivered to the US, precisely to protect consistency. Same logic here, build path dictates QC path. It’s like hiring two different contractors for the same job on your house. The work gets done, but the quality can vary. 😉
 
Back
Top