Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

LuckyCharms

(21,439 posts)
Wed Dec 24, 2025, 01:16 PM 20 hrs ago

Technical phone question regarding "OK Google".

Samsung S23 Android.

I normally use "OK Google" verbally to navigate.

I'll say "OK Google" and the OK Google thing pops up and then I'll say "Navigate me to 125 Jones Road" and it will bring me to Google maps. Google maps will then start talking to me to navigate me.

Now, when I say "OK Google", the OK Google thing pops up, and I'll instruct it navigate me somewhere, and it will say "I'm sorry, I don't understand".

However, if I say "OK Google", and then say "bring me to Google maps", it will do so, but then I have to type in my destination instead of saying it verbally, and then it will start navigating me vocally.

The fact that it won't accept my verbal commands to navigate is obviously not desirable, especially when driving, considering the fact that I'm not going to pick up my phone and type my destination in when I'm behind the wheel.

I've been on hold with Verizon Tech Coach for 25 minutes now, and still waiting.

Any ideas?

Thanks in advance, and Merry Christmas.

10 replies = new reply since forum marked as read
Highlight: NoneDon't highlight anything 5 newestHighlight 5 most recent replies
Technical phone question regarding "OK Google". (Original Post) LuckyCharms 20 hrs ago OP
It's a known issue AZJonnie 20 hrs ago #1
Thank you so much. n/t LuckyCharms 18 hrs ago #3
Jonnie... LuckyCharms 18 hrs ago #5
Apart from the top of the message, just looked it up and copy/pasted what I found to be honest buddy, but you're welcome AZJonnie 18 hrs ago #7
I'm bookmarking this with a k7r Niagara 20 hrs ago #2
Ohhhhh Nooooooo!!! LuckyCharms 18 hrs ago #4
That's terrible Niagara 16 hrs ago #9
You're the next version of Santa? LuckyCharms 16 hrs ago #10
Try using a cartoon dog voice. Harker 18 hrs ago #6
I took a different approach and it worked! LuckyCharms 17 hrs ago #8

AZJonnie

(2,713 posts)
1. It's a known issue
Wed Dec 24, 2025, 01:25 PM
20 hrs ago

Quick fixes to try (in order). As an aside, personally I recommend upgrading the digital assistant to use Gemini (it's much better) rather than the 'stock' one that comes packaged with Android OS if you've not already done (it's in the Google Play Store). I've an S25+ with Gemini and the voice nav still works, plus it's just generally much more powerful than the stock Digital Assistant, and its free.

Retraining/re-enable voice model (most common fix):
Google app → Profile → Settings → Google Assistant → Hey Google & Voice Match → Retraining (say phrases 3x). Toggle Hey Google off/on.

Clear Google/Maps cache/data:
Settings → Apps → Google → Storage → Clear cache (then Clear data if needed, re-login). Repeat for Google Maps and Assistant apps. Restart phone.

Check/disable Gemini interference:
Settings → Apps → Choose default apps → Digital assistant → Set back to Google (not Gemini/Samsung). One UI 7 beta users report Gemini hijacks voice commands.

Maps-specific voice settings:
Google Maps → Profile → Settings → Navigation → Play voice over Bluetooth (on) + Voice playback language matches your phone locale.

Microphone/permission reset:
Settings → Apps → Google/Maps → Permissions → Microphone (allow all time) + Phone (allow). Test in safe mode (hold power → long press Restart).

LuckyCharms

(21,439 posts)
5. Jonnie...
Wed Dec 24, 2025, 03:18 PM
18 hrs ago

Last edited Wed Dec 24, 2025, 10:44 PM - Edit history (1)

See my post below to Niagara. The assistant tried the steps you outlined, in the order you outlined, but nothing worked. So we tried switching to Gemini, and it still did not work.

So she tried to transfer me to level 2 assistance and we got cut off and my phone is still hosed.

I appreciate you very much for taking the time to outline those steps. Very nice of you.

AZJonnie

(2,713 posts)
7. Apart from the top of the message, just looked it up and copy/pasted what I found to be honest buddy, but you're welcome
Wed Dec 24, 2025, 03:55 PM
18 hrs ago

Fundamentally the first thing to target is determining if it's the hardware interface (i.e. the physical microphone and the driver) because obviously if there's an issue there, nothing else downstream (software wise) is likely to solve it. Do you have bluetooth headphones? If so, put them on, find out what you have to press on them to activate voice assistant if you don't already know, go to room far enough away that the onboard mic can't pick you up. Then press the activation button, then say Ok Google, then try your typical navigation command. If it works like it used to, this is a good hint

And that I did write up myself

LuckyCharms

(21,439 posts)
4. Ohhhhh Nooooooo!!!
Wed Dec 24, 2025, 03:09 PM
18 hrs ago

I've been on the fucking phone with Verizon for almost 2 hours and we tried everything, Nothing worked so she tried to transfer me to Level 2 assistance and we got cut off!!!

Dear God...

i hope you are having a better day than I am!

Niagara

(11,386 posts)
9. That's terrible
Wed Dec 24, 2025, 05:13 PM
16 hrs ago

Have you tried to reboot your phone before you smashed it into a billion pieces?

I'm not God but I'm the next version of Satan.





I'm so sorry for your rotten phone luck , Lucky.

LuckyCharms

(21,439 posts)
8. I took a different approach and it worked!
Wed Dec 24, 2025, 04:05 PM
17 hrs ago

I went into my garage, pulled out my sledge hammer, and smashed this fucking phone into a million pieces while singing the national anthem!

Merry Christmas, Harker!

Latest Discussions»The DU Lounge»Technical phone question ...