Software version 3.3.2

[BiruBoy11]

I’ve been speaking with the local service techs off and on for the last few weeks, sometimes due to scheduled service appointments (key fob) and sometimes due to something not operating correctly (key fob and minor sunshade blind issue). The following may or may not be helpful, depending on what you’ve already seen in these threads.

Many of you already know some version of this center console issue. The issues with the key cards and fobs seem to stem from the way the center console was installed in the Gravity. Apparently, the cup holders crushed/broke with varying severity one of the cables snaking to the charging/keycard reader pad during assembly, seemingly also impacting things outside of just the charge/reader pad. I would expect that Lucid has fixed this and all the cars produced in the last number of weeks will not have this problem. Everyone who had their Gravity delivered prior to the production fix (assuming it has been fixed) will have their consoles replaced.

The key fob fix that happened in conjunction with 3.3.2 has been hit and miss. My car bricked on me (after the overnight key fob-related firmware visit to the SC) in a supermarket parking lot due to no recognition of the fob or key card. Could get in the car but that’s it. Car would not go into drive. Had to walk home (fortunately less than a mile away) and leave the car in the parking lot overnight. Service techs met me in said parking lot first thing in the morning. They did a bunch of stuff but what seemed to fix everything was the following process: take battery out of fob, hold unlock button down, put battery back in, release button. It’s only been a week since then, but fob and key card have worked flawlessly, other than a momentary ‘key not detected’ warning sometimes when I enter the car.

The blacking out of the screens when first entering the car on occasion and waiting 30-60 seconds for them to come up is intentional and part of the 3.3.2 update, at least as I understand it from what the service techs told me. It is an intentional reboot to clear unnecessary warnings (rear wheel steering, headlights, etc) that had been popping up a lot. This reboot happens to me about once a day and is a little annoying. I assume this is a temporary fix that will be fully resolved at some point.

Hope this helps.

 

[WeighingGravity]

They did a bunch of stuff but what seemed to fix everything was the following process: take battery out of fob, hold unlock button down, put battery back in, release button. It’s only been a week since then, but fob and key card have worked flawlessly, other than a momentary ‘key not detected’ warning sometimes when I enter the car.

This seems like something out of an old RPG game like Zelda or something where you have to just guess at all kinds of different random arrangements of the rune stones until the Triforce is released from the magic cave. Why would anyone have even guessed to try this?

 

[electric]

I’ve been speaking with the local service techs off and on for the last few weeks, sometimes due to scheduled service appointments (key fob) and sometimes due to something not operating correctly (key fob and minor sunshade blind issue). The following may or may not be helpful, depending on what you’ve already seen in these threads.

Thank you for posting this, it helps a lot!
I only had my Gravity for 2 days and my delivery coincided with 3.3.2 release day, so I was thrown into the deep end without a chance to take a deep breath.
I freaked out at first as I never experienced a bricked car before, despite driving EVs for 15 years now, and this is my first truly expensive car (coming from Model Y, which was half the price of Gravity), so I guess I expected a bit more stable software after waiting for almost a year after placing the order, and seening multiple videos of Lucid CEO swearing that all issues will be sorted before delivering vehicles (I wonder why he really stepped down recently ).
However, after reading this forum and getting amazing help from fellow Gravity owners like you, I've learned important recovery procedures, set my expectations accordingly, and now I'm enjoying the car as much as I can, as it's truly a pleasure to drive and an amazing engineering achievement, despite software kinks which are a matter of time to resolve.

 

[socktucker]

The blacking out of the screens when first entering the car on occasion and waiting 30-60 seconds for them to come up is intentional and part of the 3.3.2 update, at least as I understand it from what the service techs told me.

no way is that a long term thing right?!?

 

[HC_79]

Have they said that it's ok to start using that feature again?

Home Assistant is a separate system I use to manage the opening and closing of the door. I turned the Gravity one off within days of using it as it was bad and since the email I haven't heard Lucid say the issue has been resolved.

 

[HC_79]

no way is that a long term thing right?!?

I doubt it but it's still concerning to say the least. That comes across as a "we don't know what the problem is or it's going to take an extremely long time to fix so just shove in constant restarts for the time being".

 

[electric]

I doubt it but it's still concerning to say the least. That comes across as a "we don't know what the problem is or it's going to take an extremely long time to fix so just shove in constant restarts for the time being".

We might be putting too much weight on words from a service center tech. In my experience guys at SCs are too far removed from engineering to know anything at a deep level.
I was in similar engineering position in my career where my software solutions were wildly misunderstood and twisted by folks in the field.
If this startup delay was intentional then it would be consistent for all users on all power up cycles, however, in my experience in the last 2 days these delays are totally random and unpredictable.
I just learned that Lucid did not develop the core software, they use underlying Android based core, which could explain many such issues. A matter of time before core owners step up the game or Lucid drops them and develops their own.

 

[Ron_Burgundy]

We might be putting too much weight on words from a service center tech. In my experience guys at SCs are too far removed from engineering to know anything at a deep level.
I was in similar engineering position in my career where my software solutions were wildly misunderstood and twisted by folks in the field.
If this startup delay was intentional then it would be consistent for all users on all power up cycles, however, in my experience in the last 2 days these delays are totally random and unpredictable.
I just learned that Lucid did not develop the core software, they use underlying Android based core, which could explain many such issues. A matter of time before core owners step up the game or Lucid drops them and develops their own.

FWIW, Rivian didn’t develop the core sw either and uses Android and, to be fair, has had less bugs in the 2.5 years I’ve owned our R1S.

I don’t think it’s an Android issue.

 

[HC_79]

I just learned that Lucid did not develop the core software, they use underlying Android based core, which could explain many such issues. A matter of time before core owners step up the game or Lucid drops them and develops their own.

Android Automotive has nothing to do with it. Many automakers are using this base OS and not having as many bugs that Lucid is experiencing. Given the software woes even with a base level OS provided I suspect it would be horrendous if Lucid went on to develop their own.

I do agree with what you were told about the rebooting as I've always suspected the car has been doing this randomly from day 1. I also wonder if it's why settings like the vibe lighting won't hold because the car is in a constant flux of rebooting and the settings just don't get permanently saved. I can count on 2 hands how many times I've gotten into the car and see Lucid written on the HUD telling me that something has gone wrong an it instigated a reboot on its own.

 

[Ron_Burgundy]

Okay. Black screens came back once today on right side and pilot screen. Lasted 51 seconds but did boot up without a reset and started to work. First time with 3.3.2.

 

[msaunders9430]

This reboot happens to me about once a day and is a little annoying. I assume this is a temporary fix that will be fully resolved at some point.

I'm also noticing the prolonged black screen or reboot only once a day; during first entry to car.

Happens whether key card or fob is used.

Occasional "Key Fob Not Detected" message. I ignore and car drives fine. Didn't happen until after 3.3.2 update Friday night.

Tech at service center said I might see the "Key Fob Not Detected" message after they did 3.3.1 update last Thursday. So it's possible the culprit was actually 3.3.1 update. Tech said Lucid was aware of the message and was working on resolving it. If 3.3.2 was the resolution, pretty sure they'll know another update is needed.

 

[archon810]

I had a very long call with an assistant service manager at San Jose today and communicated all the issues from

https://www.reddit.com/r/LUCID/comments/1npln36/my_first_impressions_after_2_days_with_the_lucid

to him in great detail. I've been adding many issues to the list and it now includes fob and black screen ones as well. They will be creating internal cases for each reported issue and following up on all of them, pulling in engineering where appropriate. I'm confident Lucid is at the very least receiving our feedback, and I'm optimistic that we will be getting many of them fixed soon. Not sure if they'll onboard me onto some trusted tester program and NDA at some point, but I hope they do. Hang in there, all!

 

[jrreno]

My buddy is borrowing mine this weekend to tow a 4000lb camper. Given we’ve had zero “you can’t drive” errors or whatever, I trust this car pretty well.

I’m hopeful more are like mine.

How does that play with the 110 pound limit on the hitch? (according to the manual page 115)

 

[RandomDesign]

How does that play with the 110 pound limit on the hitch? (according to the manual page 115)

First, if you see the 100 lb limit you have an old version of the manual - the newer one updates that to 119 lbs. https://lucidmotors.com/knowledge/vehicles/gravity/the-basics/lucid-gravity-essentials
Second, that's talking about a hitch mounted accessory like a bike rack. The towing capacity for a trailer is 6000 lbs.

 

[Bunnylebowski]

I had a very long call with an assistant service manager at San Jose today and communicated all the issues from

https://www.reddit.com/r/LUCID/comments/1npln36/my_first_impressions_after_2_days_with_the_lucid

to him in great detail. I've been adding many issues to the list and it now includes fob and black screen ones as well. They will be creating internal cases for each reported issue and following up on all of them, pulling in engineering where appropriate. I'm confident Lucid is at the very least receiving our feedback, and I'm optimistic that we will be getting many of them fixed soon. Not sure if they'll onboard me onto some trusted tester program and NDA at some point, but I hope they do. Hang in there, all!

They have very good committed talented responsive smart people working for them….which is really important because this whole black screen fob can’t drive car clusterfuck many owners are experiencing is really not ok at all. @WeighingGravity post about Zelda is spot on, or like the Nintendo cartridges where you’d have to blow on them and then force and hold them in the slot a certain way to get the game to load, and if you ever turned it off again nothing works.

 

[Bunnylebowski]

I’ve been speaking with the local service techs off and on for the last few weeks, sometimes due to scheduled service appointments (key fob) and sometimes due to something not operating correctly (key fob and minor sunshade blind issue). The following may or may not be helpful, depending on what you’ve already seen in these threads.

Many of you already know some version of this center console issue. The issues with the key cards and fobs seem to stem from the way the center console was installed in the Gravity. Apparently, the cup holders crushed/broke with varying severity one of the cables snaking to the charging/keycard reader pad during assembly, seemingly also impacting things outside of just the charge/reader pad. I would expect that Lucid has fixed this and all the cars produced in the last number of weeks will not have this problem. Everyone who had their Gravity delivered prior to the production fix (assuming it has been fixed) will have their consoles replaced.

The key fob fix that happened in conjunction with 3.3.2 has been hit and miss. My car bricked on me (after the overnight key fob-related firmware visit to the SC) in a supermarket parking lot due to no recognition of the fob or key card. Could get in the car but that’s it. Car would not go into drive. Had to walk home (fortunately less than a mile away) and leave the car in the parking lot overnight. Service techs met me in said parking lot first thing in the morning. They did a bunch of stuff but what seemed to fix everything was the following process: take battery out of fob, hold unlock button down, put battery back in, release button. It’s only been a week since then, but fob and key card have worked flawlessly, other than a momentary ‘key not detected’ warning sometimes when I enter the car.

The blacking out of the screens when first entering the car on occasion and waiting 30-60 seconds for them to come up is intentional and part of the 3.3.2 update, at least as I understand it from what the service techs told me. It is an intentional reboot to clear unnecessary warnings (rear wheel steering, headlights, etc) that had been popping up a lot. This reboot happens to me about once a day and is a little annoying. I assume this is a temporary fix that will be fully resolved at some point.

Hope this helps.

Lucid just told me the new way to get into the car and get it to drive if the screens are black and fob doesn’t work is to press up up down down left right left right AB select start on your original NES controller.

 

[allenmhc]

They have very good committed talented responsive smart people working for them….which is really important because this whole black screen fob can’t drive car clusterfuck many owners are experiencing is really not ok at all. @WeighingGravity post about Zelda is spot on, or like the Nintendo cartridges where you’d have to blow on them and then force and hold them in the slot a certain way to get the game to load, and if you ever turned it off again nothing works.

So I ran into the black screens again today picking up some last-minute pastries, and since I wasn't in a hurry, I waited for the entire system to eventually boot up.

I have a theory on the behaviors, given what I've experienced w/ both 3.3.1 and 3.3.2. There are at least 3 systems that boot in sequence:

1. The main drive systems, which you can tell by having the middle & left driver screens lit up. The stalks, wheel, etc. work and you can at least drive the car
2. The cameras, which I sometimes activate in a hurry by reversing and if they're not ready then the right + landscape screens show a "camera not available" error message, but if I go back to park then those screens black out, because…
3. The infotainment system, which also includes individual profiles, and that impacts mirror/steering wheel/seat positions

I noticed that if I wait until these systems eventually come back online, they'll do their thing and show the 360° camera and readjust the driver's seat to driving position (i.e., reversing easy entry/exit). It gives credence to another poster's hearsay from an SA that the temporary solution is to just reboot all the systems to reduce the number of erroneous notifications or to get itself into a better state before the vehicle drives.

If I had to guess, this is largely due to the car sleeping + waking up (or entering and exiting low-power modes of operation) and systems not waking up in a coherent state. This has plagued everything from game consoles to PCs to TVs, and a car is much more complicated.

 

[johnse]

How does that play with the 110 pound limit on the hitch? (according to the manual page 115)

Adding onto @RandomDesign 's excellent post:

Pages 118 and 119 list the towing ratings: 600 pounds tongue weight.

Note the maximum distance from the anchor pin hole of 7.5". Also note it prohibits weight-distribution hitches.

Page 116 lists the rear attachment capacity. At most 119 pounds at 24" center of gravity.

These are two distinct types of loads.

 

[Ron_Burgundy]

So I ran into the black screens again today picking up some last-minute pastries, and since I wasn't in a hurry, I waited for the entire system to eventually boot up.

I have a theory on the behaviors, given what I've experienced w/ both 3.3.1 and 3.3.2. There are at least 3 systems that boot in sequence:

1. The main drive systems, which you can tell by having the middle & left driver screens lit up. The stalks, wheel, etc. work and you can at least drive the car
2. The cameras, which I sometimes activate in a hurry by reversing and if they're not ready then the right + landscape screens show a "camera not available" error message, but if I go back to park then those screens black out, because…
3. The infotainment system, which also includes individual profiles, and that impacts mirror/steering wheel/seat positions

I noticed that if I wait until these systems eventually come back online, they'll do their thing and show the 360° camera and readjust the driver's seat to driving position (i.e., reversing easy entry/exit). It gives credence to another poster's hearsay from an SA that the temporary solution is to just reboot all the systems to reduce the number of erroneous notifications or to get itself into a better state before the vehicle drives.

If I had to guess, this is largely due to the car sleeping + waking up (or entering and exiting low-power modes of operation) and systems not waking up in a coherent state. This has plagued everything from game consoles to PCs to TVs, and a car is much more complicated.

When my two right screens don’t load, but the driving ones do, if I put car in reverse, I immediately get the camera views on the right cockpit and pilot screens. So those do load separately and quickly (to your point), but they’re visible. Once I put it on drive and go over my set speed, the screens go blank again…haven’t yet had the issue where drive screen loads but cameras can’t be viewed.

 

[hmp10]

Lucid just told me the new way to get into the car and get it to drive if the screens are black and fob doesn’t work is to press up up down down left right left right AB select start on your original NES controller.

Old fart and software neophyte that I am, I couldn't even tell if you were joking until I saw the reactions from other posters.