Ever since I switched over from Google Maps I’ve been driving with Waze as my Android Auto default. So when Google announced five new AI features for Waze on July 13, I thought my newly adopted app was about to get even better. The only problem is, once I checked what was actually live for me in the US, I had to temper my enthusiasm, and the feature I was most curious about didn’t work (yet).
Two features you can’t even test yet
They are closed behind beta or border.
Google’s Your announcement lists five changes, part of the same Gemini push that revamped Google Maps, but two of them aren’t available at all to most US drivers. Motorcycle mode uses AI to navigate narrow bridges, shoulder ends, and other hazards specific to two wheels, but it’s only running in Argentina, Brazil, Colombia, Malaysia, Mexico, Peru, and the Philippines. I don’t ride a motorcycle, and even if I did, I still couldn’t turn it on.
Gemini-powered destination searches, where you tap the Search Voice icon and ask something like “Find me a coffee shop that’s open right now,” are limited to Waze’s beta community. When I checked the Play Store to see if I could join, it told me plainly: the beta program is full, so it’s over.
That leaves three features every American driver can actually switch on with the latest Waze update: personalized navigation, less chatty mode, and interactive road reporting. Only two were worth my time.
The less chatty mode is the clear winner.
Fewer “in 800 feet” obstacles, with a trade-off
Once activated, the less chatty mode reduces how often the Viz speaks, only taking into account the warnings that really matter, such as hazards, turns, and lane changes, while trimming everything else. Fewer Chatty Slots in the Middle: It keeps the full navigation guidance, instead of eliminating the guidance altogether, with only less repetitive and smaller hints.
I tested both methods back-to-back on the same route with the podcast playing. In normal mode, Viz repeated each turn two or three times before I actually needed it to. With the less chatty mode turned on, I got the same direction per turn instead, no repeats, and looked significantly less at what was ahead on the road.
Still, if you trust Waze’s warnings before you head out hard, the less chatty mode gives you less runway to react. I didn’t encounter any threat alerts during my tests, so I can’t yet confirm that they come with the same immediacy. For most common turns on the route I already know, though, a neat recipe beats the three obstacles in my podcast every time.
Personalized navigation is worth continuing.
A configuration that you cannot test in a day
Waze now tracks the types of routes you actually take, like streets over highways or fewer stops over shorter distances, and starts to surface those preferences first the next time it plans a trip. The toggle resides at Settings > Privacy > Personalization > Personalized Navigation, not under Navigation Preferences where I expected to find it, and it’s actually two separate switches: Get Personalized Routes and Get Personalized ETAs.
You can’t flip the toggle either when the car is in motion. I had to park before Waze would let me change any settings here.
I’ll be honest I didn’t find the multi-day test really needed. Deciding whether Wiz has learned my habits after being toggled on for an afternoon is guessing, not reporting. But there is no real downside to skipping it. You can still choose an alternate route manually at any time, and personalization can be turned off entirely if it starts to misjudge. It’s a rare AI feature with nothing to lose by trying it out, even if I can’t yet vouch for how well it works.
Conversational street reporting didn’t work for me.
The headline feature that never talked back.
The last of the three that I can personally use as a US resident and not a beta tester, conversational reporting, allows you to tap the report button, say something like “the road is closed here”, and let Gemini update to local map editors, no need to tap a menu. He didn’t answer for me. I tried it a couple of times, tapping the mic inside Wiz’s “What do you see?” The panel and both bars are clearly speaking, and nothing is returned. The one time a report actually went through, it wasn’t through this feature at all: I’d triggered Android Auto’s system-level Gemini assistant instead, which relayed my report to Waze through a completely different path than the in-app conversational reporting Google announced. I tried connecting and disconnecting it from my car’s infotainment system via Android Auto. It doesn’t work either way.
Of course, I’m not writing this broken for everyone. Wiz’s rollout has been so uneven that any update could land a fix. But two failed attempts against an existing report button that takes one look and one tap isn’t enough for me to recommend switching.
Two features, not five.
Between a feature I can’t access, a beta that’s already loaded, and a headline feature that doesn’t work twice in a row, the less chatty mode is one I’d tell any Wiz driver to turn on today, and the personalized navigation is worth continuing for the simple reason that it can’t hurt. Conversational reporting is something I’m still waiting for Google to actually provide.