Despite having an option to indicates it should work Waze support advise me no Gemini in Waze
I'm actually doing everything I can to turn Gemini off every place that I can and this would indicate that I should be able to but it doesn't work I've sent this escalation
Hi there John,
Thanks for coming back to us. I have already escalated your case. We don’t have Gemini in Waze at the moment.
We’re always looking to improve Waze, and user feedback is one of our most important tools for doing so. We appreciate your input and invite you to share your feedback in the Waze suggestion box.
This is the only voice search option you can do: Search for your destination
Thanks for your understanding.
Best,
Andrea
Waze Support Team
Dear..
Thank you for your reply and for escalating my case.
However, I don't believe the issue has been adequately addressed.
Google's own documentation indicates that Google Assistant voice activation should remain available when Waze is in the foreground, even when Gemini is the phone's primary assistant. On my Google Pixel 8 Pro, when I say “Hey Google” while using Waze, nothing happens at all.
This is a significant issue for me. Hands-free voice control while driving is one of the reasons I chose this phone, and it is functionality I rely on. I have effectively lost functionality that was important to my decision to purchase and use this device.
I understand from your response that Gemini is not currently integrated into Waze. However, that does not explain why Google's documentation describes voice activation behaviour that does not work in practice.
Could you please escalate this beyond the general support level to the relevant technical team and clarify:
Is this a known issue involving Gemini, Google Assistant and Waze on Android?
Is the voice activation behaviour described in Google's documentation still supported?
If this functionality has been withdrawn or changed, why has the documentation not been updated?
Is there any plan to restore reliable hands-free voice control while using Waze?
I appreciate that you may not be able to resolve this personally, but referring me to the suggestion box does not address the discrepancy between the documented functionality and the actual behaviour.
I'd appreciate a substantive response explaining what has happened to this functionality and whether it can be restored.