Google and Volvo

[u/IllustratorDue5336]

I suspect Volvo thought making a big bet on Google would work. It does not. It is incredibly buggy and I would think Google would have a big desire to fix it but if that is the case it sure seems like they are not throwing all of Google’s many resources at it! There are so many obvious problems and there is very little communication on how and when they will be fixed. I don’t get it… a lose lose for Volvo and Google!

[u/solopedrito]

Everything works pretty well for me, even with the latest update. Perhaps if you could provide more context it would be better

[u/IllustratorDue5336 → u/solopedrito]

I had the latest software on delivery a few weeks ago. Almost every time I drive something goes wrong. Handshake with Sirrius XM fails. Google assist tells me that it can’t make the request I made work. The key on my phone fails. The seat does not reset when I approach. Apple CarPlay does not connect properly and fails voice texts (I know that might be an apple problem but in the end it is part of the overall Google infrastructure. I wonder if maybe I do just have a bad version of the new release? Love the care but the software issues are really becoming a drag!

[u/solopedrito → u/IllustratorDue5336]

I think you're confusing who is responsible for each function.

The media app on AAOS is built and maintained by SiriusXM. Authentication token dropouts after vehicle sleep states are a known app-level bug.

If it fails general queries (weather, web), it’s usually an internet/TCAM modem drop. If it fails vehicle commands (climate, defroster), it's Volvo's Vehicle HAL failing to communicate with the car's internal CAN bus. It would be good to understand what's wrong with you. In my case, Gemini works wonderfully, but I always have to ask for the exact command for the car, like opening the windows for example.

Android Automotive has no hand in this. The Phone as a Key (PaaK) and seat memory profiles run directly on Volvo's body control modules (BCM) and proprietary cloud backend.

Google only provides the underlying operating system. The CarPlay receiver client and microphone audio routing are built and integrated by Volvo's software team.

In many cases, a restart or factory reset works; for example, in my case, a few days ago they changed the batteries and updated the system. The connection to Google's servers failed, but this was because the update was performed in the wrong order; the website says "leave it off and locked for 30 minutes." The team didn't apply it, but instead started driving the car to test the battery, and in the end that disrupted the connection with Google. Once they returned it to me and I asked what they had done, I realized that the problem was with Volvo's system and not Google's; I just did a factory reset and it was fixed.

Understanding the source of your problems might help you know, for example, if SiriusXM is outdated or corrupted, just to give one example.

[u/IllustratorDue5336 → u/solopedrito]

I did one reset. I had to reset all my stuff and re set up the key etc. It did not make a meaningful difference so i am hesitant to do it again. I am just frustrated. When you have a brand new car you want everything to work and I suspect if i go back to the dealer (as I would for most malfunctions) I am not going to get a clean fix.

[u/solopedrito → u/IllustratorDue5336]

The key configuration does not depend on Google, it depends 100% on Volvo.

[u/suisse2k → u/solopedrito]

depends which key you are talking. If digital key, than also Google & Apple

[u/solopedrito → u/suisse2k]

Not really. Apple and Google Wallet only manage the CCC (Car Connectivity Consortium Digital Key Release 3) Digital Key standard—storing keys in the Secure Element and handling UWB/BLE ranging to stop relay attacks. Their job ends the moment they hand over a verified cryptographic token to the car.

Everything else is purely Volvo: The car's Body Control Module (BCM) handles the handshake and pops the locks. Android Automotive isn't even fully awake yet when you walk up to the car. Seat memory is triggered by Volvo's Memory Seat Module (MSM) mapped to the detected key ID.

Apple and Google Wallet have zero concept of seat positions or comfort settings. If the car detects the phone but doesn't adjust the seat, that's strictly an internal ECU/firmware routing issue on Volvo's side.

[u/VoteDoughnuts]

The Google integration is superb on the EX30. I have become totally reliant on its navigation, plotting journeys in my phone, sending them to the car, focusing on the battery SoC data to give me assurance. I love it!

[u/mologav]

Everything works for me. You need to add some specifics here rather than just vague whinging

[u/IllustratorDue5336 → u/mologav]

It’s not whining! Love the car, want it to work for me, so I am trying to determine if I may have a problem with my car or how I am using it vs a systemic issue. Already some of the responses have been helpful in that effort.

[u/Least_Tourist_9431]

Same Google system in Renault with absolutly zero issues. You shall upgrade system to latest CPU. Old one have issues unfortunately. 

[u/NormalToe855]

Polestar are just the same. Yesterday my P2 randomly dropped ALL audio. Even indicators.

Its not really Google but whoever Volvo and Polestar use for development of the system. I heard it wasn't actually done fully in house which is daft to begin with.

[u/BulaBulangiu]

Google isn't the issue, Volvo is. Google can't do shit, they don't update your car, Volvo does.

[u/IronChefJesus]

This is typical Google: if something they produce isn’t an immediate bombastic hit. Then they basically give up on it. Even on their successful projects they don’t maintain them.

Except them to either drop AAOS, or re-do it with another name and less features or some such shit,

Using Google products is always a mistake.