Gravity Bugs / Issues

[msaunders9430]

I thought it was the fan speed being to high (artic blast), not a squeak/squeal.

Like this

M

Post in thread 'Software 3.3.20 Update'

Dec 13, 2025

I installed the update this morning and have gone on a couple of drives since. The software has performed flawlessly. I wasn’t experiencing any significant issues before, so it’s not really a change. The one thing I can say seems to have improved is the fan speed on Auto, which often was too vigorous in the past (so I had stopped using it) but now seems more mellow. Just as importantly, this update doesn’t seem to have caused any new issues.

• maxtor10000

• 

 

[Ron_Burgundy]

Like this

M

Post in thread 'Software 3.3.20 Update'

Dec 13, 2025

I installed the update this morning and have gone on a couple of drives since. The software has performed flawlessly. I wasn’t experiencing any significant issues before, so it’s not really a change. The one thing I can say seems to have improved is the fan speed on Auto, which often was too vigorous in the past (so I had stopped using it) but now seems more mellow. Just as importantly, this update doesn’t seem to have caused any new issues.

• maxtor10000

• 

There was arctic blast, but there’s also a squeak/squeal coming from front vents that only started when it got cold and I started using heat. Wasn’t an issue in the summer. Others seem to have issue as well.

 

[NoseyReporter]

Update is gooooood

 

[EVCar]

Regarding Halo USB, the Gravity Manual says: "Compatible USB 2.0 devices should be at least 128GB".
USB 3.0 came out in 2008 and has been widely used for many years.
Does anyone know why USB 2.0 is used in Gravity?
Is it less costly? Technical constraint?

 

[DrZorro]

Regarding Halo USB, the Gravity Manual says: "Compatible USB 2.0 devices should be at least 128GB".
USB 3.0 came out in 2008 and has been widely used for many years.
Does anyone know why USB 2.0 is used in Gravity?
Is it less costly? Technical constraint?

It likely is USB 3.0+ but they are merely putting in a minimum requirement of USB 2.0 which is backwards compatible. The one I have in my car is USB 3.1.

 

[Ron_Burgundy]

Regarding Halo USB, the Gravity Manual says: "Compatible USB 2.0 devices should be at least 128GB".
USB 3.0 came out in 2008 and has been widely used for many years.
Does anyone know why USB 2.0 is used in Gravity?
Is it less costly? Technical constraint?

Most of us have USB 3.x and are fine. In fact, early on some folks had issues trying 2.0, so as @DrZorro said I think it’s mean to be a minimum, but 3.0+ seems to work well.

 

[borski]

Even if it is a 2.0 port, a 3.0+ drive will still be backward-compatible.

 

[EVCar]

Even if it is a 2.0 port, a 3.0+ drive will still be backward-compatible.

I assume a 2.0 port would not be as fast as 3.0, correct?

 

[socktucker]

Looks like Lucid hasn't made any progress on the issue of vehicle software automatically updating. Woke up this morning to the following notices on my iPhone - vehicle software update is available (4:46am), software update has started (4:46am), software update complete (5:33am). I'm certain that nobody was in the car and both my wife and I were asleep.

View attachment 35102

I hate the whole charging session start and stop endless alerts. I mean did they even use this app?

 

[borski]

I assume a 2.0 port would not be as fast as 3.0, correct?

Correct, but for recording video it wouldn’t make too much of a difference in this case. But again, I have no idea if it’s a 2.0 port.

 

[Alex]

I hate the whole charging session start and stop endless alerts. I mean did they even use this app?

I encounter this issue with my 80A Lucid Charging station at my vacation home. Upon arrival, I set the charge limit to 80%. There’s no scheduled charging. When the battery reaches 80%, it indicates that the charging is complete. However, approximately every 3 minutes, it attempts to charge again, displaying messages like “Starting to charge” and “Completed.” This cycle repeats multiple times, often stopping at 79% and initiating the process again. Initially, I assumed it was simply trying to reach 80%. To address this, I set the charger to 82% and then reset it to 80% when the charge reached 81%. Unfortunately, the 3-minute charge start/stop notifications persisted. Concerned about potential damage to the charging station due to frequent contactor actuations, I decided to unplug it.

 

[socktucker]

Yes. Same. Lucid

I encounter this issue with my 80A Lucid Charging station at my vacation home. Upon arrival, I set the charge limit to 80%. There’s no scheduled charging. When the battery reaches 80%, it indicates that the charging is complete. However, approximately every 3 minutes, it attempts to charge again, displaying messages like “Starting to charge” and “Completed.” This cycle repeats multiple times, often stopping at 79% and initiating the process again. Initially, I assumed it was simply trying to reach 80%. To address this, I set the charger to 82% and then reset it to 80% when the charge reached 81%. Unfortunately, the 3-minute charge start/stop notifications persisted. Concerned about potential damage to the charging station due to frequent contactor actuations, I decided to unplug it.

Same. Lucid charger. When I use it on my Tesla, it doesn’t do that. They should fix it.

 

[Alex]

Yes. Same. Lucid

Same. Lucid charger. When I use it on my Tesla, it doesn’t do that. They should fix it.

Yes, it’s likely a bug in the car. It’s not the charger because it can’t initiate a charge on the car unless the car requests it. I’ll try it on my Lucid Air, but I’ll have to drive up to the vacation home to do so. I have three Lucid chargers ready to install at home. I’m replacing the Tesla chargers with the Lucid chargers, and it’s probably a quicker way to test.

 

[Xminus6]

After hearing from someone on Reddit that a steering wheel swap could potentially fix the left d-pad being unresponsive and constantly requiring multiple taps to start/stop Drive Assist, I had Lucid swap mine out during their most recent mobile service visit.

I'm happy to report that so far in the last 3 days since the replacement, I haven't had the issue even once, and I am fully confident that it is indeed a hardware defect in many Gravity steering wheels and is not caused by software. It was one of my top annoyances with the car, and now I can cross it off the list.

So if you are still struggling with your left d-pad on the Gravity, get Lucid to swap your steering wheel.

Hi!

 

[prodolf]

I've been uber critical of Lucid since taking delivery of my GDE. I try to be fair but it's not been fun. Yesterday I allowed the most recent update to happen. .......queue angels and harp music, it is fantastic! Maybe now I can really begin to enjoy this car.

 

[jrb24]

Yes, 3.3.9 is a major update that fixes many of the issues we have been dealing with as early adopters. Makes me want to see a 3.4 rev soon! Maybe a phone key and green light detect while waiting at an intersection might be included…

 

[HC_79]

Yes, 3.3.9 is a major update that fixes many of the issues we have been dealing with as early adopters. Makes me want to see a 3.4 rev soon! Maybe a phone key and green light detect while waiting at an intersection might be included…

If you’re on 3.3.9 and think that’s an improvement then wait until to see 3.3.20

 

[Bdr100]

I've been uber critical of Lucid since taking delivery of my GDE. I try to be fair but it's not been fun. Yesterday I allowed the most recent update to happen. .......queue angels and harp music, it is fantastic! Maybe now I can really begin to enjoy this car.

Agreed. Warning, it has not fixed everything but it is a solid step forward.

 

[jrb24]

If you’re on 3.3.9 and think that’s an improvement then wait until to see 3.3.20

Oops good one!

 

[aijunli]

Fogging inside the camera/sensor housing on the windshield causing sensor alerts. It occurred in New Jersey on a cold sunny day. When I am about to park in a Costco parking lot, got two consecutive alerts, sensor blocked followed by high beam assist not available. Got out of the car and saw fogging inside the sensor housing. Took a picture, you can see clearly the two strips of fogging. After done shopping, about 34 min later, the moisture evaporated, as shown by the second picture. Reported this issue to Lucid. Other people in the area also reported same issue.