Google’s Gemini Voice Calling on Android Auto Unreliable Ahead of Assistant Sunset
What Happened — Google announced it will retire Google Assistant in September 2026, leaving Gemini as the sole voice‑assistant for Android devices. Early adopters report that Gemini’s hands‑free calling on Android Auto frequently fails with “Something went wrong. Please try again,” forcing drivers to manually interact with their phones.
Why It Matters for Compliance & Audit Readiness
- The loss of a proven, reliable assistant creates a service‑disruption risk that SOC 2‑compliant organizations must anticipate and document.
- Continuous‑compliance programs should map this functional gap to Control CC6.1 (System Operations) and Control CC7.1 (Change Management), ensuring evidence that alternative, auditable call‑handling processes are in place.
- Verisq’s Control Mapping capability can automatically capture the remediation workflow and provide audit‑ready evidence that the organization has mitigated the risk.
Who Is Affected — Consumer‑focused enterprises, fleet operators, and any organization that relies on Android Auto for hands‑free communication (e.g., logistics, field service, ride‑share).
Recommended Actions
- Conduct a gap analysis of voice‑calling functionality against SOC 2 operational controls.
- Implement a fallback procedure (e.g., Bluetooth‑paired device or manual dialing) and document it as part of your incident‑response plan.
- Use continuous‑evidence collection to monitor Gemini call‑success rates and flag deviations for audit review. Source: ZDNet article
Technical Notes — The issue is not a software vulnerability (no CVE) but a product reliability defect in Google’s Gemini AI layer, manifesting as intermittent API failures when invoked through Android Auto. The failure impacts voice‑call initiation and media playback, raising driver‑distraction concerns. Source: same as above