Gravity Bugs / Issues

But that’s not what’s happening. The frunk is not randomly opening on folks. The issue some people are having is the frunk not opening the first time they ask it to. Nobody has reported it opening without their asking.
I think his point was merely that unexpected hood openings while driving are a known hazard with cars, and that's why there's normally a secondary manual latch to provide another layer of safety. Beyond what was posted, I don't know exactly what the regulations say, nor how Gravity's frunk design meets them.

Wasn't there a post here about a Lucid's hood opening and causing damage while on the back of a tow truck? I don't recall if that was an Air or a Gravity.
 
I'm hoping they also thought about bears. You'd think so, given all the bear logos. But if they missed that, I'll be screwed when I take delivery of my GGT.
yes, and not to mention deer where you & I live....seen more damage to vehicles by them than just about any animal save humans
 
But that’s not what’s happening. The frunk is not randomly opening on folks. The issue some people are having is the frunk not opening the first time they ask it to. Nobody has reported it opening without their asking.
I didn't say it was, I said I'm scarred it could be.

Lets think about this analytically:
1. Frunk actuation is controlled by software in a computer.
2. This code base is known to have random bugs which after months continue in a whack-a-mole fashion.
3. Looks like the latch code has at minimum some kind of timing that already is known to be suspect, perhaps a clobbered interrupt, whatever.
4. To cover such stuff NHTSA says a secondary latch is required outside the car to prevent activation by humans (and presumably any entity in the vehicle) while driving.

I don't know about you professional programmers but I can tell you in 40+ years of fairly intense hobby programming (DIY CNC, controllers, etc) I never let the computer control anything that could kill me without an escape route. It often isn't convenient or cool but a physical E-Stop switch, latch or barrier is required between my code and my life.
 
But that’s not what’s happening. The frunk is not randomly opening on folks. The issue some people are having is the frunk not opening the first time they ask it to. Nobody has reported it opening without their asking.
Yes. but I couldn't drive the car as it indicated the frunk was open and limited my speed to 12 MPH. It took over 15 minutes of constantly pressing on the hood and pressing buttons before it finally opened up and then closed and was OK. The wife was not happy sitting in the car for 15 minutes while I struggled with this as she had other things to do.
 
Wasn't there a post here about a Lucid's hood opening and causing damage while on the back of a tow truck? I don't recall if that was an Air or a Gravity.
That was because the tow driver pressed the fob button to open the frunk, in attempting to turn off the alarm. Also not an applicable situation, as as far as the car was aware, it was parked.
 
Yes. but I couldn't drive the car as it indicated the frunk was open and limited my speed to 12 MPH. It took over 15 minutes of constantly pressing on the hood and pressing buttons before it finally opened up and then closed and was OK. The wife was not happy sitting in the car for 15 minutes while I struggled with this as she had other things to do.
Oh for sure, I'm not suggesting it's not frustrating. I just don't think it's a safety issue; that's all.
 
Interesting as this only started happening to me in 3.3.2 and 3.3.5
I've seen delays with my frunk opening - Also, when pressing the close button (inside the frunk) nothing happens for the first few presses (V3.3.5)
 
I didn't say it was, I said I'm scarred it could be.

Lets think about this analytically:
1. Frunk actuation is controlled by software in a computer.
2. This code base is known to have random bugs which after months continue in a whack-a-mole fashion.
3. Looks like the latch code has at minimum some kind of timing that already is known to be suspect, perhaps a clobbered interrupt, whatever.
4. To cover such stuff NHTSA says a secondary latch is required outside the car to prevent activation by humans (and presumably any entity in the vehicle) while driving.

I don't know about you professional programmers but I can tell you in 40+ years of fairly intense hobby programming (DIY CNC, controllers, etc) I never let the computer control anything that could kill me without an escape route. It often isn't convenient or cool but a physical E-Stop switch, latch or barrier is required between my code and my life.
So what is the solution you are proposing to comply with the suggested recommendation of a secondary exterior latch? Stop production, retool factory for a different frunk assembly? It’s fine to have a safety concern but I think this is a solution in need of a problem. Lucid has all sorts of safety mechanisms designed to kick in with any failure. For example if the LIN bus fails which controls the wiper motors, it defaults to circuit open to the wipers and leaves them on, so that way if the bus fails and it’s raining you can still drive with wipers on. I’d say the second detent detected when the frunk doesn’t appropriately close, which happened in my air requiring two frunk replacements, is the very thing that prevents the frunk from opening while the vehicle is being driven. I just don’t understand what it is you’re requesting they do.
 
Back to bugs. I got 3.3.5 update and have both of my fobs get the firmware update. Upon getting back into the vehicle immediately after the fob being updated it loaded the guest profile instead of mine, so be aware that may happen, although it now recognizes my profile linked to that fob every time. A few hours later when getting into the car, guess what happened? I got a fob not detected error, shake to wake up fob. It went away, it did not stop the car from driving so it was just a false error but I thought the update was supposed to get rid of all that stuff. 🤷‍♂️. I guess it just makes it so you can always drive the car even if you get fob errors? I thought that’s what 3.3.2 was supposed to do.
 
...I really recommend that Lucid hire a software QE team. Also, perhaps give every software engineer they have a Gravity and not allow them to drive anything else until the bugs are resolved.
You'd be surprised how many people suggested this 2-3 years ago due to the state of the Air's software.
 
So we have about 1200 miles on our Gravity. Delivered 10/10. Software is at 3.3.5, the fob update scheduled but not done.
For the first time had to use my app to unlock the car. In the drivers seat fob not recognized , shaking had no effect. Got out of the car, popped the battery and pressed a button, reinsert battery, fob recognized, brake did not activate driver entrance sequence so I had to manually adjust steering wheel and seat. We parked and when we returned to the car 4 hours later it was back to “normal” operation.
 
Since our newest Gravity doesn't have the rear seat squeak of the first one I always keep the second-row seats run fully back to maximize legroom.

Several times now when I have opened the back doors to vacuum the carpet I have found the seats run forward 2-3 inches -- both seats even with each other. I have called friends who've ridden in the second row to see if they adjusted the seats, but they say they didn't.

I cannot find anything in the Settings that would suggest such a "feature", nor have I seen the seats moving on their own.

Is anyone else experiencing this?
 
Since our newest Gravity doesn't have the rear seat squeak of the first one I always keep the second-row seats run fully back to maximize legroom.

Several times now when I have opened the back doors to vacuum the carpet I have found the seats run forward 2-3 inches -- both seats even with each other. I have called friends who've ridden in the second row to see if they adjusted the seats, but they say they didn't.

I cannot find anything in the Settings that would suggest such a "feature", nor have I seen the seats moving on their own.

Is anyone else experiencing this?
I have not. I do not have a third row and the second is always all the way back. My daughter rides in the second row occasionally and has never mentioned it. I will ask her in the future and let you know if it happens.
 
Back to bugs. I got 3.3.5 update and have both of my fobs get the firmware update. Upon getting back into the vehicle immediately after the fob being updated it loaded the guest profile instead of mine, so be aware that may happen, although it now recognizes my profile linked to that fob every time. A few hours later when getting into the car, guess what happened? I got a fob not detected error, shake to wake up fob. It went away, it did not stop the car from driving so it was just a false error but I thought the update was supposed to get rid of all that stuff. . I guess it just makes it so you can always drive the car even if you get fob errors? I thought that’s what 3.3.2 was supposed to do.
Yeah, for this reason I’m in no rush to get my fob updated. I still haven’t seen a “fob not detected” message on 3.3.5 without the fob firmware and prefer to keep it that way.
 
but I thought the update was supposed to get rid of all that stuff.
Read the fine print in the 3.3.5 release notes, it "reduces instances of false alerts", not getting rid of them.
I'm convinced that current Lucid team is unable to fix these bugs, all they are doing is adding kludges to catch and bypass some of them.
They need to bring an experienced bug exterminator to the team before Gravity enters the hall of fame for bad vehicle software.
Those 2 dudes in the Savage Geese video need a demotion ASAP, stop all the unicorn nonsense and make the car work reliably.
 
brake did not activate driver entrance sequence so I had to manually adjust steering wheel and seat.
I experience faults in driver entrance sequence every other time I use the car. Most annoying is when it randomly stops restoring the seat position in the middle of doing it.
It drives me crazy as I feel that seat is not there, but almost there, so I open the seat screen on the pilot panel and see the stuck "progress circle of doom" where Restore button woud normally be.
However, I discovered a quick workaround for this issue, reach down and move the seat slightly with a physical button, which instantly breaks the progress circle and brings back Restore button, then I touch Restore button and seat/wheel return to normal position. No need to exit/enter the car again or do a soft reboot.
 
Anyone slowly losing the right click on their right touch pad?

Its now taking 5-7 click attempts to switch songs.

Before I had to click near the top right corner to get the right click to work. Now it just won't work anywhere.
 
Hey all — wondering if anyone else has run into this with their Gravity. Within a week of delivery the Clearview Cockpit screen started going completely black while driving. Generally starts with a “Headlight Error” warning, followed by screen flickering. The Pilot Panel has gone black a few times but generally works. When the Cockpit screen is out I can’t put the car in drive. The only fix was to get everyone out of the car and wait ~10 minutes for it to “sleep” and reset itself. Customer Service scheduled me for two weeks from now at a service center an hour away because the local one is “at capacity” (ominous). Anyone else dealing with this tech / screen issue?
 
Back
Top