Car won’t go into DRIVE !

Hello everyone
My car in the last 3 days won’t go into DRIVE after it’s been charged and the cable is unplugged. It behaves like the charge cable is still plugged and the status wont change into READY position.
I have Lucid looking into it , but anyone with any experience on this issue please chime in.
Ps . I am on the latest 2.6.16 software version

Thanks in advance
Bobby
Probably a long shot but the only time I couldn't get into drive was when the key fob battery was low or dead.. Which does happen frequently if you don't keep you key isolated from the car by distance or an rfd pouch
 
Probably a long shot but the only time I couldn't get into drive was when the key fob battery was low or dead.. Which does happen frequently if you don't keep you key isolated from the car by distance or an rfd pouch

That’s an interesting theory. I believe my fob has a new battery as it was replaced as part of my yearly maintenance a few years ago. However the more this happens the more I think the vehicle isn’t “ready” yet because of something it’s waiting for.
 
Update from my end- this continues to happen to my Touring every morning, irrespective of whether it had been charging or not. It has occasionally happened, albeit to a lesser degree, when being away from the car for a period of time (>4hours or so). Additionally, on multiple occasions now since the last update, the front panel is indicating the rear door is open when it is not. Multiple reopens and closures can sometimes work, other times it seems I just have to wait it out. Lucid is going to bring the car in for diagnostics. The driver monitoring also seems to randomly go active and inactive, despite no change in driving position or wheel position.

Extremely frustrating and, as another poster said, embarrassing when driving with people. Beautiful new car that won't work. Really hoping they iron these things out (and hopeful others aren't experiencing this to the same degree). The driving dynamics of the car are incredible and I can deal with occasional gremlins as a relatively early adopter, but glitches that render the car inoperable are inexcusable.

Maybe I have a lemon?
 
I've noticed ever since I got the car last year (SW v2.5) that if I hop in after stopping a charging session and immediately attempt to move the car, it takes 10 or 15 seconds before the car is ready and will shift into gear. Now, with 2.6.16, it takes 70-80 seconds.
If I didn't know this was a "thing," I would be quite concerned in those instances, as many clearly are by all the posts about this behavior post-2.6.16.
 
I've noticed ever since I got the car last year (SW v2.5) that if I hop in after stopping a charging session and immediately attempt to move the car, it takes 10 or 15 seconds before the car is ready and will shift into gear. Now, with 2.6.16, it takes 70-80 seconds.
If I didn't know this was a "thing," I would be quite concerned in those instances, as many clearly are by all the posts about this behavior post-2.6.16.

Yeah my thought is that from a deep sleep there's something the car is waiting for an "ok" on, that now seems to take longer.
 
Random thought for you folks with this delayed startup issue: does it change anything if you remotely unlock your car from the app a couple minutes before you go to it? Just wondering if that would give it a kick in the pants to wake up before you get there. Not a solution obviously, just wondering.
 
Random thought for you folks with this delayed startup issue: does it change anything if you remotely unlock your car from the app a couple minutes before you go to it? Just wondering if that would give it a kick in the pants to wake up before you get there. Not a solution obviously, just wondering.
Ironically I started cooling the car yesterday and when I got to it and got in, it was the first time the car didn't go in to drive when not on charge. So "waking" it didn't seem to help
 
Ironically I started cooling the car yesterday and when I got to it and got in, it was the first time the car didn't go in to drive when not on charge. So "waking" it didn't seem to help
Interesting. Still wonder if unlocking would make any difference, because I think unlock wakes the car more than cooling does. Could be wrong.
 
I’m having this exact issue in my 2025 AT that I picked up 6 weeks ago. It’s maddening. And I agree embarrassing.

“How do you like your new Lucid?”

“It’s amazing once I wait two minutes to shift to Drive…”
 
Haven't experienced this issue in about a week now. Has anyone else had the problem magically go away?
 
I think I've been discussing this exact problem in the 2.6.16 thread with @bakerjin. I now realize this thread fits the bill. Happened to me the last two mornings.

I just posted a video on the 2.6.16 thread... don't want to spam it multiple places so here is a link. Tagging @marqie if this video is helpful to your investigation! https://lucidowners.com/threads/ota-update-2-6-16.12149/post-268868
Yes that is exactly the same problem, and your video is exactly my experience.
 
I think I've been discussing this exact problem in the 2.6.16 thread with @bakerjin. I now realize this thread fits the bill. Happened to me the last two mornings.

I just posted a video on the 2.6.16 thread... don't want to spam it multiple places so here is a link. Tagging @marqie if this video is helpful to your investigation! https://lucidowners.com/threads/ota-update-2-6-16.12149/post-268868
Yep, I'm still having this issue. It happens randomly, whether I cool and unlock my car remotely or just walk up to the car without opening the app. I always have both the mobile app with me and the fob key. I took a video and shared it with Lucid CS here in Houston and they said no one else has reported this problem so they aren't sure what to do. They did offer I bring in my car and let the foreman take a look at it but I'm not ready to leave my car overnight so I haven't taken them up on that offer yet. I've tried resetting via the Air Logo reset a dozen times and it hasn't helped. I get the loud static hisses or "clacks" as someone else described them when this occurs (though it's been a bit quieter lately which is.. nice, I guess). Also, I notice that even though the dash is frozen, I can still toggle my turn signal left/right and the lights blink appropriately, even if the dash is frozen and doesn't show that my turn signal is on.
 
Also, I notice that even though the dash is frozen, I can still toggle my turn signal left/right and the lights blink appropriately, even if the dash is frozen and doesn't show that my turn signal is on.

Oooh, I didn't notice the actual lights without the dash or chimes. That's interesting... and also kind of scary. Has anyone tried shifting into gear and hitting the pedal even though the car says you're in Park?

I wouldn't recommend it and only bring it up as a warning to BE CAREFUL!! If you use Creep instead of Hold that could be an absolute disaster.
 
Oooh, I didn't notice the actual lights without the dash or chimes. That's interesting... and also kind of scary. Has anyone tried shifting into gear and hitting the pedal even though the car says you're in Park?

I wouldn't recommend it and only bring it up as a warning to BE CAREFUL!! If you use Creep instead of Hold that could be an absolute disaster.
Oh that's interesting. I haven't but your theory is that the car is drivable but that the cockpit screen is just frozen. Interesting.
 
shared it with Lucid CS here in Houston and they said no one else has reported this problem so they aren't sure what to do
Well you got someone here in Dallas who has reported the loud, repetitive “clacks” at start up and my car is currently with Lucid service (Dallas services at Park Place in Fort Worth). “Clacks” happened 3 times after the most recent update (1st time after sitting parked for a few hours while shopping and 2nd and 3rd times immediately after unplugging from my LHCS). Also experienced the car not letting me shift into drive until after the “clacks” stop. Have all 3 times on video and provided to service. Was concerned with service being able to replicate it, but relieved to find out it did it’s “clacking” thing when working on other issues.
 
Well you got someone here in Dallas who has reported the loud, repetitive “clacks” at start up and my car is currently with Lucid service (Dallas services at Park Place in Fort Worth). “Clacks” happened 3 times after the most recent update (1st time after sitting parked for a few hours while shopping and 2nd and 3rd times immediately after unplugging from my LHCS). Also experienced the car not letting me shift into drive until after the “clacks” stop. Have all 3 times on video and provided to service. Was concerned with service being able to replicate it, but relieved to find out it did it’s “clacking” thing when working on other issues.
I'm glad that the techs in Dallas were able to replicate this with your car. Please keep us updated if they discover a way to fix this (my Houston service center said they may just try to reset the entire software module or something if I bring it in, but I don't want to go to that trouble if it won't fix anything).
 
I'm glad that the techs in Dallas were able to replicate this with your car. Please keep us updated if they discover a way to fix this (my Houston service center said they may just try to reset the entire software module or something if I bring it in, but I don't want to go to that trouble if it won't fix anything).
I’ll keep y’all updated.
 
This is a new "feature" of 2.6.16. Reddit is full of others who've had the same experiences. I too have. I just never remember to report back here.... you are not alone, however!
 
Back
Top