3.3.9 Post update

[hmp10]

We drove our other Gravity tonight for the first time since we downloaded 3.3.9 to it day before yesterday. Just as with the first Gravity after the download, we had issues with music streaming. They were a little different in details from the issues with the first Gravity, and the workaround (discovered, as usual, through trial and error) also turned out to be different. And with this one as well, we also got a "key not detected" message after the download.

So we're 0-for-2 in terms of 3.3.9 fixing anything we noticed . . . and 2-for-2 in terms of the update introducing new software errors. As near as I can tell, we would have been better off by not downloading the update.

 

[broccoli]

Hi. GGT owner here on 3.3.9. I appreciate the wealth of useful information provided by this community and for mods keeping fair thoughtful discussions alive.

Thankfully, I have only minor issues, primarily software, and overall I'm satisfied.

Here are some bugs I have encountered since the latest software upgrade:
- left turn blind spot camera got stuck while driving on the highway. Unable to turn off using blinkers, drive to park gear shift after standstill, etc. The right blind spot camera would not show up using the right turn signal tok. Only fixed after a hard reset. First time bug.
- on front A/C only, the physical button up/down temperature did not match the current car temperature. First time bug.
- nonstop chime after getting into the car. No alerts or obvious way to turn off, hard reset required. Happened one time in an earlier software version, so this is a continued bug.
- I haven't seen reported much by others, but my pilot/top screen car location during nav gets stuck every other day, requiring a swipe up and down to restore live car location while moving. I have requested lucid service to review in an upcoming appointment. This is a continued bug.

 

[borski]

At the rate the fob munches on the battery, 3.072V won't last you long. I use Panasonic batteries I got from Amazon years ago, and they're at 3.3+V.

If 2.9V is indeed confirmed low by the new update (and I believe it, since 2.9V is what I had when my fob decided to die and stop working one day recently), then we will be replacing fob batteries every few weeks until phone as key is live.

We haven’t replaced our fob batteries since we got the vehicles and both work fine

 

[borski]

I see @borski has you on probation too huh welcome to the club

I have no idea what you’re talking about. Neither of you are currently moderated lol

(or if you are, it wasn’t me )

 

[socktucker]

I have no idea what you’re talking about. Neither of you are currently moderated lol

(or if you are, it wasn’t me )

Oh we’re not, but we were both flying close to the sun

 

[Nand]

Another bug to report with 3.3.9:

I have scheduled charging set to start at midnight.
Plugged in car at 7:00 PM and it showed it will start charging at midnight.

Then I did the SW update at 8:00 PM. Car successfully did the update.
But after that it did not start charging at midnight as scheduled.
Hopefully this is a one-time thing due to the SW update.

Did anyone else's car forget the charging schedule after SW update?

 

[Ironhorse]

I with @hmp10 - 3.3.9 introduced more instability on my already sensitive car. Auto Headlight error, traction control errors, and for some reason Spotify is glitching every few minutes (atleast once per song). Spotify over Bluetooth plays ok (as a test).

The biggest issue for me is the arctic blast. I literally don’t want to get into the car without preheating, knowing full well the arctic air is incoming.

 

[msaunders9430]

Since I hadn't read any posts about cars that were functioning fine before 3.3.9 subsequently having issues, I decided to update today.
Did fob update check as well.

Experienced the usual unlock and screen activation.
Tried to change to a drive mode and got the "No Key Fob Detected" message and car wouldn't go into a drive mode.
Also received a rear wheel steering error message.

This was only the second time since delivery in early August that I received the fob message.
First time was about a month after delivery. During that instance, I waited 10 minutes, tried again; success.
This time instead of waiting 10 minutes, I exited the car, locked it, and immediately unlocked and tried again; success again.

No error message or other issues since then.
Screens maybe turning on a little faster.
Operates basically like before the update.

Key cards still work.

 

[NoseyReporter]

I really wonder how come everyone's experience is so different.

Since 3.3.5 I have almost no error messages. Now the key fob error is very infrequent and I have seen an error about charging, rear steer, etc. Ocasionally I get a DDPro sensor error but it's in the morning when I assume there's haze due to moisture or rain. It clears itself within a few minutes after driving.

Since 3.3.39 even the black screen is a non issue. Yes sometimes I get in the screens are loaded and suddenly they black out, but they return within seconds. I haven't had to sit there and wait for the screens to load.

I don't have the tech package, so I wonder if that is a factor.

 

[msaunders9430]

I really wonder how come everyone's experience is so different.

Since 3.3.5 I have almost no error messages. Now the key fob error is very infrequent and I have seen an error about charging, rear steer, etc. Ocasionally I get a DDPro sensor error but it's in the morning when I assume there's haze due to moisture or rain. It clears itself within a few minutes after driving.

Since 3.3.39 even the black screen is a non issue. Yes sometimes I get in the screens are loaded and suddenly they black out, but they return within seconds. I haven't had to sit there and wait for the screens to load.

I don't have the tech package, so I wonder if that is a factor.

Lucid is able to remotely monitor these cars.
I'm hoping the data from that monitoring along with other available data contributes to the sw updates.

The exception is owners' practices such as use of a Faraday bag, which I use. However, there are probably owners who don't and also have minimal to no issues. I don't have the tech package upgrade either, but some who do may also have minimal issues.

 

[Alex]

Lucid is able to remotely monitor these cars.
I'm hoping the data from that monitoring along with other available data contributes to the sw updates.

The exception is owners' practices such as use of a Faraday bag, which I use. However, there are probably owners who don't and also have minimal to no issues. I don't have the tech package upgrade either, but some who do may also have minimal issues.

This reminded me to check the data usage for this month:

Looks it’s uploading data, hopefully back to Lucid. So maybe someone is looking at that?

 

[JeffSter]

Still get a free blow dry upon entry
Halo Secure is effectively dead for me and has been since 3.3.8
Still can't send addresses from phone
Black Screens still exist albeit maybe not as much
Still need to tap/press buttons multiple times to register

Before this update it felt like my FOB and car was working alot better. I was on 3.5 until 3.9 was offered to me… now I have had twice a car that stayed blacked out on both screens for minutes… I walked away, came back each time and it was fine. But this is way less comfy especially in winter. For me so far this update feels like a backwards step. Are they ever gonna give us a screen where we can see what versions of the qnx crackberry sw to see what changes each time… even just letting us see if the car is rebooting… so we see something other than black screens… really disconcerting when it just takes no input and gives no responses… Even a progress bar would be better.

 

[JeffSter]

I’ll say since the update, haven’t had any black screens upon load up. Been loading right away. No other issues like others have reported.

Fascinating… as with 335 I had no black screens behavior… and now with 339 I’ve had it twice in 2 days… feels like we lost ground in the battle to help gravity behave.

 

[HC_79]

The biggest issue for me is the arctic blast. I literally don’t want to get into the car without preheating, knowing full well the arctic air is incoming.

It’s the new “Chill Mode” feature

Before this update it felt like my FOB and car was working alot better. I was on 3.5 until 3.9 was offered to me… now I have had twice a car that stayed blacked out on both screens for minutes… I walked away, came back each time and it was fine. But this is way less comfy especially in winter. For me so far this update feels like a backwards step. Are they ever gonna give us a screen where we can see what versions of the qnx crackberry sw to see what changes each time… even just letting us see if the car is rebooting… so we see something other than black screens… really disconcerting when it just takes no input and gives no responses… Even a progress bar would be better.

Similar experience with the key since updating. Have had to push the handles twice to open the car where previously the key had been extremely responsive.

I’ll take that over the Air loaner I have though. Car wouldn’t go into drive this morning after getting in and out of it multiple times (proximity worked all the time), keycard wouldn’t work and had to restart the software to get it to go into drive.

 

[socktucker]

I really wonder how come everyone's experience is so different.

Since 3.3.5 I have almost no error messages. Now the key fob error is very infrequent and I have seen an error about charging, rear steer, etc. Ocasionally I get a DDPro sensor error but it's in the morning when I assume there's haze due to moisture or rain. It clears itself within a few minutes after driving.

Since 3.3.39 even the black screen is a non issue. Yes sometimes I get in the screens are loaded and suddenly they black out, but they return within seconds. I haven't had to sit there and wait for the screens to load.

I don't have the tech package, so I wonder if that is a factor.

It could be something as simple as a single board component that had different vendors at different times of production.

 

[Ron_Burgundy]

Only issues I’ve really had with 3.3.9 are headlight and dream drive sensor warnings - both of which go away and don’t come all the time.

Otherwise, until I type this, everything has been stable. Haven’t had black screens in a very long time. Fob goes to “sleep” when I wait in car for kids - but when I shake it vigorously, it wakes up and car starts. Annoying but fine. Wasn’t an issue prior to the 3.3.5 fob update - but I am fine with it as 3.3.5 was such a massive help for fob.

 

[JeffSter]

Yes, I recognize that many people are not having major issues but virtually every review done on the Gravity over the past couple months (Motor Trend, Consumer Reports, Savage Geese, numerous YouTube Reviewers/Influencers) have mentioned fob issues, can’t get car to start, black screens. And I mean every single one. Not a single review has hinted at anything regarding software stability. All of the glowing reviews that Lucid likes to site are based on the early launch event when reviewers just had a couple hours to live with car. Once reviewers started having long term access to a Gravity, the universal tone from most all reviews has been “Great driving car, glitchy software and QC issues.”

Seems like these issues might be related to the os of the car as the latest Volvo seems have similar craptastic behavior . So… are we waiting for fixes from the Blackberry folks? Hopefully not a damn finger pointing party between the companies.

 

[JeffSter]

Only issues I’ve really had with 3.3.9 are headlight and dream drive sensor warnings - both of which go away and don’t come all the time.

Otherwise, until I type this, everything has been stable. Haven’t had black screens in a very long time. Fob goes to “sleep” when I wait in car for kids - but when I shake it vigorously, it wakes up and car starts. Annoying but fine. Wasn’t an issue prior to the 3.3.5 fob update - but I am fine with it as 3.3.5 was such a massive help for fob.

Agree that 335 helped with resetting fob… and general stability… gonna try a steering wheel reboot soon to see if it stops the new to me black screens issue post 339… starts to feel like push me,pull you fixes.

 

[msaunders9430]

Fascinating… as with 335 I had no black screens behavior… and now with 339 I’ve had it twice in 2 days… feels like we lost ground in the battle to help gravity behave.

Now if I had read this I might not have updated today.

 

[HC_79]

Only issues I’ve really had with 3.3.9 are headlight and dream drive sensor warnings - both of which go away and don’t come all the time.

Otherwise, until I type this, everything has been stable. Haven’t had black screens in a very long time. Fob goes to “sleep” when I wait in car for kids - but when I shake it vigorously, it wakes up and car starts. Annoying but fine. Wasn’t an issue prior to the 3.3.5 fob update - but I am fine with it as 3.3.5 was such a massive help for fob.

Is your Halo Secure working? Mines been effectively dead since 3.3.8, reboots don’t fix it.