New Bugs Since 3.5.1

Emphasis added by me.

No one said minor or major. Just that there have been glitches and bugs.

I think, as days between updates add up, users/owners get more and more frustrated. Then, 3.X.X will be released, some of the problems will be fixed and we'll feel vindicated that our problems were real. Then, real life experiences will occur and we'll find either new problems or issues we hadn't noticed or weren't important enough before.

There is always improvement with every update - we're just getting anxious.

Dream Ahead!

I think you're missing the context here. This was in response to the idea that just because OLD reviews of the Gravity noted all the bugs that it means that there aren't owners like myself that aren't seeing all of these recurring issues since 3.5.1 and any errors we've seen have been incredibly minor. In no way was I implying that there aren't owners with issues or that old reviews correctly noted all of the existing bugs but in the thousands of Gravity that have been sold so far I'd be willing to bet that the majority of people have little to no issues in this version compared to prior versions.
 
I think you're missing the context here. This was in response to the idea that just because OLD reviews of the Gravity noted all the bugs that it means that there aren't owners like myself that aren't seeing all of these recurring issues since 3.5.1 and any errors we've seen have been incredibly minor. In no way was I implying that there aren't owners with issues or that old reviews correctly noted all of the existing bugs but in the thousands of Gravity that have been sold so far I'd be willing to bet that the majority of people have little to no issues in this version compared to prior versions.
I get it - and agree that newer versions are more bug-free. I just think that an update should fix specific bugs - DDPro not activating, even once, means DDPro activation was not fixed. We've gotten used to "just reboot" to fix things that have been occurring for a couple revisions. I'm not talking about features - we expect a learning curve. But, backup camera not working, panels going blank - fix them. And, if you fix the backup camera but don't have the panel issue fixed yet, issue a minor update that fixes the camera - show us Lucid hears us and is working on many things all at once.

Maybe I'm just getting anxious for the new release and am cranky - haven't had my nap yet today....
 
That's a bit excessive IMO, plenty of us on 3.5.1 with no problems at all I'd suspect. Not discounting the experience of people with problems but I'd bet there are more people without these issues than with and they're just not posting about it.
I'm happy for you. I'm dealing with bad fobs since delivery. When it gets bad I had to press unlock 20+ times for the car to unlock for me (and the issue happens to both of my fobs at the same time). I could hold button for opening hood for a minute and it would do anything. Locking is even bigger problem because I can't mash the lock button as it can trigger car alarm. Car reboots, fob reboots, new batteries nothing works. Then it randomly goes away for a month and works perfectly fine. Then comes back for 2 months... After few recent updates I at least don't have issue getting the car in Drive.
I noticed a few folks the never complained about fobs started having issues after updating to 3.5.1 so from my point of view I had a good reason not to update.

All updates.
I've never regretted installing an update for Gravity, or over three years with an Air.
If you spend too much time reading this forum, you'll want to live under a sofa.
In my case people complained about fobs that are already problematic in my case. I didn't want to risk getting the issue worse than it already is. It was the first time I decided not to update.
 
Emphasis added by me.

No one said minor or major. Just that there have been glitches and bugs.

I think, as days between updates add up, users/owners get more and more frustrated. Then, 3.X.X will be released, some of the problems will be fixed and we'll feel vindicated that our problems were real. Then, real life experiences will occur and we'll find either new problems or issues we hadn't noticed or weren't important enough before.

There is always improvement with every update - we're just getting anxious.

Dream Ahead!
This guy talks like he ran a major auto supplier for thirty years or something
 
How many of those reviewers did their report AFTER 3.5.1 was released?

Some did. The UpCurrent EVs channel, for instance, specifically reported on problems they were having post 3.5.1. (I sometimes have dinner with them, and they tell me their Gravity has become significantly more problem-prone since that update.)

In my own case, prior to the 3.5.1 update we were seeing most of the software problems in our older Gravity. In fact, I posted during that time that our newer Gravity was having significantly fewer problems than the older Gravity. But after 3.5.1 the situation actually reversed, with a sharp spike in software problems in our newer Gravity. These included some things we had not seen before in either car, as well as more familiar bugs from one car showing up in the other car:

- The VIBE dashboard lighting malfunction our older Gravity had been having suddenly showed up repeatedly in the newer Gravity.
- The newer Gravity developed unlocking and locking issues it had not been having beforehand. These included some symptoms we had never seen in our older Gravity, including the passenger doors unlocking but the driver door wouldn't, and the car failing to lock and power down even long after we had parked it at restaurants or in our garage.
- The Pilot Screen buttons, the A/C toggle switches, the rotary volume knob, and the steering wheel touchpads freezing in the newer car, making it impossible to adjust A/C, audio volume, drive modes, suspension height. and audio selections through those means. This never happened prior to 3.5.1.
- The flickering of the Glass Cockpit driver binnacle and the navigation maps on both screens, again problems we had not seen prior to 3.5.1.
- The frequency of rear hatch malfunctions increased in the newer Gravity, incidents which the older car never experienced.
- The mobile app reporting false conditions, such as the car being unlocked and even being left in reverse gear -- something that should not even be possible, as the car automatically goes into Park as soon as you open the driver door. (In each of these instances I went out to check the car and found the app warning was in error.)
- The parking cameras not working.

And I am not the only one on this forum to report an uptick in software malfunctions since the 3.5.1 update.
 
Some did. The UpCurrent EVs channel, for instance, specifically reported on problems they were having post 3.5.1. (I sometimes have dinner with them, and they tell me their Gravity has become significantly more problem-prone since that update.)

In my own case, prior to the 3.5.1 update we were seeing most of the software problems in our older Gravity. In fact, I posted during that time that our newer Gravity was having significantly fewer problems than the older Gravity. But after 3.5.1 the situation actually reversed, with a sharp spike in software problems in our newer Gravity. These included some things we had not seen before in either car, as well as more familiar bugs from one car showing up in the other car:

- The VIBE dashboard lighting malfunction our older Gravity had been having suddenly showed up repeatedly in the newer Gravity.
- The newer Gravity developed unlocking and locking issues it had not been having beforehand. These included some symptoms we had never seen in our older Gravity, including the passenger doors unlocking but the driver door wouldn't, and the car failing to lock and power down even long after we had parked it at restaurants or in our garage.
- The Pilot Screen buttons, the A/C toggle switches, the rotary volume knob, and the steering wheel touchpads freezing in the newer car, making it impossible to adjust A/C, audio volume, drive modes, suspension height. and audio selections through those means. This never happened prior to 3.5.1.
- The flickering of the Glass Cockpit driver binnacle and the navigation maps on both screens, again problems we had not seen prior to 3.5.1.
- The frequency of rear hatch malfunctions increased in the newer Gravity, incidents which the older car never experienced.
- The mobile app reporting false conditions, such as the car being unlocked and even being left in reverse gear -- something that should not even be possible, as the car automatically goes into Park as soon as you open the driver door. (In each of these instances I went out to check the car and found the app warning was in error.)
- The parking cameras not working.

And I am not the only one on this forum to report an uptick in software malfunctions since the 3.5.1 update.
I think you have found that V2V has been implemented! I’m a little worried the cars are talking to each other, at night while you sleep, coming up with new ideas to drive you crazy…. 😳
 
I must admit I am using it more and more. I keep the fob in the house and if I need to move the car, I use remote start. As I become more comfortable, I'll pull the keycard from my money clip, not take the fob and use the remote start as a rudimentary PAAK substitute when I go somewhere I know will have cell coverage.

A little more confidence needed, for now, but I see it in my future.
As I was driving home a few nights ago, I started noticing my neighborhood was pitch dark. I parked in my driveway, got out, and pushed the lock button in the app (as I no longer carry the fob). Nothing. A few more times. Nothing. Then I realized the local cell towers must have been down also, so the car had no connectivity. I reached for my key card and locked the doors. Good thing I carry it for backup. No, I have never been able to lock by pushing the handles in.
 
I think you have found that V2V has been implemented! I’m a little worried the cars are talking to each other, at night while you sleep, coming up with new ideas to drive you crazy…. 😳

Well, I know the cars are talking to each other. It's just that no one can figure out why.

We're still having the issue that, when any two of our Lucids are on the road at the same time, neither will play music without constantly pausing. This happens when one car is on Spotify, the other on Tidal, or when one car is playing a USB stick and the other is streaming. The only time both cars will play music normally is when both are playing their USB sticks.
 
Well, I know the cars are talking to each other. It's just that no one can figure out why.

We're still having the issue that, when any two of our Lucids are on the road at the same time, neither will play music without constantly pausing. This happens when one car is on Spotify, the other on Tidal, or when one car is playing a USB stick and the other is streaming. The only time both cars will play music normally is when both are playing their USB sticks.
See, they're messing with you each time! Wait til both Gravity reformat both the USB sticks "by mistake" at the same time, replaced by Polish Dance music on your USB drive and Frank Sinatra on your partner's USB drive!
 
@RandomDesign I also didn't have any bugs after 3.5.1 for a couple of weeks, at some point I thought "wow, Lucid pulled a miracle", I couldn't believe it.
And then one after another bugs started to creep back in, more and more over time, some new ones I've never seen before, but mostly same old ones.
So, to rephrase @hmp10's question, how is it possible for a car software to be perfect and then fall apart over a few week's span of time?
Despite many claims of its reboots and resets while sleeping, etc etc (claims to which I no longer believe based on my own observations).
As a lifetime technologist and a software engineer I'm still scratching my head on this one....
 
@RandomDesign I also didn't have any bugs after 3.5.1 for a couple of weeks, at some point I thought "wow, Lucid pulled a miracle", I couldn't believe it.
And then one after another bugs started to creep back in, more and more over time, some new ones I've never seen before, but mostly same old ones.
So, to rephrase @hmp10's question, how is it possible for a car software to be perfect and then fall apart over a few week's span of time?
Despite many claims of its reboots and resets while sleeping, etc etc (claims to which I no longer believe based on my own observations).
As a lifetime technologist and a software engineer I'm still scratching my head on this one....
It could be a memory leak or some other long-running resource/state issue that doesn’t show itself at first but as time goes on it starts to show its ugly head again.

That being said, I haven’t rebooted the software at all on 3.5.1 and the only continued thing I’m seeing is the face cam not working 100% of the time. I think I got one rear steering error but that’s been it.

Very strange to see such drastic variations across the fleet, unless they’re doing rapid hardware changes in production thinking new components will solve the problem but has created a bigger one. Pure speculation on that part though.
 
@RandomDesign I also didn't have any bugs after 3.5.1 for a couple of weeks, at some point I thought "wow, Lucid pulled a miracle", I couldn't believe it.
And then one after another bugs started to creep back in, more and more over time, some new ones I've never seen before, but mostly same old ones.

This is exactly the same trajectory we experienced with our newer Gravity. The older Gravity got the 3.5.1 update a couple of weeks before the newer Gravity, and its software errors did, in fact, diminish somewhat after the update. While some remained, their frequency was diminished and none of them were new errors.

But the newer Gravity was a different story. It went from being less glitch-prone than the older Gravity to no errors at all for a week or more . . . and then the tsunami hit: more frequent occurrences of old glitches and a host of new ones.

How can two cars with identical powertrains and option suites and running the same software manifest such different responses to an update? And what's with an update that introduces more new bugs than it corrects?
 
It could be a memory leak or some other long-running resource/state issue that doesn’t show itself at first but as time goes on it starts to show its ugly head again.
That's what I used to think as well, but that means it should be recovering back to normal at every reset cycle, whenever that is, yet I see persistent bugs for days or weeks, which weren't there for days or weeks before. I see bugs which persist thru "sleep based reset" and/or infotainment manual reset, yet same bugs definitely weren't there for some time after the last update.
This logic implies that update initiates even deeper system reset than sleep or manual, but something we cannot initiate on our own, right?
 
This logic implies that update initiates even deeper system reset than sleep or manual, but something we cannot initiate on our own, right?
That seems to imply at the level of the QNX OS. How nice, that can't be problematic :)
 
Back
Top