Gemini call issues hit Android and Android Auto users amid transition glitches

At a glance:

• Gemini is failing to make calls via voice commands on Android and Android Auto, showing a generic error message
• Users report the bug affects both in-car and mobile call functionality, with no clear root cause identified
• Switching back to Google Assistant temporarily resolves the issue, but the transition to Gemini remains problematic

Gemini, Google's AI-powered assistant, is experiencing a critical bug that prevents users from making calls through voice commands on both Android and Android Auto platforms. The issue, confirmed by multiple users across Reddit threads this week, manifests as a vague error message stating "Something went wrong. Please try again," disrupting core functionality for drivers and mobile users alike. While initially suspected to be an Android Auto-specific problem, reports indicate the bug extends to standard Android devices, suggesting a deeper integration flaw within Google's ecosystem.

The transition to Gemini on Android Auto has faced several hiccups since its rollout, including inconsistent performance and compatibility issues. This latest bug adds to the growing list of user frustrations, particularly as voice-activated calling is a fundamental feature for hands-free driving. Google has not yet issued an official statement addressing the problem, leaving users to rely on workarounds while awaiting a permanent fix.

Several affected users have found that reverting to Google Assistant restores call functionality, though this is only a temporary solution. The need to downgrade highlights the instability of Gemini's current implementation, raising concerns about its readiness for widespread adoption. Analysts suggest that the bug may stem from a recent update to either the Gemini app or the core Google application, but without concrete evidence, the exact cause remains speculative.

Compounding the issue, some users have observed intermittent visual glitches in Android Auto where the Assistant icon reappears instead of Gemini, even when the latter is active. This inconsistency in branding and interface further underscores the challenges Google faces in transitioning users to its new AI assistant. The randomness of these visual bugs makes them difficult to reproduce, complicating troubleshooting efforts for both users and developers.

The timing of these issues coincides with broader updates to Gemini, including a redesigned macOS app icon and expanded capabilities for controlling Google TV settings. However, these enhancements have done little to offset the negative user experience caused by the call functionality bug. Google's partnership with Paris Hilton to promote Android and AI app development also contrasts sharply with the current technical setbacks, potentially impacting user trust in the platform's reliability.

As the situation develops, users are encouraged to report their experiences and await official patches. The incident serves as a reminder of the complexities involved in integrating AI assistants into existing mobile ecosystems, particularly in safety-critical environments like driving. For now, the workaround of switching back to Google Assistant remains the most viable solution for those impacted by the Gemini call issues.

What happened

Gemini's call functionality failure affects both Android Auto and standard Android devices, with users encountering a generic error message when attempting to place calls via voice commands. The problem was first reported by users on Reddit, who noted that the issue persisted across different vehicle models and Android versions. Unlike typical app-specific bugs, this problem spans multiple platforms, indicating a potential systemic issue within Google's infrastructure.

The error message itself provides little diagnostic information, making it challenging for users to troubleshoot. Google's silence on the matter has left the community speculating about the root cause, with theories ranging from server-side misconfigurations to conflicts with recent app updates. The lack of official communication has further frustrated users who depend on voice commands for daily tasks.

Why it matters

This bug highlights the risks of rolling out AI assistants in environments where reliability is paramount, such as automotive systems. Android Auto users rely on voice commands to minimize distractions while driving, and any disruption to this functionality could pose safety concerns. The issue also reflects broader challenges in transitioning users from established systems like Google Assistant to newer AI models, particularly when core features are compromised.

For Google, the bug could erode confidence in Gemini's readiness for prime time, especially as competitors like Amazon Alexa and Apple Siri continue to refine their own voice-activated ecosystems. The temporary fix of reverting to Google Assistant may be seen as a step backward, undermining the company's efforts to position Gemini as the future of its AI strategy.

What to watch next

Users should monitor official Google channels for updates or patches addressing the call functionality bug. In the meantime, those experiencing issues may need to disable Gemini temporarily and revert to Google Assistant. The incident may also prompt Google to accelerate testing and quality assurance processes for future AI assistant updates, particularly those integrated into safety-critical platforms like Android Auto.

The visual glitches in Android Auto, where the Assistant icon intermittently replaces Gemini, could indicate deeper integration issues that may require a more comprehensive overhaul. Whether these problems will delay further Gemini rollouts or prompt a return to Google Assistant remains to be seen.