OTA 2.8.16

FWIW, I agree with the people who do not like this recent flurry of nebulous OTA Updates in the name of 'robustness and general functionality'. Something odd does seem to be going on.

That said, I take great comfort in the fact that Lucid's software development now reports to Emad Dlala. I trust him to turn this thing around, but I imagine that doing so is like steering a supertanker. It certainly won't turn on a dime.
 
No regression in hands-free Drive Assist here. However it seems like general glitchiness has gotten worse over the past few updates, with audio bugs, Spotify crashes, and cameras not working. Of course, these are just my non generalizable anecdotes.
 
Other than a single issue with AA not starting once the day after the update, everything has been working reliably for me since. 2025 AT, basic sound, basic Dream Drive.
 
This comment raises an interesting (at least to me) question. It suggests that Lucid may have the 'eyes-on' sensitivity set higher for Hands-Free Drive Assist than it does for Hands-On Drive Assist. I never thought that was the case. I have only used Hands-Free Drive Assist for a few miles since 2.8.16, and it did force me to take control, but the sun was low in the sky at the time, and I've noticed that Drive Assist doesn't like that. Is it possible that some conditions just happened to change at the same time that you switched hands-free off, or that you took off those dark sunglasses in your profile image?

Wishful thinking on my part, as I'm about to hit the road.
I think this is clear and an important point. The "gain" on the "eyes-on" sensitivity is a lot higher with hands-free than it is plain old adaptive cruise.
 
No regression in hands-free Drive Assist here. However it seems like general glitchiness has gotten worse over the past few updates, with audio bugs, Spotify crashes, and cameras not working. Of course, these are just my non generalizable anecdotes.
Huh. It is so different for me. I drove from SF Bay to Las Vegas a few weeks ago with no complaints with hands-free. Now, it is unusable.
 
After a moment’s contemplation, I updated to 2.8.16 last Friday, the night before a 500 mile trip to central PA for a family wedding. I originally planned a 20 min top off charge in Bedford before hopping on the turnpike to return home. However, I was alarmed at how fast my SOC dropped on the way out there. Granted, it was into a moderate headwind and increased altitude, but I had serious concerns about not making it to my planned charging spot. Options are few and far between in that neck of the woods. Settled on a quick boost charge in Altoona, unfortunately at an EA station. Naturally, it took changing chargers twice to finally initiate a charge. Brand new chargers too. Arriving at Bedford, I had 30 miles left. It was 140 miles to home so I charged to 300 miles of range to be safe. Arrived home with 70 miles left. Something definitely seems off with mileage since the update. Also, hands free worked fine in the way out, but could not initiate either hands free or cruise control on the way back until I did an Air reset at a rest stop on the turnpike.
Another EV adventure…
I had a sudden loss of range start showing up sometime around the prior update - after a 3 year average of 3.4 m/kw, I could barely break 2.5 in several 100+ mile charging intervals - same driver, same routes, same climate, etc. Took it to service center showing 2.13 m/kw efficiency over 150 miles; they checked the vehicle and could find nothing wrong, and said they could not replicate the issue in a 10 mile drive, so there was nothing they could do.
 
I think this is clear and an important point. The "gain" on the "eyes-on" sensitivity is a lot higher with hands-free than it is plain old adaptive cruise.
OK... I think I'm getting the disconnect here. I'm talking about Drive Assist and you are talking about Adaptive Cruise. The latter does not steer the car at all, other than maybe nudging it back into the lane if you cross a road median without the turn signal on. In Adaptive Cruise, you won't get any Distracted Driver warnings unless you turn that option on in the car's settings, in which case (at least in my experience) it will drive you nuts all the time. I was saying that I think Hands-On Drive Assist has every bit as much of a Pay Attention demand as Hands-Free Drive Assist.
 
Looks like those with the 2.8.5 software who never received the subsequent three updates are being left on 2.8.5. I guess that makes sense since the 2.8.9 and 2.8.16 appear to be attempts to fix the 2.8.7 fiasco and the 2.8.5 was stable with minimal issues for most people.
 
I had a sudden loss of range start showing up sometime around the prior update - after a 3 year average of 3.4 m/kw, I could barely break 2.5 in several 100+ mile charging intervals - same driver, same routes, same climate, etc. Took it to service center showing 2.13 m/kw efficiency over 150 miles; they checked the vehicle and could find nothing wrong, and said they could not replicate the issue in a 10 mile drive, so there was nothing they could do.
Rev 2.8.9 for me . Started on a 700 mile trip Monday...immediately noticed poor miles per kW 2.2 to 2.4 where 3.0 to 3.2 is normal. Had to add 2 extra charge points to complete the drive.. saw 1.8 for a while . Cruise set at 77mph with no heat or air conditioning no DDPro. 700 miles average 2.4 miles kw. Never got close to 3.0 even in a section of 2500 foot altitude drop. Service center is looking into the data logged on trip. Service suggested that I not do the .16 update.
Hoping for some resolve before the return trip. Quite embarrassing having to add the delays associated with charging to 90% just to make 180 miles for next charger.
 
If it helps anyone feel better, my 2 year old Tesla tanked from 306mi per charge to 260, and its more like 200 in the winter. The rear windows whistle dixey on the freeway too.
Same happened to my 4 year old model 3. It also looses 1 mi/hr of range while idle. The road noise is quite loud. But its software is rock stable and it opens immediately every single time…
 
Same happened to my 4 year old model 3. It also looses 1 mi/hr of range while idle. The road noise is quite loud. But its software is rock stable and it opens immediately every single time…
I’ll never understand why Lucid can’t get a car to open like everyone else.
 
I will say, on 2.8.9 and the lock/unlock has been very reliable. It used to be something I constantly worried about, but it's gotten to the point where I never think about it.

Edit: for context, I only use my phone for my key (Android).
 
I had a sudden loss of range start showing up sometime around the prior update - after a 3 year average of 3.4 m/kw, I could barely break 2.5 in several 100+ mile charging intervals - same driver, same routes, same climate, etc. Took it to service center showing 2.13 m/kw efficiency over 150 miles; they checked the vehicle and could find nothing wrong, and said they could not replicate the issue in a 10 mile drive, so there was nothing they could do.
So did the trip get reset and the 10 miles that service put on make over 3.0 miles per kilowatt. 🤔
 
My 200 mile Thanksgiving day round trip from L.I. to N.J. yielded exactly 4.0 m/kW. Going it was just my wife and I and returning it was my wife & I and my son and his fiancé.

It still boggles my mind as to how many iterations there are of good & bad experiences after a software update. Post update I had an issue with the right front turn signal and hands free assist that self-resolved after parking for 1 hour.
 
I had a sudden loss of range start showing up sometime around the prior update - after a 3 year average of 3.4 m/kw, I could barely break 2.5 in several 100+ mile charging intervals - same driver, same routes, same climate, etc. Took it to service center showing 2.13 m/kw efficiency over 150 miles; they checked the vehicle and could find nothing wrong, and said they could not replicate the issue in a 10 mile drive, so there was nothing they could do.
I do the updates regularly and never seem to have any problems. Did 2.8.16 perhaps a week to 10 days ago and out of curiosity because of previous comments checked my trip information. I am only driver (retired), no long trips, to golf courses and back, errands, friends houses and charge weekly from 30% or 40% up to 80%. 3+ year old AGT 19" has lifetime average 3.67 mi/kWh, after last weekend charge I am at 2.03 mi/kWh, 45% less than my lifetime average. I guess something's up, and assume/hope they know and are working on.

1764452011928.webp
 
I do the updates regularly and never seem to have any problems. Did 2.8.16 perhaps a week to 10 days ago and out of curiosity because of previous comments checked my trip information. I am only driver (retired), no long trips, to golf courses and back, errands, friends houses and charge weekly from 30% or 40% up to 80%. 3+ year old AGT 19" has lifetime average 3.67 mi/kWh, after last weekend charge I am at 2.03 mi/kWh, 45% less than my lifetime average. I guess something's up, and assume/hope they know and are working on.

View attachment 34677
If more people make a service center report our chances for action should improve.
 
If more people make a service center report our chances for action should improve.
You are right, had an appointment for annual service, door handle(s) and CCCV2 update for next week but they postponed to January for lack of parts. That was on my list.
 
No regression in hands-free Drive Assist here. However it seems like general glitchiness has gotten worse over the past few updates, with audio bugs, Spotify crashes, and cameras not working. Of course, these are just my non generalizable anecdotes.
I experienced camera not available error for the first time. I am on 2.8.16.
 
Back
Top