Android Auto Thursday

[Genghis]

Yes, I agree. It appears that Lucid AA release will function similar to Car Play and it will cut out a rectangle on the cockpit LCD leaving parts of it unused. And it will not allow for extending to the pilot screen. I hear from Lucid Studio reps here in OC CA that running multiple apps on cockpit and pilot screen is the most sought after feature from the Lucid user community and their developers are well aware of it. We just have to wait and see when/if that happens. As a person with development bakground, I dream of Lucid and other car companies openings some hooks for third party extensions so that many of these requests can be realized and offered thru user communities. Oh well.

Back to the main topic. If we make the status quo assumption above, the current dongles provide the same functionality as a native Lucid AA feature with one exception. The dongles that work on Lucid cars are mostly 3-in-1 units meaning that they run their own Android OS and use their own GPS+Glonass chipsets. This is the case of CarlinKit Ai Box that others have used and Flogcexs dongle that I have used. When that is the case, the accuracy of positioning in Google Maps is at the mercy of the built-in chipsets. The native Lucid Here nav app, to the contrary uses the car's GPS which is likely to be more accurate. It is just the app itself not as powerful as Google Maps and is not integrated with Waze. So it becomes a preference choice, native Here app using the full cockpit screen and mirrored to pilot screen with better GPS accuracy or the better Google Maps using partial cockpit screen and the dongle GPS+Glonass chipsets. For me, the choice is the former. For the others, the choice may be the latter.

BTW, the album art worked right of the bat on my device and no changes were required. Possibly, because dev options were already turned on and the Bluetooth MAP mode already matched. I'll take a look.

Nice find!

 

[Steve181]

Just thinking out loud: IF the large bottom screen has an accesible HDMI port between it and the car computer, we could just wire in a cheap HDMI switch to an adapter to our phones. Problem solved, assuming the computer does not declare a fault. Does someone have a wiring diagram?

 

[SoCal_AirTouring]

Back to the main topic. If we make the status quo assumption above, the current dongles provide the same functionality as a native Lucid AA feature with one exception. The dongles that work on Lucid cars are mostly 3-in-1 units meaning that they run their own Android OS and use their own GPS+Glonass chipsets. This is the case of CarlinKit Ai Box that others have used and Flogcexs dongle that I have used. When that is the case, the accuracy of positioning in Google Maps is at the mercy of the built-in chipsets. The native Lucid Here nav app, to the contrary uses the car's GPS which is likely to be more accurate. It is just the app itself not as powerful as Google Maps and is not integrated with Waze. So it becomes a preference choice, native Here app using the full cockpit screen and mirrored to pilot screen with better GPS accuracy or the better Google Maps using partial cockpit screen and the dongle GPS+Glonass chipsets. For me, the choice is the former. For the others, the choice may be the latter.

Based on some readings, I have to make a correction to my post. That is to say not all dongles are created equal. There are some that rely on the phone's GPS instead of their built-in GPS. The 2 dongles discussed above appear to use the phone GPS instead of their own when operating AA and Car Play.