2.0.36

We're planning a road trip starting next Monday (Dec 19) in the Lucid. However, after two weeks it's still in the shop for the tow hook recall, and Lucid is saying they will "try" to get the car back to us by the weekend.

We haven't yet updated to 2.0.35. Assuming we get the car back in time for the trip, we won't have much time to download it or 2.0.36 to see if there are no issues. Do any of you who have the updates have any advice about whether to wait to download until we are back home, since the software was doing everything we needed before the car went to the shop?

Of course, this will become moot if this recall keeps dragging out and we have to take the Model S Plaid on the trip. We bought the Lucid for long road trips, and it's rather frustrating to have it unavailable due to ridiculously long repair times.

P.S. Just for full disclosure: some of the delay is caused by waiting for a part. While it was minor, ours was one of the cars that has had the chrome paint chip off the backlit Lucid logo at the leading edge of the hood. Since the bumper has to come off for that repair and also had to come off for the tow hook recall, I asked Lucid to replace the logo in the same shop visit. But I don't understand why it took them two weeks to get the part. They're using it on the assembly floor every day.
 
We're planning a road trip starting next Monday (Dec 19) in the Lucid. However, after two weeks it's still in the shop for the tow hook recall, and Lucid is saying they will "try" to get the car back to us by the weekend.

We haven't yet updated to 2.0.35. Assuming we get the car back in time for the trip, we won't have much time to download it or 2.0.36 to see if there are no issues. Do any of you who have the updates have any advice about whether to wait to download until we are back home, since the software was doing everything we needed before the car went to the shop?

Of course, this will become moot if this recall keeps dragging out and we have to take the Model S Plaid on the trip. We bought the Lucid for long road trips, and it's rather frustrating to have it unavailable due to ridiculously long repair times.

P.S. Just for full disclosure: some of the delay is caused by waiting for a part. While it was minor, ours was one of the cars that has had the chrome paint chip off the backlit Lucid logo at the leading edge of the hood. Since the bumper has to come off for that repair and also had to come off for the tow hook recall, I asked Lucid to replace the logo in the same shop visit. But I don't understand why it took them two weeks to get the part. They're using it on the assembly floor every day.
How long is the road trip? You could totally wait - I just wouldn’t get more than 2-3 versions behind.
 
We're planning a road trip starting next Monday (Dec 19) in the Lucid. However, after two weeks it's still in the shop for the tow hook recall, and Lucid is saying they will "try" to get the car back to us by the weekend.

We haven't yet updated to 2.0.35. Assuming we get the car back in time for the trip, we won't have much time to download it or 2.0.36 to see if there are no issues. Do any of you who have the updates have any advice about whether to wait to download until we are back home, since the software was doing everything we needed before the car went to the shop?

Of course, this will become moot if this recall keeps dragging out and we have to take the Model S Plaid on the trip. We bought the Lucid for long road trips, and it's rather frustrating to have it unavailable due to ridiculously long repair times.

P.S. Just for full disclosure: some of the delay is caused by waiting for a part. While it was minor, ours was one of the cars that has had the chrome paint chip off the backlit Lucid logo at the leading edge of the hood. Since the bumper has to come off for that repair and also had to come off for the tow hook recall, I asked Lucid to replace the logo in the same shop visit. But I don't understand why it took them two weeks to get the part. They're using it on the assembly floor every day.
Both updates take about 20 minutes between them. 5 for the 2.0.35 and 15 minutes for the 2.0.36
 
I called CS and they said that they show that my car has 2.0.36. She said that even if my car shows 35 on the screen, it still has 36.

Can anyone point to a new feature of this update? It would be helpful kniwing what to look for to confirm if the update really did work.
 

Attachments

  • 225722C9-BADD-4A9B-ACA9-A119AC3D5A67.png
    225722C9-BADD-4A9B-ACA9-A119AC3D5A67.png
    648.4 KB · Views: 99
Some of these updates tend to be mostly word salad. Give me specifics!

Glad to see the updates flow through, though.
 
Had the same thing happen to me (installed 2.0.36 but it still says 2.0.35)...

The weird part is that when I went to check it out, shortly after I sat in the car (and I mean shortly .. <3mins) the car shut off (while I was selecting things on the Pilot Panel .. mostly Settings selections like verifying Version number) .. I opened the door and the alarm went off .. I had the phone (w/ app open in the cup holder, so I was able to unlock the car from the app and stop the alarm). This has not happened to me before. I often sit in the car and fiddle with things (esp. after checking new update) without it thinking I walked away.
 
Had the same thing happen to me (installed 2.0.36 but it still says 2.0.35)...

The weird part is that when I went to check it out, shortly after I sat in the car (and I mean shortly .. <3mins) the car shut off (while I was selecting things on the Pilot Panel .. mostly Settings selections like verifying Version number) .. I opened the door and the alarm went off .. I had the phone (w/ app open in the cup holder, so I was able to unlock the car from the app and stop the alarm). This has not happened to me before. I often sit in the car and fiddle with things (esp. after checking new update) without it thinking I walked away.
This has happened to me occasionally in the past (prior to .35 and .36 updates) but I also occasionally see brief 'key fob not detected' msgs. So I just assumed the shutdowns were because of this and the fact that I dont have a mobile key. I have not tried to open my door when this happens, I first unlock with the key fob and then open the door.
 
I installed 2.0.35 and x.36 yesterday successfully. As others have mentioned, my version number still displays as 2.0.35. No apparent issues except SXM doesn't work, but to be fair the only thing I can say for sure is that SXM worked right after 2.0.33 update last month and I did not play with it much after that. I drove the car about 5 miles after the update without incident. I have to admit I was a little shaken by Cosmo Cruz's comments/experience in the "Problem after updating to 2.0.35" thread. I am very curious to hear a follow-up. Hopefully CS can determine a definitive reason.
 
This has happened to me occasionally in the past (prior to .35 and .36 updates) but I also occasionally see brief 'key fob not detected' msgs. So I just assumed the shutdowns were because of this and the fact that I dont have a mobile key. I have not tried to open my door when this happens, I first unlock with the key fob and then open the door.
Agree .. but this time I didn't get a message that there was no key detected. Everything just went black. Honestly, I was afraid that the installation of the update was starting again (w/o warning) and I was going to be locked in there for 15-20 mins). Just an odd sequence of events.

Later today, I'll be performing a Valet Card reset and then drive a bit to see if anything is different or not behaving correctly.
 
Same here, the app says software update is complete but car still shows 2.0.35 and says it is up to date.
Customer care re-pushed 2.0.36 to me and it displays correctly now. I don't think that the incorrect version on the display is a real issue but everyone who sees it should email customer care, it may help the OTA team find the commonality for why some cars show this bug.
 
Customer care re-pushed 2.0.36 to me and it displays correctly now. I don't think that the incorrect version on the display is a real issue but everyone who sees it should email customer care, it may help the OTA team find the commonality for why some cars show this bug.
Thanks for the heads up. Will do.
 
I would wait. As mentioned in other threads, my car died after the .35 update. Evidently, some of the files in the update didn't download properly and were either corrupt or missing. Not sure why that happened but, if the car is working fine, wait until you don't have to rely on it, when you are back home.
 
I would wait. As mentioned in other threads, my car died after the .35 update. Evidently, some of the files in the update didn't download properly and were either corrupt or missing. Not sure why that happened but, if the car is working fine, wait until you don't have to rely on it, when you are back home.
Yeah, I'm not usually one to recommend delaying updating your various computers and such. Certainly not long-term. But at this early stage of Lucid's development, if I were going on a road trip that was only for a few days, and the Air was my only car, or I really, really wanted to take it on that trip, I'd probably hold off on updating, as long as the car is currently working fine. No reason to tempt fate.
 
Anyone notice Tidal sound quality has gotten worse since 2.0.36? Same track on Spotify sounds much better than Tidal Atmos track now. I have Tidal set to Hifi plus but now sounds much worse.
 
Back
Top