Announcing our new "CLUBS" section where you can join or create a Rivian club or group! You can use this new feature to conveniently plan and discuss local events, gatherings or other club/group related topics.
So we encourage you to join (or start) special-interest and regional-based Rivian clubs at: https://www.rivianforums.com/forum/group-categories/clubs-groups.1/
So you're telling me you'd rather mirror your android phone screen to avoid a one time sign in/syncing of your google account to the native android system in your vehicle???
I think that settles the debate that AA/CP philes will never accept a native system, even if it's a better version made by the same company.....Google is sitting there shaking their heads, saying, they do realize that AA was only a temporary hack solution until we could build and sell/implement Android Automotive, right? No vehicle with Android Automotive in the future will have AA functionality, that's the literal definition of unnecessary redundancy.
This also debunks all the arguments before that offering AA/CP doesn't mean a maker can't continue building their own system. Why would they do that, when you won't even use the native version of Android Automotive??
That's focused on the present. I'm talking in general, when everything on AA is on AAOS as it's intended to be. Google would look like utter fools if people with AAOS were using AA long term.There's no Waze in the play store for AAOS, for example. AA would let people use Waze.
I'm not talking about literally right now as things stand with the state of each system. I'm talking philosophically, or in the future when AAOS does have everything AA does (because that's the point of it). AAOS is just as immature as Rivian's system, because it's still early days, but it's still a fundamentally better way to deliver a UX than a phone mirroring punting.My wife has a 2022 Volvo XC40 Recharge P8 (BEV) with AAOS. I can tell you from experience that it is only good at doing a couple of things well relative to AA, like integrating charging stations on en route and estimating your charge on arrival. Everything else is either non-existent or subpar relative to AA.
The play store is extremely limited on AAOS and the apps don't work the same way as they do on AA or your phone.
Even apps with accounts sync differently (assuming they sync which is not always the case even when you are connected to good wifi at home) and don't have all the features. As an example, Prime Music app on AAOS does not sync your playlists at all. Waze is not offered as mentioned before.
While the XC40 is a great BEV to drive and is very comfortable, the AAOS spoils the experience significantly. I am not sure if the phone app is linked to the AAOS issues, but the phone app only gives you 3 things, lock/unlock doors, charge percentage, and climatize command. My 2015 BMW i3 app offered a lot more settings and info.
In short, I would take Android Auto any day over AAOS.
It's definitely not 1, as RJ responded to a forum member and unequivocally shot down the notion of Carplay ever coming to Rivian. I don't think it's 3 either.One assumes that when Amazon offered to buy a gajillion vans and singlehandedly vouched for the Rivian brand pre-IPO they asked for a few things. Or perhaps Rivian offered/promised a few things as part of not being total jerks.
Whatever the circumstance, there are three reasons Rivian might not have CarPlay:
1, The code is a PITA and they just haven't gotten to it yet.
2, They plan to make their own Apps and App Store and don't want to be beholden to Apple.
3, They plan to sell the space to whomever will offer the most and Alexa/Amazon Music and Spotify won the bid for the time being.
It's 2 or 3, probably 3 for the time being.
Hilarious that you think Google actually has a holistic strategy. The only product Google actually has a strategy for is Search and Ads.Google is sitting there shaking their heads, saying, they do realize that AA was only a temporary hack solution until we could build and sell/implement Android Automotive, right? No vehicle with Android Automotive in the future will have AA functionality, that's the literal definition of unnecessary redundancy.
This also debunks all the arguments before that offering AA/CP doesn't mean a maker can't continue building their own system. Why would they do that, when you won't even use the native version of Android Automotive??
GM is shipping AAOS now and it works just fine with AA.That's because there is only one vehicle from an obscure brand most people have never heard of using it right now. However, several automakers are signed up to implement in mass over the next couple years. It will be a transition, but there is no reason to believe that every app available and used in AA won't be available in the AAOS app store. AAOS was built to replace AA.
This is one argument I do see against AA/CP... how do they scale to the various displays? It looks a bit silly on the RAM 12" screen as well.I think they should have made the icon buttons bigger.
Yes. I would. I don't have to synchronize data between multiple devices. I don't have to setup multiple cars with my preferences. My phone is always on me. It has the apps, accounts, and data in one place. It moves with me from car to car.So you're telling me you'd rather mirror your android phone screen to avoid a one time sign in/syncing of your google account to the native android system in your vehicle???
I think that settles the debate that AA/CP philes will never accept a native system, even if it's a better version made by the same company.....Google is sitting there shaking their heads, saying, they do realize that AA was only a temporary hack solution until we could build and sell/implement Android Automotive, right? No vehicle with Android Automotive in the future will have AA functionality, that's the literal definition of unnecessary redundancy.
This also debunks all the arguments before that offering AA/CP doesn't mean a maker can't continue building their own system. Why would they do that, when you won't even use the native version of Android Automotive??
Yes, though it's clearly not a "first-class" support like Spotify. If Amazon was pulling the infotainment strings you'd better believe they would be making a fuss about a direct competitor being the primary streaming music service.Amazon Music is supported through Alexa integration. Just fyi.
Native app support for Amazon Music is preferred, no doubt.Yes, though it's clearly not a "first-class" support like Spotify. If Amazon was pulling the infotainment strings you'd better believe they would be making a fuss about a direct competitor being the primary streaming music service.
I'm not talking about literally right now as things stand with the state of each system. I'm talking philosophically, or in the future when AAOS does have everything AA does (because that's the point of it). AAOS is just as immature as Rivian's system, because it's still early days, but it's still a fundamentally better way to deliver a UX than a phone mirroring punting.
Put some portal axles on it and you'd be good to go.…can we hack the hell out of this rig and make overlanders?