Gravity Bugs / Issues

[Bunnylebowski]

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.

I got that error literally just now, happens half the time I charge at work. It’s a false alert, ignore it.

 

[Bunnylebowski]

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.

Sometimes ambition makes you aware of your own limitations….my favorite picture on the topic.

 

[borski]

Assuming you’re talking about fobs not being recognized for driving, it is not fully fixed yet. I just got let not detected just now. I’m on 3.3.5 with updated fob firmware.

Yes, you may get the message, but it shouldn’t block you from driving. Did it?

That message may still pop up due to the fob being asleep, but shaking the fob to wake it should let you drive.

If it doesn’t, I agree - not fixed yet. If it does, I’d call that fixed, as the “shake key to wake up” is known behavior (though I imagine eventually will happen much less often).

 

[borski]

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.

I’ll put it this way: you can build extremely buggy software on Linux.

That doesn’t make Linux crap.

 

[DeaneG]

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

In addition to Lucid, at least the following carmakers currently use AAOS:
Stellantis (Dodge, Jeep, Fiat, +11 others), BMW, MINI, Dacia, GM (Chevrolet, Buick, GMC), Rivian, Porsche, Lotus, Volvo, Polestar, Renault, Honda, Acura, Nissan/Infinity, Ford, Mitsubishi, Lynk & Co

AAOS is relatively new to every manufacturer except Volvo and Polestar. Both of them have recently shifted to a completely new hardware architecture, so there are first-year problems.

 

[WeighingGravity]

Finally - not a bug, but someone dinged the passenger side door of my Gravity inside one week of ownership, a period of time in which I have religiously parked as far away from other vehicles as possible. FFFFUUUUUUUU

jeepers, and just now i had a random soccer ball hit my hood from a random field far, far away from the car while picking my kid up from school. Someone must have booted the hell out of it - there's a really high fence around the fields, plus i was two rows of parking away from the fence, too. Fortunately, no dent, but definitely some ball residue to rub out and maybe some buffing necessary. WTH? I am going to park this thing in the garage and never take it out at this rate.

 

[WeighingGravity]

Yes, you may get the message, but it shouldn’t block you from driving. Did it?

That message may still pop up due to the fob being asleep, but shaking the fob to wake it should let you drive.

If it doesn’t, I agree - not fixed yet. If it does, I’d call that fixed, as the “shake key to wake up” is known behavior (though I imagine eventually will happen much less often).

Shake to wake has never once worked for me (including just this afternoon). I have to reset the fob, or use the key card. Fortunately, those have both worked for me, so I haven't been stranded.

 

[Bunnylebowski]

jeepers, and just now i had a random soccer ball hit my hood from a random field far, far away from the car while picking my kid up from school. Someone must have booted the hell out of it - there's a really high fence around the fields, plus i was two rows of parking away from the fence, too. Fortunately, no dent, but definitely some ball residue to rub out and maybe some buffing necessary. WTH? I am going to park this thing in the garage and never take it out at this rate.

You’ll just scrape your car on the side of your garage. I’m actually glad my Gravity doesn’t quite fit in my garage cuz otherwise I’d mess it up haha.

 

[Bunnylebowski]

Yes, you may get the message, but it shouldn’t block you from driving. Did it?

That message may still pop up due to the fob being asleep, but shaking the fob to wake it should let you drive.

If it doesn’t, I agree - not fixed yet. If it does, I’d call that fixed, as the “shake key to wake up” is known behavior (though I imagine eventually will happen much less often).

This is something I don’t understand actually. How is it that an unshaken fob can allow me to open the car but then I get an alert it cannot detect the fob inside the car unless I shake it?

 

[NovemberLima]

Many of you may have already figured this out, but as there are also quite a few comments relating to the way the accessory "widgets" that appear to the right of the speed in the cockpit panel (e.g. nav guidance, current song, etc.) when in the Home tab, I figured I would share my analysis and theory. From what I can tell, the pilot panel and cockpit panel are basically completely separate devices, like having two iPads on your desk, not like a single computer with two displays. You can run the nav app, and the music app on both, but they're completely different instances of the app. Clearly they are sharing some information because when things are working right you don't have to enter an address twice, but note that they do not appear to "launch" in the background if they haven't been selected, which results in the widgets not appearing consistently in the Home tab in the cockpit panel. In addition, the nav, music, and phone views displayed in the "Home" tab are NOT the same as the full apps.
For example, if you startup the car and the cockpit panel is in the home view, and the pilot panel is used to select nav and enter an address the map in the Home tab of the Cockpit panel does show the directions, however no details will appear next to the speedometer. If you select the nav tab in the cockpit panel, you see the "Gravity" loading screen and then the nav appears, and NOW if you switch back to Home you will get the directions... Music is the same. Hopefully in a future update they will auto launch all the apps (there's not that many!) on both "devices" at the same time so you don't have this weird scenario where they're out of sync.

 

[9point81]

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.

Constantly. It seemed to be fixed on the latest app update at first, but it went back offline except on wifi and very occasionally when out and about.

 

[borski]

This is something I don’t understand actually. How is it that an unshaken fob can allow me to open the car but then I get an alert it cannot detect the fob inside the car unless I shake it?

Two different services running on one device, talking to two different nodes on the car, for example. (I'm not exactly sure, I haven't pulled it apart yet)

 

[allenmhc]

This is something I don’t understand actually. How is it that an unshaken fob can allow me to open the car but then I get an alert it cannot detect the fob inside the car unless I shake it?

From the mobile tech, it sounds like what 3.3.5 did was turn on all the external antennas outside the car so it can better detect the fob for unlock. Apparently whatever's inside the car is much weaker/less reliable.

 

[allenmhc]

Many of you may have already figured this out, but as there are also quite a few comments relating to the way the accessory "widgets" that appear to the right of the speed in the cockpit panel (e.g. nav guidance, current song, etc.) when in the Home tab, I figured I would share my analysis and theory. From what I can tell, the pilot panel and cockpit panel are basically completely separate devices, like having two iPads on your desk, not like a single computer with two displays. You can run the nav app, and the music app on both, but they're completely different instances of the app. Clearly they are sharing some information because when things are working right you don't have to enter an address twice, but note that they do not appear to "launch" in the background if they haven't been selected, which results in the widgets not appearing consistently in the Home tab in the cockpit panel. In addition, the nav, music, and phone views displayed in the "Home" tab are NOT the same as the full apps.
For example, if you startup the car and the cockpit panel is in the home view, and the pilot panel is used to select nav and enter an address the map in the Home tab of the Cockpit panel does show the directions, however no details will appear next to the speedometer. If you select the nav tab in the cockpit panel, you see the "Gravity" loading screen and then the nav appears, and NOW if you switch back to Home you will get the directions... Music is the same. Hopefully in a future update they will auto launch all the apps (there's not that many!) on both "devices" at the same time so you don't have this weird scenario where they're out of sync.

It's somewhat reminiscent of the iOS widgets framework—the widgets can receive some of the data as the full apps themselves, but are limited by the OS on the frequency/timing of the updates to save battery (and to prevent apps from taking too many resources). Now, a phone has these restrictions in place due to the need to conserve battery power, it's somewhat silly to apply the same constraints to a car with a 127 kWh's worth of power.

 

[Ron_Burgundy]

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.

Me too re the warnings…

 

[Ron_Burgundy]

Shake to wake has never once worked for me (including just this afternoon). I have to reset the fob, or use the key card. Fortunately, those have both worked for me, so I haven't been stranded.

Agree. Shake to wake may have worked a couple times, but generally doesn’t do anything BUT the most recent key not detected errors just go away and only stopped me from starting car twice. Each time, key cards worked.

Anyway, the key has always been moving in my pocket for a while before car declared it asleep, so in addition to other challenges, my fob may have narcolepsy.

 

[Nunya]

Headlight error & Rear steering fault

Some of the nanny warnings get annoying quick.

What warnings, the false alarms you mention or others? Can you expound? I assume your headlight was working functionally.

 

[Ron_Burgundy]

Did other folks get the Lucid Gravity survey from Ipsos? Just got it in my email…

 

[EVCar]

Agree. Shake to wake may have worked a couple times, but generally doesn’t do anything BUT the most recent key not detected errors just go away and only stopped me from starting car twice. Each time, key cards worked.

Anyway, the key has always been moving in my pocket for a while before car declared it asleep, so in addition to other challenges, my fob may have narcolepsy.

Supposedly, my other EV uses a fob from the same manufacturer but we've not experienced what's described on the forum.
On a wishful note, with so many technological wizards here in the forum, if Lucid could harness their collective wealth of knowledge, there many not be any fob issue any more.

 

[jrreno]

Running 3.3.5, updated the fob using the app. Last night car did not recognize the fob at all. No lights, no handles presenting, nothing. Since I was showing a friend the car I used my phone to unlock the car. With him sitting in the drivers seat fob not detected came up solid but we weren’t driving it anyway. Later after they had gone it still did not repond to the fob. Popped the battery and replaced it and the car is back to normal operation.