2.0.48

I will be watching what others say about this update because I do not seem to have any real issues with .47. I guess there is no android auto update in .48. That will get me interested. My car did not yet get the update anyway.
There will never be an auto update. Updates lock the vehicle and any occupants inside (or outside), so they are always triggered manually, for safety reasons, whether from the phone or the car.

Update once you receive it. If you fall too far behind, it will not be easy to catch up.

It is tested both internally and by a small list of “early” receivers, from what I understand.

Doesn’t mean they’re “bugless,” but as you’ll need to update to the “buggy” version before the fixed version anyway, and the future updates don’t arrive instantly, just install them when you get them.
 
After the update this morning, I once again lost all sound. A quick keycard reset worked just fine to get it back up and running.

Side note: It was the first time I actually did the reset with the turn signal. I noticed after about ten seconds, when the main signals stop blinking, the lights on the mirrors blink rapidly a few extra times, as if to "confirm" the reset is complete. Nice touch.

Really hope they address many of these entertainment-system-related issues soon. The only real issues I've had so far have all been related to various forms of sound dropping out.
 
So, after the update, car won't wake when the Lucid app is first loaded/used, car won't unlock until I'm a foot away using mobile key, and couldn't get surround view when in reverse. All new issues for me. Will try the usual resets and see what happens.
 
So, after the update, car won't wake when the Lucid app is first loaded/used, car won't unlock until I'm a foot away using mobile key, and couldn't get surround view when in reverse. All new issues for me. Will try the usual resets and see what happens.
I generally recommend a reset after every update. Please let us know if that doesn’t fix it.
 
I updated with no issues and driving with headlights on I don't seem to detect anything different.
 
I have not received 2.0.48 update on my app or car yet. I will wait until end of the week to see if I receive it. Also what is Bobby reset?
Bobby Reset: tap your avatar on the right cockpit panel. Log into guest profile. Wait for it to load. Tap again and load your profile.

Fixes some profile and entertainment related glitches.
 
Bobby Reset: tap your avatar on the right cockpit panel. Log into guest profile. Wait for it to load. Tap again and load your profile.

Fixes some profile and entertainment related glitches.
Thanks
 
I generally recommend a reset after every update. Please let us know if that doesn’t fix it.
Turn signal and valet card resets didn't correct the waking or unlocking issue (I haven't tried the camera yet). I deleted and reloaded the Lucid app and that also didn't work. Next step is notifying Customer Care.
 
Turn signal and valet card resets didn't correct the waking or unlocking issue (I haven't tried the camera yet). I deleted and reloaded the Lucid app and that also didn't work. Next step is notifying Customer Care.
The app has nothing to do with unlocking. It is just the way you set it up. My suggestion would be to go into the app and delete your mobile key. Then, set up a new one.
 
I downloaded 2.0.48 this afternoon, and we took the car to dinner tonight with a couple of stops on the way home. Only once (leaving the garage) did the backup and birds-eye-view displays both work. We got an array of malfunctions on the other stops: birds-eye working but backup display not; both not working; backup screen would be just black; backup screen would show an "Unavailable" message; front camera display not working as we returned to garage, but birds-eye view working but not showing distance to object in front of car. The malfunctions seemed completely random.

Same old, same old. Fix one bug and introduce another. Really . . . what's the point?

2.0.33-35 were the sweet spot for our car in which every feature then available seemed to work reliably. Everything before and since has been a mess of one kind or another.
 
2.0.33-35 were the sweet spot for our car in which every feature then available seemed to work reliably. Everything before and since has been a mess of one kind or another.
I agree
 
Agree with others I updated, and now on 0.48 my cameras aren't working. No reset or maneuver brought them back...

I called into customer care and they said this is an issue they're aware of.
I asked that if they could fix this and get back to getting Android auto out.

It's amusing how pretty much everyone is consistent on the carplay/android interest for media and entertainment being essentially at the top of "needs"
 
Agree with others I updated, and now on 0.48 my cameras aren't working. No reset or maneuver brought them back...

I called into customer care and they said this is an issue they're aware of.
I asked that if they could fix this and get back to getting Android auto out.

It's amusing how pretty much everyone is consistent on the carplay/android interest for media and entertainment being essentially at the top of "needs"
Can't disagree.
My cameras work fine; just checked. It must be tough for Lucid and try to chase down bugs that are only in certain vehicles. I've been in app development for 13 years and it's worlds easier to track down a bug that shows up every single time on every single device.
 
The app has nothing to do with unlocking. It is just the way you set it up. My suggestion would be to go into the app and delete your mobile key. Then, set up a new one.
Not understanding your comment about the app having nothing to do with unlocking. I frequently use the app to unlock the car, just as I do to turn on the cabin heat before getting in. In any event, I reached the same conclusion about the mobile key after I couldn't get into the car using my phone. I checked my phone and saw that the mobile key bluetooth wasn't connected even though the car's "regular" bluetooth was, so deleted and reinstalled the mobile key, which reestablished its bluetooth connection. Unfortunately, that did not fix the wake issue, so I still cannot unlock the car using the app nor can I do remote climate control.
 
Not understanding your comment about the app having nothing to do with unlocking. I frequently use the app to unlock the car, just as I do to turn on the cabin heat before getting in. In any event, I reached the same conclusion about the mobile key after I couldn't get into the car using my phone. I checked my phone and saw that the mobile key bluetooth wasn't connected even though the car's "regular" bluetooth was, so deleted and reinstalled the mobile key, which reestablished its bluetooth connection. Unfortunately, that did not fix the wake issue, so I still cannot unlock the car using the app nor can I do remote climate control.
There's a difference between unlocking the car via the app and unlocking it via Bluetooth. Since Bluetooth is a connection established in a short distance between two devices, it does not depend on any sort of cellular or Wi-Fi signal. This is why the mobile key works even if your phone is not connected to the Internet.

The app, on the other hand, does depend on such a connection. If you are in an area of weak connection, it may not work as well, if it all. Is your mobile key working just fine, i.e., you leave your phone in your pocket and the car unlocks when you get close? If that is working, why even use the app to unlock or lock the car at all?
 
Last edited by a moderator:
Back
Top