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!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.
Anecdotes are not dataFunnily 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!
City streets will be end of this year according to Lucid (as of March)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.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.
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.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.
Actually that sounds like a data point since it actually happened. I think what you are referring to is the "small sample size" effect.Anecdotes are not data![]()
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.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 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.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.
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.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.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.
Seems fineanyone knows if the pausing on Apple CarPlay with Spotify is fixed?![]()
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.