What's new
By:

New Bugs Since 3.5.1

socktucker said:
I wonder this too. From a purely business point of view I get it. There’s only a few thousand of them, they don’t sell well, how much effort do they put into them when the company is riding on the success of the Cosmos anyways.
Click to expand...

The Gravity software problems, coming on the heels of a rough first year of Air software problems, have dug a deep reputational hole for reliability from which the Cosmos has to climb. They have absolutely no room for anything like these missteps with a true mass-market product, and nothing I am seeing with the Gravity suggests they have a clue about how to avoid those missteps.

If the early reviews of the production Cosmos catch a whiff of anything smelling of the Gravity software issues, they will excoriate Lucid . . . and justly so.
 
mfdutra said:
100%. When everything works, it's the best SUV out there. I love it!

I have the same relationship with my airplane (Diamond DA62). When everything works, I love it! But boy, sometimes it tests your patience. I hear the same from boat owners.
Click to expand...
Nice plane!!!!
 
I spent a good bit of time today trying to figure out a way to reduce the aggravation of getting underway in our Gravities. I started by putting new batteries in both key fobs, although the batteries had just been in them a few weeks. Neither car responded any better to the fob than before.

When we went to the garage to go to dinner, the newer Gravity again was not responding to the fob, so I had to use the key card. That, of course, put the car into a guest profile, so I had to call up my profile and then punch in the PIN to get underway.

When we got to the restaurant the car failed to lock and power down. However, since we could see the car from our table I decided just to leave it unlocked so that I wouldn't have to screw around with trying to get it open again after dinner. When we got back in the car, this is what we saw on the screens:

IMG_2943.webp


We waited several minutes but the screens did not clear. So I tired the X/mic/brake reset. It did not work. So I called Lucid Customer Service. I told the IVR system we were having trouble starting the car, and that caused me to get directed to the Roadside Assistance line. I could not get back to the main menu, so I had to hang up and call back to start over. Meantime, nothing had changed on the screens. While I was on hold, I tried another reboot, this time holding down the buttons until my thumbs ached. I never did get the chime telling me to release, but when I let go the car finally rebooted.

At this point we had been in the goddamned car more than 10 minutes just trying to get underway.

On the way home we stopped at a cookie shop. Again, the car was still unlocked when we got back to it. This time the car was fully powered up, with the drive mode, suspension setting, and seat position still holding.

When we got home the car failed to lock. It would not respond to the key fob command to lock until I went into the house and came back out. It finally did respond to the lock command, but only after a 20-30 second delay.

I am coming to terms with the fact that Lucid is not going to do anything about this. Whether because they cannot or simply do not care to is immaterial to me at this point. I'm just tired of it all and now hate these cars as well as being unspeakably disappointed in Lucid Motors.
 
Seems you've tried everything to get the Gravity fob's to work. Have you tried turning passive lock/unlock off? Locking and unlocking the car manually (pressing the door handle to lock/unlock) may prove more reliable. Its a bit annoying and works for the Air. I'm unsure if the Gravity would function the same way.
 
Pragmatic said:
Seems you've tried everything to get the Gravity fob's to work. Have you tried turning passive lock/unlock off? Locking and unlocking the car manually (pressing the door handle to lock/unlock) may prove more reliable. Its a bit annoying and works for the Air. I'm unsure if the Gravity would function the same way.
Click to expand...

I tried turning off the auto feature. It still took the car 23 seconds to respond to a command from the fob. Try that in a south Florida rainstorm.

Remember that before and shortly after the 3.5.1 update, this car was having little if any problems with responding to the key fob. Those problems had been restricted mostly to our older Gravity (which is now having the same issues as the newer Gravity).

Our computer programmer friend who goes out to dinner with us a couple of times a week has witnessed almost all the problems at one time or another. He thinks the fact that new issues are cropping up since the 3.5.1 update has something to do with communication errors with the cloud and perhaps not something in the software coding. He asked me several questions about how Lucid uses the cloud that I could not answer. Any ideas from you digital heads here?
 
hmp10 said:
I spent a good bit of time today trying to figure out a way to reduce the aggravation of getting underway in our Gravities. I started by putting new batteries in both key fobs, although the batteries had just been in them a few weeks. Neither car responded any better to the fob than before.

When we went to the garage to go to dinner, the newer Gravity again was not responding to the fob, so I had to use the key card. That, of course, put the car into a guest profile, so I had to call up my profile and then punch in the PIN to get underway.

When we got to the restaurant the car failed to lock and power down. However, since we could see the car from our table I decided just to leave it unlocked so that I wouldn't have to screw around with trying to get it open again after dinner. When we got back in the car, this is what we saw on the screens:

View attachment 38677

We waited several minutes but the screens did not clear. So I tired the X/mic/brake reset. It did not work. So I called Lucid Customer Service. I told the IVR system we were having trouble starting the car, and that caused me to get directed to the Roadside Assistance line. I could not get back to the main menu, so I had to hang up and call back to start over. Meantime, nothing had changed on the screens. While I was on hold, I tried another reboot, this time holding down the buttons until my thumbs ached. I never did get the chime telling me to release, but when I let go the car finally rebooted.

At this point we had been in the goddamned car more than 10 minutes just trying to get underway.

On the way home we stopped at a cookie shop. Again, the car was still unlocked when we got back to it. This time the car was fully powered up, with the drive mode, suspension setting, and seat position still holding.

When we got home the car failed to lock. It would not respond to the key fob command to lock until I went into the house and came back out. It finally did respond to the lock command, but only after a 20-30 second delay.

I am coming to terms with the fact that Lucid is not going to do anything about this. Whether because they cannot or simply do not care to is immaterial to me at this point. I'm just tired of it all and now hate these cars as well as being unspeakably disappointed in Lucid Motors.
Click to expand...
What’s that radar system you have there?
 
FeelLicks said:
Some positive- Raining in Bay Area these days and the auto wipers seem to be finally working correctly and well!
Click to expand...
So my auto wipers sense “light” rain ok and work fine. However they don’t seem to be sufficiently speed variable (unlike every other car i have owned for the past 20+ years) . During a New England torrential downpour they just don’t seem to wipe anywhere near fast enough in auto mode. I have to manually flick up to max ( and reduce manually) using sequential pushes on button on the left hand stalk.
Electric has reported the same issue, Anyone else notice this?
(by the way the button works well and is much better than trying to reach for the clear view cockpit adjustments)
 
@hmp10 hypothetically speaking, if Lucid were to fix the fob issues in the next update, would that bring you back into the fold? Seems unlikely given their track record but I'm still curious.

Edit: Also, nice setup for your Uniden. I've got the R7 on my Air, so nowhere near as well integrated as the R9W, but a big fan of the product.
 
The_Don said:
@hmp10 hypothetically speaking, if Lucid were to fix the fob issues in the next update, would that bring you back into the fold? Seems unlikely given their track record but I'm still curious.
Click to expand...

I don't know. It might put me back on the fence.

We are still having other issues. The rear hatch of our newer Gravity is still malfunctioning even after the latch was replaced. We've long since quit using the frunk of our Air because it's been through four repairs (including hinge, latch, and piston replacements), one of which left us stranded and waiting for a tow truck. So I fear that's the path we're on with this Gravity hatch if we keep trying to use the rear cargo area.

And we still have problems with the Pilot Screen freezing and all the manual controls (A/C toggle switches, rotary volume knob, steering wheel touch pads) becoming inoperable. And with the car not going into gear. And with screens dithering or blacking out entirely in the middle of a drive.

So, yeah . . . I just don't know.
 
FeelLicks said:
hm can these interfere with fob signal possibly?
Click to expand...

I doubt it, as we've had prolonged periods when the fob was fairly reliable.

Given that the software seems to be driving the rear hatch malfunctions, VIBE lighting malfunctions, screen malfunctions, manual control malfunctions, I think it much more likely that the software is behind the fob malfunctions.
 
The_Don said:
Not an issue on my Air
Click to expand...

It's never been an issue on our Air, either. Although our Air does use a Radenso system whereas the Gravities have the Unidens.

(I didn't use Radenso in the Gravities, because we've had issues with the units both in our Air and in our Tesla. They spontaneously power down occasionally in the middle of a drive and have to be rebooted. The installer rechecked the wiring in both cars and installed all firmware and software updates, but the problem continued. The Tesla is long gone, but it still happens in the Air. At least we get a voice alert that the system is powering down, so we know it's happening, and we're not left unwittingly driving without radar detection.)
 
The_Don said:
Not an issue on my Air
Click to expand...

hmp10 said:
It's never been an issue on our Air, either. Although our Air does use a Radenso system whereas the Gravities have the Unidens.

(I didn't use Radenso in the Gravities, because we've had issues with the units both in our Air and in our Tesla. They spontaneously power down occasionally in the middle of a drive and have to be rebooted. The installer rechecked the wiring in both cars and installed all firmware and software updates, but the problem continued. The Tesla is long gone, but it still happens in the Air. At least we get a voice alert that the system is powering down, so we know it's happening, and we're not left unwittingly driving without radar detection.)
Click to expand...
Just thinking out loud - Wonder if its location on Gravity relative to wherever there may be some critical component maybe can still cause issues.

Is it easy possible to turn them off for a while on your Gravity? Nothing to lose now 😅
 
hmp10 said:
Any ideas from you digital heads here?
Click to expand...
Key fob RF commands shouldn't involve any internet communications, but those folks seem to be so challenged (to be polite) with software, that I wouldn't be surprised with anything.

The car maintains connectivity with AWS all the time. It has an OpenVPN tunnel and an MQTT channel. The variance you see with sending commands via the app is because of that. The cloud cannot reach out to the car, because it has no idea where the car is (network wise). So, when you send a command, you're actually just putting a command in a queue. The car is constantly trying to consume that queue. That is asynchronous in nature.
 
For those who are not following "The Long Goodbye Thread", we might now have an answer for why some owners are seeing an uptick in software problems since the 3.5.1 update.

Per Emad Dlala, the SVP of Engineering and Digital, Lucid went to a new platform architecture between the 3.4 series and the 3.5.1 update. This was necessary because of limitations of the old architecture, and they anticipated this might precipitate an increase in software errors until they could make corrections for the new platform. The software team is working 7 days a week to resolve some of these issues with the next update coming later this month, along with some new features. There will be a further update with additional fixes in the July timeframe. Lucid has also made some modifications that reduce the software processing load by about 30%, thus creating more headroom for multiple systems to run without hitting processing limits which is one of the causes of high rates of glitches in heavily-optioned cars. Finally, Lucid is introducing new quality control protocols that had been missing thus far in their software development.
 
hmp10 said:
For those who are not following "The Long Goodbye Thread", we might now have an answer for why some owners are seeing an uptick in software problems since the 3.5.1 update.

Per Emad Dlala, the SVP of Engineering and Digital, Lucid went to a new platform architecture between the 3.4 series and the 3.5.1 update. This was necessary because of limitations of the old architecture, and they anticipated this might precipitate an increase in software errors until they could make corrections for the new platform. The software team is working 7 days a week to resolve some of these issues with the next update coming later this month, along with some new features. There will be a further update with additional fixes in the July timeframe. Lucid has also made some modifications that reduce the software processing load by about 30%, thus creating more headroom for multiple systems to run without hitting processing limits which is one of the causes of high rates of glitches in heavily-optioned cars. Finally, Lucid is introducing new quality control protocols that had been missing thus far in their software development.
Click to expand...
If a fully spec'd car was already hitting CPU limits, before even half of their advertised features were deployed and activated, that is a massive failure in their development processes and hardware/software architecture decisions for the Gravity.

They'd better not make the same mistakes for Cosmos/Earth, or it will definitely be the final nail in Lucid's coffin.

For all the shortcomings of Tesla, they have absolutely set the consumer's expectations that the processing power and memory in day 1 cars should have sufficient headroom to handle years of upgrades and additional features.
 
You must log in or register to reply here.
Back
Top