Since 2.5.0, app will not wake up car?

[BS8899]

Well, we need to define what "works" mean.

FOB: low battery life, "buttons" are illegible and confusing. Yes, if I keep fiddling with it, it eventually unlocks the car.

Mobile App: takes a long time to wake. As noted in this tread, OTAs sometimes make it not work or at least not work properly. Often, Mobile Key needs to be augmented with pishes on the door lever. Multiple occasions where it has to be wiped and reinstalled.
Valet Key: my last resort if I get stuck

I think Lucid's implentation of their key entry devices come across as bad designs and lack of resolve to fix the underlying issues. I have never seen such charade in any other cars!

 

[borski]

Fob: “one click” locks. “two clicks” unlocks. That should be pretty easy to memorize. Battery life isn’t low if you don’t buy batteries with bitterant, or rub the bitterant off. Apple, the most “luxury” tech company, has this same problem with their AirTags.

Mobile key: works fine for me. Sometimes you have to move the phone around because Apple saves battery life by turning off the Bluetooth radio if the phone hasn’t moved in a while. Pressing the handle works *every time* so many people just do that.

Valet card: as I said, if you have the fob, the valet card is *always* unnecessary. The fob works perfectly fine as a method of entry without a battery or with a dead one. See here:

Please avoid the insults. You’re generally very reasonable here, but there is no reason to call it a charade or anything else; nobody is lying to you or hiding anything. The fob was a bad design, and Lucid made a bad choice. That doesn’t mean they’re making excuses; they take ownership of that decision. That also doesn’t mean they can do anything about it, as those are separate things.

You don’t have to agree with the choice. They don’t either, in hindsight. But hindsight is always 20/20.

 

[Lucken]

It’s not an excuse. It’s an explanation. People often misunderstand the difference.

Trust me, Lucid very much wishes they didn’t make this choice for the fob, given how annoyed so many owners are about it. That is obviously why they switched fobs entirely for Gravity.

They never said they can’t do anything about the mobile key; in fact, they’ve improved it significantly over time. Mine is just about flawless.


The valet key not working was a problem unique to you; that is definitely the first I’ve heard of that.

Why carry all 3? I only carry the phone and card. Others only carry the phone and fob, as the fob works as an NFC key even if the battery dies. There is no reason to carry all 3.

Nobody here is trying to convince you of anything. It definitely is a “top-brand luxury car”; whether you feel that way is entirely up to you, though, just like it is to every other owner.

Merry Christmas and Happy Hanukkah.

I only carry the fob and never have an issue. I feel almost guilty saying so.

 

[EVCar]

So we know Lucid signed a contract with supplier X to buy 2 fobs for the Airs they manufacture and they can't get out of this contract.
Lucid is therefore obligated to pay for 2 fobs for each car coming out of Casa Grande.
For the sake of discussion, what would prevent them from throwing away these 2 fobs and use a different one for their cars?
Lucid pays for the fobs and they can do whatever they want, right?
Nobody knows who the supplier is and it's not like the supplier's name is stamped onto the fob, so there's a no PR advantage for the supplier when the Air owners use their fobs.
If it's strictly a financial matter then the supplier shouldn't care as long as they're paid.
I suspect the real story is more convoluted, but it I were in this business and knew who this supplier is, I would not even get close to them.
They have earned bad reviews with the Air owners and should just take the money and enjoy it.

 

[BS8899]

Fob: “one click” locks. “two clicks” unlocks. That should be pretty easy to memorize. Battery life isn’t low if you don’t buy batteries with bitterant, or rub the bitterant off. Apple, the most “luxury” tech company, has this same problem with their AirTags.

Mobile key: works fine for me. Sometimes you have to move the phone around because Apple saves battery life by turning off the Bluetooth radio if the phone hasn’t moved in a while. Pressing the handle works *every time* so many people just do that.

Valet card: as I said, if you have the fob, the valet card is *always* unnecessary. The fob works perfectly fine as a method of entry without a battery or with a dead one. See here:

Please avoid the insults. You’re generally very reasonable here, but there is no reason to call it a charade or anything else; nobody is lying to you or hiding anything. The fob was a bad design, and Lucid made a bad choice. That doesn’t mean they’re making excuses; they take ownership of that decision. That also doesn’t mean they can do anything about it, as those are separate things.

You don’t have to agree with the choice. They don’t either, in hindsight. But hindsight is always 20/20.

First, I travel long distances and often stop at remote places, for rest or for charging. I can't afford to have problems getting in or start my car in a remote location. Being stranded in Barstow or Buttonwillow with no access to my Lucid is what nightmares are made of. Yes, I don't want to carry multiple devices and gadgets just to make sure I can get into my car. For example, Ionly carry my mobile key on the same long trips when I drive my Rivian, beacuse it actually works every single time, without rain dances or uninstall/reinstalls. But I am paranoid with the multitude of recurring and unresolved (i.e., roo-caused and dixed) with Lucid's entry devices. What if I encounter these problems when I have no mobile or WiFi connections?

Just read the prior posting in this thread! Read the couple of recent exchanges between an owner and @Bobby RE: the FOB. If I read it correctly, some NDA prevents Lucid from fixing or procuring a new FOB?! If that's not ludicrious and a charade, please help me with a kinder-and-gentlier description that's more appropriate!.

 

[Lucken]

First, I travel long distances and often stop at remote places, for rest or for charging. I can't afford to have problems getting in or start my car in a remote location. Being stranded in Barstow or Buttonwillow with no access to my Lucid is what nightmares are made of. Yes, I don't want to carry multiple devices and gadgets just to make sure I can get into my car. For example, Ionly carry my mobile key on the same long trips when I drive my Rivian, beacuse it actually works every single time, without rain dances or uninstall/reinstalls. But I am paranoid with the multitude of recurring and unresolved (i.e., roo-caused and dixed) with Lucid's entry devices. What if I encounter these problems when I have no mobile or WiFi connections?

Just read the prior posting in this thread! Read the couple of recent exchanges between an owner and @Bobby RE: the FOB. If I read it correctly, some NDA prevents Lucid from fixing or procuring a new FOB?! If that's not ludicrious and a charade, please help me with a kinder-and-gentlier description that's more appropriate!.

Maybe I'm naive, but it seems that some of us are having no problems with the fob. If that's the case than those that are having problems (barring some change in antenna/receiver equipment in some cars or something else within the chain that makes the fob work), we should all be having minimal to no issues with the fob. If that's the case, it would seem there is an issue that should be repairable with those cars not achieving a desirable lock/unlock scenario. I don't understand why those having problems aren't receiving the necessary fixes for this. Do the SCs not understand why some cars are having no issues and others are? As I said, maybe I'm naive.

 

[BS8899]

Maybe I'm naive, but it seems that some of us are having no problems with the fob. If that's the case than those that are having problems (barring some change in antenna/receiver equipment in some cars or something else within the chain that makes the fob work), we should all be having minimal to no issues with the fob. If that's the case, it would seem there is an issue that should be repairable with those cars not achieving a desirable lock/unlock scenario. I don't understand why those having problems aren't receiving the necessary fixes for this. Do the SCs not understand why some cars are having no issues and others are? As I said, maybe I'm naive.

Exactly!

 

[borski]

So we know Lucid signed a contract with supplier X to buy 2 fobs for the Airs they manufacture and they can't get out of this contract.
Lucid is therefore obligated to pay for 2 fobs for each car coming out of Casa Grande.
For the sake of discussion, what would prevent them from throwing away these 2 fobs and use a different one for their cars?
Lucid pays for the fobs and they can do whatever they want, right?
Nobody knows who the supplier is and it's not like the supplier's name is stamped onto the fob, so there's a no PR advantage for the supplier when the Air owners use their fobs.
If it's strictly a financial matter then the supplier shouldn't care as long as they're paid.
I suspect the real story is more convoluted, but it I were in this business and knew who this supplier is, I would not even get close to them.
They have earned bad reviews with the Air owners and should just take the money and enjoy it.

Money is not the issue.

 

[borski]

Maybe I'm naive, but it seems that some of us are having no problems with the fob. If that's the case than those that are having problems (barring some change in antenna/receiver equipment in some cars or something else within the chain that makes the fob work), we should all be having minimal to no issues with the fob. If that's the case, it would seem there is an issue that should be repairable with those cars not achieving a desirable lock/unlock scenario. I don't understand why those having problems aren't receiving the necessary fixes for this. Do the SCs not understand why some cars are having no issues and others are? As I said, maybe I'm naive.

Frankly? Because most people don’t ask service to look.

Service replaced my security node because it had errors. If you are having consistent issues, save timestamps and ask service to check it out.

Also, they can replace your fobs; you just have to bring both back to service.

There is no guarantee that fixes it, though. And past replacing those items, there isn’t much service can do. The Bluetooth the fob uses is finicky, prone to interference from other radios, and so on.

Plus, the battery bitterant thing is always an annoyance.

 

[EVCar]

Yes, it's surely an annoyance, but not a problem for me. So far.
It works, but it's not as user friendly, read idiot proof, as my other keys.

 

[BS8899]

Frankly? Because most people don’t ask service to look.

Service replaced my security node because it had errors. If you are having consistent issues, save timestamps and ask service to check it out.

Also, they can replace your fobs; you just have to bring both back to service.

There is no guarantee that fixes it, though. And past replacing those items, there isn’t much service can do. The Bluetooth the fob uses is finicky, prone to interference from other radios, and so on.

Plus, the battery bitterant thing is always an annoyance.

To be fair to the SCs, when I asked them to look, they looked. And they gave me new batteries, a new FOB, etc.. None of these fix the root problem.

For a while (several months) earlier this year, my Lucid was working "adequately" (vis-a-vis, it unlocks "most" of the time when I enter the garage, though not as promptly and not as reliably as my Rivian in the same garage). In September/October/November, we had the 2.4.X (multiple) and 2.5.X OTA updates. I was driving my Rivian in this time frame until this past week, when I started to drive the Lucid again. The Mobile App/PIN problems reemerged.

This thread suggests that a number of owners experienced Mobile Key problems coincidental with the OTA 2.5.X.

In defense of the SC, I don't think they are SW experts. And I doubt they have the tools to do the root-cause. This is a SW development/validation/deployment problem that the development team and the factory need to address.

 

[borski]

Yes, it's surely an annoyance, but not a problem for me. So far.
It works, but it's not as user friendly, read idiot proof, as my other keys.

Totally agreed. I use the mobile key and it works fine. I don’t use the fob because it annoys me.

With my “NYC walk” (or so I’m told) the phone moves enough that it almost always works without issue. When it doesn’t I just hit the handle.

I’m not gonna let it ruin an otherwise amazing car for me. Sorry if it does for anyone else.

 

[borski]

To be fair to the SCs, when I asked them to look, they looked. And they gave me new batteries, a new FOB, etc.. None of these fix the root problem.

For a while (several months) earlier this year, my Lucid was working "adequately" (vis-a-vis, it unlocks "most" of the time when I enter the garage, though not as promptly and not as reliably as my Rivian in the same garage). In September/October/November, we had the 2.4.X (multiple) and 2.5.X OTA updates. I was driving my Rivian in this time frame until this past week, when I started to drive the Lucid again. The Mobile App/PIN problems reemerged.

This thread suggests that a number of owners experienced Mobile Key problems coincidental with the OTA 2.5.X.

In defense of the SC, I don't think they are SW experts. And I doubt they have the tools to do the root-cause. This is a SW development/validation/deployment problem that the development team and the factory need to address.

This, I agree with, re: mobile key. The combo of software updates and Apple/Android controlling the Bluetooth stack (and changing it to save battery constantly) is a recipe for trouble.

The fob issue isn’t a SW issue, but it also isn’t one the SC can fix, short of replacements.

 

[BS8899]

This, I agree with, re: mobile key. The combo of software updates and Apple/Android controlling the Bluetooth stack (and changing it to save battery constantly) is a recipe for trouble.

The fob issue isn’t a SW issue, but it also isn’t one the SC can fix, short of replacements.

Have we post the survey question on this thread

RE: what phones (Android or iPhone) do the owners have...the one experiencing the problem and the one who don't have the problem?

I have a Samsung S22 Ultra Android phone. And YES, I am experiencing the problem that seems to coincide with the 2.5.X update.

 

[tonybot]

The issue many faced in 2.5.X was the app failing to wake up the car (myself included). I am not aware of it impacting the ability to use mobile key - in my case it worked fine. The app wake-up issue is resolved by turning off the WiFi, assuming you have a stable enough ATT connection on your parking location. Lucid acknowledged the issue with WiFi and are working on a fix.

Just highlighting a possibility that we may be mixing multiple issues here. Only issue I had with my mobile key has been sometime I need to wake the phone up (I thought I needed to open the app, but later figured out as @borski mentioned it is Apple conserving power). 95% of time my mobile key works with any intervention and 5% of time I need to wake my phone. Sharing this additional data point for my 2024 pure to indicate that @BS8899 ’s experience is not universal.

 

[EVCar]

60% my app can't wake the car up -- that's one reason for me to use the fob.
I was told that the Lucid app uses SMS text for this function and that may be a problem.
Lucid is sending a mobile tech to my house to check the cell signal.
They're aware that my EQS app which also uses AT-T always works instantly whereas the Lucid app can take a minute or two when it works.

 

[tonybot]

60% my app can't wake the car up -- that's one reason for me to use the fob.
I was told that the Lucid app uses SMS text for this function and that may be a problem.
Lucid is sending a mobile tech to my house to check the cell signal.
They're aware that my EQS app which also uses AT-T always works instantly whereas the Lucid app can take a minute or two when it works.

Is this issue only when your car is in your garage/at home? If so, is it connected to your WiFi? If yes, I suggest turning off the WiFi in your settings and see if that improves the app wake up behavior. It did for several of us.

 

[EVCar]

Is this issue only when your car is in your garage/at home? If so, is it connected to your WiFi? If yes, I suggest turning off the WiFi in your settings and see if that improves the app wake up behavior. It did for several of us.

This happens in my garage.
Have turned off the wifi but didn't seem to make a difference.

 

[borski]

60% my app can't wake the car up -- that's one reason for me to use the fob.
I was told that the Lucid app uses SMS text for this function and that may be a problem.
Lucid is sending a mobile tech to my house to check the cell signal.
They're aware that my EQS app which also uses AT-T always works instantly whereas the Lucid app can take a minute or two when it works.

Hang on, there’s some confusing things here: do you have mobile key set up? That uses Bluetooth when you’re nearby and does not require any kind of cell signal or WiFi signal at all.

It is only remote app wake-up that requires cell signal in the car.

 

[Bobby]

Hang on, there’s some confusing things here: do you have mobile key set up? That uses Bluetooth when you’re nearby and does not require any kind of cell signal or WiFi signal at all.

It is only remote app wake-up that requires cell signal in the car.

Exactly. This has been discussed literally hundreds of times here on the forum. MOBILE KEY DOES NOT USE THE CELLULAR SIGNAL, IT USES BLUETOOTH!!!!!!