Lucid Gravity UX 3.6 is here!

@marqie I know it's too late and I didn't see this post yesterday, but perhaps mine can be still be added? 7UUG1GHK9TA006257
 
I feel that keeping the HERE maps but with the search through Google's API is a good compromise. My biggest issue has been with finding places, more than the navigation itself.
Funnily enough, for all the people that swear by Google being the greatest, the very FIRST POI I selected after the update was actually navigating me to the wrong place. I had to manually drop the pin a block over. Go figure!
 
How about posting some new screens showing some new operations and tweaking of the media screen the dream drive screens anything new please post new screen so we can see some differences thank you
 
Funnily enough, for all the people that swear by Google being the greatest, the very FIRST POI I selected after the update was actually navigating me to the wrong place. I had to manually drop the pin a block over. Go figure!
Anecdotes are not data :)
 
Any change to 3.6 ADAS on city streets? Would love to see a YT on that. Last I saw it was essentially unusable on anything besides a well marked limited access highway.
 
Any change to 3.6 ADAS on city streets? Would love to see a YT on that. Last I saw it was essentially unusable on anything besides a well marked limited access highway.
DD Pro in Gravity has always worked on city streets as long as the roads are clearly marked. It tends to struggle a bit when approaching stopped traffic but I use it often around town. Guessing as they get closer to L2++ and implement things like traffic light recognition it will become more responsive to stopped traffic etc.
 
This has been discussed elsewhere in these forums but answer is most likely NO. HERE is better optimized for ADAS systems and thus most auto companies use it vs google for their ADAS systems. Adding google places to the Lucid native app is a good step toward dealing with some of HEREs shortcomings. Some companies are using Google as an overlay for what you see on infotainment but have HERE still baked in for their ADAS systems.
I agree that Google Maps would be a massive upgrade. Since Tesla and Rivian both utilize Google's platform, it would be great to see Lucid adopt a similar approach for the embedded navigation system. Even if HERE is technically superior for ADAS, having the option for Google Maps would significantly improve the overall usability of the infotainment system.
 
I agree that Google Maps would be a massive upgrade. Since Tesla and Rivian both utilize Google's platform, it would be great to see Lucid adopt a similar approach for the embedded navigation system. Even if HERE is technically superior for ADAS, having the option for Google Maps would significantly improve the overall usability of the infotainment system.
At least a dozen manufacturers are shipping cars with native Google Maps. But if I'm not mistaken (@HC_79 ), Tesla and Rivian use Google Places' POI database, the same as Gravity, while using another navigation engine.

Google Places is a great improvement over HERE's POI dtatabase. But it's still a halfway solution compared to using native Google maps, which has accident/police/construction reporting and alerts, and much better integration with Google Maps on our phones.

Our Gravity has been utterly wonderful except for this. If you're a dedicated CarPlay customer, then no worries, all is moot.
 
A question for @marqie (or anyone "in the know" on the OTA process.

Do the OTA updates get pushed on every day of the week or just on certain days of the week?
 
At least a dozen manufacturers are shipping cars with native Google Maps. But if I'm not mistaken (@HC_79 ), Tesla and Rivian use Google Places' POI database, the same as Gravity, while using another navigation engine.

Google Places is a great improvement over HERE's POI dtatabase. But it's still a halfway solution compared to using native Google maps, which has accident/police/construction reporting and alerts, and much better integration with Google Maps on our phones.

Our Gravity has been utterly wonderful except for this. If you're a dedicated CarPlay customer, then no worries, all is moot.
I am pretty sure that Google Maps navigation requires that the car's infotainment be built on Android Automotive with Google Automotive Services (GAS). The automakers with Google Maps, like GM, Polestar, Volvo, Nissan, etc. are all using AA with GAS. GAS is the cesspool of anti-privacy and a reason not to buy a car. Be grateful for your luck. Automakers using GAS often require a google ID for the car to fully enable all features, and this gives Google access to your personal and drive data. For people who are not Google, and especially those who a wary of Google's privacy abuses, GAS is of the devil.
 
At least a dozen manufacturers are shipping cars with native Google Maps. But if I'm not mistaken (@HC_79 ), Tesla and Rivian use Google Places' POI database, the same as Gravity, while using another navigation engine.

Google Places is a great improvement over HERE's POI dtatabase. But it's still a halfway solution compared to using native Google maps, which has accident/police/construction reporting and alerts, and much better integration with Google Maps on our phones.

Our Gravity has been utterly wonderful except for this. If you're a dedicated CarPlay customer, then no worries, all is moot.
The realtime accident/lane closure is a huge part IMO. I was using the Lucid nav around Los Angeles this weekend and while trying to get from Glendale to the Lucid Owner's Club meetup at EVFest it routed me to a freeway exit that was closed for construction twice on just that part of our roadtrip. It was able to recalculate but it would have been nicer to have a "clean" route from the start.
 
I am pretty sure that Google Maps navigation requires that the car's infotainment be built on Android Automotive with Google Automotive Services (GAS). The automakers with Google Maps, like GM, Polestar, Volvo, Nissan, etc. are all using AA with GAS. GAS is the cesspool of anti-privacy and a reason not to buy a car. Be grateful for your luck. Automakers using GAS often require a google ID for the car to fully enable all features, and this gives Google access to your personal and drive data. For people who are not Google, and especially those who a wary of Google's privacy abuses, GAS is of the devil.
We have GAS with native Google maps and voice assistant (soon Gemini) in our Volvo EV, and use it many times per day. It's far more usable and helpful than the average nav, as it knows our habits, search history, etc. I think no more and no less of signing into Google in my car than I do on my phone. It's another connected personal device, the same as having a second phone, tablet, or desktop signed into Google.

It is the reason we are strongly considering the EX60 instead of Lucid's midsize, and why I nearly bought a Cayenne EV instead of Gravity. As more and more competent EV options appear, there will be fewer and fewer reasons to buy one with compromised maps and connectivity.

I completely understand why iOS users would have a markedly different perspective on this.
 
I am pretty sure that Google Maps navigation requires that the car's infotainment be built on Android Automotive with Google Automotive Services (GAS). The automakers with Google Maps, like GM, Polestar, Volvo, Nissan, etc. are all using AA with GAS. GAS is the cesspool of anti-privacy and a reason not to buy a car. Be grateful for your luck. Automakers using GAS often require a google ID for the car to fully enable all features, and this gives Google access to your personal and drive data. For people who are not Google, and especially those who a wary of Google's privacy abuses, GAS is of the devil.
I feel like Google already has most of our driving data since we have our phones with us while driving or use their products on CarPlay or AA. Unless you are not logged in to any of their products.
 
Just got to try the update on the commute home. Took the long way to give DD Pro the chance to calibrate and start working and only had about 5-10 miles with it but it is clearly greatly improved! It takes lanes on its own with ease and much smarter, no unnecessary changes for my drive at all. It got over safely when it needed to pass and then back in lane when safe to do so, all on conservative mode. I hadn't tried the aggressive mode (if that's what it's called) yet. Handled slow downs, lane centering, curves and even getting out of the fast lane relatively quickly bc someone was flying up on me, so I imagine it was to let them pass, but it could have just been going to do it anyway. Very impressed and can't wait to try it out on my trip to Gulf Shores next weekend. I've not driven Teslas much, but it was a weird and disconcerting feeling taking my hands off the wheel and just sitting there, looking around but not driving. Like I had to make an effort to keep my hands off the wheel! The improved graphics for DD are VERY nice and would be great if they just stayed on all the time IMO.
Tried the Google search and it worked as expected, a very nice addition to be able to search places and see info from Google. I didn't get to really mess with much else. My key fob had been working pretty consistently for months, but I did notice it is opening the door from a bit further away now, but not as far away as it used to several months ago when the car would light up and turn on when I was like 100 feet away. Very happy with the update so far and may go out again this evening to drive a bit more. Try the adaptive headlights at night too. Also, install took about 2 hours for me. Thanks Lucid for the hard work as it is definitely showing!
 
anyone knows if the pausing on Apple CarPlay with Spotify is fixed? :D
 
I feel like Google already has most of our driving data since we have our phones with us while driving or use their products on CarPlay or AA. Unless you are not logged in to any of their products.

Screenshot From 2026-06-09 14-04-11.webp
 
Back
Top