Software version 3.2.2

[Jackles]

I was referring to this happening with a previous release long ago in my Air.

I haven’t had key fob issues since taking delivery of my Gravity in June but as I mentioned earlier, if the car is in Park and you’re fumbling about in the car the key goes to sleep after about 60 seconds of non movement. Are you seeing this message after sitting in the car for an extended period of time while it’s in Park or is I happening as soon as you get in the car.

Also, if you haven’t had Lucid update your fob firmware this is a moot topic.

I’ll call lucid tomorrow to ask. You’d think they’d update the fob before I took delivery yesterday lol..

I get the warning constantly when I’m driving.

 

[borski]

You are shifting the burden of proof to an owner, who I am sure will end up seeking help for the issue, but it’s the company who needs to prove that an issue is fixed during the warranty period.

No, I am not. Lucid, by virtue of stating in the release notes that this fixes key fob issues, contingent upon a service visit after installation of the update, has stated the issue is fixed. If this owner does not believe it is, it is incumbent upon the owner to deduce whether or not they have satisfied the contingency as specified in the release notes.

I'm not really sure why I have to spell it out like this. The burden of proof is on the owner, as the owner is the one making the claim that the update doesn't fix the keyfob. Maybe it doesn't! But if it doesn't, it is on the owner to show that, as Lucid thinks it does, based on the above release notes.

Either way, I am here for the data.

Then you should not be in opposition to gathering it, rather than assuming the update doesn't do what it says on the tin and jumping to conclusions.

 

[borski]

I’ll call lucid tomorrow to ask. You’d think they’d update the fob before I took delivery yesterday lol..

Yeah, they definitely should have. I'm not sure they had that as part of the PDI yet though, so it's possible the timing was such that it just happened to slip through the cracks.

I get the warning constantly when I’m driving.

That's definitely unusual. We've gotten it a few times, but not constantly. But we also haven't had the service visit for it yet either

 

[9point81]

My software update completed remotely, I did it while I'm here in Germany and all went well from what I can tell. Can't see anything on the live feed yet but it's in the garage and it's still dark at home. Will try to remote in later in the day and see if it works right.

 

[Ron_Burgundy]

I can see live view and my location is now correct. Car must’ve needed a good night’s sleep. Also, some of my home WiFi settings may be weird - or app - as I can’t connect to live view unless I turn off WiFi on my phone.

Anyway, it’s super cool and works fine. Of note, Lucid does say Halo and drive recording are Beta and they may not work as expected, etc. Will find an old USB 2.0 stick today to test recording when I get car back from SC (today, I hope).

 

[037]

No, I am not. Lucid, by virtue of stating in the release notes that this fixes key fob issues, contingent upon a service visit after installation of the update, has stated the issue is fixed. If this owner does not believe it is, it is incumbent upon the owner to deduce whether or not they have satisfied the contingency as specified in the release notes.

I'm not really sure why I have to spell it out like this. The burden of proof is on the owner, as the owner is the one making the claim that the update doesn't fix the keyfob. Maybe it doesn't! But if it doesn't, it is on the owner to show that, as Lucid thinks it does, based on the above release notes.


Then you should not be in opposition to gathering it, rather than assuming the update doesn't do what it says on the tin and jumping to conclusions.

Your view amuses me. I do support for a living and I would love to walk around and tell people it’s fixed cause it works for me when I test it.

No one care unless it works for them when I am not around, and no one is going to sit there and spend hours trying to figure out all the possible variations of how to get a feature to work.

If it’s not simple enough to figure out, Lucid will end up paying for it on service visits.

And obviously, as a tech, data gathering is always step one to make sure an issue actually exists and if it does, if it has anything to do with the latest update or unrelated.

A new vehicle delivery on 3.3.1 I am confident in assuming it should work, do I straight think that Lucid screwed it up and skipped FOB update? I do not, I give them the benefit of doubt for competence.

Now if it doesn’t work, they get to troubleshoot and fix it, naturally.

 

[msaunders9430]

I got the 3.3.1 sw update notification this morning.

I know this question has been asked somewhere in the forum, but I haven't been able to find it.

I'd like to delay the update until I'm back from an upcoming weekend trip. My fob works fine and we know sometimes updates not only fix bugs, they sometimes introduce new ones. The manual allows scheduling up to 48 hours later, delaying for an hour, and cancelling.

How long can I delay a sw update?

 

[hmp10]

Good L-rd. I can only imagine how frustrated and deflated you are. I have a much smaller issue and they’ve had my car for just over a week and I almost lost it when they told me last week it was waiting for something (already wrote about it in Service thread).

There’s definitely a difference between being a patient early adopter but supported by Lucid (your Air experience) and feeling like they’re just leaving you.

This, too, shall pass, but I’m really sorry you have to go through this.

As you’ve said before, I really think it’s a product of delivering the Gravity before they were really ready. So yes, there may only be some folks with big issues, but there are systemic issues as well (I.e. service is overwhelmed and has little guidance)…

Thanks for your concern. I'm going to respond with a report of a call yesterday, but I'm going to do it on the Gravity Bugs/Issues thread, where I really should have put the post about the call to the Roswell Service Center, as it was more about other issues than the software updates.

 

[msaunders9430]

I got the 3.3.1 sw update notification this morning.

I know this question has been asked somewhere in the forum, but I haven't been able to find it.

I'd like to delay the update until I'm back from an upcoming weekend trip. My fob works fine and we know sometimes updates not only fix bugs, they sometimes introduce new ones. The manual allows scheduling up to 48 hours later, delaying for an hour, and cancelling.

How long can I delay a sw update?

Service center says dismiss or ignore until ready. I thought I read somewhere that the update would automatically download if not responded to after a certain time. I would think even then, I'd have to agree to the install.

 

[Ron_Burgundy]

Pretty cool Halo secure feature. You can view the side mirror cameras. But most of the time, since you won’t be near your car, they’ll be folded and so it’s kind of like a view right down the side of your car.

You can press a rear view mirror-looking button and it unfolds the camera immediately to get a full view of the side of the car. So it’s not using b-pillar cameras but can get you a very comprehensive view of side of car. Then of course front and back.

Here are pics of left side mirror folder and unfolded. Note the view angle changes on car icon to show field of view.

 

[EdL-ATX]

Maybe I'm just a stickler but it seems like more 3.3.1 talk should NOT be in the thread specifically about 3.2.2

 

[Ron_Burgundy]

Maybe I'm just a stickler but it seems like more 3.3.1 talk should NOT be in the thread specifically about 3.2.2

Fair point. The 3.2.2 thread just pops up for me. I keep forgetting there’s a different thread.

Feels like there’s no need for the 3.2.2 thread now, but not sure how folks handled the current update thread, etc for the Air. I say no need not because everyone is on 3.3.1 but effectively all bugs, etc and fixes for 3.2.2 have been discussed as nauseam here. But I guess the answer is I should stop “watching” this thread.

 

[HC_79]

Your view amuses me. I do support for a living and I would love to walk around and tell people it’s fixed cause it works for me when I test it.

No one care unless it works for them when I am not around, and no one is going to sit there and spend hours trying to figure out all the possible variations of how to get a feature to work.

If it’s not simple enough to figure out, Lucid will end up paying for it on service visits.

And obviously, as a tech, data gathering is always step one to make sure an issue actually exists and if it does, if it has anything to do with the latest update or unrelated.

A new vehicle delivery on 3.3.1 I am confident in assuming it should work, do I straight think that Lucid screwed it up and skipped FOB update? I do not, I give them the benefit of doubt for competence.

Now if it doesn’t work, they get to troubleshoot and fix it, naturally.

You mentioned being in a support role, so you know the basics. The first step in troubleshooting is reproducing an issue with enough detail for the engineers to confirm what’s happening. That’s the owner’s responsibility here. Lucid already stated in the release notes that the fix is contingent on a service visit + update, which means the burden is on the owner to show those conditions were met and the problem persists.

Otherwise, jumping straight to “Lucid didn’t fix it” without reproduction is just speculation. Support (whether IT, auto, or software) only works when the person reporting the problem provides enough data to validate the claim. You literally took the first report online with no further context to what the owner was doing or had done and just wildly posted that the update didn't fix the problem.

You constantly claim you're "all about the data" but 1 data point is not something to use to claim "Lucid didn't fix it" and as someone who is in a support role you of all people should know 1 reported issue doesn't mean a fleet wide issue.

 

[GoDestruction]

Fair point. The 3.2.2 thread just pops up for me. I keep forgetting there’s a different thread.

Feels like there’s no need for the 3.2.2 thread now, but not sure how folks handled the current update thread, etc for the Air. I say no need not because everyone is on 3.3.1 but effectively all bugs, etc and fixes for 3.2.2 have been discussed as nauseam here. But I guess the answer is I should stop “watching” this thread.

It would indeed be nice if someone who already has the 3.3.1 could start a new thread for “life after post-3.3.1” by sharing their personal experience.

Bueller? Bueller??

 

[borski]

I can see live view and my location is now correct. Car must’ve needed a good night’s sleep. Also, some of my home WiFi settings may be weird - or app - as I can’t connect to live view unless I turn off WiFi on my phone.

Anyway, it’s super cool and works fine. Of note, Lucid does say Halo and drive recording are Beta and they may not work as expected, etc. Will find an old USB 2.0 stick today to test recording when I get car back from SC (today, I hope).

You can use USB3 as it’ll degrade gracefully. Those are minimum speeds.

 

[borski]

It would indeed be nice if someone who already has the 3.3.1 could start a new thread for “life after post-3.3.1” by sharing their personal experience.

Bueller? Bueller??

Someone should definitely do that.

 

[037]

You mentioned being in a support role, so you know the basics. The first step in troubleshooting is reproducing an issue with enough detail for the engineers to confirm what’s happening. That’s the owner’s responsibility here. Lucid already stated in the release notes that the fix is contingent on a service visit + update, which means the burden is on the owner to show those conditions were met and the problem persists.

Otherwise, jumping straight to “Lucid didn’t fix it” without reproduction is just speculation. Support (whether IT, auto, or software) only works when the person reporting the problem provides enough data to validate the claim. You literally took the first report online with no further context to what the owner was doing or had done and just wildly posted that the update didn't fix the problem.

You constantly claim you're "all about the data" but 1 data point is not something to use to claim "Lucid didn't fix it" and as someone who is in a support role you of all people should know 1 reported issue doesn't mean a fleet wide issue.

I listed a single person having an issue after receiving a new vehicle, I added 1 data point.

I was arguing against having the customer go and prove that Lucid did in fact update the fob when 3.3.1 was installed, it’s not on the customer to go and prove that Lucid did the update correctly.

 

[borski]

I listed a single person having an issue after receiving a new vehicle, I added 1 data point.

I was arguing against having the customer go and prove that Lucid did in fact update the fob when 3.3.1 was installed, it’s not on the customer to go and prove that Lucid did the update correctly.

To be clear, how exactly would you like Lucid to do this? You want Lucid to reach out to this customer, without them telling Lucid there is an issue, and magically inform them of whether or not the service visit for the key fob was completed?

I presume you would agree that Lucid needs, first, to be informed by the customer that they have an issue, yes? If so, said customer’s first question (and service’s, if the customer doesn’t ask) should be “was the required update applied for the fobs at service.” That is how solving problems works.

What, precisely, are you desiring otherwise? The only suggestion anyone has made is that the customer should contact service to find out whether this has been done or not yet for their vehicle.

So, has it? If you want data… go ask the customer to get it, instead of continuing on with just a single data point.

If a bird craps on my head, I assume that bird needed to take a crap, not that all birds suddenly desire to crap on my head.

 

[037]

To be clear, how exactly would you like Lucid to do this? You want Lucid to reach out to this customer, without them telling Lucid there is an issue, and magically inform them of whether or not the service visit for the key fob was completed?

I presume you would agree that Lucid needs, first, to be informed by the customer that they have an issue, yes? If so, said customer’s first question (and service’s, if the customer doesn’t ask) should be “was the required update applied for the fobs at service.” That is how solving problems works.

What, precisely, are you desiring otherwise? The only suggestion anyone has made is that the customer should contact service to find out whether this has been done or not yet for their vehicle.

So, has it? If you want data… go ask the customer to get it, instead of continuing on with just a single data point.

If a bird craps on my head, I assume that bird needed to take a crap, not that all birds suddenly desire to crap on my head.

I am responding to one point at a time, and many posts ago I already said the user will have to go back and troubleshoot with Lucid.

It’s not on the owner to know that the 3.3.1 update needs to have fob updated, at least not in the new car first look stage.

You can have some expectation if it’s a home update and then a lot of people don’t read the notes and just hit update.

 

[borski]

I am responding to one point at a time, and many posts ago I already said the user will have to go back and troubleshoot with Lucid.

It’s not on the owner to know that the 3.3.1 update needs to have fob updated, at least not in the new car first look stage.

You can have some expectation if it’s a home update and then a lot of people don’t read the notes and just hit update.

Which is why it was also sent via email to all owners who received the update.

Again: what is the argument you’re trying to make?

If they received a car with the update installed, they should also have seen an email. I assume given enough time Lucid will also call people, though I’d argue that would be above and beyond.

Anyway, I feel like I’m repeating myself.