Polestar Forum banner

Android Auto

9.8K views 38 replies 19 participants last post by  spacecadet  
#1 ·
#4 ·
It's here. Now all the whining can stop. And we can kiss AAOS apps goodbye.
Well, no...

If you already own a car with an Android Automotive head unit and want to try out the Android Auto Receiver app, there is some bad news. Rahman reveals that the app can only be installed on builds that “declare com.goog.android.car.feature.AARECEIVER.” This currently only applies to the official Android Automotive OS emulator and IVIs with Renault’s openR link system.
Also, I doubt it'll work anyway on the PS2 for the same reason they couldn't implement wireless Apple CarPlay - there's no direct connection between the infotainment unit and the WiFi which is hosted by the TCAM.
 
#7 ·
Well, no...



Also, I doubt it'll work anyway on the PS2 for the same reason they couldn't implement wireless Apple CarPlay - there's no direct connection between the infotainment unit and the WiFi which is hosted by the TCAM.
We might get this sooner than all the apps people claim they need.

I still believe that with the implementation of this concept, AAOS as an application platform is dead. It's just going to become a back-end server.
 
#12 ·
While other manufacturers are absolutely converting to ASOS, many of them have also implemented AA. It's simply doesn't bode well for AAOS because the financial incentive is taken away for app developers.

Once AA is on a car I as an app developer have already satisfied that user. No need to spend any more effort because I don't gain any extra market share.
 
#13 ·
Yeah, until Google forces its developers’ hands (i.e. “if you want to be in cars you’ll develop for both AAOS and AA or not at all”), AAOS is DOA as an ecosystem. And Google isn’t good at exerting that level of control.

It’s possible this is for the best. Even the AAOS parts that have nothing to do with apps are so much buggier than anything else I’ve ever experienced (or care to experience) in a car. Understanding we won’t get this in the 2, I really wouldn’t mind an industrywide retreat to a more rock-solid base layer + optional Google/Apple takeover.

Just personal opinion. Based on this experience, I’d go out of my way to purchase a next vehicle that isn’t AAOS-based, and AAOS would be one of the key things keeping me from sticking with Polestar for the long run.
 
#15 ·
Google’s interest is in collecting data and getting AAOS on cars accomplishes that, they don’t really care about the user experience beyond that.

With no easy way to upgrade the infotainment system CarPlay and Android Auto make more sense considering cars last way more than typical IOS or Android devices anyway.
 
#18 ·
It is an interesting one, but it is more sharing across devices sdk then anything else, yes they say they'll make it available for more than just android but we will see. Probably part of a next version (v14!?) of AAOS...

It's here. Now all the whining can stop. And we can kiss AAOS apps goodbye.
The whining won't stop :p Apple CarPlay isn't great in its implementation either, no suggestion that if AA arrives it will be any better...
 
#23 ·
we are all moaning about AAOS and lack of apps, not that we all need AA, if we think about that.
There are only two significant upsides with AAOS - Maps and Assistant integration that makes the journey super accurate. Not Waze, definitely not Apple Maps (👀) nor 3rd parties can give what Maps can give

While there are no Apple OS car on the market and already most of the major makers committed to AAOS, it is a matter of time that makers will push it on
As for my own opinion - I'd rather have a (currently) limited number of apps, but super accurate, open and flexible system, than be locked to what Apple wants me to do in the way Apple wants me to drive and in the sequence the want me to...
 
#24 ·
What on earth is 'open' about the current AAOS system? There is literally nothing open about it at all unless you want to hack together yet another crappy media playback app.

You're currently completely 'locked into what Google wants you to do in the way Google wants you to drive and in the sequence they want you to' yet you take issue with being 'locked to what Apple wants you to do in the way Apple wants you to drive and in the sequence they want you to'?

Double standards or what...
 
#34 ·
I literally see no benefit to Waze for years. Here in the UK even Apple Maps has better routing, real time traffic and much better speed/safety camera notifications...Other than warnings for safety cameras, the built in Google Maps does it all. It even provides a speeding notification right in the dashboard in front of me where I need it without having to look away :)
 
This post has been deleted
#39 · (Edited)
I have been using this "Carlinkit" device for the last week or so (there is also a "max" version I guess)-- it is much, much better than the built-in system. Presents itself to the car as a CarPlay device and then you connect to it with your phone and it lets you use Android Auto Projected.

The AAP display has a black border around it which is a little annoying, but Waze in dark mode is great and everything runs on your phone so it's a lot faster than the in-car system.

Connecting AA wireless:
Image


And Waze running on actual Android Auto. Note the extra border -- it must be the "AutoKit Ambient" app that supports Android Auto Projected, as the device itself uses the whole screen area available.

Image


I tried this other one as well, and it used the whole screen for AAP, but the aspect ratio was off (looked squashed vertically) and was less stable overall. I want to try a couple more to see if there's one that works best, but the Carlinkit version linked above works really well.

Overall this is such a better experience than trying to use Waze or Google Maps onboard. I really wish Polestar would just support Android Auto Projected out of the box, it's insanity that they support CarPlay but not AAP.