Android Auto in 2.7.0 - Initial Impressions

OK, I've been using AA quite a bit lately and here are a couple of observations.

1- My phone (Pixel 8) gets pretty warm when using AA. And that means crazy drain to the point of anything long distance means I'm going to have to plug it in.
2- AA usually launches automagically when I select it, or if it was being used the last time the car was driven. But occasionally, the phone doesn't seem to want to connect via BT unless I explicitly go to the car's"connected devices" screen and select it.

Observation one is clearly not a Lucid implementation issue. And observation 2 probably isn't either.

Over all, I give the AA implementation an A. It was a long wait,but all is now forgiven.
 
..1- My phone (Pixel 8) gets pretty warm when using AA. And that means crazy drain to the point of anything long distance means I'm going to have to plug it in.
2- AA usually launches automagically when I select it, or if it was being used the last time the car was driven. But occasionally, the phone doesn't seem to want to connect via BT unless I explicitly go to the car's "connected devices" screen and select it...
I recently had a similar experience in two different rental Toyotas for a week each. I did have to manually start Android Auto occasionally on both the older and the newer-infotainment Toyotas. AA was invaluable during each day's 2-4 hour planned drive. We occasionally plugged in the AA source phone to give it a charge boost during the day.

Our last week's rental was a new Volvo with built-in Google maps, which was nicer. A premium experience by comparison.
 
OK, I've been using AA quite a bit lately and here are a couple of observations.

1- My phone (Pixel 8) gets pretty warm when using AA. And that means crazy drain to the point of anything long distance means I'm going to have to plug it in.
2- AA usually launches automagically when I select it, or if it was being used the last time the car was driven. But occasionally, the phone doesn't seem to want to connect via BT unless I explicitly go to the car's"connected devices" screen and select it.

Observation one is clearly not a Lucid implementation issue. And observation 2 probably isn't either.

Over all, I give the AA implementation an A. It was a long wait,but all is now forgiven.
Pixel 8 Pro and I haven't noticed any heating on my phone .. will have to check for drain. I did buy a new high-speed USB cable to use for wired. Also one of the few AA settings seems to be whether it should launch always, only if used last time, etc. I changed it to only if used last time but haven't really bothered to check how well that's actually working. I love how seamless it is to go in / out of AA .. so even if I'm used AA routing, I can hit the lucid music icon, switch my music source to tidal (etc) and then get back into AA for my routing. It's a few button clicks but is still usable. I agree, "A" on the implementation - especially the integration of routing and album art / track name onto the native lucid display .. that really helps to extend the AA capability beyond the given screen, thought that was very clever. Also I like that incoming texts etc pause the music source even if native to the car. I get an occasional wonky thing (startup issue, etc) but it's not very frequent at all.
 
The setting choices for automatic launching are honestly laughably stupid.
  • "Always". Ok, sure!
  • "Default (set by the vehicle)". Lucid has no option available, so this is "Always".
  • "If used on last drive". There's literally no way to get out of this loop after connecting once if you use mobile key lmao. If you disable WiFi, AA automatically turns it on. If you disable Bluetooth, you can't get into your car. If you manually disconnect AA after connecting, it doesn't matter because it was "still used on last drive" for those few seconds.
It's like they don't even have a QA team.
 
The setting choices for automatic launching are honestly laughably stupid.
  • "Always". Ok, sure!
  • "Default (set by the vehicle)". Lucid has no option available, so this is "Always".
  • "If used on last drive". There's literally no way to get out of this loop after connecting once if you use mobile key lmao. If you disable WiFi, AA automatically turns it on. If you disable Bluetooth, you can't get into your car. If you manually disconnect AA after connecting, it doesn't matter because it was "still used on last drive" for those few seconds.
It's like they don't even have a QA team.
yeah I wasn't sure about what 'if used last time' meant .. anytime in the drive or just at the end of the drive (active at disconnect time). I'm guessing lucid didn't to a default option yet don't have a way for AA not to have that as an option, so it's kind of a mismatch that maybe they couldn't fix. will fool with the last time option.
 
I was successfully using AA with Samsung S24 & all of the sudden it stopped connecting. I drove myself nuts for the week trying all troubleshooting options on the car and phone & then it occurred to me to try a Lucid logo reset & it started working again & has ever since. Strange!
 
yeah I wasn't sure about what 'if used last time' meant .. anytime in the drive or just at the end of the drive (active at disconnect time). I'm guessing lucid didn't to a default option yet don't have a way for AA not to have that as an option, so it's kind of a mismatch that maybe they couldn't fix. will fool with the last time option.

The funny thing is that not only is "if used" is ambiguous, but so is "last drive".

Think you can just leave your phone behind/disable Bluetooth/etc one time and use your FOB or card? Guess again, because "last drive" is determined by the phone... not the car. So if the phone isn't there, it doesn't know there was a drive. And if it doesn't know there was a drive, it still thinks it was used last drive 🤣
 
I have both AA and CarPlay. I did a recent 1500 mile roadtrip and AA was flawless. I truly believe the AA integration is better than the current CarPlay integration, but I’m biased as I use Waze and mostly Google apps on both 😜
 
Back
Top