TL;DR
A widespread bug is preventing Gemini from making phone calls on Android and Android Auto, disrupting hands-free calling for thousands of users. The issue, first reported in mid-June 2026, highlights ongoing instability in Google’s transition from Google Assistant to Gemini as the default digital assistant on Android devices.
What Happened
On Monday, June 15, 2026, users began flooding forums with reports that Gemini — Google’s replacement for Google Assistant — had suddenly stopped placing calls on Android phones and Android Auto. The outage appears to affect both direct dialing via voice commands and contact-based calling, with some users reporting that Gemini either fails to initiate the call or returns an error message without connecting. The disruption is particularly acute for Android Auto users, who rely on hands-free calling while driving.
Key Facts
- The bug was first reported on June 15, 2026, with complaints surging on Google Issue Tracker, Reddit, and XDA Developers forums.
- Android Auto users are disproportionately affected, as the feature is critical for hands-free driving compliance in jurisdictions with strict distracted-driving laws.
- Google confirmed the issue on June 16 via a Google Support post, stating the company is “investigating reports that Gemini is unable to complete phone calls on Android and Android Auto.”
- The problem appears to be server-side, not a client update, meaning users cannot fix it by clearing cache, reinstalling the app, or rebooting their devices.
- This marks the third major Gemini-related outage in 2026, following a May 12 incident where Gemini failed to send text messages and an April 3 event where the assistant could not set timers or alarms.
- The transition from Google Assistant to Gemini began in early 2025, with Google mandating Gemini as the default for new Android devices starting January 2026.
- Affected devices include Pixel 9, Samsung Galaxy S26, and OnePlus 13 series phones running Android 16.
Breaking It Down
The core problem is that Gemini, which relies on Google’s cloud-based large language models (LLMs) to process voice commands, appears to be failing at a basic telephony function that Google Assistant handled flawlessly for years. Unlike Assistant, which processed call commands locally or through a lightweight cloud API, Gemini routes voice requests through a more complex AI pipeline. When that pipeline breaks — as it did on June 15 — the entire calling feature collapses.
According to Google’s own support documentation, Gemini processes phone calls by first transcribing the voice command, then interpreting the intent via its LLM, and finally executing the call through Android’s telecom API. The June 15 bug likely disrupts the intent-interpretation stage, causing Gemini to either misinterpret the command or fail to pass it to the telecom layer.
This architectural complexity creates a single point of failure. Google Assistant’s calling feature had an uptime of 99.97% over its final two years, according to internal metrics leaked to Android Authority in March 2026. Gemini’s uptime for the same function is now estimated at 98.2% — a seemingly small drop that translates to roughly 6.5 days of cumulative downtime per year for heavy users. For a feature as essential as making phone calls, that is unacceptable.
The timing is particularly damaging for Google’s automotive ambitions. Android Auto is installed in over 200 million vehicles worldwide, according to Google’s 2025 I/O presentation. Automakers like Ford, GM, and Volkswagen have integrated Android Auto as a core infotainment feature. When hands-free calling fails, it undermines the safety value proposition that Google has marketed heavily since 2023, when it began positioning Android Auto as a “driver-first” platform.
The May 12 texting outage and the April 3 timer/alarm failure form a pattern: each incident affects a different core function, suggesting that Google’s quality assurance process is not catching regressions before they reach users. The June 15 calling bug is the most disruptive yet because it involves real-time communication — users cannot simply wait for a fix to check their messages or set a reminder.
What Comes Next
- Google’s fix timeline: Based on previous Gemini outages, a server-side fix typically takes 48–72 hours. If the calling bug is more complex, users may face disruption until June 18 or later. Google has not yet provided an estimated resolution time.
- Potential rollback option: If the fix is delayed beyond 72 hours, Google may temporarily revert Gemini to Google Assistant for calling functions only — a partial rollback that would signal deep architectural issues. This happened during the May 12 texting outage, when Google rerouted SMS commands to Assistant for 36 hours.
- Regulatory scrutiny: The National Highway Traffic Safety Administration (NHTSA) has previously warned automakers about unreliable hands-free systems. A formal complaint from Consumer Reports or AAA could trigger an investigation into whether Android Auto’s calling reliability meets safety standards.
- Developer response: Independent developers on XDA are already working on a Magisk module that bypasses Gemini for telephony, routing voice call commands directly to Android’s native dialer. This could gain traction if Google’s fix is slow.
The Bigger Picture
This incident is a case study in AI Transition Risk — the danger of replacing a proven, specialized system with a more powerful but less reliable general-purpose AI. Google’s move from Google Assistant to Gemini mirrors similar transitions at Microsoft (Cortana to Copilot) and Amazon (Alexa to Alexa+LLM) . In each case, the company prioritizes AI capability over reliability, assuming that users will tolerate occasional failures for access to advanced features. But telephony is not a “nice-to-have” feature; it is a core utility that must work every time.
The second trend is Single-Threaded Dependency. By routing all voice commands — calls, texts, timers, navigation — through a single Gemini pipeline, Google creates a system where one bug can paralyze multiple functions. The April 3 timer failure and June 15 calling failure both stem from this architecture. A more resilient design would separate critical telephony functions into a dedicated, low-latency pathway, reserving the LLM for complex queries like “find the nearest Italian restaurant and call them.”
Finally, this story highlights the Automotive Safety Backlash brewing against AI assistants. Automakers have spent years convincing regulators that hands-free systems are safe. Every high-profile failure — especially one that affects calling, a core safety tool — gives ammunition to critics who argue that drivers should not rely on AI intermediaries for essential vehicle functions.
Key Takeaways
- [Core Failure]: Gemini cannot place phone calls on Android or Android Auto as of June 15, 2026, due to a server-side bug in its intent-interpretation pipeline.
- [Affected Users]: The outage impacts all Android 16 devices with Gemini as the default assistant, with Android Auto users facing the most severe disruption.
- [Pattern of Instability]: This is the third major Gemini outage in 2026, following failures in texting (May 12) and timers/alarms (April 3), indicating systemic quality issues.
- [Safety Implications]: The bug undermines hands-free calling, a critical safety feature in vehicles, and could attract regulatory attention from NHTSA and consumer advocacy groups.
