Air Version 2.9.0

Still enduring massive battery drain on iPhone 17 with latest iOS app and 2.9 in the car. 18% yesterday. I’ve resorted to turning background activity off in the settings. This appears to have stopped it today and has not affected phone as a key operation.

Settings > Type “Lucid” in search at bottom > turn off the slider for background refresh as pictured.
As you're probably aware, the iPhone kills your battery as it does it's indexing thing for a day or more after recent iOS updates. Apple has gotten really sloppy with its software over the past couple years.
 
Where'd you get that 6.2 GB figure? My car only pulled down a little under 4 GB. Just curious - your point stands either way; the download will take time.
Eero mesh network reported that for the car connected for that timeframe. Do you have DD Pro? Maybe that’s the difference? 🤷‍♂️
 
Eero mesh network reported that for the car connected for that timeframe. Do you have DD Pro? Maybe that’s the difference? 🤷‍♂️
I have DD Pro and eero reported a 5.3 GB download for me.
 
I also have an EEro, but it's in bridge mode so no per device stats. But, my Firewalla "Gold Plus" (awesome device and can keep up with my 2GB fiber) reported the Lucid downloaded 6.3 GB just before the update was available. DDPro here.
 
I wonder how many fewer posts we'd have on our forum if most people would perform a reset as a first-step before coming here to talk about issues with a new update?

I'm not saying that to be a wise guy. It's just whenever I run into a software bug like the many reported here for 2.9.0—particularly those common bugs that have been reported over and over by others for months with earlier updates—I always try a quick reset. Either a logo or a nuke.

After updates, the car needs to do a full reboot, and as we have known for many years, the reboot sequence for the Air is a bit of a crap shoot, due to the sheer number of processors that have to boot in a very specific sequence in order for everything to function correctly. It's a design flaw in the car, and there's not much that can be done about it without a massive hardware change on Lucid's part. So it's unfortunately going to be with us for as long as we own our cars.

I've come to refer to this phenomenon of random bugs after reboot as my car "waking up on the wrong side of the bed." A reset almost always cures it. So I start there. If all is well post reboot, I move on with my day and quickly forget it ever happened.

I honestly don't run into this a lot, anyway, and a quick reset saves me from being mad at my car for several days, or thinking there's some massive new problem when more likely it's just a symptom of the reboot sequence having gotten out of whack.

If the issue does NOT go away after a reset, or the reset is required many more times in a row, then I might consider it a real problem and report it here.

Should we have to deal with problems like this? Absolutely not. But I do think it's worth accepting some of the known limitations of the car and considering issues like the reboot sequence could very well explain a lot of what folks here think are introductions of new bugs in other systems.

That's not to say new updates don't sometimes cause regressions or new bugs. Just that much of what might appear to be a new problem could very well be just a new manifestation of a very old, unfixable problem.

Food for thought, anyway.
 
I wonder how many fewer posts we'd have on our forum if most people would perform a reset as a first-step before coming here to talk about issues with a new update?

I'm not saying that to be a wise guy. It's just whenever I run into a software bug like the many reported here for 2.9.0—particularly those common bugs that have been reported over and over by others for months with earlier updates—I always try a quick reset. Either a logo or a nuke.

After updates, the car needs to do a full reboot, and as we have known for many years, the reboot sequence for the Air is a bit of a crap shoot, due to the sheer number of processors that have to boot in a very specific sequence in order for everything to function correctly. It's a design flaw in the car, and there's not much that can be done about it without a massive hardware change on Lucid's part. So it's unfortunately going to be with us for as long as we own our cars.

I've come to refer to this phenomenon of random bugs after reboot as my car "waking up on the wrong side of the bed." A reset almost always cures it. So I start there. If all is well post reboot, I move on with my day and quickly forget it ever happened.

I honestly don't run into this a lot, anyway, and a quick reset saves me from being mad at my car for several days, or thinking there's some massive new problem when more likely it's just a symptom of the reboot sequence having gotten out of whack.

If the issue does NOT go away after a reset, or the reset is required many more times in a row, then I might consider it a real problem and report it here.

Should we have to deal with problems like this? Absolutely not. But I do think it's worth accepting some of the known limitations of the car and considering issues like the reboot sequence could very well explain a lot of what folks here think are introductions of new bugs in other systems.

That's not to say new updates don't sometimes cause regressions or new bugs. Just that much of what might appear to be a new problem could very well be just a new manifestation of a very old, unfixable problem.

Food for thought, anyway.
If we can trigger the “best” reset manually, why can’t the car do it automatically after update? This is not a new observation…
 
I also have an EEro, but it's in bridge mode so no per device stats. But, my Firewalla "Gold Plus" (awesome device and can keep up with my 2GB fiber) reported the Lucid downloaded 6.3 GB just before the update was available. DDPro here.
Mine was actually clocked at 6.3 but I deducted the 60-100 MB normal daily Lucid download from that.
 
I wonder how many fewer posts we'd have on our forum if most people would perform a reset as a first-step before coming here to talk about issues with a new update?

I'm not saying that to be a wise guy. It's just whenever I run into a software bug like the many reported here for 2.9.0—particularly those common bugs that have been reported over and over by others for months with earlier updates—I always try a quick reset. Either a logo or a nuke.

After updates, the car needs to do a full reboot, and as we have known for many years, the reboot sequence for the Air is a bit of a crap shoot, due to the sheer number of processors that have to boot in a very specific sequence in order for everything to function correctly. It's a design flaw in the car, and there's not much that can be done about it without a massive hardware change on Lucid's part. So it's unfortunately going to be with us for as long as we own our cars.

I've come to refer to this phenomenon of random bugs after reboot as my car "waking up on the wrong side of the bed." A reset almost always cures it. So I start there. If all is well post reboot, I move on with my day and quickly forget it ever happened.

I honestly don't run into this a lot, anyway, and a quick reset saves me from being mad at my car for several days, or thinking there's some massive new problem when more likely it's just a symptom of the reboot sequence having gotten out of whack.

If the issue does NOT go away after a reset, or the reset is required many more times in a row, then I might consider it a real problem and report it here.

Should we have to deal with problems like this? Absolutely not. But I do think it's worth accepting some of the known limitations of the car and considering issues like the reboot sequence could very well explain a lot of what folks here think are introductions of new bugs in other systems.

That's not to say new updates don't sometimes cause regressions or new bugs. Just that much of what might appear to be a new problem could very well be just a new manifestation of a very old, unfixable problem.

Food for thought, anyway.
Excellent advice. By the same token, I always reboot my phone, iPad, and Mac after an update. For the same reason. Even though there’s only one processor, there are subsystems and it seems to take a hard reboot to get everybody on the same page, so to speak.
 
If we can trigger the “best” reset manually, why can’t the car do it automatically after update? This is not a new observation…
Because the car has no idea it’s in a borked state. This can happen after any reboot. Not just when the car is updated.

And I never claimed it was a new observation. Just that it was one folks clearly still don’t get, judging by the posts in this thread.
 
Wow! This sounds better after updating to 2.9.0.
 

Attachments

  • IMG_1572.webp
    IMG_1572.webp
    655.2 KB · Views: 151
I wonder how many fewer posts we'd have on our forum if most people would perform a reset as a first-step before coming here to talk about issues with a new update?

I'm not saying that to be a wise guy. It's just whenever I run into a software bug like the many reported here for 2.9.0—particularly those common bugs that have been reported over and over by others for months with earlier updates—I always try a quick reset. Either a logo or a nuke.

After updates, the car needs to do a full reboot, and as we have known for many years, the reboot sequence for the Air is a bit of a crap shoot, due to the sheer number of processors that have to boot in a very specific sequence in order for everything to function correctly. It's a design flaw in the car, and there's not much that can be done about it without a massive hardware change on Lucid's part. So it's unfortunately going to be with us for as long as we own our cars.

I've come to refer to this phenomenon of random bugs after reboot as my car "waking up on the wrong side of the bed." A reset almost always cures it. So I start there. If all is well post reboot, I move on with my day and quickly forget it ever happened.

I honestly don't run into this a lot, anyway, and a quick reset saves me from being mad at my car for several days, or thinking there's some massive new problem when more likely it's just a symptom of the reboot sequence having gotten out of whack.

If the issue does NOT go away after a reset, or the reset is required many more times in a row, then I might consider it a real problem and report it here.

Should we have to deal with problems like this? Absolutely not. But I do think it's worth accepting some of the known limitations of the car and considering issues like the reboot sequence could very well explain a lot of what folks here think are introductions of new bugs in other systems.

That's not to say new updates don't sometimes cause regressions or new bugs. Just that much of what might appear to be a new problem could very well be just a new manifestation of a very old, unfixable problem.

Food for thought, anyway.
Couldn’t have said it better myself.
 
If we can trigger the “best” reset manually, why can’t the car do it automatically after update? This is not a new observation…
It can. It probably should. It already may.

But a reset is such an easy thing to try It just seems worth doing post-update.
 
Happiness of response and crispiness ended in less than 24hrs.

PAAK works only 10% times before update now it only works 5% of times. Camera lags all times now vs most times before. Moving between screens lags every time. Didnt have this before and may have seen very few times since ownership.

Yes, yes i rebooted many times ☹️.
Has anyone noticed similar issues since the update?
 
We’re not offering the CCCv2 upgrade through the rewards program at this time, but it’s something we hope to revisit in the future.
Is there a definitive way for us to see whether our car has CCCv2 already installed? I have a 2024 Pure and I believe some cars have differing versions that model year. Thx.
 
I have a way if you use Spotify. Search for the thread.
 
24 hours later and it still looks like this. Always an adventure Lucid, thanks.

View attachment 38676
Has anyone gotten this before with previous updates? Am I really going to be sitting there with a red update failed banner in my app until they push a new update (which was 55 days since the last one)?
 
Happiness of response and crispiness ended in less than 24hrs.

PAAK works only 10% times before update now it only works 5% of times. Camera lags all times now vs most times before. Moving between screens lags every time. Didnt have this before and may have seen very few times since ownership.

Yes, yes i rebooted many times ☹️.
Has anyone noticed similar issues since the update?
Weird I was coming to say the opposite for PAAS. I've been having to unlock my phone to get the doors to unlock. After this update, my phone stays in my pocket most of the time and I'm able to get my doors to open. It's been night and day experience. I didn't want to post here since I didn't want to jinx it, but I wanted to share my experience. A positive change of pace. I'm hoping I'm not speaking too soon.

Running Pixel 8 Pro.

Wondering if anyone else is getting a better experience after this update. Please note that I've been messing around with Dev Options for bluetooth on my phone to try and get better reliability. So it's possible one of the changes I made improved my situation and it's not the update.
 
Having some minor power charging issues after the update. Yesterday and today, when the scheduled charging time occurred, charging failed to start and I got a notification. Yesterday and today I had to restart my charger by power cycling it from the breaker and then after a restart it started charging fine. Before the update, it was a seamless experience. I have a chargepoint charger since last 3yrs and has worked very well.
 
I wonder how many updates now between this and 3.0
 
Back
Top