adb steps, and the Google Account you actually drive with (a second work or test account on the same phone is the most common cause of "my settings didn't apply")
adb (Android Debug Bridge — a command-line tool that talks to your phone over USB) on a laptop, version from the platform-tools package. It lets you confirm which packages are installed instead of guessing from menu labels.Menu labels differ between Android versions and between the Google app builds. If a label below does not match your screen exactly, open Settings and use its search box with the same wording — do not assume the setting is missing.
If you are still choosing hardware or planning how long your phone will keep receiving security patches (privacy controls are only meaningful on a supported build), see how to check how many years of updates your Android phone will get.
Example: in Platform Tools on Linux or macOS you run adb version and expect a first line of the form Android Debug Bridge version <version>; on Windows you run .\adb.exe version from the extracted folder.
What to do: record which Google Account is active on the phone, which Android Auto and Google app builds are installed, and which account the car sees. On the phone: Settings → Passwords & accounts → confirm the Google account marked as the one used by Google apps. Then, optionally, connect the phone by USB and run:
adb devices
adb shell pm list packages | grep -i gearhead
adb shell pm list packages | grep -i googlequicksearchbox
adb shell dumpsys package com.google.android.projection.gearhead | grep -m1 versionName
Expected output (identifiers are stable, versions are not):
List of devices attached
<RANDOM_SERIAL> device
package:com.google.android.projection.gearhead
package:com.google.android.googlequicksearchbox
versionName=<version>
Why: com.google.android.projection.gearhead is the Android Auto package and com.google.android.googlequicksearchbox is the Google app that handles voice requests. If the second package is missing or signed in to a different account, every privacy toggle you change later applies to an account the car never uses — this is the single most common false "it worked" result.
How to check: the two package: lines appear and adb devices shows your serial with the word device (not unauthorized). Write the versionName value into your notes file.
Example: your notes file after this step:
2025-xx-xx gearhead=<version> googlequicksearchbox=<version> account=<you@example.com>

What to do: change controls in this order, on the phone, before you start driving.
1. Web & App Activity — Settings → Google → Manage your Google Account → Data & privacy → Web & App Activity. Open "Choose what to save" and decide whether voice searches and assistant interactions are stored. Turn the main switch off if you want the car's requests not attached to your account history.
2. Gemini Apps Activity / your AI chat history control — same Data & privacy page; open the entry for your AI assistant activity and set auto-delete to the shortest period the screen offers. Read the options on your own screen and note the one you picked; the available durations depend on your account and region, so confirm in the product documentation rather than assuming a value.
3. Android Auto in-car behaviour — on the phone: Settings → Connected devices → Android Auto → Customize launcher / Messaging, and disable reading message previews aloud if you do not want message text spoken inside the car with passengers present.
Then verify permissions, because a control is only as good as the permission behind it:
adb shell dumpsys package com.google.android.googlequicksearchbox | grep -i "android.permission.RECORD_AUDIO"
adb shell dumpsys package com.google.android.projection.gearhead | grep -i "android.permission.RECORD_AUDIO"
Expected: a granted=true line for whichever package you allow to listen. granted=false is also a valid end state — it means voice input will not work in the car, which is a legitimate privacy choice.
Why: activity controls decide what is stored after the fact; permissions decide whether the microphone is reachable at all. Changing one without the other leaves a gap — the classic case is activity history switched off while the microphone permission stays granted, so audio still leaves the device for processing.
How to check: reopen Settings → Google → Manage your Google Account → Data & privacy and confirm the switches show the state you just picked. Then open Android Auto → Messaging and confirm "Read messages aloud" is off if that was your choice. Both screens must agree with your notes file.
Example: after step 2 your notes read Web&App Activity=off, AI activity auto-delete=<period shown on screen>, read aloud=off, RECORD_AUDIO granted=true.
For households where the car is shared with children, pair this with the device-level restrictions in how to set up parental controls for AI chat apps on iPhone and Android — account-level controls do not stop a second signed-in account from making requests.

What to do: perform this checklist in the car with the engine on and the phone connected, before you drive.
adb shell dumpsys package com.google.android.googlequicksearchbox | grep -i RECORD_AUDIO still prints the value you recorded.Then open your Google Account activity page on the phone browser and check the most recent entries. Anything logged in the last few minutes is what the car just sent.
Why: settings can be reverted by an app update or by a second account being added during setup, and the only reliable check is to read the state back after a real connection cycle. Reading the activity page confirms what was stored, not just what the toggle claims.
How to check: success looks like a responsive assistant in the car, a settings page that still shows your chosen values after reconnecting, and an activity list you can explain line by line. If any line surprises you, return to step 2 for that single control.
Example: the activity page shows one voice query at the current time and nothing containing message text — that matches a configuration with read-aloud off and history off.
| Control | Where it lives | Safe value for a shared car | Evidence to look for |
|---|---|---|---|
| Web & App Activity | Google Account → Data & privacy | Off, or shortest retention available | No new entries after a query |
| AI assistant activity / auto-delete | Google Account → Data & privacy | Shortest period offered on your screen | Period shown matches notes |
| Read messages aloud | Android Auto → Messaging | Off | No message text spoken |
| Microphone permission | App permissions or `adb dumpsys` | Granted only if you want voice | `granted=true/false` recorded |
Problem. The command line cannot see the phone, so the permission check is impossible.
error: no devices/emulators foundadb kill-server && adb devices and accept the "Allow USB debugging?" dialog on the phone. A device line means you can continue with step 2.Problem. A settings shortcut does not open on your Android build.
Error: Activity not started, unable to resolve Intent { act=android.settings.PRIVACY_SETTINGS flg=0x10000000 }Problem. The assistant answers at home but not in the car.
Can't reach Google at the momentYou now have a dated record of the account, the packages and the three privacy controls that the car actually uses, plus a five-minute checklist you can repeat before any trip. Next, re-run step 3 after every Android Auto or Google app update, and compare the result with your notes file.
Does turning off activity history stop Gemini or the assistant from working in the car?
No. Activity controls govern what is stored in your account afterwards; voice input keeps working as long as the microphone permission stays granted.
Is auto-delete retroactive — will past trips disappear immediately?
Auto-delete applies to future data on a rolling window. What happens to data already stored depends on your account and region — check the documentation shown on that same settings page before relying on it.
Does Android Auto send location to Google even with activity controls off?
Location handling is separate from activity history and depends on device-level location settings and the maps app in use. Verify it in Settings → Location, and treat any specific claim about retention as "check the documentation" for your build.
Do I need adb to do this check?
No. Every control in step 2 is reachable from the phone's Settings app; adb only makes the verification in steps 1 and 3 reproducible and gives you exact strings to compare. If you are comparing assistants for a shared car, the trade-offs are summarised in the AI assistant comparison.
Status: practical guide. Some statements come from vendors; verify in your environment.
Time to complete: 5 minutes You will need: an Android phone with Android Auto installed, the Google app signed in to the same account you use in the car, USB debugging enabled only if you want the optional command-line checks, a USB-C cable for the optional adb steps, and the Google Account you actually drive with (a second work or test account on the same phone is the most common cause of "my settings didn't apply")
Machine data: Citation Map JSON · JSON-LD · Semantic Embeddings — separate stage.
| Entity | Type | Role |
|---|---|---|
| Gemini Android Auto приватность | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| Android Auto Gemini настройки | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| как отключить историю Gemini | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
| Android | платформа/технология | упоминается в заголовке, TL;DR или разделах гайда |
| компания | упоминается в заголовке, TL;DR или разделах гайда | |
| Gemini | тема/инструмент | упоминается в заголовке, TL;DR или разделах гайда |
No independent confirmation is provided; source claims and editorial conclusions are separated below.
| Source | Type | Role |
|---|---|---|
| No external links | — | — |
Cite as: AI Release. Как настроить приватность Gemini в Android Auto: проверка за 5 минут перед поездкой. ai-release.org.