OTA Update 2.7.0

[Bunnylebowski]

Which reset is that? I did the steering wheel reset and I still have the center screen lagging to boot every now and then since 2.7.0.

Oh yeah the steering wheel reset used to be called the nuke reset and was strongly discouraged by Lucid as it also would wipe logs they could access and potentially cause errors in data writing. However they made it into the “steering wheel reset” who’s purpose is there for when you can’t reset via a display and it doesn’t wipe logs now.

 

[Celeras]

Anyone else had the issue where all interior sounds don’t work for a drive? Including AirPlay, drive mode shift sounds, even the indicator “blink” — as through the speakers just got disconnected. Everything else works fine, and it goes back to normal the next drive.

Happened to me twice since 2.7.0

Yes, but it happened prior to this update for me. Talked about in this thread, linking to a specific reply where I posted a weird video: https://lucidowners.com/threads/audio-issues.11483/post-265835 . Many others post to the effect of "happens sometimes" so I don't think it's related to this update.

 

[kopik]

I think it is pretty clear that OTA's both fix prior issues (while occasionally bringing new features) and introduce new bugs. Lucid has done a pretty decent job in fixing the existing bugs. I wish every OTA did not bring up a new ones though...

 

[LucidPea]

still waiting on the update.....these rollouts are pretty slow

 

[JandrewAnsen]

Yes, but it happened prior to this update for me. Talked about in this thread, linking to a specific reply where I posted a weird video: https://lucidowners.com/threads/audio-issues.11483/post-265835 . Many others post to the effect of "happens sometimes" so I don't think it's related to this update.

Ah, thanks! First time I experienced it was after 2.7 so I assumed it was related to the update, but perhaps not. Hard to keep up with everything that's been discussed in this forum!

 

[segbrk]

still waiting on the update.....these rollouts are pretty slow

We've reached the point where it's reasonable to ask Customer Care to push it to you.
Rollouts aren't this slow, but if it fails to push to you for some reason you may have to ask.

 

[Chrome]

Another 2.7 update issue (other than the annoying “window open “ warning that I can’t shut off), is a charging problem. At 70% charge my home 220 charger starts at 9 kw and within 3-4 minutes decreases to 4 kw. Never did this before and does it with using my other cars Audi charger cord as well as the Lucid one. This is using a dedicated 50 amp breaker in my main box. Really makes charging long. Had been 9 kw the whole charging time before the update.

I've had this exact issue for the majority of my at-home charging sessions since 2.7.0. I use the Mobile Charging Cable with a NEMA 14-50, 50A breaker. It was always 9 kW in the past, now it is frequently reduced to 3 or 4 kW for the entire session.

In fact, right now it's charging in my garage... at 4 kW. Estimate of 3h 55m to add 12%. I also noticed that the short, low-gauge "adapter section" of the cable is very warm (as I expect), while the long portion with the J1772 is practically room-temperature. I could have sworn the entire cable was fairly warm during sessions in the past. Of course I can't do a comparison now. Maybe another user with the same home charging configuration could chime in on this for us.

Glad to hear someone else has observed this. All of my searches (even on other sites) have turned up no similar cases. It obviously isn't widespread, because owners would be flocking to this forum to ask why their Level 2 sessions are suddenly taking twice as long.

 

[JJ_5]

Yes, but it happened prior to this update for me. Talked about in this thread, linking to a specific reply where I posted a weird video: https://lucidowners.com/threads/audio-issues.11483/post-265835 . Many others post to the effect of "happens sometimes" so I don't think it's related to this update.

I hadn't experienced it until this update. It's happened twice in the past week.

 

[Takeshi]

Just drove home with 2.7.0.

Android Auto Works flawlessly as intended. Although small , but directions and music were playing wonderfully.

One annoyance that was definitely noticeable was the audio. The audio was pausing whenever the navigation turn by turn direction was announced on Android Auto. It would have been better to lower down the music volume while still letting the navigation directions output from the speakers at the same time.

 

[Bunnylebowski]

I think the iPhone has a setting where you can change that where it lowers background but continues playing instead of pausing, I’d guess Android phones have a preference like that also? That’s not something the car controls as far as I know.

 

[Bobby]

I think the iPhone has a setting where you can change that where it lowers background but continues playing instead of pausing, I’d guess Android phones have a preference like that also? That’s not something the car controls as far as I know.

I think that’s all controlled by the car not the phone.

 

[Bunnylebowski]

I must be confusing it with Apple itself where you can tell it to leave your podcast playing in the background while Apple Maps is giving directions, but maybe if your music is CarPlay or AA but Navigation is Lucid or music is Lucid but navigation is AA then AA or CarPlay doesn’t continue Lucid audio and vice versa?