Gravity Bugs / Issues

From Facebook user 'The Lucid Report' posted 12/9/2025:

*An Open Letter to Lucid Motors:
It’s Time for a Reliability Reset**
Lucid, this message comes from a place of commitment — and urgency.
You’ve built the most efficient, most elegant electric vehicles on the market. The Air remains a benchmark. The Gravity is poised to break open an entire segment. But one issue threatens to overshadow all of that innovation:
Software reliability — and the public perception surrounding it.
Before we address what Lucid must do, it’s important to show a critical truth:
Every premium automaker has gone through this.
Not “many.” Not “some.”
All of them.
• BMW iX had widespread software failures leading to blank screens, charging interruptions, and recalls for the high-voltage battery control unit. Owners saw total power shutdowns and “Vehicle Not in Park” errors that bricked the SUV.
• Mercedes EQS faced major recalls due to failing MBUX infotainment systems, emergency-call system failures, stalling risks, and even cases where the car automatically initiated the wrong displays. The software was so problematic Mercedes had to halt sales temporarily.
• Porsche Taycan suffered early 12-volt battery failures, sudden power-loss events, charging system bugs, and repeated recalls for software that caused the car to shut down unexpectedly. Porsche issued multiple OTA campaigns because the control software simply wasn’t ready.
These brands are giants. They had decades of experience, billions in capital, and enormous dealer networks. Yet they still stumbled.
This means Lucid is on the same turbulent path the premium incumbents already walked.
The key difference is how a company responds.
And right now, Lucid has a golden opportunity to respond better than any of them.
⸻
1. Issue a Transparent and Direct “Reliability Reset” Message
A clear, CEO-level announcement acknowledging:
• The past issues
• The fixes already deployed
• The roadmap to stability
• The commitment to long-term reliability
Tesla did this. Mercedes did this. Porsche did this.
Lucid should do it better — with plain English and real accountability.
Transparency is not a weakness, it’s a strength. Nick Twork, head of Lucid Communicatons recently acknowledged the issues but more needs to be done.
⸻
2. Deploy a Concentrated Wave of Stability-First OTA Updates
Forget flashy features. Owners need stability.
The next batch of OTAs should focus on:
• Drive-unit monitoring bugs
• Infotainment freezing
• Display blackouts
• Camera/sensor miscalibrations
• App connectivity bugs
• System reboots
• Navigation glitches
And you must publish detailed changelogs.
This alone rebuilds trust.
⸻
3. Add a Critical Feature: The In-Car Bug Report Button
This is vital.
A Bug Report button inside the UI that:
• Captures the last 1–2 minutes of logs
• Compresses a memory dump
• Encrypts it
• Uploads directly to Lucid engineering
• Automatically tags VIN + software version
With an on-screen message:
“Thank you — your report has been securely sent. We will deligently work on this issue and provide you with an update as soon as one is available”. The last thing people want to feel is that their issue is ignored.
Tesla’s early “voice bug report” was one of the smartest tools in their entire history.
Lucid can implement a more modern, more powerful version.
This transforms frustration into actionable data.
⸻
4. Expand Service Capacity Before It Damages the Brand
You cannot have luxury owners waiting weeks for appointments or hearing “we have 60+ cars ahead of you.”
A premium brand requires:
• More technicians
• More mobile-service vehicles
• Better parts availability
• Guaranteed loaners for safety issues
• Live service chat
• Clear service timelines
• Push notifications for repair status
This is what Porsche, BMW, and Mercedes did to restore customer confidence after their tech failures.
⸻
5. Launch the “Lucid Owner Software Feedback Network”
Invite 500–1500 real owners to test pre-release builds.
Offer perks like:
• Service priority
• Early access to features
• Exclusive invites to Lucid events
This converts customers into collaborators — and dramatically reduces post-release chaos.
Tesla’s early community proved this model works.
Rivian copied it.
Lucid should embrace it.
⸻
6. Release a Milestone Update: Lucid UX 4.0
This should not be incremental — it should be transformative.
Focus on:
• Faster UI
• Higher stability
• Navigation improvements
• Better driver-assist behavior
• Stronger Bluetooth/app connections
• Fewer reboots
• A more polished interface overall
Then market it confidently:
“Quality. Stability. Refinement.”
When BMW launched their post-fix OTA campaign for iX and i4, public sentiment flipped from “broken” to “they fixed it.”
Lucid can spark the same turnaround.
⸻
7. Put Updated Cars in Reviewers’ Hands
Send updated vehicles (running UX 4.0 and above) to:
• Doug DeMuro
• Marques Brownlee
• Edmunds
• Car & Driver
• Out of Spec
• Throttle House
• Engineering Explained
If reviewers who experienced problems return and say:
“Lucid fixed it — the car is phenomenal now,”
the PR battle is won instantly.
People believe owners and reviewers more than corporations.
⸻
8. Make the Gravity the Redemption Story
This has to be your “Porsche Taycan 2.0 moment.”
If Gravity launches smoothly — with stable software and clean OTA updates — it reframes the entire narrative:
“The Air had early issues, but Lucid learned from them and perfected the Gravity.”
Porsche pulled this off with later Taycan software updates.
BMW turned the corner with recent iX patches.
Mercedes fixed MBUX stability with updated hardware and new software builds.
Lucid can outperform all of them if Gravity is bulletproof.
⸻
9. Invite Independent Validation
Request formal evaluations from:
• JD Power
• Consumer Reports
• IIHS
• Euro NCAP
• Reliability analytics firms
Publish results openly — even if they include critiques.
Nothing builds confidence like third-party confirmation.
⸻
10. Host a “Lucid Software Day” for Investors
Show how the entire software pipeline has matured:
• New architecture
• Testing procedures
• Stability metrics
• Bug-fix velocity
• Real-world data from the Bug Report button
• Roadmap for continuous improvement
Investors don’t fear problems.
They fear silence.
Give them data — and they’ll give you confidence.
⸻
Conclusion: Lucid, This Is Your Turning Point
Every premium automaker has faced early software or quality disasters — BMW, Mercedes, Porsche, Audi, Ford, Tesla. What separates the winners from the failures is whether they choose to:
• Hide the problems,
or
• Attack them openly and fix them completely.
Lucid now stands at that crossroads.
Your engineering is world-class.
Your design language is a statement.
Your driving dynamics innovation is real.
But your software reliability has to catch up to your ambition.
The good news?
You’re closer than you think — and your customers want you to succeed.
“Compromise Nothing”
If you find these articles useful, please Like, Follow and Share The Lucid Report for more Lucid and related EV content.
Wow, this is good stuff (mostly). It's not whining, or bitter criticism, or overly emotional angry backlash... it's requesting honest dialog and proposing solutions. It's a well thought out path forward. Its visionary.
I'm super laid-back (unless you're going slow in the passing lane ahead of me!) and adapt to inconveniences easily with general optimistic hope that things will get better and be ok but this bug thread seriously has me wondering if I'm making a mistake ordering at this stage and causing me to contemplate retracting that order before the LT enters production and just hang on the sidelines to see what goes down in the next 8-10mo's with this company. How Lucid responds to all this may sway me either way as I'd love to own this beast that is Gravity but don't want to have to pay BofA extra to lease it (so I'd have an "out" if the company chokes). Waiting/watching for their response...
 
Interesting that your right pads light up.

Both of my pads work fine, but they've never lit up during a night time drive.
same here

in Kyle's review video he even complains how they aren't backlit at around 38:40

 
same here

in Kyle's review video he even complains how they aren't backlit at around 38:40

For me, I'm fine with not having back lit pads.
One less light distraction during night time driving.
Eyes should be on the road, not the steering wheel.

I kinda have the actions for the pads memorized.
I go by feel.
I lower the lighting for the Clearview Panel and turn the Pilot Panel off.
The headlights light up the road so much, that's where I keep my focus.
Especially during deer mating season.
 
I mentioned this elsewhere, but I just wish the bottom of the D Pad had a physical rim on it to help me distinguish between the "down" button of the D-Pad and the two buttons below. There is a divider between the two buttons, so I can usually nail the two of them OK, but I have to find that ridge and then slide up a bit for down, but not too far, or I've swiped the center of the D Pad.
 
1765471262503.webp

Wonder when the software update will come out…

Even if it came out, I’m actually afraid to update to it right away. I have a roadtrip planned for the end of December and I can’t afford to go into it blindly not knowing wha new issues will arise from the update.

At least with the current software version, I more or less have a sense of what bugs I expect to be greeted with whenever I return to the car.
 
View attachment 35001
Wonder when the software update will come out…

Even if it came out, I’m actually afraid to update to it right away. I have a roadtrip planned for the end of December and I can’t afford to go into it blindly not knowing wha new issues will arise from the update.

At least with the current software version, I more or less have a sense of what bugs I expect to be greeted with whenever I return to the car.
If you know how to deal with those current bugs such that they won't disrupt your trip more than you already know, I'd wait until after the trip to install any update.
 
I recall reading a few posts about the time between locking and unlocking the car and how it might affect drive mode capability/key fob detection.
The suggestion in those posts was that during short intervals (less than 10 minutes) between lock and unlock, the car is going to sleep, but isn't in "deep sleep".

I did a little test today with my key fob and drive mode capability/key fob detection using a lock/unlock interval as the variable.

The one time in my 4+ months of ownership that I had the key fob not detected message and the inability to go into drive mode was about a month into ownership; before 3.3.5 and 3.3.9 updates. For that one instance, I went back inside my gym, waited 10 minutes, returned, and problem solved.

Today I unlocked my Gravity with the key fob, sat in the seat, put my foot on the brake to activate seating/steering wheel adjustments, put car in drive and reverse modes, put the car in park, exited car, locked car, and went inside. I repeated this procedure with intervals of 2, 4, 7, 10 minutes of wait time before repeating. I even did 15 and 20 minutes just to see what would happen.

Observation:
  • With each unlock, while looking in from the outside, I would see the screens come on and while entering car to sit down, the right and center screens would go off for about 3-5 seconds. This is normal for me. In daily driving I usually use this time to get my sunglasses out of the center console and fasten my seat belt.
  • Success at every interval except 7 minutes. Key fob not detected message appeared. I tried again immediately and had drive/reverse mode capability. The one difference in my action at this interval was that I rushed to attempt drive/reverse mode instead of allowing the 3-5 seconds for the screens to come back on. During that brief moment, the key fob detection message appeared, followed immediately by the ability to enter drive/reverse mode.
  • There is a definite start/boot up process taking place. I'm fine with this. I liken it to computer startup/systems check.
 
Yes early EV’s had minimal SW. But people demand increasingly shorter cycles for improvements and enhancements. SW updates OTA are the only way to really do that easily. So the fundamental philosophy of a large suite of sensors, buttons, touch screen inputs, etc connected through a robust and redundant network makes total sense. As such we can expect some pretty significant growing pains and not much different than my two Tesla’s ago experiences. My Dream Edition is pretty quirky. As I write this I am rebooting as the proximity chime of death just started while I was going 25 mph down the street. What the heck? So I think the general design philosophy for modern high end EV’s makes sense. The tremendous success of Model Y underscores that. However, we should be expecting better from Lucid by now. The HW is fabulous, I just wish even a portion of the same care in engineering was applied to the SW readiness and robustness.
 
I haven't checked yet. However, I did test the feature a few days ago and it instructed me to insert a memory stick although I had done that when I first set it up. It was working at setup, but I've seen posts from others that also had the system quit after initial setup. Perhaps it has to do with its still being in beta release?
Any update on what Halo Secure captured during your accident, if anything? Does anyone know what features Halo is supposed to have when fully functional? Will it record people approaching the car, similar to Tesla Sentry?
 
Any update on what Halo Secure captured during your accident, if anything? Does anyone know what features Halo is supposed to have when fully functional? Will it record people approaching the car, similar to Tesla Sentry?
My Tesla Sentry mostly records butts walking next to my parked car, and sometimes the wall in front of it.
 
Any update on what Halo Secure captured during your accident, if anything? Does anyone know what features Halo is supposed to have when fully functional? Will it record people approaching the car, similar to Tesla Sentry?

Not yet. When I try to read the chip it says format not supported although there were a lot of files on the chip. I had a computer-programmer friend try to change the last three letters at the end (forgot what he called them) to see if that worked, but it didn't. I haven't yet tried to read the chip from our other Gravity, as it's no longer reading the chip I loaded in it some time ago.

My understanding was that the chip should automatically store the 30 seconds before and after certain events, of which this crash was one.
 
Not yet. When I try to read the chip it says format not supported although there were a lot of files on the chip. I had a computer-programmer friend try to change the last three letters at the end (forgot what he called them) to see if that worked, but it didn't. I haven't yet tried to read the chip from our other Gravity, as it's no longer reading the chip I loaded in it some time ago.

My understanding was that the chip should automatically store the 30 seconds before and after certain events, of which this crash was one.
That is unfortunate. Someone vandalized my driver’s window and my Halo did nothing. I love the driving dynamics of the Gravity, but this software is not what I expected for a $140,000 car. My brother’s $39,000 2022 Kia Telluride has better software.
 
Not yet. When I try to read the chip it says format not supported although there were a lot of files on the chip. I had a computer-programmer friend try to change the last three letters at the end (forgot what he called them) to see if that worked, but it didn't. I haven't yet tried to read the chip from our other Gravity, as it's no longer reading the chip I loaded in it some time ago.

My understanding was that the chip should automatically store the 30 seconds before and after certain events, of which this crash was one.
Send me the files, if you don’t mind. I can try to take a look.
 
That is unfortunate. Someone vandalized my driver’s window and my Halo did nothing. I love the driving dynamics of the Gravity, but this software is not what I expected for a $140,000 car. My brother’s $39,000 2022 Kia Telluride has better software.
Halo Secure is, specifically, in beta.
 
For me, I'm fine with not having back lit pads.
One less light distraction during night time driving.
Eyes should be on the road, not the steering wheel.

I kinda have the actions for the pads memorized.
I go by feel.
I lower the lighting for the Clearview Panel and turn the Pilot Panel off.
The headlights light up the road so much, that's where I keep my focus.
Especially during deer mating season.
Only thing about them that I have issue with is that there’s no tactile feedback when you’ve slid from the D-Pad to the lower buttons. There should be a small raised nub or line at the bottom of the D-Pad to distinguish the two button pads. They actually made them completely flush, which makes it even harder.
 
Back
Top