Gravity Bugs / Issues

After a couple days of driving it I think I am only seeing one weird issue with my GGT, which is that the front driver side turn signal (sometimes?) blinks at a weird fast/uneven cadence. It doesn’t happen all the time because when I was parked in my driveway I asked my wife to look and she said they were all acting normal, but I’ve definitely seen the issue out driving when it’s reflected on the back of other cars.

I haven’t rebooted the car yet since owning it so I’ll probably give that a shot and see if it goes away.
Reboot didn’t work so it’s getting transported to KOP in a couple weeks. Surprisingly (to me) Tyson’s Corner had no appointments available in October or November, not that it matters since they are both ~4 hours away.
 
Reboot didn’t work so it’s getting transported to KOP in a couple weeks. Surprisingly (to me) Tyson’s Corner had no appointments available in October or November, not that it matters since they are both ~4 hours away.
The app is grayed out entirely - so don’t look there for availability. You have to call and they’ll triage you based on whether it’s drivable and if it’s a safety issue. Thy are very responsive in Tysons.

If your rear passenger sunshade is stuck in the up position (random example), or there’s a weird noise coming from some seat, you’re not getting a slot any time soon.
 
The app is grayed out entirely - so don’t look there for availability. You have to call and they’ll triage you based on whether it’s drivable and if it’s a safety issue. Thy are very responsive in Tysons.
Ahh interesting, I just assumed it meant they were booked up since KOP had plenty of available dates in the app.
 
the 3.3.2 update has made things way way worse for me.. I just got stranded in parking lot. Car wouldn't turn on past the blank screens. Key fob or key card it didn't matter. Resets didn't work either. I had to walk away for about 30 min and then the car woke up and after 3 min got past the blank screens.. This is seriously going from annoying to actually making the car unreliable.
 
I think there may be a bit of a workaround for the black screen issue...I've noticed that if you open the app on your phone a minute or two before you plan to go anywhere, it seems to wake up the car enough to turn on the screens pretty fast once you open the door. Not sure if this just works with my vehicle and is anecdotal. Feel free to try it out and let me know.
 
I think there may be a bit of a workaround for the black screen issue...I've noticed that if you open the app on your phone a minute or two before you plan to go anywhere, it seems to wake up the car enough to turn on the screens pretty fast once you open the door. Not sure if this just works with my vehicle and is anecdotal. Feel free to try it out and let me know.
For the last two days I can't even get the app (Android v2.8 2) to even connect to/wakeup my car. Posted in the app thread.
 
I think there may be a bit of a workaround for the black screen issue...I've noticed that if you open the app on your phone a minute or two before you plan to go anywhere, it seems to wake up the car enough to turn on the screens pretty fast once you open the door. Not sure if this just works with my vehicle and is anecdotal. Feel free to try it out and let me know.
This is similar to my preconditioning workaround which seems to work most of the time and I forgot to do earlier today.
 
(A post in multiple parts apparently due to Character Limit errors)
We took our new GDE for a drive Sunday: Phoenix to Flagstaff and back. Encountered quite a bit of weather on the way there and back. Extremely heavy rain at times driving directly through a thunderstorm. Handled wonderfully. Roughly 300 miles. Grabbed about 20% charge in Flagstaff and arrived home with 28%. EA Plug&Charge handshake performed flawlessly.

She was delivered with V3.3.1. Confirmed with Delivery Advisor that both our key fobs (yes, we got two) had been updated, "Yes, that's why we can give you 2 of them." Had the various sporadic key not found, USB charging not available, etc. issues to be expected from 3.3.1. Saturday night after dinner we came out to completely black screens that did not clear after a couple minutes waiting. Took 3 reboots to clear that up.
 
So was happy to see V3.3.2 ready to install yesterday morning. After the install, went out to see the Charging screen showing finished (as expected) with 605 km range?! Why in KM? Went into the settings and found that the units were not selected at all:

Units Settings Blank.webp

So made those selections and things were fine after that. But there were several other settings that also got changed.

So then we were on the road and the HUD was strangely dim... Pulled over, tried changing the brightness, rebooting, no effect. It was like it was all a dim red.

Then my wife asked, "Don't your sunglasses interfere with the HUD?" D'oh! Took off my polarized prescription sunglasses and there's the HUD! User error! Need to get non-polarized sunglasses.

The HUD does seem to have some auto-dimming capabilities, but it seems to struggle right around dusk. It kept bouncing between too-bright and too-dim. As it was starting to get towards dusk the brightness of it caused the background rectangle to become apparent. Manually dropping the brightness to about 50% solved that.

At certain sun angles with the sun behind me, I was getting a white oval--not blue. A bit annoying but not blocking visibility. My wife could see it from the passenger side during a wider sun angle, even when I could not see it.
 
Loved taking her through the twisty roads between Flagstaff and Sedona on route 89a. But had to turn off the HUD as it was too distracting. The projection of the HUD info would draw my eyes away from the line of the curves I needed to focus on. It would be great if the UI could be changed to surface HUD On/Off to an easier-to-access place--or even put it as an option for assignable keys.

We were completely surprised, however, to find that one needed to be stopped, in Park, to turn the HUD back on. Anyone have any idea why they put this limitation in?

We did have a few instances of Key Not Found. Notably just after unplugging from the EA charger it was apparently not a false report as it would not shift into drive. Jiggling the keyf ob in my pocket worked. Note that we had both our fobs in the car at the time.
 
(A post in multiple parts apparently due to Character Limit errors)
We took our new GDE for a drive yesterday: Phoenix to Flagstaff and back. Encountered quite a bit of weather on the way there and back. Extremely heavy rain at times driving directly through a thunderstorm. Handled wonderfully. Roughly 300 miles. Grabbed about 20% charge in Flagstaff and arrived home with 28%. EA Plug&Charge handshake performed flawlessly.

She was delivered with V3.3.1. Confirmed with Delivery Advisor that both our key fobs (yes, we got two) had been updated, "Yes, that's why we can give you 2 of them." Had the various sporadic key not found, USB charging not available, etc. issues to be expected from 3.3.1. Saturday night after dinner we came out to completely black screens that did not clear after a couple minutes waiting. Took 3 reboots to clear that up.
Interesting it wasn’t delivered with 3.3.2…that does take care of some of the errant warnings.

Not surprised to effectively hear they were purposely holding back one of the two GDE fobs until issue was addressed.

The black screen…no idea. If it’s supposed to be a short term “solve” it’s pretty clunky and I can’t imagine that was their intent. Hopefully, we get another patch within two weeks.

Don’t need new features, just need existing features to work.

Enjoy the car!!!
 
Here’s a new one. Tire pressure warning light got me worried starting the car, but all tires reported proper pressure and never showed a decreasing trend.

Went away after a few drives.
 

Attachments

  • IMG_1166.webp
    IMG_1166.webp
    1.3 MB · Views: 130
Loved taking her through the twisty roads between Flagstaff and Sedona on route 89a. But had to turn off the HUD as it was too distracting. The projection of the HUD info would draw my eyes away from the line of the curves I needed to focus on. It would be great if the UI could be changed to surface HUD On/Off to an easier-to-access place--or even put it as an option for assignable keys.

We were completely surprised, however, to find that one needed to be stopped, in Park, to turn the HUD back on. Anyone have any idea why they put this limitation in?

We did have a few instances of Key Not Found. Notably just after unplugging from the EA charger it was apparently not a false report as it would not shift into drive. Jiggling the keyf ob in my pocket worked. Note that we had both our fobs in the car at the time.

I don’t know why they have that limitation but I noticed it also. In terms of quick access to adjusting the HUD, they added a button to the quick glance drop down (swipe down from the top of the pilot panel), same place you adjust the mirrors / steering wheel
 
The other thing that seemed strange was that invoking TACC or DDPro HA was hit or miss at times.
I've got it set to activate TACC on one press and HA on a double press, and to set the target speed to the current speed. Sometimes that worked flawlessly. Other times I would press multiple times and it would not engage.

I think it might have something to do with the current speed at the time of trying to engage. E.g. in a 75 mph zone, it would engage at 75, but not at 80. But once engaged I could bump it up to 80 with no complaints. On the other hand, in a 65 mph zone, I was able to engage at 76 mph.

I'm also getting used to the timing of clicking on the control pad to increase or decrease the speed:
  • Quick tap: does nothing
  • .5-1 second (approx): increment/decrement by 1mph on release.
  • long press: increment/decrement by 5mph with another 5 very quickly while holding
Any guidance?
 
In terms of quick access to adjusting the HUD, they added a button to the quick glance drop down
Good to know. Thank you. Fortunately, my wife played copilot so I didn't try to hunt for it myself :)
 
The other thing that seemed strange was that invoking TACC or DDPro HA was hit or miss at times.
I've got it set to activate TACC on one press and HA on a double press, and to set the target speed to the current speed. Sometimes that worked flawlessly. Other times I would press multiple times and it would not engage.

I think it might have something to do with the current speed at the time of trying to engage. E.g. in a 75 mph zone, it would engage at 75, but not at 80. But once engaged I could bump it up to 80 with no complaints. On the other hand, in a 65 mph zone, I was able to engage at 76 mph.

I'm also getting used to the timing of clicking on the control pad to increase or decrease the speed:
  • Quick tap: does nothing
  • .5-1 second (approx): increment/decrement by 1mph on release.
  • long press: increment/decrement by 5mph with another 5 very quickly while holding
Any guidance?
Wish I had guidance on control pad. Seems fairly inconsistent for me. Similar to what you describe. A quick tap does nothing. Oftentimes, though, a press does nothing (for DDPro or on other side for volume).

I’ve kind of gotten used to using the roller for volume as the control pad just isn’t sensitive/consistent.
 
Back
Top