Gravity Bugs / Issues

[Bunnylebowski]

I had this issue and although I was told I was sent an "update", ultimately I was told it was just a reset and there is no guarantee that the issue won't happen again until they resolve the issue. The good news is that it's been two weeks and I haven't had that problem come back.

This is reassuring. Is there anyone in here who has had persistent keyfob/keycard/not being able to put car into drive issues AFTER the 3.2.1 update has been re-pushed? I’m not talking about getting your car delivered with 3.2.1 already on it, but I’m curious if anyone is having keycard/fob failure after 3.2.1 reinstall?

 

[DrZorro]

So, today for the first time after having the car for over a month with ZERO problems, I was bitten by the key not working bug.

Went to leave the house for work this morning and pushed the button on the back of the car to open the trunk to put my bag in there....and no response from the car. Waited a few seconds, still nothing. Pushed the button the keyfob and it opened.

Then I went to open the door. Pushed on the handle....nothing. Used the keyfob button to unlock without isssue. I then went to put it in Reverse. Got the dreaded "no key detected/shake the key" message. Tried that...didn't work. Did a quick steering wheel reboot....still didn't work. Pulled out the keycard from my wallet and swiped it on the center console location and thankfully that worked instantly.

Interestingly, when reflecting on the situation, I did notice after using the button on the key to manually open the door, the car did seem to be in a deeper state of "sleep" than usual. For instance, I saw the "(LUCID)" splash screen on the HUD which I usually don't see. I suspect that a lot (or all) of the key issues are actually all software related with no true hardware issue.

I have to admit I did have a bit of anxiety all day at work that my car might not work when it was quitting time...however, luckily I had no issues with the key when leaving work. I hope this was truly a one-off for me.

 

[bryway]

This is reassuring. Is there anyone in here who has had persistent keyfob/keycard/not being able to put car into drive issues AFTER the 3.2.1 update has been re-pushed? I’m not talking about getting your car delivered with 3.2.1 already on it, but I’m curious if anyone is having keycard/fob failure after 3.2.1 reinstall?

My reset (3.2.1 overwrite with 3.2.1 that fixed the fob issue) was just hours before I had to go to the airport. Car is in the airport parking lot right now, sleeping. Will know for sure whether the issue remains resolved after the car has had several days of deep sleep. I'm back Wednesday night. If I can't drive myself from the airport home I'm gonna be pissed.

 

[Bunnylebowski]

So, today for the first time after having the car for over a month with ZERO problems, I was bitten by the key not working bug.

Went to leave the house for work this morning and pushed the button on the back of the car to open the trunk to put my bag in there....and no response from the car. Waited a few seconds, still nothing. Pushed the button the keyfob and it opened.

Then I went to open the door. Pushed on the handle....nothing. Used the keyfob button to unlock without isssue. I then went to put it in Reverse. Got the dreaded "no key detected/shake the key" message. Tried that...didn't work. Did a quick steering wheel reboot....still didn't work. Pulled out the keycard from my wallet and swiped it on the center console location and thankfully that worked instantly.

Interestingly, when reflecting on the situation, I did notice after using the button on the key to manually open the door, the car did seem to be in a deeper state of "sleep" than usual. For instance, I saw the "(LUCID)" splash screen on the HUD which I usually don't see. I suspect that a lot (or all) of the key issues are actually all software related with no true hardware issue.

I have to admit I did have a bit of anxiety all day at work that my car might not work when it was quitting time...however, luckily I had no issues with the key when leaving work. I hope this was truly a one-off for me.

Was your car on software prior to 3.2.1 when you got it, and then you installed 3.2.1?

 

[Bunnylebowski]

My reset (3.2.1 overwrite with 3.2.1 that fixed the fob issue) was just hours before I had to go to the airport. Car is in the airport parking lot right now, sleeping. Will know for sure whether the issue remains resolved after the car has had several days of deep sleep. I'm back Wednesday night. If I can't drive myself from the airport home I'm gonna be pissed.

Good luck and yeah hopefully the 3.2.1 re-push fixed it for good, although I’m scratching my head as to why that would fix anything, aside from clearing out cobwebs that could just pile up again. But I also think it’s strange for CS to re-send software unless they have a strong suspicion that initial 3.2.1 installation was problematic.

 

[iThinkEV]

The email stated updates would be coming over the next couple of months. No set date was mentioned.

You are correct. I re-read it today. for some reason. I got July 31st stuck in my head from that email. weird.

-iThinkEV-

 

[iThinkEV]

That's super encouraging!

I'm a little envious. My GDE is parked with only 75 miles on the odo, and is still at a 78% SoC from the initial pre-delivery power-up I received at the delivery center. Like you, I took delivery last Thursday. The next morning in my own garage, I had that key fob issue (resolved with sw push overwriting existing 3.2.1) then I had to head to the airport for a business trip. Won't be back until Wednesday night and am hoping (praying) the key fob fix persists so I can actually drive it again. I've spent the last few days dreaming about the ride quality compared to various ride-shares and limos I've been in while on this business trip. Sigh.

that's worst part. away from the Gravity. I've been enjoying mine, so much that I haven't bring it into the shop to get it wrapped. I know my paint must be getting dinged left and right, but I don't care. I'm not sure I can part with it for 2 weeks. decisions, decisions.

-iThinkEV-

 

[iThinkEV]

Anybody have issues with the scheduled charging?

I noticed my car for the past few weeks, have been charged by the time the scheduled time (12am) starts. Then one day, I just noticed a charging started notification on my app, in the middle of the day. Car started charging on its own. When it was set to scheduled charging. Happened 3 times already. Not a big issue. But wondering if everybody else having a similar experience? Another software issue?

And another time, I noticed. Car is plugged in, scheduled charge set. I left jacket in car. When back (probably 2 or 3 hours later), opened door and grab jacked. The minute I closed the door, I can hear my wall charger clicked, and I see 'starting to charge' on the screen, and it started to charge. I unplug and plug back in, then it settled back into 'scheduled charging' state.

-iThinkEV-

 

[HC_79]

Anybody have issues with the scheduled charging?

I noticed my car for the past few weeks, have been charged by the time the scheduled time (12am) starts. Then one day, I just noticed a charging started notification on my app, in the middle of the day. Car started charging on its own. When it was set to scheduled charging. Happened 3 times already. Not a big issue. But wondering if everybody else having a similar experience? Another software issue?

And another time, I noticed. Car is plugged in, scheduled charge set. I left jacket in car. When back (probably 2 or 3 hours later), opened door and grab jacked. The minute I closed the door, I can hear my wall charger clicked, and I see 'starting to charge' on the screen, and it started to charge. I unplug and plug back in, then it settled back into 'scheduled charging' state.

-iThinkEV-

Haven’t had an issue with it. I’ve had to actually go into the app on multiple times to override it when I’ve needed to charge it outside the window. I’m using the LHCS.

 

[DrZorro]

Was your car on software prior to 3.2.1 when you got it, and then you installed 3.2.1?

My car came with 3.2.0....never had any issues on that version... and upgraded to 3.2.1 the day it was released and hadn't had any problems ever with the key until today. Luckily the fob buttons still continued to work and the credit card key allowed the car to start so it was a relatively minor incident compared to what others have experienced.

 

[Bunnylebowski]

My car came with 3.2.0....never had any issues on that version... and upgraded to 3.2.1 the day it was released and hadn't had any problems ever with the key until today. Luckily the fob buttons still continued to work and the credit card key allowed the car to start so it was a relatively minor incident compared to what others have experienced.

Yeah sounds like yours has worked nearly trouble free which is great, and I think that’s pretty common too, @borski @hydbob and @HC_79 have not seemed to have “Can’t drive the car with fob or keycard” problem. It’s obviously beyond my ability to figure out, but at least we’re learning more.

 

[jered]

Yeah sounds like yours has worked nearly trouble free which is great, and I think that’s pretty common too, @borski @hydbob and @HC_79 have not seemed to have “Can’t drive the car with fob or keycard” problem. It’s obviously beyond my ability to figure out, but at least we’re learning more.

Since I have absolutely no additional evidence or data, I'm going to continue to speculate it's a problem with the Marquardt MCU firmware getting wedged on a race condition and a hard reboot not re-initializing it. I have nothing to directly support that other than 30+ years of debugging complex systems.

 

[EVCar]

Yeah sounds like yours has worked nearly trouble free which is great, and I think that’s pretty common too, @borski @hydbob and @HC_79 have not seemed to have “Can’t drive the car with fob or keycard” problem. It’s obviously beyond my ability to figure out, but at least we’re learning more.

For my test drive, the car could not be shifted into Drive, with the fob in the center console. The SA just kept flipping, moving the key card and finally it worked. Took him maybe 10 attempts.
Everything else seemed ok. Didn't see the HUD reflection, driving East and West at 2 p.m.. No extraneous sound coming from the second row seats -- the SA was sitting there, though.

 

[Neilnaples]

Since I have absolutely no additional evidence or data, I'm going to continue to speculate it's a problem with the Marquardt MCU firmware getting wedged on a race condition and a hard reboot not re-initializing it. I have nothing to directly support that other than 30+ years of debugging complex systems.

This evening my car was in deep sleep…. It took several tries for the key card to work. I think you are largely correct with your ideas. Somewhat incompatible systems that when in deep sleep seem to get confused. I was able to get the car to respond after multiple tries however I worry when I leave the car at an airport valet that the valet will struggle to get the car to respond. Last week the valet was successful - next week I go to Brazil - hopefully it responds when I return.
I have also seen various random errors and of course the constant charging errors for the wireless phone charging. I hope the next software update is more significant. 3.2.1 really didn’t make that much difference to me - I’m more concerned with key access and the random error messages. Let’s hope lucid gets a new update out soon. By the end of next week will have 1000 miles on the GDE. Not a big milestone but progress….