I have three different things to comment about. Two of which are obnoxious; one of which as a possible work around doesn't seem to be working around! Sorry about the wall of text at least on mobile.
My first issue with the new Android Auto connection has something to do with my specific phone, as when my wife's phone connects (more on that in a second) there is no issue.
I have the pre production notice appear when my phone connects either with USB or with Bluetooth. I have a Xiaomi phone, which *maybe* is the reason why? Perhaps the certificate for a Xiaomi phone is significantly different than a phone for sale in the US? However, I'm not sure that's really the issue, since these cars are in Saudi Arabia and my phone is a global variant. So there is that issue which on its own is annoying enough.
Second issue occurs when my wife and I both plug our phones in to the USB to charge (wireless charging is too slow, I don't use or like). The car doesn't seem to know what to do and will pick one Android Auto to connect to, and then at some point decide to switch to the other phone's Android Auto. This is *also* an annoying new situation that has begun. I haven't tested it, but I presume the same would happen with Bluetooth connection as well.
Android Auto itself isn't helpful in this regard, as if you go into regular settings it will only allow you options that trigger launch as opposed to ignore. If you go into developer options you can disable auto launch when connected, but then I would think you would lose out on a one tap connection (or auto connect) when you are in the car alone.
Going back to the pre production software notice, I have also tested all of the release types in developer options and none remove that notice.
I have attempted (this was silly but I figured why not try) to use my Tbox Ambient to launch Android Auto through the Tbox (as opposed to Apple) and the funny thing is that while it can sometimes see the Lucid's Bluetooth, it fails to connect to it. It will "connect" and then reboot itself while the Lucid is trying to negotiate the communication. When the Tbox is back up it will not connect to the Lucid Bluetooth that is now in the list of available connections. I only tried this because I thought I could bypass both phones by not connecting Android Auto to the car and just using the Android Auto that the Tbox has. Apparently that won't work either.
I have:
Followed Lucid's directions from the release notes with no luck. After each attempt below I Air logo rebooted the car.
I have fully uninstalled and reinstalled Android Auto from my Xiaomi phone.
I have changed which version of Android Auto that is running via developer settings. <- now I did not change the developer setting, then uninstall, reinstall, etc. so maybe I need to spend 45 min doing this with each option? Uninstall/disconnect/forget on phone and car, then reboot the car, choose a different release in developer options, and then connect?
As I said, an interesting note is that my wife's Samsung phone has no issue and does not display the pre production software notice.
Help?
