What's new
By:

Software version 3.3.2

Thierry said:
This is weird. I tried to install 3.3.2 10+ days ago and it went South; and I heard other people having the same experience.
My first try just failed, but the second attempt "killed" both the key fob and the key cards which resulted in the car being towed.
If the update was the issue, I'd expect a 3..3.3 release because how trying to install 3.3.2 for a *third* time could help?
Click to expand...
3.3.2 just released....you could not have tried this version of the software on Gravity 10+ days ago.
 
9point81 said:
3.3.2 just released....you could not have tried this version of the software on Gravity 10+ days ago.
Click to expand...
Please explain this then:
3.3.2 failed on 9:16.webp
 
9point81 said:
As per the point of this thread, 3.3.2 just released. I just successfully installed it a couple hours ago myself
Click to expand...
They pushed 3.3.2 to the car hoping it’d fix the problem. New versions of a software are not necessarily pushed to all vehicles at once. More though when things are sketchy as it is the case with Lucid software.
 
Thierry said:
They pushed 3.3.2 to the car hoping it’d fix the problem. New versions of a software are not necessarily pushed to all vehicles at once. More though when things are sketchy as it is the case with Lucid software.
Click to expand...
This would be the first I've seen or heard of this on Gravity if this is the case. Had my Gravity a few months now and not seen nor heard of this @borski can you confirm if this has happened before?
 
Thierry said:
Please explain this then:View attachment 32792
Click to expand...
Clearly the 3.3.1 update failed, not 3.3.2. The current version shown is incorrect as others have also stated the sw version shown on their app differed from what's shown in car.
 
Two for two post update. Immediately get the no key message but I can shift into gear. 😆

I don't have the fob update tho. Really, as long as I can drive I don't care. 😁

My live view has also stopped working, but this was prior to the update.
 
NoseyReporter said:
Two for two post update. Immediately get the no key message but I can shift into gear.

I don't have the fob update tho. Really, as long as I can drive I don't care.
Click to expand...
Just a suggestion, can we maybe not blow this thread up with key fob issues. If you HAVEN’T had your fob updated then hold off on saying you’ve still got issues.

Now, if you HAVE had your fob updated and still see the message then definitely post.
 
Jeffgtx said:
the current version in that photo is 3.2.2. Not 3.3.2.
Click to expand...

I don't understand what people are missing here.

The version of the software (prior to any update was 3.2.2). Lucid pushed version 3.3.2 to the vehicle hoping it would fix he issues. After the first attempt failed they agreed to push another update. That second try failed more dramatically (nothing was working after that) and I was asked to bring the vehicle to the Lucid center. The car was never on 3.2.1, or may be it was AFTER the first attempt which would explain why the key fob started working again.
TL;DR: they pushed 3.2.2 to the vehicle 10 days ago and it ended up with my car being towed.
 
Jackles said:
I had a software mismatch issue that @Allnatt was also having.

Car was 3.3.1 but app said we were 3.2.2 so we couldn’t use live link.

Glad this fixes that. Live link worked for me as well.
Click to expand...
Yep, Installed last night and the version mismatch is resolved. To early to tell for sure about FOB issues but the car did unlock automatically as I approached.
 
Thierry said:
I don't understand what people are missing here.

The version of the software (prior to any update was 3.2.2). Lucid pushed version 3.3.2 to the vehicle hoping it would fix he issues. After the first attempt failed they agreed to push another update. That second try failed more dramatically (nothing was working after that) and I was asked to bring the vehicle to the Lucid center. The car was never on 3.2.1, or may be it was AFTER the first attempt which would explain why the key fob started working again.
TL;DR: they pushed 3.2.2 to the vehicle 10 days ago and it ended up with my car being towed.
Click to expand...
This is 3.3.2 not 3.2.2. You said in one sentence that they pushed 3.3.2 and then in another that they pushed 3.2.2 10 days ago.

There was 3.2.1 and 3.2.2. Then came 3.3.1 and 3.3.2. You couldn’t have had 3.3.2 10 days ago, it didn’t exist.
 
HC_79 said:
Just a suggestion, can we maybe not blow this thread up with key fob issues. If you HAVEN’T had your fob updated then hold off on saying you’ve still got issues.

Now, if you HAVE had your fob updated and still see the message then definitely post.
Click to expand...
Is there a way to tell if a fob is updated? I just got the car yesterday so hopefully they would have done it beforehand but I didn’t think to ask (yet).
 
PGHGravity said:
Is there a way to tell if a fob is updated? I just got the car yesterday so hopefully they would have done it beforehand but I didn’t think to ask (yet).
Click to expand...
No, but you would hope they did it. You can either ask or just wait and see how it plays out. If you don’t get “key fob not detected” messages and no issues getting the car to unlock etc. you’re probably good.
 
Jeffgtx said:
the current version in that photo is 3.2.2. Not 3.3.2.
Click to expand...
Hmmm.
Now that I didn't even notice.
The power of suggestion; 3.3.2 was suggested, so I saw 3.3.2. :)

Good catch.
 
Thierry said:
I don't understand what people are missing here.

The version of the software (prior to any update was 3.2.2). Lucid pushed version 3.3.2 to the vehicle hoping it would fix he issues. After the first attempt failed they agreed to push another update. That second try failed more dramatically (nothing was working after that) and I was asked to bring the vehicle to the Lucid center. The car was never on 3.2.1, or may be it was AFTER the first attempt which would explain why the key fob started working again.
TL;DR: they pushed 3.2.2 to the vehicle 10 days ago and it ended up with my car being towed.
Click to expand...
WE are not missing anything. WE are trying to tell you that you have your versions mixed up. So either all of us are mistaken, or you are...
 
HC_79 said:
Just a suggestion, can we maybe not blow this thread up with key fob issues. If you HAVEN’T had your fob updated then hold off on saying you’ve still got issues.

Now, if you HAVE had your fob updated and still see the message then definitely post.
Click to expand...
My fob is updated and I’ve gotten the message three times today. All at the beginning of a drive and it goes away. I don’t care as it’s not impacting ability to drive, but do hope they get it to go away at some point.

That said, I did not receive any of the other random warnings I used to get about wireless charging, etc.
 
You must log in or register to reply here.
Back
Top