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)
| OEM | Cooperation layer | Latest status |
|---|---|---|
| Volvo Cars | AAOS + GAS + Gemini | Google's preferred reference hardware platform; Gemini replaced Google Assistant in May 2025 |
| 通用汽车 GM | AAOS + GAS + Gemini (some models drop projection) | From Apr 2026, Gemini pushed to ~4M existing vehicles; some new EVs remove Android Auto projection |
| Ford / Lincoln | AAOS + GAS | Debuted on the 2024 Lincoln Nautilus, expanding gradually |
| Honda / Acura | AAOS + GAS + Gemini | Adopted since 2022; Gemini support added in 2025 |
| Hyundai / Kia / Genesis | AAOS + Google Maps Platform (Places API) | Announced Dec 2024; from 2026 models, North America Kia first |
| Nissan（雷诺-日产-三菱联盟） | AAOS + GAS | 2018 alliance-wide multi-year deal; 2026 Rogue offers Google built-in on some trims |
| Renault 雷诺 | AAOS + AAOS SDV | First production-ready AAOS SDV case (Trafic e-Tech van); volume production late 2026 |
| 大众集团（含保时捷） | AAOS (One.Infotainment) + GAS | Porsche 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 only | Refused 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 |
| Polestar | AAOS + GAS | First 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 |
| 小鹏 XPENG | Google 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 |
| Rivian | Google 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 |
| 极氪 Zeekr | No Google deal; uses Mapbox | 2025 Europe navigation built on Mapbox SDK (with Intellias); won 2025 AutoTech Breakthrough award |
| 小米汽车 Xiaomi | No official Google deal | No Google services in the official OS; third-party dongles (e.g. WIZCAR M1 Pro) unlock Android Auto/Maps unofficially; enters Europe H2 2027 |
| Stellantis | Announced AAOS, later withdrew | Announced 2020, withdrew 2022; Uconnect 5 on AAOS without GAS |
| Qualcomm（芯片伙伴） | AAOS scaling partner | At 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
- Android Automotive OS overview | Android for Cars
- Android Automotive — Wikipedia
- Android for Cars — Google Developers
- Car Manufacturers Are Ditching Android Auto In 2026 — Engadget
- BMW won't use Google apps when it transitions to Android Automotive — Android Police
- BMW brings Android to its cars without giving in to Google — Autoevolution
- Android Automotive: Who's partnering with Google? — CarExpert
- Google Maps Auto SDK drives new Rivian navigation — IoT Tech News
- XPeng Taps Google Maps to Power Navigation and ADAS in Europe
- Volvo Cars, Google expand partnership to deploy Gemini AI — WardsAuto
- Volvo Cars and Google expand partnership with Gemini — Volvo Media
- GM deploys Google Gemini AI to 4 million vehicles — CBT News
- GM brings Google Gemini to millions of vehicles — GM News
- Ford unveils Android Automotive based in-vehicle platform — SamMobile
- Ford's NEW integrated Android Automotive experience — YouTube
- Cars with Google Built-In: Everything You Need To Know — Android Headlines
- Hyundai Motor Group and Google Collaborate on Software — Hyundai Newsroom
- File Manager for Hyundai, Kia, and Genesis Cars — AnExplorer
- Renault-Nissan-Mitsubishi and Google join forces — Nissan News
- Does the 2026 Nissan Rogue offer Google built-in? — Cardinale Nissan
- Beyond Infotainment: Extending AAOS for SDV — Android Developers Blog
- CES 2026: Qualcomm Expands Partnerships — Mobility Engineering Tech
- Porsche expands partnership with Google — Volkswagen Group
- Android Automotive is coming to a Porsche near you — Android Police
- BMW To Start Using Android Automotive OS Next Year — Carscoops
- Toyota Not Implementing Android Auto Due To Privacy — Reddit/Android
- Toyota announces 2020 cars with Android Auto — Reddit/Toyota
- Google Cloud Automotive AI Agent & Mercedes-Benz — LinkedIn
- Google Cloud's Automotive AI Agent arrives for Mercedes-Benz — Google Blog
- Mercedes-Benz and Google Partner on AI-powered Search — Google Cloud Press
- Google apps seen on BYD — Reddit/BYD
- Will Xpeng's XOS ever switch from TomTom to Google Maps? — Reddit/Xpeng
- Rivian taps Google to bring custom maps into its EVs — Yahoo Finance
- Rivian and Google partner on Google Cast and YouTube — Facebook/Rivian
- Zeekr Navigation System Wins AutoTech Breakthrough — LinkedIn
- Zeekr Partners with Mapbox to Elevate Smart Driving — Mapbox
- How to get Android Auto on Xiaomi SU7/YU7 (WIZCAR M1) — YouTube
- Xiaomi Auto Goes Global: A 'German Exam' That Must Be Won — Gasgoo
- An ecosystem approach to the future of automotive — Qualcomm
- Xiaomi leads European EV imports from China despite tariffs — LinkedIn
- Qualcomm and Google Cloud Deepen Collaboration — Google Cloud Press
Google 与汽车主机厂（OEM）的合作，已从早期的手机投屏（Android Auto），演变为深度嵌入式操作系统（Android Automotive OS / Google built-in）、云端生成式 AI 代理（Gemini / Automotive AI Agent），以及独立于操作系统层的地图数据 API（Google Maps Auto SDK / Places API）等多条并行主线，共同构成一个分层、可拆分的合作生态。本次更新在原有欧美日韩主流车企基础上，补充核实了雷诺-日产-三菱联盟、宝马、丰田、小鹏、Rivian、极氪、小米等此前未覆盖或存在事实偏差的案例，并修正了对"合作深度"的分类方式。
Google 汽车合作的四层技术栈
结合最新检索，Google 对 OEM 的合作应拆分为四个可独立采购的层级，而非笼统的三层：
- Android Auto：手机投屏方案，把手机界面镜像到车机屏幕，不依赖车辆算力，是最轻量、门槛最低的合作形式。
- Android Automotive OS（AAOS，开源版 / AOSP）：车企基于开源代码自行定制车机内核，但不必接入 Google 服务；宝马即选择这一路径以避免"受制于 Google"。
- Google Automotive Services（GAS，市场名 "Google built-in"）：叠加在 AAOS 之上的授权服务包，含 Google 地图、Gemini / Google 助手、Play 商店，需与 Google 单独签署商业合同，是最深度的整车集成模式。
- Google Maps Auto SDK / Platform API（独立地图数据层）：车企完全保留自研车机系统（非 AAOS），仅调用 Google 地图的路由、实时路况、地点数据能力，自建界面与体验；这是 2025–2026 年新兴的"轻量级、非绑定式"合作模式，代表案例为 Rivian 与小鹏。
这一分层修正很重要：此前把小鹏、Rivian 归入笼统的"Google Maps 集成"，但需明确它们与沃尔沃 / 通用等没有采用 AAOS 操作系统，合作仅限于第四层的数据 / SDK 调用，车机主权仍完全归车企自身。
主流 OEM 合作现状一览（更新版）
| OEM | 合作层级 | 最新进展 |
|---|---|---|
| Volvo Cars | AAOS + GAS + Gemini | Google 首选参考硬件平台；2025 年 5 月 Gemini 替代 Google 助手 |
| 通用汽车 GM | AAOS + GAS + Gemini（部分车型收缩投屏） | 2026 年 4 月起向约 400 万辆存量车推送 Gemini；同时部分新 EV 移除 Android Auto 投屏 |
| Ford / Lincoln | AAOS + GAS | 2024 款林肯 Nautilus 首发，逐步扩展 |
| Honda / Acura | AAOS + GAS + Gemini | 2022 年起采用，2025 年新增 Gemini 支持 |
| Hyundai / Kia / Genesis | AAOS + Google Maps Platform（Places API） | 2024 年 12 月宣布，2026 新车型起搭载，北美 Kia 率先落地 |
| Nissan（雷诺-日产-三菱联盟） | AAOS + GAS | 2018 年联盟三方与 Google 达成多年期协议；2026 款 Nissan Rogue 部分车型已提供 Google built-in |
| Renault 雷诺 | AAOS + AAOS SDV | 2026 年成为 AAOS SDV 首个生产就绪案例（Trafic e-Tech 商用车），年末量产 |
| 大众集团（含保时捷） | AAOS（One.Infotainment）+ GAS | 保时捷 2023 年宣布长期合作，'十年中期'投产，保留混合生态 |
| BMW 宝马 | AAOS（AOSP 开源版，不含 GAS） | 2023 年起在 iDrive 9 部分车型采用开源 AAOS，刻意不引入 Google 服务与 Play 商店，改用第三方商店（如 Aptoide），保留数据主权 |
| Toyota 丰田 | 仅 Android Auto 投屏 | 2018 年因隐私顾虑拒绝深度合作，2020 款起仅支持手机投屏级 Android Auto，至今未采用 AAOS |
| Mercedes-Benz 奔驰 | Google Cloud Automotive AI Agent（非 AAOS） | 2025 年 CLA 首发 Gemini 驱动的新一代 MBUX 虚拟助手，运行于自研 MB.OS |
| Polestar | AAOS + GAS | 首款量产 AAOS 车型（2020 Polestar 2）；中国市场转用魅族 Flyme Auto |
| 比亚迪 BYD（海外） | GAS（部分欧洲车型） | 2025 年起欧洲 Atto 2 / Atto 3 等车型以 Google built-in 替代 DiLink；中国本土车型不适用 |
| 小鹏 XPENG | Google Maps Auto SDK（非 AAOS，自建界面） | 2026 年 7 月慕尼黑 L03 全球首发，亚太首个搭载 Auto SDK 的车企；海外 NGP / XPILOT ASSIST 接入 Google 地图数据，仅限中国以外；此前用 TomTom |
| Rivian | Google Maps Auto SDK（非 AAOS，自建界面） | 2025 年 7 月推出 'Rivian Navigation with Google Maps'，历时 18 个月，自建界面并保留自有充电评分 / ABRP；同步推进 Google Cast / YouTube |
| 极氪 Zeekr | 未与 Google 合作，采用 Mapbox | 2025 年欧洲导航由 Zeekr Technology Europe 联合 Intellias 基于 Mapbox SDK 开发，获 2025 AutoTech Breakthrough 年度导航应用奖 |
| 小米汽车 Xiaomi | 未与 Google 官方合作 | 官方车机未内置 Google 服务；市场有第三方外接盒（如 WIZCAR M1 Pro）变通解锁 Android Auto / Google Maps，但非官方合作；2027 下半年才进入欧洲 |
| Stellantis | 曾宣布 AAOS，后撤回 | 2020 年宣布、2022 年撤回；Uconnect 5 基于 AAOS 但不含 GAS |
| Qualcomm（芯片伙伴） | AAOS 规模化部署伙伴 | 2026 CES 成为 AAOS '主力规模化合作伙伴'，联合推出运行于 Google Cloud 的 Snapdragon vSoC |
纠错：小鹏与 Rivian 的合作性质
需对此前报告作出重要修正：小鹏与 Rivian 均未采用 Android Automotive OS 或 Google built-in，两者车机的操作系统主权完全保留在自己手中，仅通过 Google Maps Auto SDK 这一独立地图数据接口，把 Google 的路由、实时路况、地点数据、卫星影像能力"嵌入"到自研界面中。这与沃尔沃、通用等"操作系统层深度绑定 Google"完全不同，属于合作谱系中最轻的一端。小鹏进一步把该数据源接入其 NGP 智能辅助驾驶与 XPILOT ASSIST 系统，是目前已知唯一将 Google 地图数据用于驾驶辅助（而非仅导航显示）的案例，且范围明确限定在中国以外市场。
竞争性替代：并非所有车企都选择 Google
检索进一步发现，相当一部分车企主动选择了 Google 的竞争对手或完全自研：宝马采用开源版 AAOS 内核以获取技术红利，却刻意剥离 GAS 服务包以保留数据主权与界面自主；丰田自 2018 年因隐私顾虑，至今仅接受最基础的 Android Auto 投屏，从未松口 AAOS 或 GAS；极氪在欧洲选择 Mapbox 而非 Google，并凭此斩获行业导航应用奖项，表明 Mapbox 在中国新势力出海地图选型中具备实质竞争力；小米汽车目前完全没有官方 Google 合作，仅有非官方第三方硬件方案变通实现 Android Auto，且海外交付计划要到 2027 年才启动。这些案例共同说明，"是否与 Google 合作""合作到何种深度"本质上是车企在数据主权、品牌差异化、成本结构与用户体验之间的战略取舍，并非行业标准动作。
Gemini 与 Automotive AI Agent 的双轨扩张
Google 正通过两条路径向车企输出生成式 AI：一是把 Gemini 直接整合进 AAOS / GAS 车型、替代 Google 助手（沃尔沃率先、通用规模最大）；二是通过 Google Cloud 的 Automotive AI Agent，向非 AAOS 车企（如奔驰）输出可嵌入自研架构的定制化语音助手能力。2025 年 9 月 Google Cloud 与高通深化合作，将该 Agent 与 Snapdragon 数字底盘打通，构建"边缘到云端"的混合多模态 AI 代理能力。
AAOS 向"软件定义汽车"（SDV）演进
2026 年 3 月 Google 发布 AAOS SDV，将 AAOS 扩展至覆盖整车域控制的模块化架构，并计划开源至 AOSP；雷诺 Trafic e-Tech 商用车是首个生产就绪案例，计划 2026 年末量产。高通同步推出运行于 Google Cloud 的 Snapdragon vSoC，作为规模化部署的关键基础设施。
逆向趋势与中国品牌的双轨路径
通用汽车 2026 年在部分纯电车型上移除 Android Auto 投屏，出于数据主权与车联网数据资产考量，转向"自研系统 + Gemini"混合模式。中国品牌分化更明显：比亚迪仅在欧洲出海车型采用 Google built-in，小鹏仅在海外车型采用 Google Maps SDK（且限定中国以外），而极氪、小米则完全绕开 Google，分别选择 Mapbox 或暂无官方合作，反映出中国车企出海的地图 / 车机选型高度依赖具体目标市场与自身数据战略，并非统一路径。
关键结论
修正后的合作图谱显示，Google 与 OEM 的关系可按"操作系统主权让渡程度"分为四档：完全绑定（沃尔沃、通用，AAOS+GAS+Gemini）、部分绑定（宝马，AAOS 内核但拒绝 GAS）、纯投屏（丰田，仅 Android Auto）、纯数据层（小鹏、Rivian，仅 Auto SDK、不涉及操作系统）。这一更细粒度的分层，对中国车企评估出海车机战略更具参考价值——采用 Google Maps Auto SDK 这类"轻量、可保留自研界面主权"的合作模式，可能是兼顾用户体验与数据自主权的更优选择，这也解释了小鹏在中国以外市场的选择逻辑，以及极氪、小米完全绕开 Google 的战略考量。
参考资料
- Android Automotive OS overview | Android for Cars
- Android Automotive — Wikipedia
- Android for Cars — Google Developers
- Car Manufacturers Are Ditching Android Auto In 2026 — Engadget
- BMW won't use Google apps when it transitions to Android Automotive — Android Police
- BMW brings Android to its cars without giving in to Google — Autoevolution
- Android Automotive: Who's partnering with Google? — CarExpert
- Google Maps Auto SDK drives new Rivian navigation — IoT Tech News
- XPeng Taps Google Maps to Power Navigation and ADAS in Europe
- Volvo Cars, Google expand partnership to deploy Gemini AI — WardsAuto
- Volvo Cars and Google expand partnership with Gemini — Volvo Media
- GM deploys Google Gemini AI to 4 million vehicles — CBT News
- GM brings Google Gemini to millions of vehicles — GM News
- Ford unveils Android Automotive based in-vehicle platform — SamMobile
- Ford's NEW integrated Android Automotive experience — YouTube
- Cars with Google Built-In: Everything You Need To Know — Android Headlines
- Hyundai Motor Group and Google Collaborate on Software — Hyundai Newsroom
- File Manager for Hyundai, Kia, and Genesis Cars — AnExplorer
- Renault-Nissan-Mitsubishi and Google join forces — Nissan News
- Does the 2026 Nissan Rogue offer Google built-in? — Cardinale Nissan
- Beyond Infotainment: Extending AAOS for SDV — Android Developers Blog
- CES 2026: Qualcomm Expands Partnerships — Mobility Engineering Tech
- Porsche expands partnership with Google — Volkswagen Group
- Android Automotive is coming to a Porsche near you — Android Police
- BMW To Start Using Android Automotive OS Next Year — Carscoops
- Toyota Not Implementing Android Auto Due To Privacy — Reddit/Android
- Toyota announces 2020 cars with Android Auto — Reddit/Toyota
- Google Cloud Automotive AI Agent & Mercedes-Benz — LinkedIn
- Google Cloud's Automotive AI Agent arrives for Mercedes-Benz — Google Blog
- Mercedes-Benz and Google Partner on AI-powered Search — Google Cloud Press
- Google apps seen on BYD — Reddit/BYD
- Will Xpeng's XOS ever switch from TomTom to Google Maps? — Reddit/Xpeng
- Rivian taps Google to bring custom maps into its EVs — Yahoo Finance
- Rivian and Google partner on Google Cast and YouTube — Facebook/Rivian
- Zeekr Navigation System Wins AutoTech Breakthrough — LinkedIn
- Zeekr Partners with Mapbox to Elevate Smart Driving — Mapbox
- How to get Android Auto on Xiaomi SU7/YU7 (WIZCAR M1) — YouTube
- Xiaomi Auto Goes Global: A 'German Exam' That Must Be Won — Gasgoo
- An ecosystem approach to the future of automotive — Qualcomm
- Xiaomi leads European EV imports from China despite tariffs — LinkedIn
- Qualcomm and Google Cloud Deepen Collaboration — Google Cloud Press