OTA Update 2.7.0

[Minnesota Mike]

I've experienced #1 multiple times since the update.

Same here. It appears to be a slow reboot of the dash as I just sit an wait without touching the brake.

 

[californiaboy935]

Their software group has much to be desired to live up to the hardware. Not great when the most interactions occur via software!

It feels like the updates were applied to the previous, master build, not the latest. Hence the return of the jerky DDP steering. I’m sure it’s difficult to track since the US and rest of the world are not version synced.

Consult the software iceberg Lucid’s software people have done marvelous things to make the vehicle as efficient and reliable as it is today.

UX leaves something to be desired for some. But I give Lucid’s software team credit where credit is due. Engineering gets the glory, and well deserved, but software is the Gravity that holds all those components together.

 

[terrycs]

Got the update 2 days ago. The start up time has improved. I no longer need to wait 1 minute to shift to D or R.

New issue. I use CarPlay but use the native Spotify for music. The car now no longer remembers the source I was using right before I get out of the car and the default is CarPlay. For instance, I was driving and using the native Spotify app. I got out of the car and picked up my daughter. Back in the car, the source is no longer Spotify. It would default back to CarPlay. Never an issue before. Not end of the world but annoying.

As with others, I’m having the same issue when using Tidal. As a matter of fact, I sometimes can’t even select any Tidal playlists unless I switch to another source like AM/FM, then switch back to Tidal.

 

[ChipEdwards]

Dunno if anyone else is encountering this.. but since the 2.7.0 update:
1) at least once a day, i will get into the car to a completely black pilot screen that eventually turns on about 10-20sec after I press the brake pedal.
2) the 'knock' I feel in my steering wheel for low speed turns from a stop are A LOT more frequent and consistent
3) probably not related, but the car not unlocking w/ remote key or the fob is worse. way worse. and no.. i'm not taking my car to the service center again for this to be w/o a car for two weeks to again be told that I need to keep cycling bluetooth connection on my phone or wave the key fob around the car like a shamen chanting "pleeeeasssse open".

I have the blank pilot screen frequently. For the first time I am having intermittent failures of the automatic door closing. I NEVER had this until the last update and I have had it 5 or 6 times. I went back to the auto sensing of my mobile key because the door handle push is a total crap shoot. If its raining its a 60 second time lapse for sure.

 

[hourglass]

I have three different things to comment about. Two of which are obnoxious; one of which as a possible work around doesn't seem to be working around! Sorry about the wall of text at least on mobile.

My first issue with the new Android Auto connection has something to do with my specific phone, as when my wife's phone connects (more on that in a second) there is no issue.

I have the pre production notice appear when my phone connects either with USB or with Bluetooth. I have a Xiaomi phone, which *maybe* is the reason why? Perhaps the certificate for a Xiaomi phone is significantly different than a phone for sale in the US? However, I'm not sure that's really the issue, since these cars are in Saudi Arabia and my phone is a global variant. So there is that issue which on its own is annoying enough.

Second issue occurs when my wife and I both plug our phones in to the USB to charge (wireless charging is too slow, I don't use or like). The car doesn't seem to know what to do and will pick one Android Auto to connect to, and then at some point decide to switch to the other phone's Android Auto. This is *also* an annoying new situation that has begun. I haven't tested it, but I presume the same would happen with Bluetooth connection as well.

Android Auto itself isn't helpful in this regard, as if you go into regular settings it will only allow you options that trigger launch as opposed to ignore. If you go into developer options you can disable auto launch when connected, but then I would think you would lose out on a one tap connection (or auto connect) when you are in the car alone.

Going back to the pre production software notice, I have also tested all of the release types in developer options and none remove that notice.

I have attempted (this was silly but I figured why not try) to use my Tbox Ambient to launch Android Auto through the Tbox (as opposed to Apple) and the funny thing is that while it can sometimes see the Lucid's Bluetooth, it fails to connect to it. It will "connect" and then reboot itself while the Lucid is trying to negotiate the communication. When the Tbox is back up it will not connect to the Lucid Bluetooth that is now in the list of available connections. I only tried this because I thought I could bypass both phones by not connecting Android Auto to the car and just using the Android Auto that the Tbox has. Apparently that won't work either.


I have:

Followed Lucid's directions from the release notes with no luck. After each attempt below I Air logo rebooted the car.

I have fully uninstalled and reinstalled Android Auto from my Xiaomi phone.

I have changed which version of Android Auto that is running via developer settings. <- now I did not change the developer setting, then uninstall, reinstall, etc. so maybe I need to spend 45 min doing this with each option? Uninstall/disconnect/forget on phone and car, then reboot the car, choose a different release in developer options, and then connect?

As I said, an interesting note is that my wife's Samsung phone has no issue and does not display the pre production software notice.

Help?

I had the issue of AA stuck in day mode and audio not ducking(it pauses the song playing when navagation speaks). In an attempt to try to fix it I followed Lucid's instruction and unpair-cleared cache -repaired. Then I got the preproduction message after this, you know, like how you are suppose to REMOVE the message and not make the message appear /s.

It also removed Waze from AA for me for some reason, and I searched online and followed this and got the pre production message removed.

Go to settings - Apps - Android Auto - Three dots on top right - Uninstall updates
Then install Android Auto 10.3.633404-release(arm64-v8a). I got it from apkmirror
After installing it, do not update to the newest version yet. Open AA on Lucid and the pre production message should go away
Then you can update it to the newest version of AA.

Btw after all this work the same issue I had still presists....

 

[GT2022Owner]

Ever since I updated to 2.7.0, my AGT reboots almost every time it’s parked for awhile. When I get back in the car, the system is rebooting.

Anyone else seeing this?

 

[idiot900]

I think periodic infotainment reboots have been standard behavior for as long as the car has been out - but for you it's happening so often that you nearly always see it?

 

[GT2022Owner]

I think periodic infotainment reboots have been standard behavior for as long as the car has been out - but for you it's happening so often that you nearly always see it?

Yeah this is about every fifth time I start the car. I’ve never had this happen so often before

 

[idiot900]

Weird. Service can query the car to check on error codes. Might be worth a shot especially if you’re still under warranty.

 

[Chrome]

Ever since I updated to 2.7.0, my AGT reboots almost every time it’s parked for awhile. When I get back in the car, the system is rebooting.

Anyone else seeing this?

Yes. Prior to 2.7.0, my center/speed display would be ready and waiting for me before I could even get seated. Now I often have time to sit, close door, buckle up, and equip sunglasses before it's finished with the startup sequence (Lucid logo over Arizona background). Pilot Panel and upper multi-function displays are immediately working upon opening the door, so those are unaffected for me. I've done a couple of logo resets since 2.7.0 to fix the No Audio bug; these didn't resolve it.

It adds several seconds to the start of a drive, but I'm willing to wait and see if the next OTA update knocks it out.

 

[kopik]

Yes. Prior to 2.7.0, my center/speed display would be ready and waiting for me before I could even get seated. Now I often have time to sit, close door, buckle up, and equip sunglasses before it's finished with the startup sequence (Lucid logo over Arizona background). Pilot Panel and upper multi-function displays are immediately working upon opening the door, so those are unaffected for me. I've done a couple of logo resets since 2.7.0 to fix the No Audio bug; these didn't resolve it.

It adds several seconds to the start of a drive, but I'm willing to wait and see if the next OTA update knocks it out.

Same happens to my 2025 AT every few days since 2.7.0. I'm sure the next OTA will fix it (while introducing new bugs) as before...
And we all have to brace for the upcoming cloud update on 7/8/25. I really hope I am wrong on this one!

 

[Bunnylebowski]

Same happens to my 2025 AT every few days since 2.7.0. I'm sure the next OTA will fix it (while introducing new bugs) as before...
And we all have to brace for the upcoming cloud update on 7/8/25. I really hope I am wrong on this one!

This reboot when getting unit the car thing happened to me for the first time yesterday, of course when I was going to be late for an appointment if I didn’t leave right then. It took 2 minutes. So I drove faster and made it on time. Lucid just wants you to drive faster that’s why this is happening

 

[Bunnylebowski]

I decided to nuke reset my car just cuz of these issues and when I did it it didn’t even make the audio noise for the reboot it normally does so it was needing a reboot anyway. I think it’s a given Lucid is aware of these issues and is probably already cooking another OTA to fix it. The nuke reset worked BTW.