New Bugs Since 3.5.1

What do you consider as working well? Mine are still crap, doesn't speed up when rain is pouring hard, so I have to distract myself on manual adjustment while driving with already limited view due to water all over the windshield.
First it has auto activated immediately everytime so far when previously never did for me.

And it has adjusted speed beautifully so far everytime, like today I was on the highway and it sped up wipers quickly when rain got heavy and slowed down when rain was light.
 
What do you consider as working well? Mine are still crap, doesn't speed up when rain is pouring hard, so I have to distract myself on manual adjustment while driving with already limited view due to water all over the windshield.
Mine work well on the "auto" setting.
 
The wide array of software issues we are seeing in both our Gravities suggest more than just tying up a few remaining loose ends is needed. It's been over nine months since we took delivery of our first Gravity and four months since the second one. We are still having key fob issues; the cars not locking and powering down automatically; a rear hatch refusing to latch or to open; VIBE lighting errors; Pilot Screen, toggle switches, rotary volume knob, and steering wheel buttons failing to respond.

The notion that they're now focusing on an upcoming model while moving Gravity issues to a back burner really, really pisses me off if true. I have paid Lucid $590,000 for their products. But I will never buy another one if I find any reliable indication they are now moving on in their priorities.
I can't be confident, because I just don't have enough information, but it seems highly likely that the weirdly random (non-deterministic, in engineering parlance) bugs that cross such a large array of modules in the Gravity software is a sign of an common underlying software architecture flaw. Could be memory management, asynchronous event handling, network packet handling, process priority issues, or many other possibilities. But whatever it is, there's a good chance that it needs to be solved for Cosmos as well, and so I'd be surprised if Lucid stops working on it for Gravity. The danger of Gravity being abandoned is when the common platform is stable, but Gravity has unique software modules for the hardware in the car. Not that I necessarily think Lucid will abandon the Gravity. But if they do, that probably won't occur until after some big improvements have been made.
 
Mine work well on the "auto" setting.
Mine do not. They turn on when on “auto” less than 50% of the time. Usually, I need to start them and then they’ll stay on auto, but they also don’t seem to adjust to rain intensity. Not a huge deal to me so I added it to my list. I also think it’s software-related and they’ll keep improving it.
 
So…this weekend my driver side passenger door handle stopped presenting consistently. I’ve never had an issue with it in 9+ months. This is the type of thing that kills me. It’s totally like whack-a-mole. Bugs come and go with no rhyme or reason. I’ve never had an issue with handles, but 3.5.1 was supposed to address issues people did have….

An OTA comes, smooth sailing for 2-4 weeks, then weird stuff happens. And I am afraid to call service because the car DOES drive so well, no showstoppers now, and if I take it to service they’ll keep it for a while and I don’t think there’s really a “fix”.

Love, love the car and driving, etc. So frustrated with random stuff. Also concerned Lucid does just stop chasing its tail in the Gravity once mid size is out.

We know they’re listening and laser focused on Gravity now, so I do hope long term, stable fixes will come.

Taking another family with us on a 1,000 mile road trip this week and I just have the feeling crazy stuff is going to happen. I almost want to take wife’s R1S, and I would, except she’d NEVER let me live it down if I did that… 😢
 
So…this weekend my driver side passenger door handle stopped presenting consistently. I’ve never had an issue with it in 9+ months. This is the type of thing that kills me. It’s totally like whack-a-mole. Bugs come and go with no rhyme or reason. I’ve never had an issue with handles, but 3.5.1 was supposed to address issues people did have….

An OTA comes, smooth sailing for 2-4 weeks, then weird stuff happens. And I am afraid to call service because the car DOES drive so well, no showstoppers now, and if I take it to service they’ll keep it for a while and I don’t think there’s really a “fix”.

Love, love the car and driving, etc. So frustrated with random stuff. Also concerned Lucid does just stop chasing its tail in the Gravity once mid size is out.

We know they’re listening and laser focused on Gravity now, so I do hope long term, stable fixes will come.

Taking another family with us on a 1,000 mile road trip this week and I just have the feeling crazy stuff is going to happen. I almost want to take wife’s R1S, and I would, except she’d NEVER let me live it down if I did that… 😢
Totally hear what you’re saying. I’m not booking mine in for the recall until I have a list of other things that need to be fixed. They keep the cars for way too long for such trivial things.
 
On the weird bug side, my driver window has once again started to not go up when I pull the button. It goes down a bit, then all the way down on next pull “up” then up once it’s gone all the way into the door.

Folks here said it was a simple seal fix issue, but it’s been in service twice and they weren’t able to address it. It stopped happening during winter and now, with warmer temps, has started “up” again…so
Sounds like a seal issue could be the problem, but doesn’t seem like service center has the memo yet.

Different issue from my rear driver side saga which is quiet for now (not really, but close enough for now)…
 
So…this weekend my driver side passenger door handle stopped presenting consistently.
On the weird bug side, my driver window has once again started to not go up when I pull the button. It goes down a bit, then all the way down on next pull “up” then up once it’s gone all the way into the door.

We'e had both these issues in our newer Gravity in the past 2-3 weeks but not in our older Gravity.

With the doors, sometimes it's only the driver door that won't present, and sometimes that's the only door that will present (either automatically or when pressing the second button on the key fob that is supposed to unlock all the doors).

For a while, almost all the bugs were happening in our older Gravity. Since 3.5.1 it's been the newer Gravity that is most beset by bugs -- except for the VIBE dashboard malfunction, which is still occurring mostly (but not exclusively) in the older Gravity.

When choosing which car to take I find myself trying to decide which bug(s) would most annoy me that day and which car is less likely to experience them. For instance, if I'm going to the recycling center, I always take the older Gravity which has not yet experienced the rear hatch issues. If we're going out for dinner we choose the newer Gravity, as its VIBE lighting is less likely to malfunction. If I've got stacked appointments on a tight schedule, I used to favor the newer Gravity as it had fewer unlocking issues and screen freezes. That particular situation has now reversed, and I take the older Gravity.

I never thought that, almost ten months after getting a Gravity, we'd still be dealing with this kind of shit. (It was ten months after we got our Air DE that UX 2.0 came along and began to resolve software issues. I'm praying that May brings similar news for the Gravity. As far as I'm concerned, UX 3.0 is a total bust, and we need a UX 4.0.)
 
Mine do not. They turn on when on “auto” less than 50% of the time. Usually, I need to start them and then they’ll stay on auto, but they also don’t seem to adjust to rain intensity. Not a huge deal to me so I added it to my list. I also think it’s software-related and they’ll keep improving it.
I drove 800+ miles yesterday in conditions ranging from no rain to heavy downpour. Wipers worked well with 3.5.1. I kept it on Auto 1 most of the time. Increased to Auto 3 during a heavy downpour where everyone was slowing down to 35 mph on a 70 mph freeway.

I don’t remember if I actually needed to adjust to Auto 3 - the downpour was so bad I wanted it to be at max. I did verify that Auto 3 during the downpour was the same as Manual Max speed, so I kept it on Auto 3.

Wipers adjusted automatically to speed and rain conditions very well. I did have to initiate a wipe once or twice by pressing the left stalk button as we transitioned from no rain to very light rain, but this is very easy and not a big deal. Auto took over after that initial wipe.

I do agree having real buttons for the wiper is preferable, where we can adjust by feel and keep our eyes on the road.
 
Last edited:
With the doors, sometimes it's only the driver door that won't present, and sometimes that's the only door that will present (either automatically or when pressing the second button on the key fob that is supposed to unlock all the doors).
For me, pressing it once unlocks the driver's door, pressing it twice unlocks all doors.
 
For me, pressing it once unlocks the driver's door, pressing it twice unlocks all doors.
I believe that’s a setting. You can choose to only have it unlock/present driver door first. That’s the default. Too lazy to go take a picture of settings, but fairly certain.
 
For me, pressing it once unlocks the driver's door, pressing it twice unlocks all doors.
same here
I believe that’s a setting. You can choose to only have it unlock/present driver door first. That’s the default. Too lazy to go take a picture of settings, but fairly certain.

You're all correct, and that's the way I use the Gravity fobs. I had a brain fart and defaulted back to the way our recent Honda fob worked in my post.

It's a confusing landscape with multiple cars. Months before we got our first Gravity I posted about what a relief it would be to become an all-Lucid household. For years I've been bedeviled by trying to keep the operating protocols of different brands separate, especially the tendency of Japanese brands to reverse the location of so many controls compared to U.S. and German brands. I was really looking forward to the same protocols working across our Lucid line-up.

But then the first Gravity arrived. Different key fob from our Air. Different screen menus. Different functions. As I now drive a Gravity much more often than an Air, I sometimes get in the Air and have to stop to think a second before remembering how to do what I want. For instance, changing drive modes is a very different exercise between the two cars if you have satellite maps displayed on the Pilot Screens.

For all my griping about Gravity UI software, there's one point I want to stress. The design and layout of the Gravity user interfaces are the best I've ever seen in a car . . . and we've owned two Teslas. Every function is easy to find, the range of display choices and the means of executing them are exceptional, and their locations in your field of vision are well thought out.

After almost 10 months with a Gravity, there are really only two things I would like to see improved on the design front: the ability to select which ride height you want automatically paired with which drive mode, and the ability to select text size on the screens. On this latter point, there is plenty of screen real estate to allow larger text for most readouts, and I suspect many Gravity buyers or at the age when near vision begins to weaken and reading small text becomes more difficult. I don't need glasses to see the road, but there are many things on the displays I cannot read easily without putting on my reading glasses.

But . . . please, Lucid, fix the software reliability first.
 
But then the first Gravity arrived. Different key fob from our Air.
True! And the Gravity's buttons are tiny and have all the same shape, so it pretty much requires you to memorize the order to know what you are pressing. Rivian and most of the Chinese brands have taken a different approach to fob design and I love it, much easier to use.
 

Attachments

  • the-gen-2-key-fob-is-totally-worth-it-v0-7rktaqw69oce1.webp
    the-gen-2-key-fob-is-totally-worth-it-v0-7rktaqw69oce1.webp
    35.9 KB · Views: 98
For all my griping about Gravity UI software, there's one point I want to stress. The design and layout of the Gravity user interfaces are the best I've ever seen in a car .
Agree, it's well designed. The only issue in my opinion and experience is that the pilot panel sits very low, so it requires you to take your eyes off the road to change anything. Some things (ie audio) can be used from the cockpit, but many others (ie HVAC) can't. Not very safe when you are going 70+ mph in heavy traffic.
 
True! And the Gravity's buttons are tiny and have all the same shape, so it pretty much requires you to memorize the order to know what you are pressing. Rivian and most of the Chinese brands have taken a different approach to fob design and I love it, much easier to use.
We never used the fob in our first Rivian (PaaK was great) and the newer Rivians don’t come with a fob - just like Tesla. I’d LOVE to see Lucid get to that type of PaaK stability. I don’t need or want a fob. Our R1S PaaK and WaaK (love that acronym) are perfect and make for a great experience. I wish Lucid would just ditch the fob and focus on PaaK, but my guess is that’s a tough implementation for some reason. Shouldn’t be, but neither should a fob.

Agree with @hmp10 on UI for 3.0 - love it and also desperately need stability.

Bottom line - I really don’t want ANY new features unless and until everything that exists today works darn near perfectly.

P.S. - I DO love CarPlay. It’s helpful. However, I have CarPlay at the expense of a bug that won’t allow front camera to automatically appear on clearview while parking…Lucid giveth and Lucid taketh away…

P.P.S. - anyone else still getting random screen freezes on pilot panel? They go away quickly by switching to another screen, but come on. Also, the icons at bottom of pilot panel often take 2-3 touches to change screens for me…
 
We never used the fob in our first Rivian (PaaK was great) and the newer Rivians don’t come with a fob - just like Tesla. I’d LOVE to see Lucid get to that type of PaaK stability. I don’t need or want a fob. Our R1S PaaK and WaaK (love that acronym) are perfect and make for a great experience. I wish Lucid would just ditch the fob and focus on PaaK, but my guess is that’s a tough implementation for some reason. Shouldn’t be, but neither should a fob.

Agree with @hmp10 on UI for 3.0 - love it and also desperately need stability.

Bottom line - I really don’t want ANY new features unless and until everything that exists today works darn near perfectly.

P.S. - I DO love CarPlay. It’s helpful. However, I have CarPlay at the expense of a bug that won’t allow front camera to automatically appear on clearview while parking…Lucid giveth and Lucid taketh away…
Fully agree, PaaK eliminates the discussion of badly designed fobs. But if you need to use one, I prefer Rivian's or Tesla's.
 
I'm experiencing a problem when trying to answer a second incoming call while already on another call. Although the display clearly shows the second call, the answer button (the green phone icon) appears to overlap with the reject button (the red phone icon). This makes it difficult to select the right option and answer the call properly.
 

Attachments

  • Phone call in Lucid2.webp
    Phone call in Lucid2.webp
    568 KB · Views: 116
Back
Top