Gravity Bugs / Issues

[HC_79]

It weird becuase my 2023 Model 3, no problems. I also have a 2023 Model Y Performance and it had a myriad of problems. To be fair, my Lucid has had more issues in 60 days than my Model Y has had in 2 years, but the Model Y still had crashes ocassionally and just random stuff like the spoiler falling off.

It seems to be luck of the draw with all the models but agree that the Gravity probably takes first prize in how many times it needs a reboot. We all know Lucid loves a trophy for being number one at everything but I think they missed the memo that said "We don't want the gold trophy for most bugs introduced into a production vehicle"

To be fair, 3.3.5 and 3.3.8 seem to have started to stabilize things a lot (at least for me). I haven't seen a "key fob not detected" message since installing 3.3.5 and I think in the past 2 weeks I've seen one random "AR HUD" false error message show up, that's all! no more USB charging messages etc. Even the vibe lighting seems to be holding its preference 90% of the time. The only thing I'm really noticing on 3.3.8 is Halo Secure seems messed up, doesn't work 90% of the time and removing and re-inserting the USB doesn't solve anything, rebooting doesn't seem to fix it nor does the eject or format USB work in the menu. I also updated my fob when it was available to do so in the Mobile App.

 

[Ron_Burgundy]

It seems to be luck of the draw with all the models but agree that the Gravity probably takes first prize in how many times it needs a reboot. We all know Lucid loves a trophy for being number one at everything but I think they missed the memo that said "We don't want the gold trophy for most bugs introduced into a production vehicle"

To be fair, 3.3.5 and 3.3.8 seem to have started to stabilize things a lot (at least for me). I haven't seen a "key fob not detected" message since installing 3.3.5 and I think in the past 2 weeks I've seen one random "AR HUD" false error message show up, that's all! no more USB charging messages etc. Even the vibe lighting seems to be holding its preference 90% of the time. The only thing I'm really noticing on 3.3.8 is Halo Secure seems messed up, doesn't work 90% of the time and removing and re-inserting the USB doesn't solve anything, rebooting doesn't seem to fix it nor does the eject or format USB work in the menu. I also updated my fob when it was available to do so in the Mobile App.

I get headlight errors daily now on 3.3.5 as well as the sensor blocked errors. Fob not detected has come up more frequently recently, but it’s been an annoyance, not stopped me from driving.

So yes, all in all, huge improvements, especially with fob, but still whack stuff happening.

My vibe light performance is opposite of @HC_79 and car drivers and reverts towards to white/zen 95% of the time upon starting. Now, I could care less if they ever fix that bug. But the random errors, especially fob not detected, need to be killed. There has been progress…

 

[HC_79]

I'm starting to think that engineers on the forum are full of crap, pardon my French.
Just saw a review of Polestar 3 with bunch of the same issues, presumably also based on AA.
Even though I have no hands on experience with AA, but being a lifelong hardware/software engineer myself, what I experience in Gravity and loaner Air and hear about Rivian and now also Polestar, leads me to believe the issues are deep down in the core OS, not the surface level UI/UX programming.
To be clear, when I say "deep down in the core OS", it might be what we are commonly refer to as drivers in the PC world, where responsibility is fuzzy between the OS maker and the hardware maker, but it doesn't make customers feel any better when involved parties blame each other. This is where vertical integration like in Apple and Tesla are best, only one party to blame and they know it.

Google provides the base OS and probably lays out the foundation of how it should be used as best practice etc. The problem is, they don't really know what each automaker is going to do with it nor probably care. As you point out, every car has different hardware and it's probably on the automaker to test, validate and make sure it plays nice with Android Automotive. I haven't studied AAOS enough to know how it deals with all the variants of different hardware an automaker can use but not overly confident Google goes that deep themselves making sure everything everyone chooses works.

Lucid has more vertical integration going on than most other automakers period but on the software side they chose AAOS and while it's proved troublesome it was probably a smart choice. I don't think Lucid has the team in place nor the experience to make its own software stack for its cars. If they're struggling this much with AAOS you could only imagine what hand we would have been dealt if they built the software themselves.

 

[BSheppard]

I have been following the bugs thread since I took ownership of my Gravity about three weeks ago... My fob shut down when trying to update from the app and required a trip to the SC to resolve, the most annoying. I have had experiences with slow wake up, the occasional black screen, and numerous "error messages." However this thread left me with the impression that these were just software issues. I can't reconcile the variation of the users present in the thread with my own experience; it does lead me to sympathize with the engineers that are looking for the solution(s)! I still feel that the vehicle and the decision to be an earlier adopter was the right one. On a road trip to wine country this weekend Dream Drive was a big hit. (Would recommend the 2022 John Sebastiano Vineyard Pinot Noir & Syrah from Peake Ranch) Cheers!

 

[HC_79]

My vibe light performance is opposite of @HC_79 and car drivers and reverts towards to white/zen 95% of the time upon starting. Now, I could care less if they ever fix that bug. But the random errors, especially fob not detected, need to be killed. There has been progress…

How much are you messing around with triggering things remotely in the mobile app? The few times I've seen the lighting go back to Zen seems to have been related to when I've triggered something from the app (unlock, climate, etc.). It might be coincidence but something I thought was interesting and to pay closer attention to.

Oh, I still get the black screens on 3.3.8 but they're much quicker to disappear and don't show up all the time.

 

[Ron_Burgundy]

How much are you messing around with triggering things remotely in the mobile app? The few times I've seen the lighting go back to Zen seems to have been related to when I've triggered something from the app (unlock, climate, etc.). It might be coincidence but something I thought was interesting and to pay closer attention to.

Oh, I still get the black screens on 3.3.8 but they're much quicker to disappear and don't show up all the time.

I use the app maybe 30% of time. But interesting point and I will watch for it.

I haven’t had huge issues with black screens and 3.3.5. That is, until I just typed that. Now I will have issues….

 

[Pragmatic]

I'm starting to think that engineers on the forum are full of crap, pardon my French.
Just saw a review of Polestar 3 with bunch of the same issues, presumably also based on AA.
Even though I have no hands on experience with AA, but being a lifelong hardware/software engineer myself, what I experience in Gravity and loaner Air and hear about Rivian and now also Polestar, leads me to believe the issues are deep down in the core OS, not the surface level UI/UX programming.
To be clear, when I say "deep down in the core OS", it might be what we are commonly refer to as drivers in the PC world, where responsibility is fuzzy between the OS maker and the hardware maker, but it doesn't make customers feel any better when involved parties blame each other. This is where vertical integration like in Apple and Tesla are best, only one party to blame and they know it.

Does anyone know if GM has similar issues with their implementation of the Android based operating system?

 

[BobFM]

I did get the black screens yesterday, though, I was able to drive home with no issues. Upon getting home, did the soft reboot and everything popped back up. No issues since (knock on wood). That said, this is part of the reason why I'll be driving the Gravity until that type of thing is completely squashed, as my wife is not likely to want to deal with it. Based on my experience with the Air, it'll get fixed, just a matter of when...

 

[socktucker]

It seems to be luck of the draw with all the models but agree that the Gravity probably takes first prize in how many times it needs a reboot. We all know Lucid loves a trophy for being number one at everything but I think they missed the memo that said "We don't want the gold trophy for most bugs introduced into a production vehicle"

To be fair, 3.3.5 and 3.3.8 seem to have started to stabilize things a lot (at least for me). I haven't seen a "key fob not detected" message since installing 3.3.5 and I think in the past 2 weeks I've seen one random "AR HUD" false error message show up, that's all! no more USB charging messages etc. Even the vibe lighting seems to be holding its preference 90% of the time. The only thing I'm really noticing on 3.3.8 is Halo Secure seems messed up, doesn't work 90% of the time and removing and re-inserting the USB doesn't solve anything, rebooting doesn't seem to fix it nor does the eject or format USB work in the menu. I also updated my fob when it was available to do so in the Mobile App.

.9 has only had one issue on my Air, and it might have been CarPlay really. I still don't know why the phone key works the way it does, but, its bad and I don't expect them to change it.
The preconditioning seats and wheel still don't work but after 4 years it probably wont, or I don't understand how it is supposed to work.
Thing drives amazing though, I definately haven't had any issues with drive units or being completely locked out. Definately getting better. The amount of Gravity issues is unacceptable thought, but if I had to guess they were trying to get them out the door so people could still get their 7500 credit...which is arguably what most people would have wanted.

 

[mickey6]

not sure if this has been mentioned, but 40-50% of the time, pressing or selecting the homelink door does nothing (door does not open/close). I have to press the right garage from the menu several times for it to make it work.

 

[WeighingGravity]

I revert to Zen, I think, close to 100% of the time. I almost never use the app. And usually the strip of lights on the front dash don’t light up. Not sure if that’s intentional so as not to create a distraction when driving?

Also getting “sensor blocked” and “high beam assist unavailable” almost every time I use the car.

 

[jrreno]

I have had a 2018 Tesla S 100D and still have my Rivian R1T Launch Edition, actually one of the first 2500 off of the assembly line. Both these vehicles are "software defined" and I never had to reboot my Tesla and only have rebooted my Rivian once in the first week of ownership. The Lucid Gravity's issues are an order of magnitude greater than anything I've experienced with my software defined vehicles.

My experience with our 2018 Tesla S was different than yours. I rebooted it about once a month. We had FSD and often streamed Slacker both of which seemd to require reboots over time.

 

[jrreno]

Tesla was able to pull logs remotely which came in handy when we had issues whille traveling.
Does Lucid have to physically connect to scan the vehicle logs?

 

[Bunnylebowski]

Tesla was able to pull logs remotely which came in handy when we had issues whille traveling.
Does Lucid have to physically connect to scan the vehicle logs?

YES, that was how they found my HV battery needed replaced on my Air at 18k miles cuz remote diagnostics detected a fault in a single cell. Lucid’s remote abilities are super advanced, they can even do a lot to control the car remotely as long as it’s not totally bricked, like they can do a remote reset, etc.

 

[Bunnylebowski]

You can tell service “I had X fault at this time and date” and they can remotely pull the logs.

 

[tomclaussen]

Ran into the dreaded Vehicle offline error on the Lucid app today. Oddly enough it works fine when vehicle is connected via WiFi. Anyone else see that behavior?

I'm wondering if it worth categorizing some of these re-occurring bugs by when the car was built? Say pre and post September. Many of these errors can be attributed to either wiring issues or maybe even just noise/interference on the ethernet/CAN bus. Case in point was the center console pinched wiring.

 

[PGHGravity]

Ran into the dreaded Vehicle offline error on the Lucid app today. Oddly enough it works fine when vehicle is connected via WiFi. Anyone else see that behavior?

I'm wondering if it worth categorizing some of these re-occurring bugs by when the car was built? Say pre and post September. Many of these errors can be attributed to either wiring issues or maybe even just noise/interference on the ethernet/CAN bus. Case in point was the center console pinched wiring.

I hadn’t seen a single Vehicle Offline error until after getting my car back from the SC (which included the 3.3.5 update), and now I feel like it’s offline at least half the time it’s not on WiFi.

 

[Bunnylebowski]

I hadn’t seen a single Vehicle Offline error until after getting my car back from the SC (which included the 3.3.5 update), and now I feel like it’s offline at least half the time it’s not on WiFi.

I’ve not gotten a single Vehicle Offline error for Gravity, ever, and my car wakes up from the app in less than 5 seconds, so faster than my wife’s Volvo. I do get dream drive sensors blocked and rear steering and headlight alerts every 2-3 days though, which all seem to be false alerts.

 

[electric]

Does anyone know if GM has similar issues with their implementation of the Android based operating system?

I own 2 Chevy Bolt EVs, 2018 and 2023 models. Both have been rock solid since day one, never needed an OTA update.
UI on these is so intuitive, simple, effective, includes CarPlay, sometimes I forget it's all software, it just feels 100% solid and never fails to work.
I wish I could transplant Chevy Bolt infotainment into my Gravity, you would never see me again on this forum, as I've never been on Chevy Owners forum.

 

[ClearlyLucid]

Headlight error & Rear steering fault

Took my first trip today from Atlanta to Orlando. Made one Tesla charger stop. Dream Drive Pro was great. Some of the nanny warnings get annoying quick. I got the headlight error-call service after the charging stop. And my rear steering was inoperative after the charging stop. It told me to contact service. Anyone had the later? I did a soft reboot once I got to Orlando and the warning went away… for now.