2.8.17 update

Installed 2.8.17 and did the steering wheel reset as I always do. Then I had an hour long drive.
Immediately, it said my Lidar was blocked (it wasn't). Then native Tidal experienced dropouts and static.
Didn't listen to music on the long ride home. Then the blinker cameras stopped working.
I got home and did another reset. Hopefully it fares better tomorrow.
 
New 2.8.17 bug: while driving on Adaptive Cruise (not on DA) it randomly disengages with red alert saying "Drive Assist Cancelled".
 
Asking sincerely not sarcastically as I'm not a software person...but why is Lucid struggling so much with software? I would think a company would know this going into this business that software experience and UX design is probably the second highest importance item that defines their expert with a vehicle...why such struggles? What might be making lucid struggle this much on software after excelling in hardware? Again, asking sincerely and to deepen understanding on my end cos I got really frustrated at the 2.8.16 update...thanks.
 
Asking sincerely not sarcastically as I'm not a software person...but why is Lucid struggling so much with software? I would think a company would know this going into this business that software experience and UX design is probably the second highest importance item that defines their expert with a vehicle...why such struggles? What might be making lucid struggle this much on software after excelling in hardware? Again, asking sincerely and to deepen understanding on my end cos I got really frustrated at the 2.8.16 update...thanks.
My 2¢ - they tend to regress on bugs they have already fixed which points to lack of automated tests. Leadership team needs to make automation a requirement rather than nice to have. Engineers need to think of writing tests right from the beginning and not think of it as an after thought.
 
My 2¢ - they tend to regress on bugs they have already fixed which points to lack of automated tests. Leadership team needs to make automation a requirement rather than nice to have. Engineers need to think of writing tests right from the beginning and not think of it as an after thought.
I've been really curious about what their CI/CD and testing frameworks look like, and what they are missing that, say, Tesla has or does that results in more software success.
 
I'll also add, while I understand and agree with the concept behind rolling out updates to vehicles over a period of time, I really wish Lucid would provide some form of "Check for Updates" functionality for those of us who are eager to get a new update or fix.
 
It feels that way to me, but it's really hard to say overall. I got 2.8.9 and 2.8.16 really really early compared to when I started seeing posts on here about them. I'm still waiting on .17. However, it's fine, .16 hasn't caused me the issues that I hear from others on here.
Same I got .16 quickly and haven’t had any issues with it except one audio crash.
 
New 2.8.17 bug: while driving on Adaptive Cruise (not on DA) it randomly disengages with red alert saying "Drive Assist Cancelled".
Installed 2.8.17 and did the steering wheel reset as I always do. Then I had an hour long drive.
Immediately, it said my Lidar was blocked (it wasn't). Then native Tidal experienced dropouts and static.
Didn't listen to music on the long ride home. Then the blinker cameras stopped working.
I got home and did another reset. Hopefully it fares better tomorrow.

Hell’s bells
 
Just got the update late this afternoon. Has anyone noticed that the turn signal volume has switched to the rear speakers instead of the front? I haven't detected any other changes. I still have connectivity issues with the app while in my house, but I've been having this issue since two updates ago. Very frustrating.
 
Well, the additional “robustness” STILL does NOT include returning to the last audio source selected. My need to manually select Lucid native Tidal from scratch every single time I get in… Remains!!!

WTAF? While it seems like a small thing, nothing reminds me more daily about the unstable state of this car’s software. So frustrating!
 
Well, the additional “robustness” STILL does NOT include returning to the last audio source selected. My need to manually select Lucid native Tidal from scratch every single time I get in… Remains!!!

WTAF? While it seems like a small thing, nothing reminds me more daily about the unstable state of this car’s software. So frustrating!
Same frustration here. What's crazy is when I get in it's on my last audio source for a second, then it switches. Seems like a simple thing to get working.
 
Anyone else have the feeling that they are doing a slow roll out on this one? If the last few updates are any indication, I would have this one by now.
Either they are slow rolling it, or they have already pulled it because it was causing new problems.

Also known as Tuesday at Lucid.

I don’t have it yet, either.
 
Asking sincerely not sarcastically as I'm not a software person...but why is Lucid struggling so much with software? I would think a company would know this going into this business that software experience and UX design is probably the second highest importance item that defines their expert with a vehicle...why such struggles? What might be making lucid struggle this much on software after excelling in hardware? Again, asking sincerely and to deepen understanding on my end cos I got really frustrated at the 2.8.16 update...thanks.

My best guess: Lucid started as a company led by a guy who loves cars and automotive engineering. But not so much infotainment software. So when they designed Air, they had some vague idea software would be important, but they didn’t think to bring their software team into the design of the hardware of the car itself. They more or less just wired a bunch of computers together and said “Here. Make software for this.”

It’s similar to how 1990s Microsoft was led by salespeople. And thus design wasn’t part of the ethos of the company. Everything was driven by what would appeal to the guy signing the checks for whatever company bought x number of licenses. Home buyers would buy it because it was what they used at work.

Then Apple started succeeding in the consumer space with their fancy design, and Microsoft lost footing with the general public fast.

So Microsoft, Facebook, and every other company with ugly software hired designers, thinking that would take care of it immediately. But it didn’t. Their stuff still sucked, because design was an afterthought. What good are fancy designers if the salespeople and the engineers can just shut them down in every meeting? It’s not enough to hire talented people. You have to give them a seat at the table.

The good news is Microsoft eventually got their design house in order, to the point where their newer stuff isn’t half bad. But it took many years.

Lucid is climbing out of a hole. We warn companies about getting into this position all the time when they shortcut and force releases to the public before they are ready. It always feels like the right thing at the time; just release and worry about it later. But the core of the issue is how the car is physically wired. Which can’t be changed post delivery. So you end up playing whack-a-mole trying to get all the components to speak to each other and stop glitching.

It’s the worst possible position to be in as a software organization. Even the best of leaders would have a rough time making it work. And to date, I have no idea what software leadership looks like at Lucid. It’s a black box, as far as the public is concerned, once Mike Bell left.

Of course, Gravity did have some software team input in its computer hardware design. Which led me to believe Gravity was going to go more smoothly. That obviously hasn’t worked out. They did have to start from scratch with a whole new stack, but they likely needed another year or two to get it together. Instead they shipped it, digging yet another hole for themselves.

I’ve said it many times; I don’t envy them. I also think they need a fire lit under them if it isn’t all hands on deck to get this straightened out.

I do think they can get past these issues. But they are clearly not there yet.

They have a year or so to get the newer Gravity stack up to snuff before it gets put into Midsize. Then they can redesign Air’s computer system and put the same platform there.

Hopefully they can make this coming year count.
 
Asking sincerely not sarcastically as I'm not a software person...but why is Lucid struggling so much with software? I would think a company would know this going into this business that software experience and UX design is probably the second highest importance item that defines their expert with a vehicle...why such struggles? What might be making lucid struggle this much on software after excelling in hardware? Again, asking sincerely and to deepen understanding on my end cos I got really frustrated at the 2.8.16 update...thanks.
Chicken and egg problem. Software engineering is highly specialized with a ton of technical jargon. Software engineering lives almost entirely in the world of abstract and intangible beyond the touch points where a user interacts. Even "experts" can be experts technically without any grasp of maintainable solutions that address business needs.

Even amongst software engineers, the ability to discern the good from the bad can be incredibly difficult without the necessary expertise, experience, and perspective. I have worked on teams and led efforts derailed by blatantly objective crap decisions and inputs that sound "nice" but in reality cripple efforts mid to long-term. Good luck discerning as a company that has never had a solid footing to begin with the charlatans from the experts. Given the massive turnover for software engineers, lessons learned and actual improvements (rather than selecting an alternative and equally bad solution) is likely minimal at an organization level.
 
In honor of our Lucid updates, I have decided to submit the word "robustness" to Oxford for Word of the Year 2026.

On a related note, and with respect to the word 'soon'. I have proposed an additional definition to the Cambridge Dictionary...

Soon - Meaning of:​

in or within a short time; before long; quickly:

She'll soon be here./She'll be here soon.
It will soon be impossible for foreigners to enter the country.
The sooner we leave, the sooner we'll get there.

A
t the same time or a very short time after:

As soon as I saw her, I knew there was something wrong.

As soon as possible:

We need the repairs done as soon as possible.

Soon - Recent Cultural Adaptations:​

Sometime between five minutes from now and the very end of time itself:

I know we promised those features three years ago, but rest assured that they will be released soon.


Just funnin' around on a Saturday morning. Good things come to those who wait, although I am kind of old to be waiting too much longer. :-)
 
My best guess: Lucid started as a company led by a guy who loves cars and automotive engineering. But not so much infotainment software. So when they designed Air, they had some vague idea software would be important, but they didn’t think to bring their software team into the design of the hardware of the car itself. They more or less just wired a bunch of computers together and said “Here. Make software for this.”

It’s similar to how 1990s Microsoft was led by salespeople. And thus design wasn’t part of the ethos of the company. Everything was driven by what would appeal to the guy signing the checks for whatever company bought x number of licenses. Home buyers would buy it because it was what they used at work.

Then Apple started succeeding in the consumer space with their fancy design, and Microsoft lost footing with the general public fast.

So Microsoft, Facebook, and every other company with ugly software hired designers, thinking that would take care of it immediately. But it didn’t. Their stuff still sucked, because design was an afterthought. What good are fancy designers if the salespeople and the engineers can just shut them down in every meeting? It’s not enough to hire talented people. You have to give them a seat at the table.

The good news is Microsoft eventually got their design house in order, to the point where their newer stuff isn’t half bad. But it took many years.

Lucid is climbing out of a hole. We warn companies about getting into this position all the time when they shortcut and force releases to the public before they are ready. It always feels like the right thing at the time; just release and worry about it later. But the core of the issue is how the car is physically wired. Which can’t be changed post delivery. So you end up playing whack-a-mole trying to get all the components to speak to each other and stop glitching.

It’s the worst possible position to be in as a software organization. Even the best of leaders would have a rough time making it work. And to date, I have no idea what software leadership looks like at Lucid. It’s a black box, as far as the public is concerned, once Mike Bell left.

Of course, Gravity did have some software team input in its computer hardware design. Which led me to believe Gravity was going to go more smoothly. That obviously hasn’t worked out. They did have to start from scratch with a whole new stack, but they likely needed another year or two to get it together. Instead they shipped it, digging yet another hole for themselves.

I’ve said it many times; I don’t envy them. I also think they need a fire lit under them if it isn’t all hands on deck to get this straightened out.

I do think they can get past these issues. But they are clearly not there yet.

They have a year or so to get the newer Gravity stack up to snuff before it gets put into Midsize. Then they can redesign Air’s computer system and put the same platform there.

Hopefully they can make this coming year count.
Thank you. Why do you think that they will redesign the Air's computer system? I have noticed little tangible difference in functionality for the latest OTAs. In fact the recent one seems to have degraded efficiency, surround view and connection with CarPlay' connection for Sirius. Nothing serious if the efficiency improves for longer than local drives but from a lifetime 3.5 m/kWh to well under 2 got my attention and it is not that cold here. Past winters in NH and CO had better efficiency and it was colder in those locations than VA.
 
It feels that way to me, but it's really hard to say overall. I got 2.8.9 and 2.8.16 really really early compared to when I started seeing posts on here about them. I'm still waiting on .17. However, it's fine, .16 hasn't caused me the issues that I hear from others on here.
Same here. App version is still 2.11.0(3928) in my App Store.
 
Same frustration here. What's crazy is when I get in it's on my last audio source for a second, then it switches. Seems like a simple thing to get working.
Speaking of audio it was fine for 2 days after the install. Today audio was garbled from all sources.. break up, distortion. Even the turn signals sounded horrible. Have rebooted, and will see (hear) how it goes later. Sheesh.
 
Speaking of audio it was fine for 2 days after the install. Today audio was garbled from all sources.. break up, distortion. Even the turn signals sounded horrible. Have rebooted, and will see (hear) how it goes later. Sheesh.
THIS is what I really want to understand from a software perspective...one day things work...the next day they don't...how does that happen...!?
 
Back
Top