Search results

Public beta releases are significantly behind internal dogfooding releases.

I couldn't wait any longer, so I jerry-rigged it myself out of plywood, but honestly, it came out surprisingly well:

You're right. The confusion likely stems from the fact that Android Automotive Embedded was also demonstrated during the same 2026 I/O demo, which requires an OEM-side update. In our scenario, however, both the applications and the composing reside on the phone.

Just to clarify, the improved map graphics are a separate enhancement that comes directly through the Google Maps app update, rather than the Android Auto integration itself.

+1 to what @borski said. I’ve confirmed with the Android Auto team that no OEM-side software update from Lucid is required to enable full-screen support. I have been running the internal beta version with 3.5.1 and everything is working just fine.

For context, you should be on at least version 3.5.7 by now. If you haven't received any updates in several months, I recommend reaching out to your service advisor to check if there is an issue with your vehicle.

i don't think so, at least I didn't update mine and it's at v 02.35.08

I'm not sure if it's related to 3.6 update since I had the same issue about a couple months ago and it was self-fixed next day (after deep sleep, i guess).

This might have been mentioned here already, but based on my observations, the frunk opens way more reliably now. There is a noticeable delay right after the unlock and before the lid actually starts lifting. Also, like many have already pointed out, the walk-away auto lock/unlock works...

I can confirm that right after the install, the UI stays the same, which seems to be a bug. As soon as I started driving, the new items appeared including Hands-Free Drive Assist, but they were marked as temporarily unavailable (which is good). What surprised me was that everything became...

Yes, I do have Dream Drive 2 Pro (at least i paid for it :))

No, I haven't driven it yet since the update only finished yesterday evening, but I'm planning to take it out today.

But IIUC, the menu items should show up right away but be marked as unavailable until I complete the calibration process. Like this: But in my case, though, no new options have appeared at all, i.e. the DreamDrive menu look exactly as before the update:

I just recently updated to 3.6 and completed the Identity Verification, but my DreamDrive menu hasn’t changed at all—none of the new options like Hands-Free Drive Assist or anything else have shown up. Is this normal? Is it just a matter of the feature configuration flags not loading yet, and I...

we can ask admins to delete the attached photo :) BTW, I still don't have 3.6 :(

Yeah, that's what was shown at Google I/O 2026, and I hope it'll be available to everyone soon. There are updates to Android Auto (UI changes and full-screen utilization), as well as Google Maps (new 3D compositing, lanes, junctions, hints, etc.).

I can't say anything about Apple Maps since I haven't used an iPhone in a long time, but if we're comparing the built-in Lucid navigation, Waze, and Google Maps, the latter wins for me by a landslide. I used to like Waze at one point, but now that Maps has added user alerts, and especially after...

Already did :)

I’d try to reboot the phone. Downloaded media - especially if it's an audiobook - can have a much lower bitrate than what you're trying to stream. In most cases, audio stuttering in CarPlay and Android Auto is caused by lag on the phone itself. In other words, the phone's CPU just can't keep up...

I wonder how many people are still waiting for the 3.6 update? Reading through this thread, I'm starting to feel like I’m the only one who didn't get the update - maybe I’ve been talking too much?