Every time I call out to my dog... "Hey, Coco" or "Okay, Coco"... it triggers a "Hey, Google" search on my Android 10 phone. Very annoying. I've gone through the entire "Voice Training" exercise twice, and it didn't help. Is there any way to train Android to better distinguish (or better yet 'ignore') my dog's name?

Has anyone experienced it before? The speech recognition (Google Now and speech input) is not working in Redmi Note 4G at all. I've tried cleaning cache, re-training, re-authentication, etc. but every time it says- "Didn't catch it. Please try again." Can anyone please tell me what's wrong? Thanks for your help! P.S: I'm having excellent WiFi connection with mic turned on. I've also checked all permission settings.

I have a Pixel 9, Android Version 14. Often I have need to spell out dot, as in dept of transportation, and it keeps giving me a period. Even in the context of "polka dot" it output "polka." This is clearly an error with it recognizing the word "dot" to represent punctuation, but is there a way to disable this version of the punctuation?

I got a new OnePlus One recently and have noticed that the Google Maps Navigation Voice is in English (India) ( I bought the phone in India). This is very annoying and refuses to change no matter how much i change the TTS settings and delete the English(India) voice. It just redownloads and speaks in that voice. It is just fine English (US) on a Moto X I also bought in India (App not Updated).So my questions: a) Is this a "feature"? b) How do I fix it? I would like the English(US) Google TTS voice to work.

When I tried to use speakometer , it keeps saying Speech Recognizer Service is not available or disabled in your phone. Where is the service located or where can I install it? I am on Honor 10.

Do any versions of Google's "Voice Typing" work completely offline? Note that when I specify ***"completely offline"***, I mean with absolutely no data sent to Google or other parties.

From time to time on my Android phone (currently a Samsung Galaxy S23 Ultra) I use speech recognition in English and then translate the transcription into a different language, and finally use that translation in some input field in some application. For example I might use Telegram or Line, and need to send a message in Korean or German, but I want to use speech recognition in English as this is the language I commonly speak. What's the fastest way to do so? Currently I use the Google Translate app to transcribe and translate. However this requires me to copy paste the resulting translation into the target application. Is there a more efficient way to do so?

I read https://android.stackexchange.com/questions/66285 , and it says the command "pound sign" will produce a # for UK English which it does. How do I get a £ instead? My system language is English UK.

I activated my Pixel 7 on September 21. Voice recognition worked for two days, now hasn't worked since September 22. Phone calls work, people can hear me. The Camera successfully captures sound when recording video. However, voice recognition no longer works for apps where it is the primary purpose of the app. - I open **Google Assistant**, the screen indicates it is listening for my input, but nothing changes or comes on screen when I speak to it - When using GBoard, I click the mic icon to begin **speech to text**. The phone dings, the mic flashes indicating it is ready for me to speak, but does not transcribe any text as I am speaking - I hit record in **Recorder**, and it doesn't capture any audio when speaking to it - **Now Playing** doesn't work, no songs have been captured since 9/22 despite being around plenty of music Here's everything I've tried: - Install all latest system updates - Ensure all Google Assistant and voice permissions are enabled - Restart phone in Safe Mode and out of Safe Mode - Factory reset phone and log in with a different Google account The phone has never been dropped or seen any liquids. Everything else functions as expected. Does anyone have advice on how to correct this? (I would assume it's not a hardware issue, if phone calls and video audio capture work with no issue)

I'm on a Sprint Samsung Galaxy S3 with Android 4.3. I would love to become a power user of the dictation feature to dictate text messages and emails. More often than not, however, I have to hand-edit the dictated text not because of text comprehension issues but because of punctuation, capitalization and spacing problems. These are the "commands" I've found to work. What is the full list? "period" --> . (works fairly reliably) "comma" --> , (works fairly reliably) "new line" --> \n (works about 50% of the time) I've not gotten capital or anything like that to work, or acronyms. If you know how it works, please share.

So I'm sure this is primarily because the contacts aren't listed in one of the linked gmail accounts. It's killing me because my dad can't use voice commands to call his contacts like he did on his BlackBerry. The only solution I've found so far is to export the exchange contacts to one of the linked gmail accounts. But obviously this must be redone EVERY time he changes something in outlook. So, is there some way to get voice commands to recognize the Exchange contacts? Or do I have to look for some sort of 3rd party solution that will sync the contacts between the two services? Also, he doesn't like how the contacts are listed by the person instead of by the company. Any way to change that?

In English, I can type :-) by voice by saying "smiley". How can I voice type :-) in French? I use Google speech recognition on Pixel 6 + Android 12.

I use Google's default voice input all the time, for texting and navigation and searching and such. Previously, if a scenario arose when I needed to include a symbol (such as an exclamation point!) or a special case, like a smiley face ":-)", I simply said these into the voice input: text mom i love you exclamation point smiley face used to yield Text to: Mom Message: I love you! :-) now yields: Text to: Mom Message: i love you exclamation point smiley face I noticed the change after upgrading to ICS (AOKP, latest builds) but realized the issue now happens across OS usage, which I would attribute to Google's interpretation methods changing. Does anyone else have this problem or know how to fix it? I loved this feature!

I was wondering whether there exist any Android wheelchairs that run Android. These could allow people that were unable to move their limbs but could still use voice to control their wheelchair through voice by talking into a phone in the front part of the wheelchair connected to the wheelchair via Bluetooth. Currently, Android has something known as voice access to control your phone via voice. But it could be nice, if, this mechanism could be extended to connect to a wheelchair via Bluetooth and control it via voice. Perhaps the phone can also be powered on and off via a voice command. Not sure about the charging part, but I think a robotic part that could find the wall socket and charge wheelchair and phone simultaneously would be nice. This would be very useful to people with no arms and legs or to people whose arms and legs were paralyzed such as paraplegic or tetraplegic people, but who could still use their voice to connect to their phone, operate their wheelchair, move about and communicate. Thank you.

https://android.stackexchange.com/q/219797/330250 clarified that Google Translate cannot translate voice offline. Are there any other possibilities to translate voice offline (e.g. abroad)? I have already checked Google Translate, Bing Translate, Yandex Translate and DeepL. Maye a combination of Apps/Extensions can achieve this goal?

I am using Samsung Galaxy S7 and recently, I used the speech-to-text feature in the default Voice Recorder application. When I play one of the audio files that was recorded with that feature, the application is able to show the text in sync with the audio. I saw that there was the text stored in another text file together with the audio file, but it was just the raw text. I'm trying to figure out how this works. Is this information for syncing the text and audio stored in the audio file? In this case, all the recordings are only in M4A files. Hence, I tried searching what M4A files can store, like if they can store subtitles because it would seem that it could be subtitles that enable this syncing. However, I can't seem to find any information on this. Or it could also be that the application just has this information stored in some sort of storage or cache, which would mean that if I moved the files over to my computer, there would not be any text synced with the audio.

My Android 10 phone's voice recognition for English works extremely well, but when I travel to India it switches to expect an Indian accent, and I can barely get it to take my dictation that way, even though I can adapt to speak the local accent some of the time. Can we tweak some settings to avoid this change in the underlying machine learning model so that it keeps interpreting my English dictation as either UK or US accents of English, thus retaining its existing, pre-travel, levels of accuracy? I really rely on voice dictation quite a lot. When referring to voice recognition, I primarily mean the voice typing feature available through the Google Keyboard's microphone icon, but I suspect that the same underlying components also handle the "Hello Google" stuff. When I go outside of India, it clearly does revert back to expecting US or UK accents again, as if over-adapting to the geography rather than remaining loyal to the user that's already using it. Actually, at least one person native to India who speaks the Indian accent and dialect of English has mentioned the same issue to me, which they only experience in reverse ― voice recognition accuracy plummets for them when they travel to other English-speaking countries.

I'm trying to use Google's voice typing, but it is not able to punctuate my sentences. No matter I say "point", "dot" or "comma", it always writes it into my text. Earlier I though this is only because I wanted to use the voice typing in other languages (not English). But now I'm trying to reach this functionality in English. Is there any hidden tricks to enable the punctuation on Android 11 (Samsung)? I found someone used the Swype keyboard which is obsolete now (since 2018). So really what are my options?

When using [Gboard](https://play.google.com/store/apps/details?id=com.google.android.inputmethod.latin) voice to text input, an atrocious bell sounds to prompt the user to start talking. It wakes up the ... Sure, I could turn down its volume with the four Android volume sliders. Indeed, on different phones it is on a different sliders. But that doesn't matter, because that is not the solution I am looking for. Why? Because it affects other apps. Throwing the baby out with the bathwater. Yes, in a Utopian world one could have [A](https://android.stackexchange.com/questions/92530/set-different-volume-for-multiple-apps-running-at-the-same-time) and [B](https://android.stackexchange.com/questions/222202/how-to-block-an-app-from-accessing-my-speaker) , and even my [groundbreaking landmark Android Speaker Permissions proposal](https://issuetracker.google.com/issues/277029750) . But today I am merely wanting to _deball_ this one bell, on my run of the mill Samsung A13 5G Android 13 phone. The logcat is: > 04-02 19:24:44.433 I/VoiceInputManager(3099): VoiceInputManager.startVoiceInput():194 startVoiceInput () : VoiceSessionParams{audioInputStream=null, primaryLanguageTag=en-US, secondaryLanguageTags=null, triggerApplicationId=null, triggerFieldName=null, blockOffensiveWords=true, autoStarted=false, fallbackAvailable=false, **suppressBeepSoundAtRecognitionStart=false**, connectOnly=false} : VoiceTranscriptionState : UI = NOT open : Microphone = NOT listening : Recognizer = NOT running If only I could somehow go in and toggle that **suppressBeepSoundAtRecognitionStart** to true! https://support.google.com/android/thread/201115689/google-voice-typing-ding-sound-is-way-too-loud

I am running Android 11 on a Realme 8 5G phone. I would like Google Assistant to answer basic questions about people's age and birth dates, including my own. I don't understand why it doesn't do this. When more than one user is present on the phone, it should recognize the person speaking on the basis of the voice being used, and answer the question (even providing more than one answer if it cannot disambiguate between voices). Questions such as: "What is my age?" "When is my birthday/birth date"? "How old is X?" (it should retrieve this information from the Contacts app). "When is X's birthday/birth date?" It is not uncommon for people who get older or develop some learning disability or dementia or other mind problem or who are simply lazy or forgetful to not be able to subtract the date of birth from the current date to compute their age. The same goes for other people's data. A feature was introduced at some point where you could define kinship in the Contrats app and then just say "call mom/mum". This is also an Accessibility feature. But it would be just as useful if Google Assistant could answer "What is mom's/mum's age?". Why is this important accessibility feature missing from Google Assistant? When will it be added? Is anyone willing to add it? It would be highly appreciated. (Here are some screenshots that display for Google Assistant is currently failing when I address the issue in Italian): UPDATE; Perhaps this is just a flaw of Google Assistant in Italian. Perhaps, it does not work very well in other languages. Ad a matter of fact, it does not understand correctly non English names. For instance, when I ask Google Assistant, how old is Imma Bonuomo, an Italian name for one of my contacts, Google Assistant does not understand the mixed English and Italian speech (wouldn't it make sense that it did, looking in my contacts first, and, only then, searching on the web? It could even ask me "sounds I look in your contacts?",0 if it was unsure. Or alternatively, it could ask, back, "Search from contacts, or search from the web?", (not sure if Google Assistant has access to any other data sets, then these two places. Perhaps other apps may make data available though a content provider. Or, perhaps, it could ask, back, "Imma Bonuomo found in contacts. Use this result?" and you could specify back, "search the web", if that is not what you wanted. A list of other places to retrieve the data associated with or computed from the name, could be specified in the horizontal scrollable area of Google Assistant. In any case, Google Assistant hears "Emma Barnett" instead of "Imma Bonuomo", and fails (with the result given in the image below). Indeed, it gives me this result, when I run such search: Why is Google Assistant giving me this wrong result? Thank you for any contributed improvements to Google Assistant. And thank you for your answers. UPDATE: I had placed the birth date in the notes, rather than in a separate field (due to a complication where two birth dates were existing separately for this person (the real birth date, and the one recorded at the registry office. Google Assistant was unable to search the notes field for this contract and find the birth date using DeepL (or something similar). Thanks. In any case, after reinserting the contact's information in the birthday field instead of in the notes field, the Italian counterpart answers properly to "quando è nata Imma" and "quanti anni ha Imma" (but the English counterpart still mishears). But when asking "how old am I?" In English, it works, but in Italian, "quanti anni ho io", which, is the same thing, doesn't work. Thanks you for your contributed improvements. Thank you for your answers. Thanks.