Gravity SW update inbound...

9point81

Active Member

Verified Owner
Supporting Member
Joined
Mar 30, 2025
Messages
972
Reaction score
2,038
Cars
26 Gravity GT Black, EV9
IMG_0752.webp

I am just the messenger here. Hoping this update goes forward on those bugs and PLEASE no steps back...
 
where is this post from?
 
I like Emad Dlala, but given that some Gravity drive units have already failed, I'm not sure putting more on this plate -- especially as heaping a serving of trouble as the UI software -- is a good idea. It strikes me as more a symptom of an organization that is running short on the talent it needs than an organization that has found the path to a solution.

I do hope I'm wrong.
 
I like Emad Dlala, but given that some Gravity drive units have already failed, I'm not sure putting more on this plate -- especially as heaping a serving of trouble as the UI software -- is a good idea. It strikes me as more a symptom of an organization that is running short on the talent it needs than an organization that has found the path to a solution.

I do hope I'm wrong.
I hear you, but just doing what they were doing was clearly not working. And as others have said they couldn’t ignore things any longer, EE video or otherwise. Sometimes you need to decide who your best is, give them the ball and then figure out how you support/ backfill. I also suspect the drive unit failures are taking a different type of bandwidth: root cause analysis, five whys, etc, while software probably needs ruthless re-prioritization: these are the non-negotiable, shelve the other stuff. So as long as it’s something he’s ready to take on I’m ok with it. While hiring like hell in parallel, obviously- this isn’t scalable.
 
(Putting on my second guessing cap on for a brief moment)
I wonder, since they are programming in Android auto - maybe the software platform does not handle all the complexity of the Lucid platform? Maybe they need to develop software apart from Android to use if that is even possible. The reason I say this is the early days of JAVA (had to inject C/C++ to speed up functions) or scripting languanges that do a certain function really well but falls flat doing other tasks. Just thinking out loud. I am sure someone will be offended. Therefore, correcting myself - The general software randomness is due to just squashing the bugs within the current software stack. Most likely the later and non of the initial 'evil' thoughts. (just provoking thought...)
 
I hear you, but just doing what they were doing was clearly not working. And as others have said they couldn’t ignore things any longer, EE video or otherwise. Sometimes you need to decide who your best is, give them the ball and then figure out how you support/ backfill. I also suspect the drive unit failures are taking a different type of bandwidth: root cause analysis, five whys, etc, while software probably needs ruthless re-prioritization: these are the non-negotiable, shelve the other stuff. So as long as it’s something he’s ready to take on I’m ok with it. While hiring like hell in parallel, obviously- this isn’t scalable.

Eric Bach is gone with no replacement announced, and I believe his portfolio was moved to Dlala. The software head departed recently, and now that work is being picked up by Dlala.

Although I think Peter Rawlinson had a huge software blindspot, he was a major automotive engineering talent. Winterhoff is an electrical and electronics engineer by education, but his career was in management consulting on operational issues before joining Lucid, so I doubt he can fill the engineering hole left by Rawlinson and into which Bach stepped before his own departure.

So, basically, this means Dlala is covering the engineering ground of his original portfolio, plus what he picked up from Bach and thus indirectly from Rawlinson, and now plus what he's picking up on the software side.

It feels to me more like a formula for induced failure than for breakthrough success. I'm not sure Lucid understands the approach they're taking isn't scalable.
 
Let's wait and see how the next Gravity Software update performs.
It'll likely show up before Christmas day. I hope it brings good tidings.

Meanwhile, probably best to refrain from speculation and armchair-ceo-ing the crap out of this thread. That's probably too much to ask.
 
I'm not sure Lucid understands the approach they're taking isn't scalable.
If they don’t they have real issues at the board level. Which isn’t out of the question, but given Rawlinson‘s departure that seems less likely (though recognizing and constructively addressing an issue are completely unrelated in my experience, so maybe that’s wishful thinking).
Meanwhile, probably best to refrain from speculation and armchair-ceo-ing the crap out of this thread.
But it’s a beautiful Saturday morning, what the hell else we gotta do?

Looking forwards to the next update…
 
I believe the software update will be days away at most.

I’m sure there is a software team we never see or know the names of who are tasked very hard with fixing bugs and expanding features.
 
(Putting on my second guessing cap on for a brief moment)
I wonder, since they are programming in Android auto - maybe the software platform does not handle all the complexity of the Lucid platform? Maybe they need to develop software apart from Android to use if that is even possible. The reason I say this is the early days of JAVA (had to inject C/C++ to speed up functions) or scripting languanges that do a certain function really well but falls flat doing other tasks. Just thinking out loud. I am sure someone will be offended. Therefore, correcting myself - The general software randomness is due to just squashing the bugs within the current software stack. Most likely the later and non of the initial 'evil' thoughts. (just provoking thought...)
I’ve got a software engineering background and was kinda thinking about this too, my thought was wondering if they’re moving towards integration with uber/nuro for the autonomous stuff? Maybe trying to prepare entry points for other systems or starting to work with additional hardware? Integrations can be a bi-atch! Then again, there’s probably enough variances in hardware components to keep the devs on their toes as it is
 
Meanwhile, probably best to refrain from speculation and armchair-ceo-ing the crap out of this thread. That's probably too much to ask.

It's also a lot to ask people to pay $140,000 for cars delivered with the issues we've seen with our two Gravities.

I own a lot of Lucid stock. I'm going to noodle about what might be going on behind the scenes in this company because there's certainly no reason to own the stock based on its current financials and product launch stumbles.
 
...and internal org struggles

Yes.

It's interesting that people who know something about software have filled half this thread (and many others) with speculation about what's going on behind the scenes at Lucid on the software front, although their speculation is nothing but surmise and extrapolation based on what they think they can infer from what they see from the outside. But let someone who knows something about organization design and effectiveness speculate on that front, and they're being armchair CEOs who should keep their mouths shut.
 
I’ve got a software engineering background and was kinda thinking about this too, my thought was wondering if they’re moving towards integration with uber/nuro for the autonomous stuff? Maybe trying to prepare entry points for other systems or starting to work with additional hardware? Integrations can be a bi-atch! Then again, there’s probably enough variances in hardware components to keep the devs on their toes as it is
I was the liason between software engineering and marketing at Cisco. Yeah, it is challenging for sure! It a path every software development group must go though - rapid software development is never fast enough. Patience.
 
As a former CEO of a software company, I don't see any reason you can't have the same executive in charge of both hardware and software. He's leading teams, not doing it all himself, so that's how companies scale, and often times that will result in better communication and accountability in my opinion than having things siloed.
 
I was the liason between software engineering and marketing at Cisco. Yeah, it is challenging for sure! It a path every software development group must go though - rapid software development is never fast enough. Patience.

I'm sure you're right about this.

However, the issue with Lucid and the Gravity is less about how fast the software development was or can be. It is about putting a car on the market before all the work to produce reliable software performance was done.
 
The person from lisa had said the software is imminent so as soon as someone gets it, please post everything online so we can see all the details. Find a personal note after I did the key fob update change the battery and the latest software update. I have absolutely zero problems with my key fob the vehicle run flawlessly
 
But let someone who knows something about organization design and effectiveness speculate on that front
To be clear: this would be fine. If someone has actually had significant experience as a CEO or COO or similar of a major public company, especially if in tech or automotive, by all means - speculate! In fact, I'd encourage it.

Most people do not have that experience. There are more competent software engineers than there are past CEOs of large public companies, and so it is less likely a software engineer is talking out of their ass; but still entirely possible, to be clear.

So yes - if you have that experience - please, feel free to speculate and criticize and problem solve.

But if you don't, your feelings are perfectly valid; just less useful, and usefulness is (most of the time) a proxy for whether something is valuable, at least in this forum. :)
 
Back
Top