Gravity Bugs / Issues

Yesterday after locking the car I noticed the front passenger handle did not retract. Have done full reset and let it sleep overnight. No joy. Tech has been notified.
So after an overnight we drive about 3 miles, we attend church, drive back home and amazingly the handle now retracts and is working normally. As we used to say in the trade , FM.
 
think its been posted before but this morning I had to use a plastic straw to get the ice off of the door handles gaps as it would not present itself- 3 minutes of finger numbing frustration
 
BLACK SCREENS ARE BACK

Since 3.3.20 I have not had an instance of black screens… until this morning. Got in car and had the Bear Logo Screens. Waited a while and eventually the center screen came up giving me ability to shift into Reverse but right side (and pilot panel) stayed black. Reverse cameras worked but not sensors. After backing up, I realized that Homelink was not coming up. Put car in park thinking I might have to do a reset and then right screens popped up and I had access to Homelink to close the door. Total time delay was about 2-3 minutes. Not end of the world but I did have to put up with my wife rolling her eyes and saying “this is why I won’t drive your car.” So any claim that 3.3.20 has “totally” fixed the fob (I had one issue of fob not working a couple weeks ago) and black screen issues is false. It has definitely improved but not totally fixed. So be sure to keep you key car and you patience with you going forward.
 
Our mobile tech came out this morning to see what was going on with the piece of underbody panel that is protruding under the car. He said there were no signs of impact damage (which was not likely given it was ahead of the rear axle well inboard of the rear wheel). He thinks the panel just spontaneously warped and caused that end of it to break loose. He's going to order a new part.

He also said Lucid has not gotten back to them on whether the malfunctioning dashboard LED strip is a software or hardware problem, so the car is going to have to be trucked over to the Miami Service Center so that they can sort it out there.

And . . .

SAFETY ALERT: On Friday I raised the suspension to the highest setting so that I could get under the car enough to photograph the warped underbody panel. I did so with no problem. Today (Monday) I again raised the suspension to the highest setting so that the mobile tech could get under the car. I got out of the car after doing so, as I had on Monday. But today the suspension suddenly started lowering while the tech was under the car. Thank God he managed to get out from under the car in time.

But WTF? There was no one in the car. I did not have my phone with me, so there's no chance I hit something in the app. The mobile tech was taking photos with his phone, but it is not linked to the car, and he said he did nothing to lower the suspension.
 
Our mobile tech came out this morning to see what was going on with the piece of underbody panel that is protruding under the car. He said there were no signs of impact damage (which was not likely given it was ahead of the rear axle well inboard of the rear wheel). He thinks the panel just spontaneously warped and caused that end of it to break loose. He's going to order a new part.

He also said Lucid has not gotten back to them on whether the malfunctioning dashboard LED strip is a software or hardware problem, so the car is going to have to be trucked over to the Miami Service Center so that they can sort it out there.

And . . .

SAFETY ALERT: On Friday I raised the suspension to the highest setting so that I could get under the car enough to photograph the warped underbody panel. I did so with no problem. Today (Monday) I again raised the suspension to the highest setting so that the mobile tech could get under the car. I got out of the car after doing so, as I had on Monday. But today the suspension suddenly started lowering while the tech was under the car. Thank God he managed to get out from under the car in time.

But WTF? There was no one in the car. I did not have my phone with me, so there's no chance I hit something in the app. The mobile tech was taking photos with his phone, but it is not linked to the car, and he said he did nothing to lower the suspension.
It tries to automatically level based on the amount of weight it senses in the car, if nobody is in the vehicle. For example, the same thing happens when you sit in the frunk - you’ll sense it raise in a few seconds. Then if you hop off, it will lower again a few seconds later.

I don’t know of a way to “lock” it into a height.
 
It tries to automatically level based on the amount of weight it senses in the car, if nobody is in the vehicle. For example, the same thing happens when you sit in the frunk - you’ll sense it raise in a few seconds. Then if you hop off, it will lower again a few seconds later.

I don’t know of a way to “lock” it into a height.
I think that there are two different things here with regard to suspension height. One is with regard to keeping the car level, such as when you load the rear with a bunch of bags of mulch and sod like an owner on here posted the other day. In that case, the car should raise or stiffen the rear shocks to compensate for this increased load to keep the rear at same level as front so you are not driving down the road with front end pointing upward.

The other case is when you switch from standard height to high setting because you want to take car off-road and have greater clearance. Then, the car should raise both front and back to max and keep it there (as long as you don’t exceed the speed limit for the high setting.)

Now two things could possibly have happened. Car might have been slightly compensating for driver weight when he was in car and then made a slight adjustment to height when he exited to keep it level and tech may have sensed this small adjustment and wisely rolled out thinking it could be coming down. This is the “Give Lucid the benefit of the doubt scenario.”

More likely, the car sensed the driver exiting and closing the door and assumed “we are done off-roading and time to go back to standard ride height” possibly even based on easy exit/entry settings.

For me I had kind of an opposite issue. I was washing it and used the phone app to lower it to lowest so I could more easily reach top and it staying that way whole time. When done, I tried to raise it back to standard using the app and it refused. I had to get back into the car and use the pilot panel to reset height.
 
It tries to automatically level based on the amount of weight it senses in the car, if nobody is in the vehicle. For example, the same thing happens when you sit in the frunk - you’ll sense it raise in a few seconds. Then if you hop off, it will lower again a few seconds later.

I don’t know of a way to “lock” it into a height.
I think that there are two different things here with regard to suspension height. One is with regard to keeping the car level, such as when you load the rear with a bunch of bags of mulch and sod like an owner on here posted the other day. In that case, the car should raise or stiffen the rear shocks to compensate for this increased load to keep the rear at same level as front so you are not driving down the road with front end pointing upward.

The issue is that it behaved differently in two almost identical situations. On Friday I was in the garage by myself when I raised the suspension, got out of the car, and slid under it. It remained in the highest setting until I got back in the car and lowered it using the Pilot Screen command.

Today I raised the suspension and again got out of the car, leaving no one in it. This time the suspension lowered itself without anyone giving it a command.

It may be another manifestation of how this particular car has anomalous software behavior. It's the only one of our three Gravities that doesn't geofence Homelink. It's the only one in which it takes multiple attempts to get Homelink to accept a command to operate a garage door. It's the only one that has the spinning satellite maps that show the car driving through woods and fields instead of on the road. It's the only one with the erratic Vibe lighting behavior. It's the only one that has refused certain software downloads.

Several time now I have asked both the Miami Service Center and Lucid HQ to take this car in for a thorough diagnostic of both the UI hardware and software. So far I have met with no response, and I am beginning to conclude that Lucid is not going to make any attempt to get to the bottom of its erratic behavior and instead just keep paying to have the car trucked back and forth across the state to deal with one-off situations as they arise.

Fortunately, our newest Gravity (built six months later) seems to be relatively free of such behavior, only experiencing the normal level of glitches that are being reported on this forum since the 3.3.20 update. But I have a feeling that this early Gravity is going to be source of perpetual aggravation.
 
Got a nice system warning icon, but don’t know what the error is for. No notification for it anywhere…

What’s the point of having the notification section if it doesn’t even log all the notifications and errors.

This car is a joke

IMG_1295.webp
 
It tries to automatically level based on the amount of weight it senses in the car, if nobody is in the vehicle. For example, the same thing happens when you sit in the frunk - you’ll sense it raise in a few seconds. Then if you hop off, it will lower again a few seconds later.

I don’t know of a way to “lock” it into a height.
Yes. Mine adjusts the suspension when I get out no matter what - even when I have it set to “standard”. Nowhere near as overactive and absurd as our R1S, but it always makes a noise and adjust upon exit.

Now, to be fair, maybe I am too darn fat and my poor car is just letting out a deep breath after having to hold my a— in the car for so long…
 
The issue is that it behaved differently in two almost identical situations. On Friday I was in the garage by myself when I raised the suspension, got out of the car, and slid under it. It remained in the highest setting until I got back in the car and lowered it using the Pilot Screen command.

Today I raised the suspension and again got out of the car, leaving no one in it. This time the suspension lowered itself without anyone giving it a command.

It may be another manifestation of how this particular car has anomalous software behavior. It's the only one of our three Gravities that doesn't geofence Homelink. It's the only one in which it takes multiple attempts to get Homelink to accept a command to operate a garage door. It's the only one that has the spinning satellite maps that show the car driving through woods and fields instead of on the road. It's the only one with the erratic Vibe lighting behavior. It's the only one that has refused certain software downloads.

Several time now I have asked both the Miami Service Center and Lucid HQ to take this car in for a thorough diagnostic of both the UI hardware and software. So far I have met with no response, and I am beginning to conclude that Lucid is not going to make any attempt to get to the bottom of its erratic behavior and instead just keep paying to have the car trucked back and forth across the state to deal with one-off situations as they arise.

Fortunately, our newest Gravity (built six months later) seems to be relatively free of such behavior, only experiencing the normal level of glitches that are being reported on this forum since the 3.3.20 update. But I have a feeling that this early Gravity is going to be source of perpetual aggravation.
Mine stays in “highest” if that’s what it was in, but it still moves a bit like the auto-level.

IDK. There’s a 0% chance I am ever getting under the car…unless my wife runs me over. Which may very well happen if she gets locked out again.
 
Are other still getting the “sensors blocked, dream drive limited” error regularly? That’s the only one I get every single time I drive, multiple times. Yet, DD works fine and nothing is blocked. I don’t believe it’s the condensation issue folks have mentioned as I see none. Huge win compared to the error extravaganza back in August, etc, but still odd.
 
At one time I saw these alerts while looking for a parking spot in a lot. I parked about 30 seconds later and immediately took a look of the sensor housing on the windshield and found that the condensation around the heating wires had already been cleared (see the picture). I think the system turned heating after detecting sensors being blocked. So these alerts can be ignored.
 

Attachments

  • IMG_8141.webp
    IMG_8141.webp
    430.1 KB · Views: 92
Are other still getting the “sensors blocked, dream drive limited” error regularly? That’s the only one I get every single time I drive, multiple times. Yet, DD works fine and nothing is blocked. I don’t believe it’s the condensation issue folks have mentioned as I see none. Huge win compared to the error extravaganza back in August, etc, but still odd.
Yes, pretty much in every drive
 
Haven't had the sensors blocked since the morning humidity dropped here in LA in the last week. I did however this morning have the first experience of unlocking and opening the door to see the seat reclining, moving back and down until it jammed into the back seat. I sat down, pressed the brake pedal and it went back to my profiles position. I reported the incident.
 
Back
Top