Gravity Bugs / Issues

[TahoeMichael]

Strange, mine turn off automatically 90% of the time. It’s really only if it’s a larger sweeping turn that they don’t automatically turn off.

It's very possible that my report was pilot error, as I wasn't behind the wheel long enough to really get used to the car.

 

[Knucklehead]

Owner here. We took delivery about a month ago. Was very excited about the car because honestly, it's beautiful... and it checks all the boxes.

But holy crap do we have a lot of problems with it. I'll share my own:

- Key Fob / Key card issue - Not recognizing it. Seems like the recent helped a bit. Support also helped by walking me through on how to reset the damn key fob.
- Black screen / infotainment
- Glitchy screen
- Driver's seat scoots all the way back and DOWN - This is not OKAY. We have our kid usually seated right behind us and we're lucky the seat doesn't crush him.
- Windshield wipers - They randomly turn on. Spray water. Get stuck in the middle of windshield.
- Volume for music doesn't adjust. You have to manually adjust the volume on the phone AND the car.
- Bluetooth is basically worthless as you can't talk to people on the phone. It's too soft on both sides.
- Car will not shift. Doesn't matter what you do. You just have to sit there awkwardly.
- Software is extremely slow to load up.

I really hope Lucid gets their act together and fixes a lot of these issues. It's not acceptable... especially for a car at this price point. If I had known about all the issues, I would've just gotten something else.

I have had to reboot my "software defined" Rivian probably 30 times since I got it in March. Your regret is totally valid, and unfortunately rebooting our "software defined" vehicles may become the new normal. Have you tried that? In my experience with Rivian, rebooting after a OTA update often helps prevent weird behavior.

Rebooting probably won't help with the more common problems discussed in this thread, but it may help especially with the ones that have been fixed in an update (but your Gravity seems to still have the problem).

 

[Ron_Burgundy]

Has anyone else had an issue with the rear liftgate? Today I closed the rear hatch using the auto-close button and walked around the car to the driver's seat to get moving. The main "car" screen on the pilot panel showed the liftgate was open, which it did not appear to be. I got out and looked out back, and it appeared the liftgate was ever so slightly ajar. Pushing the open button on the liftgate caused it to beep, but nothing would happen. I tried to pull it open manually, to no avail. The app didn't work to open it either, but I could hear it trying to do something. Finally I just pushed hard on the liftgate and it auto-cinched closed. Then I could open and close as normal. Nothing was in the way of the liftgate. I know the frunks have had issues, so I'm curious if I'm alone in having had a rear trunk latch glitch.

I’ve had that happen maybe five times since I took delivery. SC couldn’t replicate it. It’s not really been an annoying issue but it is on the list…the frunk issue happens every time, whereas the
trunk one is extremely rare (for me).

 

[Ron_Burgundy]

Can any owners who recently picked up their Gravity tell us if your were informed of how to do a fob reset and/or a steering wheel reset when you went through your delivery orientation? I know that Lucid may be reluctant to admit they are having these issues but if they don’t, they are going to have a large number of owners getting stranded, assume more serious problem with car and call for tow. Most new owners are not following this forum and otherwise would not have this knowledge.

This also should be required info given to reviewer loan cars. I know Lucid does not want to admit these issues to reviewers, but might be better to say “there is a small bug that we are working on that you might experience. If you do, these workarounds should fix things. We hope to have this little bug corrected soon.” Might be better to admit this issue up front than to leave customer or reviewer stranded out on the road somewhere.

I took delivery almost three months ago and the first thing they did was explain how to reset the car and tell me not to rely on the fob yet. Always use the key card until they got some issues with the fob worked out. The “fob reset” wasn’t known widely by anyone at that point. If it had been, I am confident my SA would’ve mentioned it.

That said, there isn’t a script or list they appear to follow, so I am sure some folks don’t get that info.

 

[hmp10]

Strange, mine turn off automatically 90% of the time. It’s really only if it’s a larger sweeping turn that they don’t automatically turn off.

That's the case as well in our Gravities that I'm describing: larger sweeping turns. But those are extremely common in Naples, and it happens with the Gravities on turns where our other cars , including our two Airs, have consistently self-canceled. Also, the issue seems to have become more frequent, leaving me hoping this is something happening with the software that can therefore be addressed with an OTA update. If it's in the turn-signal mechanism itself, then we're more likely stuck with it.

 

[Ron_Burgundy]

That's the case as well in our Gravities that I'm describing: larger sweeping turns. But those are extremely common in Naples, and it happens with the Gravities on turns where our other cars , including our two Airs, have consistently self-canceled. Also, the issue seems to have become more frequent, leaving me hoping this is something happening with the software that can therefore be addressed with an OTA update. If it's in the turn-signal mechanism itself, then we're more likely stuck with it.

Haven’t noticed it being an issue. Now, of course, it will be an issue as I’ve jinxed myself!

 

[NovemberLima]

Owner here. We took delivery about a month ago. Was very excited about the car because honestly, it's beautiful... and it checks all the boxes.

But holy crap do we have a lot of problems with it. I'll share my own:

- Key Fob / Key card issue - Not recognizing it. Seems like the recent helped a bit. Support also helped by walking me through on how to reset the damn key fob.
- Black screen / infotainment
- Glitchy screen
- Driver's seat scoots all the way back and DOWN - This is not OKAY. We have our kid usually seated right behind us and we're lucky the seat doesn't crush him.
- Windshield wipers - They randomly turn on. Spray water. Get stuck in the middle of windshield.
- Volume for music doesn't adjust. You have to manually adjust the volume on the phone AND the car.
- Bluetooth is basically worthless as you can't talk to people on the phone. It's too soft on both sides.
- Car will not shift. Doesn't matter what you do. You just have to sit there awkwardly.
- Software is extremely slow to load up.

I really hope Lucid gets their act together and fixes a lot of these issues. It's not acceptable... especially for a car at this price point. If I had known about all the issues, I would've just gotten something else.

The gravity has several different volumes that you can control, so that phone, music, nav, etc. are at different levels. In addition, for some reason the way they're implementing bluetooth they are allowing the device to control volume independently of the car, which is confusing. As you found with music, when on a call, grab your phone and turn the volume all the way up - on the phone - then make further adjustments using the steering wheel or volume wheel on the car. This allowed me to make it plenty loud to hear my calls, they just still couldn't hear me very well as other owners have reported. Either the Gravity has a crap microphone, or they need some more software refinement (fingers crossed) to improve it. I also only had to do this once, then my phone I believe remembers the last volume for each bluetooth device?

 

[socktucker]

Driver's seat scoots all the way back and DOWN

This is how easy entry works on the Air, even though it’s laughable and makes it harder to get in and out. I wonder if it’s related.

 

[Ron_Burgundy]

The gravity has several different volumes that you can control, so that phone, music, nav, etc. are at different levels. In addition, for some reason the way they're implementing bluetooth they are allowing the device to control volume independently of the car, which is confusing. As you found with music, when on a call, grab your phone and turn the volume all the way up - on the phone - then make further adjustments using the steering wheel or volume wheel on the car. This allowed me to make it plenty loud to hear my calls, they just still couldn't hear me very well as other owners have reported. Either the Gravity has a crap microphone, or they need some more software refinement (fingers crossed) to improve it. I also only had to do this once, then my phone I believe remembers the last volume for each bluetooth device?

The same wonkiness occurred in our R1S. It has settings to allow for different volumes for phone calls, etc and they always get overridden by current phone settings or something else. My ringtone comes blaring through the speakers even when turned down or off in the R1S

 

[socktucker]

The same wonkiness occurred in our R1S. It has settings to allow for different volumes for phone calls, etc and they always get overridden by current phone settings or something else. My ringtone comes blaring through the speakers even when turned down or off in the R1S

Mine too, does Rivian use android auto?

 

[hwy17er]

It's very possible that my report was pilot error, as I wasn't behind the wheel long enough to really get used to the car.

Well I noticed something strange with the turn signals on my test drives too. On the second one, a SA came along and she explained that if you just click the stalk once or gently the blinker blinks three times and self cancels but if you pull it again or harder it sustains the blinking. I'm not sure it really registered at the time on such a short drive but now that you guys mention this I remembered something funky about the blinkers on this car.

 

[Ron_Burgundy]

Mine too, does Rivian use android auto?

Yes. Android Auto is foundation for Rivian (and Lucid) and then they build on top of it. The engineers on the forum say AA is generally stable and good, but it gets complex with the specializations

 

[prodolf]

I have had to reboot my "software defined" Rivian probably 30 times since I got it in March. Your regret is totally valid, and unfortunately rebooting our "software defined" vehicles may become the new normal. Have you tried that? In my experience with Rivian, rebooting after a OTA update often helps prevent weird behavior.

Rebooting probably won't help with the more common problems discussed in this thread, but it may help especially with the ones that have been fixed in an update (but your Gravity seems to still have the problem).

I have had a 2018 Tesla S 100D and still have my Rivian R1T Launch Edition, actually one of the first 2500 off of the assembly line. Both these vehicles are "software defined" and I never had to reboot my Tesla and only have rebooted my Rivian once in the first week of ownership. The Lucid Gravity's issues are an order of magnitude greater than anything I've experienced with my software defined vehicles.

 

[Ron_Burgundy]

I have had a 2018 Tesla S 100D and still have my Rivian R1T Launch Edition, actually one of the first 2500 off of the assembly line. Both these vehicles are "software defined" and I never had to reboot my Tesla and only have rebooted my Rivian once in the first week of ownership. The Lucid Gravity's issues are an order of magnitude greater than anything I've experienced with my software defined vehicles.

I agree that Gravity issues are an order of magnitude greater, BUT, I reset my Rivian R1S g1 quad probably once every two weeks for glitches. Not an issue on Tesla.

Lucid will likely figure it out. Or they won’t. Not much we can do.

 

[DeaneG]

Yes. Android Auto is foundation for Rivian (and Lucid) and then they build on top of it. The engineers on the forum say AA is generally stable and good, but it gets complex with the specializations

Both use Android Automotive Operating System (AAOS), something completely unrelated to Android Auto, which like CarPlay, is a phone mirroring function.

FWIW I had to reboot my 2018 Model 3 pretty much every time I drove it for the first several months.

 

[HC_79]

I have had a 2018 Tesla S 100D and still have my Rivian R1T Launch Edition, actually one of the first 2500 off of the assembly line. Both these vehicles are "software defined" and I never had to reboot my Tesla and only have rebooted my Rivian once in the first week of ownership. The Lucid Gravity's issues are an order of magnitude greater than anything I've experienced with my software defined vehicles.

you're an outlier then with your Rivian and Tesla. I know owners of both brands who've had to reset them many times to clear out random quirks that pop up.

 

[Ron_Burgundy]

Both use Android Automotive Operating System (AAOS), something completely unrelated to Android Auto, which like CarPlay, is a phone mirroring function.

FWIW I had to reboot my 2018 Model 3 pretty much every time I drove it for the first several months.

Thanks for the clarification. I know the difference but was lazy in my response!

 

[socktucker]

you're an outlier then with your Rivian and Tesla. I know owners of both brands who've had to reset them many times to clear out random quirks that pop up.

It weird becuase my 2023 Model 3, no problems. I also have a 2023 Model Y Performance and it had a myriad of problems. To be fair, my Lucid has had more issues in 60 days than my Model Y has had in 2 years, but the Model Y still had crashes ocassionally and just random stuff like the spoiler falling off.

 

[WeighingGravity]

(The fob thing is fixed, so while that’s fair, it’s now outdated)

Assuming you’re talking about fobs not being recognized for driving, it is not fully fixed yet. I just got let not detected just now. I’m on 3.3.5 with updated fob firmware.

 

[electric]

Yes. Android Auto is foundation for Rivian (and Lucid) and then they build on top of it. The engineers on the forum say AA is generally stable and good, but it gets complex with the specializations

I'm starting to think that engineers on the forum are full of crap, pardon my French.
Just saw a review of Polestar 3 with bunch of the same issues, presumably also based on AA.
Even though I have no hands on experience with AA, but being a lifelong hardware/software engineer myself, what I experience in Gravity and loaner Air and hear about Rivian and now also Polestar, leads me to believe the issues are deep down in the core OS, not the surface level UI/UX programming.
To be clear, when I say "deep down in the core OS", it might be what we are commonly refer to as drivers in the PC world, where responsibility is fuzzy between the OS maker and the hardware maker, but it doesn't make customers feel any better when involved parties blame each other. This is where vertical integration like in Apple and Tesla are best, only one party to blame and they know it.