Gravity Bugs / Issues

Maybe, but from the perspective of putting power down on the road, you want the additional power at the rear of the car. As the car accelerates, the front lifts and the rear squats. The rear should be able to handle more power relatively speaking. Its why you see the Rivian take a "cheetah" stance when launching.
Yeah, that's the argument against the DE and why the 0-60 is almost identical to the GT.
 
Yeah, that's the argument against the DE and why the 0-60 is almost identical to the GT.

I'm not sure a 0.3-0.4 second faster time to 60 is almost identical? I've only seen 0-150 and quarter-mile times for the Dream Edition, so I'm not sure what kind of differences those numbers will show relative to the GGT.
 
I'm not sure a 0.3-0.4 second faster time to 60 is almost identical? I've only seen 0-150 and quarter-mile times for the Dream Edition, so I'm not sure what kind of differences those numbers will show relative to the GGT.
Drag Times measured the GT at 3.12s (w/ rollout) and 3.31 (wo/ rollout).
Both versions don't reach peak horsepower until after 60mph and the DE is much quicker at very high speeds.
 
Thanks. I am curious if Customer Care was misinformed in saying the cars had to be taken to Service Centers for the final steps of the 3.3.1 update and, if so, why the release notes wouldn't simply have said the work could be done either by a Service Center of a Mobile Technician.

However, it won't actually matter in my case. Our first Gravity is at a Service Center, anyway, having its rear drive unit replaced and a replaced HUD calibrated (if they can get the unit to accept the necessary software that it is thus far refusing to recognize), and they will do the 3.3.1 update there. Our second Gravity has already had 3.3.1 downloaded at the factory, where it is now waiting for transport to us.

The mobile tech was able to reprogram both key fobs at my house. I received the second fob when my DE was in for an RDU replacement about two weeks ago. I did ask them for it and I would encourage you to as well. I’m going to bet that they will find one for you.
 
As was another poster whose rear drive unit was replaced, I'm not sure the drive unit actually failed. Nor am I sure that Lucid is sure. The problem corrected with a software reboot, and we drove the car with no other drive unit issues at highway speeds for the remaining couple of hundred miles of the trip. Lucid said they were replacing the unit "out of an abundance of caution."

There is some really bizarre stuff going on with the software of this car. We have had destination routes spontaneously switch to unknown destinations while driving down the road. We have had the blind spot displays put up frozen images from some miles or some minutes earlier instead of the real-time live displays we are supposed to get. And at least two other posters have reported one or the other of the same issues. And our car has refused at least twice to download software modules that Lucid technicians were trying to install.

I think it is possible that the RDU faults some of us are seeing originate with the software but Lucid, not knowing what's what at this point, is replacing the drive units just in case . . . and probably so that they can get the affected units back to engineering to dive deeper into the cause.

I’m not sure if I’m the other poster you referred to, but I want to reiterate that the numerous error messages I received when my rear drive unit “failed” cleared with a reboot and the car drove fine after the reboot. I wasn’t eager to have the RDU replaced because the car seemed just fine. In contrast, when my Model X had a rear drive unit failure, you KNEW it had failed.
 
I’m not sure if I’m the other poster you referred to, but I want to reiterate that the numerous error messages I received when my rear drive unit “failed” cleared with a reboot and the car drove fine after the reboot. I wasn’t eager to have the RDU replaced because the car seemed just fine. In contrast, when my Model X had a rear drive unit failure, you KNEW it had failed.

I think it might have been your post I was remembering. I also think another poster had an RDU failure that actually stranded him, but I'm not sure I'm remembering it correctly. As with you, when the drive units failed in both our 2015 Model S and our Air Dream P, we knew it. The Tesla couldn't make it out of our garage and had to be wenched onto a truck, and our Air went into an 8mph limp mode. (We were almost home and made it the last couple of miles by getting onto residential side streets.)

With the Gravity, while its speed was capped at 51mph, it accelerated to that speed completely normally and repeatedly.


The mobile tech was able to reprogram both key fobs at my house. I received the second fob when my DE was in for an RDU replacement about two weeks ago. I did ask them for it and I would encourage you to as well. I’m going to bet that they will find one for you.

Assuming the work referred to in the release notes as requiring an "in-person technician" has to do with reprogramming the key fob and not something else, I wish Lucid had made it clear that it could be done by a mobile tech (and that Lucid Customer Care was properly informed), as it would have saved a good bit of angst on the part of owners who live a long way from a Service Center.
 
Last edited:
Maybe, but from the perspective of putting power down on the road, you want the additional power at the rear of the car. As the car accelerates, the front lifts and the rear squats. The rear should be able to handle more power relatively speaking. Its why you see the Rivian take a "cheetah" stance when launching.
To be fair on the Rivian, I don’t know if I’ve ever driven a car whose front pulls up so high on acceleration and dives down on braking as our R1S…so I don’t know if they’ve got it all figured out out.
 
Has anyone successfully gotten a USB flash drive to work for Halo? I purchased a SanDisk with double the speed requirements of Lucid and all I get are messages that the drive is too slow. I called customer service as it says to do if you insert a drive that meets the requirements and it still doesn't work. They didn't have an answer for me and are supposed to follow up tomorrow.
 
Has anyone successfully gotten a USB flash drive to work for Halo? I purchased a SanDisk with double the speed requirements of Lucid and all I get are messages that the drive is too slow. I called customer service as it says to do if you insert a drive that meets the requirements and it still doesn't work. They didn't have an answer for me and are supposed to follow up tomorrow.
Yes, mine works fine. I had to format it twice using the car but it did work.
 
Has anyone successfully gotten a USB flash drive to work for Halo? I purchased a SanDisk with double the speed requirements of Lucid and all I get are messages that the drive is too slow. I called customer service as it says to do if you insert a drive that meets the requirements and it still doesn't work. They didn't have an answer for me and are supposed to follow up tomorrow.

Make sure it's a real SanDisk, unfortunately there are a ton of fake ones out there (especially from Amazon sellers). The real ones are great but for a while it was a total crapshoot whether you'd get a genuine one or not.
 
Has anyone successfully gotten a USB flash drive to work for Halo? I purchased a SanDisk with double the speed requirements of Lucid and all I get are messages that the drive is too slow. I called customer service as it says to do if you insert a drive that meets the requirements and it still doesn't work. They didn't have an answer for me and are supposed to follow up tomorrow.
this is the one I'm using.
SanDisk 512GB Ultra Fit USB 3.2... https://www.amazon.com/dp/B0BY2X88LD?ref=ppx_pop_mob_ap_share
 
this is the one I'm using.
SanDisk 512GB Ultra Fit USB 3.2... https://www.amazon.com/dp/B0BY2X88LD?ref=ppx_pop_mob_ap_share

Okay, I'm totally confused. The release notes specify that it has to be a USB 2.0 stick. There are relatively few of them available, so I ordered four SanDisk sticks (SDCZ60-256GB-B35) sticks from Amazon -- two for each of our Gravities. They double the storage, write speed, and read speed that Lucid says is the minimum required.

Like you, @Jackles is using a 3.2 stick.

Yet @Steve11ca is reporting the SD sticks of the same specs that I ordered per the release notes are not working and that Customer Care cannot yet give an explanation or suggest a fix.

As neither of our Gravities are currently accessible to us (one in the shop and one pending delivery), I cannot try these out myself. I already had a supply of SanDisk 3.0 sticks on hand (SDCZ73-256G-G46). Will they work?

What's going on? Why must everything about Gravity release notes be so confusing? (People are still trying to sort out whether their cars really have to go to a Service Center to complete the 3.3.1 download or whether mobile techs can do it.)

 
Sigh . . . who writes these release notes?

I assumed they just meant the minimum spec, USB3.2 is backwards compatible.
 
Sigh . . . who writes these release notes?
You’ll be fine. The release notes specified a minimum; I can see how it was confusing, but any USB3 stick will degrade gracefully to USB2.

The people having issues are having issues due to the feature being new and buggy, not because their USB stick doesn’t have the right special sauce.

It took me two tries.
 
I assumed they just meant the minimum spec, USB3.2 is backwards compatible.

You’ll be fine. The release notes specified a minimum; I can see how it was confusing, but any USB3 stick will degrade gracefully to USB2.

The people having issues are having issues due to the feature being new and buggy, not because their USB stick doesn’t have the right special sauce.

It took me two tries.

I guess I should post beforehand about anything I plan to order based on release notes in order to be sure I understand all the unsaid things the release is saying to those who aren't well-informed on such things.
 
Back
Top