2.5.3 OTA Update

RM-S8

Active Member
Verified Owner
Supporting Member
Joined
Sep 9, 2022
Messages
1,119
Reaction score
1,536
Location
PA
Cars
Sapphire, GT-P, Huracan
Today around 4 am I've got a notification on my Sapphire that 2.5.3 is available for a download.
I confirmed it without reading what's new and i left home.
Does anybody know what's there?
 

Attachments

  • Screenshot_20241120_074243_Lucid.webp
    Screenshot_20241120_074243_Lucid.webp
    45.5 KB · Views: 158
  • Screenshot_20241120_074243_Lucid.webp
    Screenshot_20241120_074243_Lucid.webp
    45.5 KB · Views: 161
"Resolved a rare instance in which rapid switches between drive modes could result in an issue with on-screen images"
Thank you, it took 30 min, btw.
 
Maybe I'm forgetting something, but I believe this is the first time the release notes have ever been specific about a bug fix. I'm hoping the clarity continues.
 
Sounds vaguely like with what happened (only once) to me in 2.5.0 - pilot screen went black and then appeared (moved to, albeit distorted) the right area of the cockpit screen above it. Fixed itself, but the pilot and infotainment screens were essentially useless when it happened. No idea if this is what is addressed in this update, but when it happened it was a bit disorienting and pretty much made all controls unavailable.
 
Installing it now. Any bug fix is welcome, of course, but out of so many other bugs I didn't have this one :)
 
Hi to all, first post here. My 24 Touring is at the service center for that exact reason since yesterday and I also noted the 2.5.3 release around 4 a.m this morning too. Of course, yesterday, I was unable to reproduce the fault at service center but the last time it happenned I took a picture. Picture worth a thousand word they say so here it is ...
20241119_081231.webp
20241119_081231.webp
 
Seems odd to me that this bug, as described, would warrant its own update.
Perhaps this type of failure causes some car controls to be unavailable. Seems that way in the picture. I would definitely want an accelerated fix for this.
 
Hi to all, first post here. My 24 Touring is at the service center for that exact reason since yesterday and I also noted the 2.5.3 release around 4 a.m this morning too. Of course, yesterday, I was unable to reproduce the fault at service center but the last time it happenned I took a picture. Picture worth a thousand word they say so here it is ...
View attachment 24686View attachment 24686
Okay. Yeah. That's a bug that deserves its own update. Yikes.
 
I might be losing my already few marbles, but I THINK they made some changes to the sound system: the front bass is not as boomy anymore and the volume doesn't change as abruptly as it did after 2.5. Or I'm just getting used to it. Anyone feels the same?
 
After the 2.5 update, my ambient lights stopped working, I got an error on one of my proximity sensors, my audio started popping at loud volumes, and my highway assist would shut off without warning. I reported it all immediately as it all happened right after the install. I was told this update also addressed these things as well.

Just updated, and now my ambient lights are back on. The sensor warning is gone too. Hopefully the highway assist will work as well.
 
I might be losing my already few marbles, but I THINK they made some changes to the sound system: the front bass is not as boomy anymore and the volume doesn't change as abruptly as it did after 2.5. Or I'm just getting used to it. Anyone feels the same?
Gonna pickup my car this afternoon, I'll check that for sure before leaving. They have to do the A pillar mod as well anyway. Stay tune !
 
Seems odd to me that this bug, as described, would warrant its own update.

Since a number of people have taken umbrage with my comment... First off, I'm happy for the people who had this issue resolved. That said, the bug fix note says that it... "Resolved a rare instance in which rapid switches between drive modes could result in an issue with on-screen images". That led to a certain amount of speculation on my part, which I think has proved correct... First, if it was the left and center upper panels that went dark, that to me would have been a very big deal, but not so much the on-screen images, which are in the upper right and pilot panels. Second, while some controls are lost there, those that are mission critical, like adjusting the seats or mirrors, should be changed while driving. Third, I figured that a logo reset would fix this at the next stop, which does seem to be the case. And last, if something rarely happens, and then only to those few people who are rapidly switching between driving modes, I figured this was rare indeed.

If this had been a fix for those people who have lost access to mission critical cameras after 2.5, and are still waiting to get them back, that would have been a no-brainer to me. This one... not so much.

Maybe I'm just disappointed that this update today means there's probably no good news on the Android Auto front tomorrow. :)
 
Since a number of people have taken umbrage with my comment... First off, I'm happy for the people who had this issue resolved. That said, the bug fix note says that it... "Resolved a rare instance in which rapid switches between drive modes could result in an issue with on-screen images". That led to a certain amount of speculation on my part, which I think has proved correct... First, if it was the left and center upper panels that went dark, that to me would have been a very big deal, but not so much the on-screen images, which are in the upper right and pilot panels. Second, while some controls are lost there, those that are mission critical, like adjusting the seats or mirrors, should be changed while driving. Third, I figured that a logo reset would fix this at the next stop, which does seem to be the case. And last, if something rarely happens, and then only to those few people who are rapidly switching between driving modes, I figured this was rare indeed.

If this had been a fix for those people who have lost access to mission critical cameras after 2.5, and are still waiting to get them back, that would have been a no-brainer to me. This one... not so much.

Maybe I'm just disappointed that this update today means there's probably no good news on the Android Auto front tomorrow.
It’s not a competition. I’ll take more good updates over fewer, and honestly prefer smaller ones. Less to possibly break.
 
"A pillar" mod?
The TSB to replace some acoustic tape that affects the front footwell woofers' audio characteristics.
 
The TSB to replace some acoustic tape that affects the front footwell woofers' audio characteristics.

The TSC actually, which replaced a similar, but not quite as good TSB. You need the TSC to get the full SSP benefits, which I know some are not wild about.
 
Gonna pickup my car this afternoon, I'll check that for sure before leaving. They have to do the A pillar mod as well anyway. Stay tune !
Ok got my car late afternoon and didn't have time to update. Even if I didn't have woofer distortion in the A pillar the sound quality wasn't there (tape was probably still holding well) there is a major improvement with the butyl tape AND 2.5.0 and no I didn't notice any "speed"reaction on volume control. The 2.5.3 fix the display image after switching regen mode for sure. Lucid Montreal was way ahead any dealership I dealt with in my life and that's include Toyota, BMW and Polestar. As a side note it took 4 years Polestar to iron out every glitches in the car, app, infotainment, phone as a key, etc, ( 2 years + to release Apple carplay and still no Android Auto) in my Polestar 2, so I know it's a pain in the butt but that is the way it is for any new EV. I'm willing to wait and see up to 2 more years for any improvements as long as they (Lucid) continue their good work to fix and/or upgrade "programmation " cause the car performance by itself is a freaking blast. 😉
 
Back
Top