What's new
By:

Gravity Bugs / Issues

Ron_Burgundy said:
I will say this. This thread used to be lit up like a Christmas tree daily. Literally. There minute by minute posts about the fob, random errors, etc. It’s amazing to see it’s really nowhere near as active as it was.

Yes, work still to be done, but wow, it’s come a long way.
Click to expand...
There's also some "just live with it" effect. We find workarounds that we get used to. We just write some things off and don't bother even trying to use them anymore. Some people have just turned HUD off completely, for instance. Some almost never lower the windows (like me). Some don't try to use AUTO PARK. Some use AA or CP instead of the car's native nav, or native audio streaming.

And honestly, that's true in any car (although maybe not to the same degree). There's always a few things in every car that either don't work at all, or correctly, or as we hoped for. I'd say my Gravity still has more of those than normal, but the gap is shrinking as they gradually fix a thing here or there.
 
We had much improved software performance after the 3.6.0 update in our two Gravities, but problems are now creeping back in. We sometimes lose audio, and the auto-dimming headlight feature has become erratic.

A problem we had in the nav system of our older Gravity a year ago has now shown up in our newer Gravity. The screens often show our location as being the Lucid HQ in Newark, CA instead of our actual location in southwest Florida. Sometimes we can correct the location by hitting "Re-Center", sometimes not. This started intermittently but has now begun to occur with almost every startup.

Here's what showed up on our upper and lower screens yesterday when we were, in fact, driving along a rural lakeshore. It took a reboot to correct the image, and that is not something I'm interested in doing almost every time we start up the car.

IMG_2997.webp
IMG_2998.webp
 
hmp10 said:
We had much improved software performance after the 3.6.0 update in our two Gravities, but problems are now creeping back in. We sometimes lose audio, and the auto-dimming headlight feature has become erratic.

A problem we had in the nav system of our older Gravity a year ago has now shown up in our newer Gravity. The screens often show our location as being the Lucid HQ in Newark, CA instead of our actual location in southwest Florida. Sometimes we can correct the location by hitting "Re-Center", sometimes not. This started intermittently but has now begun to occur with almost every startup.

Here's what showed up on our upper and lower screens yesterday when we were, in fact, driving along a rural lakeshore. It took a reboot to correct the image, and that is not something I'm interested in doing almost every time we start up the car.

View attachment 40119View attachment 40120
Click to expand...
Interesting. We also had the GPS for our Gravity say we were at Lucid HQ randomly last week. And the app said the car was at our home, but it was actually in San Jose!

Reset didn’t work to fix this but going to sleep and waking up later seemed to clear it. So far it has not recurred.

🤔
 
hmp10 said:
We had much improved software performance after the 3.6.0 update in our two Gravities, but problems are now creeping back in. We sometimes lose audio, and the auto-dimming headlight feature has become erratic.

A problem we had in the nav system of our older Gravity a year ago has now shown up in our newer Gravity. The screens often show our location as being the Lucid HQ in Newark, CA instead of our actual location in southwest Florida. Sometimes we can correct the location by hitting "Re-Center", sometimes not. This started intermittently but has now begun to occur with almost every startup.

Here's what showed up on our upper and lower screens yesterday when we were, in fact, driving along a rural lakeshore. It took a reboot to correct the image, and that is not something I'm interested in doing almost every time we start up the car.

View attachment 40119View attachment 40120
Click to expand...
Bummed to hear this. Also bummed to hear you’re experiencing the destabilization challenge post OTA. I haven’t had it yet with the last OTA, but what you describe has been pretty common for me over the past year of ownership. Amazing right after OTA and then gremlins creep back. For me, at least, it’s less and less each time.

You’ve GOT to be living over some absurd magnetic field or, sadly, cursed. Would be cool if Lucid swapped out one of your GDEs with one of the ones apparently still sitting in AZ…
 
Hey Google: "An OTA update cannot permanently fix a physical binding issue caused by acoustic glass running in a non-acoustic channel. While software can alter motor parameters, a physical component mismatch creates severe mechanical and regulatory limitations that software alone cannot bridge."

I got the response above after configuring with, or without, acoustic rear passenger glass (Comf & Conv) and wondering whether retrofits were possible. The answer why one should not just swap the glass might inform a possible source of window problems. **this is not to assume Lucid messed up**. When I read about this particular issue, I'm not keeping track or seeing which windows people report being unreliable, front and/or back?? If back, the Comfort & Convenience package's thicker rear acoustic glass may be a cause, if Lucid didn't use a wider channel. It could trigger binding/an obstruction response (you want up/it goes down)? That, or maybe Lucid used thinner channels all around?

I'm only speculating, and Gemini's response is generic. This is one place where having a parts catalog would tell us if the rear window framing had separate part numbers for the Comfort & Convenience package, implying they compensated for glass width. Perhaps new part numbers (2027 went all-acoustic) would suggest iteration, like Tesla does all the time. Either way, it seems the regulators may be seeing higher friction and the solution could be more involved.

Ron_Burgundy said:
Not so sure about that. I just got my car back from service and one of the regulators was just replaced (again) and it still has the same issue. I’m told it’s actually some sort of software issue (maybe). My other window still has an issue after two new regulators. Thankfully, they both work (eventually) but they go up vs down and vice versa…so…regulators do not seem to have improved (YMMV).
Click to expand...
 
Ron_Burgundy said:
I will say this. This thread used to be lit up like a Christmas tree daily. Literally. There minute by minute posts about the fob, random errors, etc. It’s amazing to see it’s really nowhere near as active as it was.

Yes, work still to be done, but wow, it’s come a long way.
Click to expand...
Yeah, after being scared off buying with all the reports of gremlin infested vehicles last December, I'm now feeling comfortable enough with the tone of the Gravity conversation to move forward and buy one. I have a busy summer of traveling, so I plan to see what lease terms look like in September.
 
TahoeMichael said:
Yeah, after being scared off buying with all the reports of gremlin infested vehicles last December, I'm now feeling comfortable enough with the tone of the Gravity conversation to move forward and buy one. I have a busy summer of traveling, so I plan to see what lease terms look like in September.
Click to expand...
I think you're right...though I've had plenty of issues with mine, I feel like we're coming out of that first adopter era of ownership now nearly a year in.

Not only have they fixed a lot of the bugs, they also now have a decent history of issues/problems that they can solve more easily for other owners. I had 2 big issues that required 7-10 day SC visits. Both times, 80-90% of the time was diagnosis...figuring out what was causing the error. Now that these are in the SC database (you're welcome. lol), next time these come up for an owner, the times to fix should be much less.

Even despite the issues I've had, I have zero regrets. This car is amazing.
 
gamix said:
Hey Google: "An OTA update cannot permanently fix a physical binding issue caused by acoustic glass running in a non-acoustic channel. While software can alter motor parameters, a physical component mismatch creates severe mechanical and regulatory limitations that software alone cannot bridge."

I got the response above after configuring with, or without, acoustic rear passenger glass (Comf & Conv) and wondering whether retrofits were possible. The answer why one should not just swap the glass might inform a possible source of window problems. **this is not to assume Lucid messed up**. When I read about this particular issue, I'm not keeping track or seeing which windows people report being unreliable, front and/or back?? If back, the Comfort & Convenience package's thicker rear acoustic glass may be a cause, if Lucid didn't use a wider channel. It could trigger binding/an obstruction response (you want up/it goes down)? That, or maybe Lucid used thinner channels all around?

I'm only speculating, and Gemini's response is generic. This is one place where having a parts catalog would tell us if the rear window framing had separate part numbers for the Comfort & Convenience package, implying they compensated for glass width. Perhaps new part numbers (2027 went all-acoustic) would suggest iteration, like Tesla does all the time. Either way, it seems the regulators may be seeing higher friction and the solution could be more involved.
Click to expand...
Interesting. The front and back doors have the special glass.

It could be something where the OTA greatly rescues the false positives that cause the window to go down once it starts going up and thinks it’s hitting something.

IDK, as with most bugs here, they’re not experienced by everyone. Also, one of the windows on my car has never had an issue…until I just jinxed myself by saying that.
 
@hmp10 - what do you mean the auto dimming is erratic?

The latest update rolled out the dynamic dimming feature that supposedly keeps the high beams on but adapts them to not blind other drivers. I am having a tough time trusting it and getting used to the indicator lamp showing they are just on, so I'm a bit confused by it myself, but I think supposedly it's doing what it's supposed to.

Or are you seeing something else?

FWIW to some of the other comments - my key fob is now acting nearly flawlessly, after months of extremely erratic behavior. I haven't even installed the latest fob update - I'm afraid to. But I think I've only had one unlocking delay in the last month.
 
WeighingGravity said:
FWIW to some of the other comments - my key fob is now acting nearly flawlessly, after months of extremely erratic behavior. I haven't even installed the latest fob update - I'm afraid to. But I think I've only had one unlocking delay in the last month.
Click to expand...
I'm in the same boat. My fob actually started off great for the first few months of ownership last summer but then was extremely intermittent (almost always requiring me to to stand there for 10s of seconds to unlock and also often not autolocking when leaving) for the next ~8 months. Since 3.6 though I have not had a single instance of it failing to auto unlock/lock upon arrival/departure as the design intended.
I was also reluctant to update the fob FW but eventually did a week or 2 ago and have not noticed anything that impacted behavior negatively.
 
WeighingGravity said:
[…]The latest update rolled out the dynamic dimming feature that supposedly keeps the high beams on but adapts them to not blind other drivers. I am having a tough time trusting it and getting used to the indicator lamp showing they are just on, so I'm a bit confused by it myself, but I think supposedly it's doing what it's supposed to. […]
Click to expand...
Here is my test criteria:
  • Are the headlights illuminating the road well?
  • Do I see the headlights adjusting for oncoming traffic? Is the left side decreasing while the right side remains bright?
  • Am I being flashed by oncoming traffic more than with high beams off?
I was paying attention to this very closely when 3.6.0 first came out and did a set of experiments. The matrix headlights seem to be working well, and I stopped thinking about it.
 
J-Dub said:
I'm in the same boat. My fob actually started off great for the first few months of ownership last summer but then was extremely intermittent (almost always requiring me to to stand there for 10s of seconds to unlock and also often not autolocking when leaving) for the next ~8 months. Since 3.6 though I have not had a single instance of it failing to auto unlock/lock upon arrival/departure as the design intended.
I was also reluctant to update the fob FW but eventually did a week or 2 ago and have not noticed anything that impacted behavior negatively.
Click to expand...
Same for me. After months of continued shaking and battery replacements, and sometimes slow/delayed opening, my fob is 99.999% perfect now…that is, until I wrote this and jinxed myself.

Seriously, yes, it was tough for a while, but Lucid seems to have overcome the fob issues completely.

Again, there used to be literally 10 posts a day about the issues and now there’s very few per week - if at all.

Also, it’s worth noting the NHTSA release notes for 6.3.2 seem to refer to something about even better fob performance. So Lucid is still refining. We shall see.
 
J-Dub said:
For me, and I'm assuming the original comment, the reluctance to upgrade the fob was only because locking and unlocking was finally working as intended and was scared to do something to break it again. 😀
Click to expand...
My fob hasn't gotten worse, it just hasn't gotten much better. Still standing there at the door waiting for 5-20 seconds about half the time. Doesn't matter if I shake the fob, change the battery, wipe the battery, update the fob software, press the door handle, press the fob unlock button, etc. Nothing matters until the car "wakes up" (for lack of a better way to describe it) and recognizes the fob first. Once it finally does that, it all works.
 
I'm awfully reticent to generally declare mission accomplished on the fob Gravity-wide considering how many times things would improve for a little while then get worse again. And as we can see, at least some people are still having issues. @DeaneG, my fear of installing the fob update doesn't come from any specific feedback, it just comes from months of watching this go back and forth, and also realizing from this forum that everyone seems to experience different forms of different issues, so I don't really trust my specific hardware/software combination to just work flawlessly from here on out. I have my Jenga tower jusssst right and I am not keen on pulling another piece out just yet, even if I'm told "hey, that one is totally safe."
 
WeighingGravity said:
@hmp10 - what do you mean the auto dimming is erratic?

The latest update rolled out the dynamic dimming feature that supposedly keeps the high beams on but adapts them to not blind other drivers. I am having a tough time trusting it and getting used to the indicator lamp showing they are just on, so I'm a bit confused by it myself, but I think supposedly it's doing what it's supposed to.

Or are you seeing something else?
Click to expand...

That may be what we're seeing, too. The lights no longer automatically dim with oncoming traffic, but we're also not getting high beam flashes from other cars indicating they are being blinded or annoyed by our headlights.
 
The audio occasionally dropping out for several seconds is a new bug for us, since the release of 3.6.0. I'd heard others complaining, but we never had it. Very annoying.
 
You must log in or register to reply here.
Back
Top