Software version 3.3.1

[NoseyReporter]

It’s probably deliberate. It’s illegal to drive a vehicle without a working speedometer. Screens black, you can’t see it, illegal. It actually makes the vehicle unroadworthy and you could be fined or face citation if you got caught driving a vehicle without a working speedometer. Makes sense why you can’t put it into drive when you’ve dead screens, Lucid would be playing with fire if they let you do that.

What kinda bug is this?! Good enough to enforce legal statute but bad enough so none of my screens load up?

 

[Ron_Burgundy]

What kinda bug is this?! Good enough to enforce legal statute but bad enough so none of my screens load up?

You can actually drive a Tesla and reset it on the highway. Just did it at 75mph with FSD on over the weekend. My wife flipped out as both screens were black for about a minute, but FSD worked fine and cat just kept crushing g.

 

[HC_79]

What kinda bug is this?! Good enough to enforce legal statute but bad enough so none of my screens load up?

Clearly it’s not a good one that Lucid needs to fix ASAP.

 

[Bunnylebowski]

Yeah I’m gonna veer away from my usual “Yay Lucid” enthusiasm, which I sincerely mean, and say “WTF Lucid” this time. I swear I’m not trying to pile on, but seriously, it’s time to get these releases more stable. You can do that Lucid, right?

 

[borski]

Agreed except for console spot. When I put fob there, I get “key not detected” consistently every couple of minutes. More so than if I leave it in my pocket. It’s odd.

But I think my center console is like the Bermuda Triangle.

You need to take it to service; you almost certainly have the center console wiring harness pinched.

 

[VeryPowerful]

Clearly it’s not a good one that Lucid needs to fix ASAP.

I really hope we won't need to wait for 1-2 months for a bigger update with this fix. They should just push a small update with just this fix (aka 3.3.2) to get it sooner to owners. But who knows what is the root cause and how complex the fix will be.

 

[HC_79]

I really hope we won't need to wait for 1-2 months for a bigger update with this fix. They should just push a small update with just this fix (aka 3.3.2) to get it sooner to owners. But who knows what is the root cause and how complex the fix will be.

Don’t think we’ll be waiting 2 months but I do agree, the OTA schedule needs to be sped up a bit.

 

[Ron_Burgundy]

You need to take it to service; you almost certainly have the center console wiring harness pinched.

It just came from service for 9 days. I would expect they checked that since it’s a bulletin.

But yes, it does seem like mine could have the issue. Except the fob works now with the update. IDK. I will call today.

 

[merveille07]

Disclaimer: I don't currently own any Lucid vehicle.

I have been told here that Lucid has Testers for new products or software, something I do not doubt. From the time , I have been on this forum; there is always a new bug that get introduced when Lucid release a new version of software. I know bugs are inherent to software development, but if you constantly keep introducing new bugs; shouldn't that put into question the QA team or process. The black screen issue seems to be affecting all gravities, so how wasn't that picked up during testing? I love Lucid and I am sure things will get better but I don't think midsize will be willing put up with all these issues.

 

[joec]

Mine is hit and miss, but there are times where I am like WTF app, and then I get into my car and my kids have moved the window down like 1/8 inch and then I forgive the app. Sometimes it's completely wrong though =P

Having had a peek at the API for how those window open warnings are implemented, I can say I understand why you get so many false positives. Hopefully they can work that out.

 

[Ron_Burgundy]

Disclaimer: I don't currently own any Lucid vehicle.

I have been told here that Lucid has Testers for new products or software, something I do not doubt. From the time , I have been on this forum; there is always a new bug that get introduced when Lucid release a new version of software. I know bugs are inherent to software development, but if you constantly keep introducing new bugs; shouldn't that put into question the QA team or process. The black screen issue seems to be affecting all gravities, so how wasn't that picked up during testing? I love Lucid and I am sure things will get better but I don't think midsize will be willing put up with all these issues.

The hope is mid size comes out with 3.x.x and so there are no major bugs as Gravity will have worked them out.

It’s tough. I can say I’d rather my fob work (which it does now) and have the black screens (which go away in about 30 seconds or so) then no fob working. Using the keycard for weeks was really, really annoying.

That said, I don’t need halo secure right now, so certainly they could’ve worked on something other than that for 3.3.1.

Ultimately, early adopters know (or should) this will happen. It’s annoying, but if you don’t like it, just wait until main bugs are gone. There are probably still less than 1,000 or so Gravity out there. Want it now? Deal with some annoying bugs. (Me). Don’t want bugs, wait for delivery (my wife).

Lucid is extremely flexible with when you take delivery - waiting is easy if you want to wait. Sorry, but no one is forcing a buyer to make a $100,000+ purchase now.

 

[NoseyReporter]

The hope is mid size comes out with 3.x.x and so there are no major bugs as Gravity will have worked them out.

It’s tough. I can say I’d rather my fob work (which it does now) and have the black screens (which go away in about 30 seconds or so) then no fob working. Using the keycard for weeks was really, really annoying.

That said, I don’t need halo secure right now, so certainly they could’ve worked on something other than that for 3.3.1.

Ultimately, early adopters know (or should) this will happen. It’s annoying, but if you don’t like it, just wait until main bugs are gone. There are probably still less than 1,000 or so Gravity out there. Want it now? Deal with some annoying bugs. (Me). Don’t want bugs, wait for delivery (my wife).

Lucid is extremely flexible with when you take delivery - waiting is easy if you want to wait. Sorry, but no one is forcing a buyer to make a $100,000+ purchase now.

Damn I hope by midsized they are 5.x

 

[EdL-ATX]

I have a disconnect between my app and the vehicle. The App shows Version 3.2.2 but the gravity itself shows 3.3.1. Any ideas for how to reconcile the two? I tried deleting the app from the iPhone and reinstalling. Its preventing me from using the "Live View" feature.

For the various folks who have seen this, I also had it from the time my GDE was first delivered. Were yours DELIVERED with 3.3.1 in the Gravity? What I found was the first time I did an OTA update (3.2.2->3.3.1 in my case), the app and vehicle were sync'd up. Nothing resolved the mismatch before doing a vehicle SW update AFTER my app/LucidID was sync'd to it. So basically you have to wait for the next OTA update.

 

[Allnatt]

For the various folks who have seen this, I also had it from the time my GDE was first delivered. Were yours DELIVERED with 3.3.1 in the Gravity? What I found was the first time I did an OTA update (3.2.2->3.3.1 in my case), the app and vehicle were sync'd up. Nothing resolved the mismatch before doing a vehicle SW update AFTER my app/LucidID was sync'd to it. So basically you have to wait for the next OTA update.

That makes sense. I also noticed in delivery prep they had to install 3.3.1 twice. I wonder if there was an issue even then.

 

[borski]

It just came from service for 9 days. I would expect they checked that since it’s a bulletin.

But yes, it does seem like mine could have the issue. Except the fob works now with the update. IDK. I will call today.

I would hope so, but because it’s new, I just double check everything

 

[borski]

Damn I hope by midsized they are 5.x

Haha touché. But it’ll be the same platform either way

 

[allenmhc]

I've only had the car for a few days. I received it already updated to 3.3.1, but this morning I got a message saying that an OTA updated the software—but as far as I can tell, it's still on 3.3.1 in both the app and in the vehicle. I didn't notice anything, other than that the electronics took a bit longer to boot up this morning, maybe 20–30 seconds. Is this…expected?

 

[prodolf]

Since the 3.3.1 update I have to use the Lucid app to charge at EA DC Chargers. It used to be plug-and-charge, this is not progress.

 

[Ron_Burgundy]

I've only had the car for a few days. I received it already updated to 3.3.1, but this morning I got a message saying that an OTA updated the software—but as far as I can tell, it's still on 3.3.1 in both the app and in the vehicle. I didn't notice anything, other than that the electronics took a bit longer to boot up this morning, maybe 20–30 seconds. Is this…expected?

Yes re: the notification of the update. That will come off and on from time to time even if you’re on 3.3.1. It was more frequent with 3.2.2. It’s not actually updating, it just tells you it’s updated…odd.

No, you shouldn’t have to wait for wake. That’s a bug in 3.3.1.

 

[9point81]

I've only had the car for a few days. I received it already updated to 3.3.1, but this morning I got a message saying that an OTA updated the software—but as far as I can tell, it's still on 3.3.1 in both the app and in the vehicle. I didn't notice anything, other than that the electronics took a bit longer to boot up this morning, maybe 20–30 seconds. Is this…expected?

The previous, and apparently this new version, would often give false alerts that the software was recently updated. Feel free to ignore it