What's new
By:

2.6.11 Update

borski said:
So basically, between 2.6.2 and 2.6.11 were a bunch of internal versions, either to fix some bug or just to update a dependency or literally builds that didn’t work.
Click to expand...

Our car went straight from 2.6.0 to 2.6.11. I had been watching for 2.6.2 to show up, but it never did. The app says our software is up to date.

Is this as it should be?
 
hmp10 said:
Our car went straight from 2.6.0 to 2.6.11. I had been watching for 2.6.2 to show up, but it never did. The app says our software is up to date.

Is this as it should be?
Click to expand...
Yes. Some versions are for some specific cars.

For example, imagine your DE has a camera made by Bosch. It needs an updated driver Bosch shipped out. Someone’s GT, though, might have a camera made by Continental, which needs a different driver.

There are many ways to solve that problem, but one is to link a VIN to a software version, so that not all cars are necessarily on one version at all times, but *eventually* are.

So yes, you missed 2.6.1 and 2.6.2, because you were meant to. :)

And no, they aren’t “cumulative,” in that 2.6.11 did not also install 2.6.2. However, they are “final,” in that once you’re on 2.6.11 so is everyone else. It just matters that you got the right *interim* updates.

Yes, this should be clearer, and yes, they should post this on the website somewhere along with release notes and an indicator of which versions apply to which cars. :)
 
Bobby said:
My CarPlay will unlink every time I charge at home. I need to go into the devices menu and tap the CarPlay icon next to the name of my phone and it solves it.
Click to expand...
It appears that 2.6.11 fixed this bug -- at least for me. My first overnight charge was last night after the update, and CarPlay worked without having to re-link. That felt great. So, Lucid does seem to fix a lot of bugs that they do not explicitly reference in the release notes. That's fine with me. Some vendors cite every little bug fix; others just quietly fix the bugs with each maintenance release. Lucid obviously falls into the latter category, which is fine with me. Just keep squashing bugs and adding features.
 
borski said:

Semantic Versioning 2.0.0

Semantic Versioning spec and website
semver.org semver.org

Summary​

Given a version number MAJOR.MINOR.PATCH, increment the:
  1. MAJOR version when you make incompatible API changes
  2. MINOR version when you add functionality in a backward compatible manner
  3. PATCH version when you make backward compatible bug fixes
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format, such as 2.0.3-beta2.

So basically, between 2.6.2 and 2.6.11 were a bunch of internal versions, either to fix some bug or just to update a dependency or literally builds that didn’t work. You don’t reuse version numbers, so that you can maintain a proper historical record; you increment them as needed, and you simply don’t release those versions to the public that should not go out.
Click to expand...
Ok thanks for the GitHub reference. Lucid, a car manufacturer, use what all software company use for semantic and versionning except they call "software update" whatever the third number is when in fact it is a "software patch". Wich is what most software company use. Marketing wise it may looks better.
Once again thanks to you and Bobby.
 
AZLucidGuy said:
It appears that 2.6.11 fixed this bug -- at least for me. My first overnight charge was last night after the update, and CarPlay worked without having to re-link. That felt great. So, Lucid does seem to fix a lot of bugs that they do not explicitly reference in the release notes. That's fine with me. Some vendors cite every little bug fix; others just quietly fix the bugs with each maintenance release. Lucid obviously falls into the latter category, which is fine with me. Just keep squashing bugs and adding features.
Click to expand...
Sadly it didn’t fix it for me.
 
After installing 2.6.11, HOLD stopped working. I almost ran into someone before I realized what was happening. I went into the vehicle settings and it wouldn't let me select HOLD. A logo reset fixed the issue. Hope there are no more gremlins.
 
For my AT, the 2.6.11 update screwed the graphics of played media on the right side of the central cockpit panel. It is now stuck on the first played song and doesn't change to reflect the next played one. Quite a minor bug, but still new since the last update...
 
David Ross said:
Installed the update. I will report any issues.
Click to expand...
Only issue detected thus far is the inability to select or deselect the hold/roll feature in Stop Mode Drive Settings. It is grayed out on the screen.
 

Attachments

  • IMG_2898.webp
    IMG_2898.webp
    859.3 KB · Views: 190
Bobby said:
Sadly it didn’t fix it for me.
Click to expand...
Same here, 2.6.11 broke wireless CarPlay in my experience, I didn’t have any issues before 2.6.11 and it used to work almost flawlessly, but after updating to 2.6.11, I need to go to Bluetooth setting, forget my iPhone and reconnect it to get CarPlay to work again
 
mikecronis said:
I find after a Lucid Update, a soft-Air-Logo reset is a healthy option. Your results may vary. Happy motoring.
Click to expand...
I already did the logo reset before driving the car.
 
I had to do the microphone + X + hold brake reset to restore my cameras after 2 days of into. Logo reset did not work.
 
David Ross said:
I already did the logo reset before driving the car.
Click to expand...
I went to charge Lucy and was pleased to see that the car had fixed itself, perhaps by falling asleep.
 
Looking forward to that Android Auto update of course (for distinguished Men of Culture who shun the Apple philosophy).
The front-end enjoys periodic restarts like a modern smartphone or PC Operating System and, well, it doesn't hurt. Just my opinion.
 
Not sure if related but just got a drive system fault - automatic vehicle hold fault.

First drive since the update. 2023 Air T.
 
mikecronis said:
I find after a Lucid Update, a soft-Air-Logo reset is a healthy option. Your results may vary. Happy motoring.
Click to expand...
I second this… a nice logo reset after an OTA update removes some of the weird quirks I’ve seen after previous updates.
 
ME2U said:
Ok thanks for the GitHub reference. Lucid, a car manufacturer, use what all software company use for semantic and versionning except they call "software update" whatever the third number is when in fact it is a "software patch". Wich is what most software company use. Marketing wise it may looks better.
Once again thanks to you and Bobby.
Click to expand...
Basically. All patches are updates, just like all major and minor updates are updates.

But not all updates are patches.
 
After 2.6.11.... on the first drive:
1. Would not respond to the gearshift - this was temporary - after repeated tries, I was able to get moving. Hasn't recurred.
2. I got an airbag warning light on the first drive. Cleared after parking/on/off. Hasn't recurred.
3. Highway Assist and Adaptive Cruise would not engage when I hit the SET button. Came back after a couple of minutes of driving/trying.
(Yet-another "confidence builder for Lucid SW release quality.")
 
Anybody having issues with charging since the update? Mine randomly starts and stops. I'm using the Lucid mobile charger at 30amps on a dryer outlet. Nothing has changed but that. Was charging when I went to sleep last night and woke up and it had stopped 5 min later. Vehicle didn't charge overnight but soon as I opened the app it started charging again. I'll do a reset but just curious.
 
You must log in or register to reply here.
Back
Top