Android auto

[Fittrjb3]

Newly released Android auto. Has anyone been able to access it?

 

[DeaneG]

OTA 2.7.0, containing Android Auto, hasn't rolled out to the general public just yet.

 

[Fittrjb3]

OTA 2.7.0, containing Android Auto, hasn't rolled out to the general public just yet.

8

 

[lucidtouringman]

FEAST THY EYES!

SOURCE:

https://insideevs.com/news/762899/lucid-air-android-auto-carplay/

 

[Fittrjb3]

FEAST THY EYES!
View attachment 29804

SOURCE:

https://insideevs.com/news/762899/lucid-air-android-auto-carplay/

Were u able to install it?

 

[lucidtouringman]

Were u able to install it?

No, it's what I found on a website that shared news about AA release and they had this image...I've mentioned the source too...I was really hoping it would cover the curved areas of the screen but I guess we'll be left with a black empty space after all...

 

[Bobby]

No, it's what I found on a website that shared news about AA release and they had this image...I've mentioned the source too...I was really hoping it would cover the curved areas of the screen but I guess we'll be left with a black empty space after all...

Same as CarPlay. You can have your background cover the area but no functional stuff.

 

[northernstar]

I was really hoping it would cover the curved areas of the screen but I guess we'll be left with a black empty space after all

Yikes... I really hope that wasn't the case.
I was in Costa Mesa Service Center today, and I was able to seat inside Gravity and try the UI..
Looks like Android Auto / Apple Carplay will have a better-integrated 'real estate' screen size with the curved screen in Gravity.

 

[Bobby]

Yikes... I really hope that wasn't the case.
I was in Costa Mesa Service Center today, and I was able to seat inside Gravity and try the UI..
Looks like Android Auto / Apple Carplay will have a better-integrated 'real estate' screen size with the curved screen in Gravity.

View attachment 29807

Yes, the gorgeous curved screen in the Air is indeed artwork, but limits functionality because most software likes rectangles.

 

[Beast]

FEAST THY EYES!
View attachment 29804

SOURCE:

https://insideevs.com/news/762899/lucid-air-android-auto-carplay/

Excellent! Live Android Auto. Cant wait

 

[northernstar]

Yes, the gorgeous curved screen in the Air is indeed artwork, but limits functionality because most software likes rectangles.

Yes the "rectangle" rule... I wonder if it's an enforced UI protocol from Google.

Come to think about it.. Rivian, Kia, BMW, Hyndai, Honda, Toyota, Audi, VW...etc they all went with a rectangular screen.
Their display panels might be slightly curved.. but actual screen-wise, they maintain a strict rectangular geometry.

 

[segbrk]

Yes the "rectangle" rule... I wonder if it's an enforced UI protocol from Google.

Come to think about it.. Rivian, Kia, BMW, Hyndai, Honda, Toyota, Audi, VW...etc they all went with a rectangular screen.
Their display panels might be slightly curved.. but actual screen-wise, they maintain a strict rectangular geometry.

If you think about it, basically every smartphone is a rectangle. Every tablet is a rectangle. Nearly everything Android and iOS and all their apps run on is a rectangle. So if you, a small car company, went to Apple or Google and said "hey, can we be a funky curved shape?" the answer is going to be "hell no." It's a huge pain to make everything support that. That's why so many smart watches are rectangles instead of nice circles, everything has to be redesigned to fit a non-rectangle. Software graphics have been rectangular and x/y coordinate based for so long, doing something else breaks the brains of the average UX developer.

 

[northernstar]

So if you, a small car company, went to Apple or Google and said "hey, can we be a funky curved shape?" the answer is going to be "hell no."

I keep forgetting the Android Auto is a projection of our phone...
I hope someday the AA works like the "Android Automotive", a native, embedded solution-esq flexible option.

 

[msaunders9430]

My understanding, shown below, after reading tons of posts, mostly in this thread, but I'm missing something, so I have two questions.

Android Auto (AA) is now available on the Air and soon-to-be on the Gravity.
Google Maps (GM), running on AA, can be used for travel/route planning that will include the location of charging stations and will factor in charging time when determining total travel time/distance.

Lucid does not use Google Automotive Services (GAS) like Volvo and Polestar, that provides Google built-in services.
I understand the benefits of not using GAS as it relates to Lucid ADAS features and the reliance on HERE maps.
GM is not able to initiate battery pre-conditioning before arriving at a charging location.
The native Lucid navigation app will be needed for pre-conditioning.

Does that mean at some point, both GM and the Lucid navigation app will have to be running during travel if the driver wants to do pre-conditioning?

Is GM is able to provide charging locations and factor in charging time because GM is able to access the Air/Gravity battery SOC because Android Automotive OS (AAOS) is also used by Lucid, so AAOS facilitates the communiction between GM and the Air/Gravity battery managment system?

 

[msaunders9430]

Google Maps (GM), running on AA, can be used for travel/route planning that will include the location of charging stations and will factor in charging time when determining total travel time/distance.

This can't be right.
GM through AA is just a representation of my Android phone.
My phone is not interacting with the Lucid battery system.

 

[segbrk]

GM is not able to initiate battery pre-conditioning before arriving at a charging location.
The native Lucid navigation app will be needed for pre-conditioning.

You don't need to use Lucid nav, you'll just have to manually activate preconditioning from the charging screen on the pilot panel.

This can't be right.
GM through AA is just a representation of my Android phone.
My phone is not interacting with the Lucid battery system.

It's not just a representation of your phone, it also has a side channel that is capable of passing battery information and stuff like that back to your phone. I don't know if Lucid has actually implemented this, but it is possible. Nothing special about Lucid's software being based on AAOS, it's just a feature that AA implementors can choose to implement (or not).

 

[DeaneG]

My understanding, shown below, after reading tons of posts, mostly in this thread, but I'm missing something, so I have two questions.
...
Does that mean at some point, both GM and the Lucid navigation app will have to be running during travel if the driver wants to do pre-conditioning?

Is GM is able to provide charging locations and factor in charging time because GM is able to access the Air/Gravity battery SOC because Android Automotive OS (AAOS) is also used by Lucid, so AAOS facilitates the communiction between GM and the Air/Gravity battery managment system?

Google Maps over Android Auto on the Air doesn't know anything about the car's SOC. It does not add charging stops. It can't initiate preconditioning. You can change your car type on your phone to "Electric" and "Lucid Air", but doing so doesn't do anything useful yet that I can tell.

However, Google Maps on AA will get you to the destination you previously identified on your phone or desktop.

You can manually search for charging stops along the way and add them, but this is done without any guidance from Google Maps based on range or SOC.

This is in contrast to cars which use native Google Maps on AAOS. That choice has excellent EV routing capability.

 

[msaunders9430]

Android Auto, as used with the Air, doesn't know anything about the car's SOC. It does not add charging stops. It can't initiate preconditioning. You can change your car type on your phone to "Electric" and "Lucid Air", but doing so doesn't do anything useful yet that I can tell.

However, Google Maps on AA will get you to the destination you previously identified on your phone or desktop.

You can manually search for charging stops along the way and add them, but this is done without any guidance from Google Maps based on range or SOC.

This is in contrast to cars which use native Google Maps on AAOS. That choice has excellent EV routing capability.

According to the post before yours, AA has the capability to pass battery info to my phone, but Lucid may not be implementing this capability.
However, you're saying AA doesn't know anything about the car's SOC. If so, AA won't have any info to pass to my phone.

So AA has the capability in general, but as used with the Air that capability isn't functional?

 

[DeaneG]

According to the post before yours, AA has the capability to pass battery info to my phone, but Lucid may not be implementing this capability.
However, you're saying AA doesn't know anything about the car's SOC. If so, AA won't have any info to pass to my phone.

So AA has the capability in general, but as used with the Air that capability isn't functional?

Right. Few companies have implemented this so far.

 

[DeaneG]

According to the post before yours, AA has the capability to pass battery info to my phone, but Lucid may not be implementing this capability.
However, you're saying AA doesn't know anything about the car's SOC. If so, AA won't have any info to pass to my phone.

So AA has the capability in general, but as used with the Air that capability isn't functional?

Note that the A Better Route Planner phone app has the ability to route plan using your car's SOC and realtime efficiency, weather, elevation, etc, if you pay the modest monthly fee. It could be very useful for road trips. I haven't tried it with my Air yet.