I actually raised the Android Automotive angle with the local dealer and to their credit they took it up the chain. LOTUS HQ came back and stated that it would cost to much to re-contract and have it put back in (and passed the buck to Android Auto).
Virtually everyone so far on the forum that has made reference to Screen mirroring has said that "carPlay" has been working fine. Given that carPlay uses WiFi for the connection the BlueTooth issue would be unlikely to show up and hence it would be good to understand the breakdown
Do you use (1) CarPlay or (2) Android Auto
Unfortunately the documentation on the car's use of CarPlay/Android Auto is woefully small (read non-existent), so I don't know how much is actually possible, hidden behind a bad UX, or how much is what I would consider as software bugs (bad UX is still considered a bug).
- The Android Auto implementation appears to have no way to actually have it on demand rather than all the time. That is, Disabling Wireless AA (so as to only use the cable attachment) is actually turning off the Bluetooth itself off, so I no longer can link the phone independently. Turn Bluetooth back on via the connections option and AA comes back on again (no separation of connection).
- Hence even if not actively using AA it has been draining the battery on the phone (connecting regardless)
- While Google removed the ability to "turn off" Android Auto in their own UI a few years back, that capability is passed to the OEM (ie car manufacturers) to implement. The options for AA activation being "Always", "As per last trip", "Per the Car". In this case the bespoke infotainment went for the "Per the car" = "always", so there is no way to actually turn it off without effectively disabling AA completely (so no only when plugged into a cable)
As an aside,
- The native navigation system is still acknowledged in the driver binnacle and sits there spinning wheels trying to activate the maps (at least the icon was removed from the main screen)