Google's partnerships with automakers (OEMs) have evolved from early phone-projection (Android Auto) into several parallel tracks: a deeply embedded operating system (Android Automotive OS / Google built-in), cloud-based generative-AI agents (Gemini / Automotive AI Agent), and a map-data API layer that sits independently of the OS (Google Maps Auto SDK / Places API). Together they form a layered, separable ecosystem. This update verifies cases previously missing or mis-stated — the Renault-Nissan-Mitsubishi Alliance, BMW, Toyota, XPeng, Rivian, Zeekr and Xiaomi — and revises how "depth of cooperation" is classified.

Google's four-layer automotive stack

Google's OEM cooperation is best split into four independently purchasable layers, rather than the loose "three layers" of earlier framing:

  • Android Auto: phone projection that mirrors the handset UI onto the car screen, independent of vehicle compute — the lightest, lowest-barrier form of cooperation.
  • Android Automotive OS (AAOS, open-source / AOSP): automakers customise the OS kernel from open-source code without adopting Google services; BMW chose this path to avoid being "beholden to Google."
  • Google Automotive Services (GAS, marketed as "Google built-in"): a licensed service pack layered on AAOS — Google Maps, Gemini / Google Assistant, the Play Store — requiring a separate commercial contract, the deepest integration.
  • Google Maps Auto SDK / Platform API (standalone map-data layer): the automaker keeps its own OS entirely (not AAOS) and only calls Google Maps' routing, live traffic and place data, building its own UI. This is the emerging 2025–2026 "lightweight, non-binding" model, exemplified by Rivian and XPeng.

This correction matters: XPeng and Rivian were previously lumped into a generic "Google Maps integration," but unlike Volvo or GM they use no AAOS operating system — cooperation is limited to the fourth (data/SDK) layer, with OS sovereignty fully retained by the automaker.

Mainstream OEM status (updated)

OEMCooperation layerLatest status
Volvo CarsAAOS + GAS + GeminiGoogle's preferred reference hardware platform; Gemini replaced Google Assistant in May 2025
通用汽车 GMAAOS + GAS + Gemini (some models drop projection)From Apr 2026, Gemini pushed to ~4M existing vehicles; some new EVs remove Android Auto projection
Ford / LincolnAAOS + GASDebuted on the 2024 Lincoln Nautilus, expanding gradually
Honda / AcuraAAOS + GAS + GeminiAdopted since 2022; Gemini support added in 2025
Hyundai / Kia / GenesisAAOS + Google Maps Platform (Places API)Announced Dec 2024; from 2026 models, North America Kia first
Nissan（雷诺-日产-三菱联盟）AAOS + GAS2018 alliance-wide multi-year deal; 2026 Rogue offers Google built-in on some trims
Renault 雷诺AAOS + AAOS SDVFirst production-ready AAOS SDV case (Trafic e-Tech van); volume production late 2026
大众集团（含保时捷）AAOS (One.Infotainment) + GASPorsche announced a long-term deal in 2023, production mid-decade, keeping a hybrid ecosystem
BMW 宝马AAOS (AOSP, no GAS)Since 2023 uses open-source AAOS on some iDrive 9 cars, deliberately without GAS/Play Store; third-party store (e.g. Aptoide)
Toyota 丰田Android Auto projection onlyRefused a deep tie-up in 2018 over privacy; from 2020 supports only phone-projection Android Auto, no AAOS
Mercedes-Benz 奔驰Google Cloud Automotive AI Agent (not AAOS)2025 CLA debuts a Gemini-powered next-gen MBUX assistant running on in-house MB.OS
PolestarAAOS + GASFirst mass-production AAOS car (2020 Polestar 2); China market uses Meizu Flyme Auto
比亚迪 BYD（海外）GAS (some European models)From 2025, European Atto 2/3 use Google built-in instead of DiLink; not for China-market cars
小鹏 XPENGGoogle Maps Auto SDK (not AAOS, custom UI)July 2026 Munich L03 global premiere; first APAC OEM on Auto SDK; overseas NGP/XPILOT ASSIST use Google Maps data, ex-China only; previously TomTom
RivianGoogle Maps Auto SDK (not AAOS, custom UI)July 2025 launched 'Rivian Navigation with Google Maps' (18-month build); custom UI keeps own charging scores/ABRP; Google Cast/YouTube next
极氪 ZeekrNo Google deal; uses Mapbox2025 Europe navigation built on Mapbox SDK (with Intellias); won 2025 AutoTech Breakthrough award
小米汽车 XiaomiNo official Google dealNo Google services in the official OS; third-party dongles (e.g. WIZCAR M1 Pro) unlock Android Auto/Maps unofficially; enters Europe H2 2027
StellantisAnnounced AAOS, later withdrewAnnounced 2020, withdrew 2022; Uconnect 5 on AAOS without GAS
Qualcomm（芯片伙伴）AAOS scaling partnerAt CES 2026 named lead scaling partner for AAOS; Snapdragon vSoC runs on Google Cloud

Correction: the nature of XPeng's and Rivian's cooperation

An important correction to the earlier report: XPeng and Rivian both use neither Android Automotive OS nor Google built-in. Each retains full OS sovereignty and only embeds Google's routing, live traffic, place data and satellite imagery into its own UI via the standalone Google Maps Auto SDK. This is fundamentally different from the "OS-level, deeply bound to Google" model of Volvo or GM, and sits at the lightest end of the cooperation spectrum. XPeng goes further, feeding that data source into its NGP assisted-driving and XPILOT ASSIST systems — the only known case of Google Maps data used for driver assistance rather than navigation display alone — explicitly limited to markets outside China.

Competitive alternatives: not everyone chooses Google

A meaningful share of automakers actively chose Google's rivals or a fully in-house path. BMW adopts the open-source AAOS kernel for its technical benefits but deliberately strips out GAS to keep data sovereignty and UI control. Toyota, citing privacy concerns since 2018, still accepts only the most basic Android Auto projection and has never conceded AAOS or GAS. Zeekr picked Mapbox over Google in Europe and won an industry navigation award for it, showing Mapbox is a real competitor in the map choices of Chinese challengers going global. Xiaomi's cars currently have no official Google partnership — only unofficial third-party dongles work around Android Auto — and its overseas deliveries do not begin until 2027. Together these cases show that whether to work with Google, and how deeply, is fundamentally a strategic trade-off among data sovereignty, brand differentiation, cost structure and user experience — not an industry default.

Twin-track expansion of Gemini and the Automotive AI Agent

Google is pushing generative AI to automakers along two paths: integrating Gemini directly into AAOS/GAS cars to replace Google Assistant (Volvo first, GM at the largest scale); and, via Google Cloud's Automotive AI Agent, offering non-AAOS automakers (such as Mercedes-Benz) a customisable voice assistant that embeds into their own architecture. In September 2025 Google Cloud deepened its work with Qualcomm, wiring the Agent into the Snapdragon Digital Chassis to build an "edge-to-cloud" hybrid multimodal AI agent.

AAOS evolves toward the software-defined vehicle (SDV)

In March 2026 Google launched AAOS SDV, extending AAOS into a modular architecture covering vehicle-wide domain control, with plans to open-source it to AOSP; Renault's Trafic e-Tech van is the first production-ready case, targeting volume production in late 2026. Qualcomm concurrently introduced the Snapdragon vSoC running on Google Cloud as key infrastructure for scaled deployment.

Counter-trends and Chinese brands' twin-track path

In 2026 GM removed Android Auto projection from some battery-electric models — driven by data sovereignty and connected-vehicle data assets — shifting to an in-house-OS-plus-Gemini hybrid. Chinese brands diverge more sharply: BYD uses Google built-in only on European export cars, XPeng uses the Google Maps SDK only on overseas cars (ex-China), while Zeekr and Xiaomi bypass Google entirely, choosing Mapbox or no official partner respectively. This reflects that Chinese automakers' map and cockpit choices for global markets depend heavily on the specific target market and their own data strategy, not a single path.

Key takeaways

The revised map sorts Google-OEM relationships by "degree of OS-sovereignty ceded" into four tiers: fully bound (Volvo, GM — AAOS+GAS+Gemini), partly bound (BMW — AAOS kernel but no GAS), projection-only (Toyota — Android Auto), and data-layer-only (XPeng, Rivian — Auto SDK, no OS). This finer-grained layering is more directly useful for Chinese automakers weighing their overseas cockpit strategy: a "lightweight, keep-your-own-UI" model like the Google Maps Auto SDK may be the better balance of user experience and data autonomy — which explains XPeng's choice outside China, and Zeekr's and Xiaomi's decision to bypass Google entirely.

References

  1. Android Automotive OS overview | Android for Cars
  2. Android Automotive — Wikipedia
  3. Android for Cars — Google Developers
  4. Car Manufacturers Are Ditching Android Auto In 2026 — Engadget
  5. BMW won't use Google apps when it transitions to Android Automotive — Android Police
  6. BMW brings Android to its cars without giving in to Google — Autoevolution
  7. Android Automotive: Who's partnering with Google? — CarExpert
  8. Google Maps Auto SDK drives new Rivian navigation — IoT Tech News
  9. XPeng Taps Google Maps to Power Navigation and ADAS in Europe
  10. Volvo Cars, Google expand partnership to deploy Gemini AI — WardsAuto
  11. Volvo Cars and Google expand partnership with Gemini — Volvo Media
  12. GM deploys Google Gemini AI to 4 million vehicles — CBT News
  13. GM brings Google Gemini to millions of vehicles — GM News
  14. Ford unveils Android Automotive based in-vehicle platform — SamMobile
  15. Ford's NEW integrated Android Automotive experience — YouTube
  16. Cars with Google Built-In: Everything You Need To Know — Android Headlines
  17. Hyundai Motor Group and Google Collaborate on Software — Hyundai Newsroom
  18. File Manager for Hyundai, Kia, and Genesis Cars — AnExplorer
  19. Renault-Nissan-Mitsubishi and Google join forces — Nissan News
  20. Does the 2026 Nissan Rogue offer Google built-in? — Cardinale Nissan
  21. Beyond Infotainment: Extending AAOS for SDV — Android Developers Blog
  22. CES 2026: Qualcomm Expands Partnerships — Mobility Engineering Tech
  23. Porsche expands partnership with Google — Volkswagen Group
  24. Android Automotive is coming to a Porsche near you — Android Police
  25. BMW To Start Using Android Automotive OS Next Year — Carscoops
  26. Toyota Not Implementing Android Auto Due To Privacy — Reddit/Android
  27. Toyota announces 2020 cars with Android Auto — Reddit/Toyota
  28. Google Cloud Automotive AI Agent & Mercedes-Benz — LinkedIn
  29. Google Cloud's Automotive AI Agent arrives for Mercedes-Benz — Google Blog
  30. Mercedes-Benz and Google Partner on AI-powered Search — Google Cloud Press
  31. Google apps seen on BYD — Reddit/BYD
  32. Will Xpeng's XOS ever switch from TomTom to Google Maps? — Reddit/Xpeng
  33. Rivian taps Google to bring custom maps into its EVs — Yahoo Finance
  34. Rivian and Google partner on Google Cast and YouTube — Facebook/Rivian
  35. Zeekr Navigation System Wins AutoTech Breakthrough — LinkedIn
  36. Zeekr Partners with Mapbox to Elevate Smart Driving — Mapbox
  37. How to get Android Auto on Xiaomi SU7/YU7 (WIZCAR M1) — YouTube
  38. Xiaomi Auto Goes Global: A 'German Exam' That Must Be Won — Gasgoo
  39. An ecosystem approach to the future of automotive — Qualcomm
  40. Xiaomi leads European EV imports from China despite tariffs — LinkedIn
  41. Qualcomm and Google Cloud Deepen Collaboration — Google Cloud Press