Talk to Text on Android Not Working? A Fix-by-Symptom Guide

If talk to text on Android is not working, start with a controlled test in Gmail or Google Keep. Confirm that Gboard is the active keyboard, its microphone icon appears, voice typing is enabled and microphone permission is allowed. Then check Android’s system-wide microphone control, the selected language and pending updates. Clear only the Gboard cache before considering a full data reset.

Google calls this feature Gboard voice typing. It is different from recording audio, transcribing an existing file and using Voice Access to control the whole phone. This guide fixes the keyboard workflow specifically, rather than repeating a general Android speech-to-text overview.

Identify the exact failure

Open Gmail or Keep, tap an empty text field and look for Gboard’s microphone. Try one short sentence. Note what happens: the icon is missing, permission is denied, “Speak now” never appears, listening stops immediately, or words appear incorrectly.

This distinction prevents unnecessary resets. If voice typing works in the test app but not in one banking, work or browser field, the problem is probably app-specific. Some secure fields deliberately reject dictation. If it fails everywhere, continue with keyboard and system checks.

Confirm that Gboard is active

Android phones can have several keyboards installed. The microphone setting you changed does nothing if Samsung Keyboard, SwiftKey or another keyboard is active. Open a text field, tap the keyboard selector when available and select Gboard. Manufacturer labels and paths vary.

Google’s official type with your voice instructions say Gboard supports talk-to-text in most places where you can type, but not all languages are supported. If your organisation manages the phone, ask whether keyboard or voice services are restricted before removing an approved keyboard.

Turn on Gboard voice typing

With Gboard open, tap its settings icon, choose Voice typing, and turn voice typing on. If the toolbar is collapsed, expand it or open Gboard settings through Android’s keyboard settings. Return to the test field and tap the microphone.

On supported Pixel devices, advanced voice typing has additional device and language requirements. Google’s advanced voice typing documentation says the primary Gboard language and device language must match for advanced features. Basic voice typing and advanced Pixel features should therefore be diagnosed separately.

Restore microphone permission and privacy access

Open Android Settings, find Apps, select Gboard, open Permissions, then allow microphone access while using the app. Next, pull down Quick Settings and confirm the system microphone control is not blocked. Google documents that Android 12 and later can expose a global camera and microphone control.

Test the physical microphone with the phone’s recorder or camera app. If every app captures silence, remove a case that covers a microphone opening, disconnect Bluetooth audio and restart the phone. A hardware or audio-routing problem cannot be solved in Gboard.

Match the keyboard language

Select the language you are actually speaking. Hold the space bar or use Gboard’s language control, depending on the layout. Do not assume that an English keyboard automatically recognises German, French or mixed-language names reliably.

Google notes that talk-to-text does not support every language and that punctuation availability varies. For advanced Pixel voice typing, language and device eligibility are narrower. If ordinary dictation works but editing commands do not, that can be a feature-availability issue rather than a broken microphone. The broader dictation guide explains where language support and live input differ from file transcription.

Check connectivity, updates and battery restrictions

Connect to a stable network and test again, particularly after setting up a new phone or language. Some configurations can operate locally, while others depend on downloaded components or online processing. Do not claim an offline workflow until you have tested the exact device, language and mode.

Update Gboard from Google Play and install approved Android system updates. Temporarily disable aggressive battery saving for the test if it closes keyboard services, then restore the organisation’s required policy. Restarting after updates is a low-risk way to reload the keyboard and speech components.

Need to capture a longer conversation rather than dictate into a field? Kuno is a physical AI recorder designed and developed in Munich, with EU-hosted processing and storage; current core features are marketed without a subscription. Record only with explicit agreement. Explore Kuno

Clear cache before clearing storage

Go to Android Settings, Apps, Gboard, Storage and cache, then choose Clear cache. Google’s official Gboard troubleshooting guide recommends cache clearing for voice-input problems. Reopen Gboard and test.

Use Clear storage or Clear data only if cache clearing fails. That action resets Gboard and can remove preferences or learned data. Record enabled languages and settings first. Reinstalling or removing updates is a later step, especially on managed devices where the keyboard configuration may be controlled centrally.

Isolate Bluetooth and app conflicts

Disconnect earbuds, a car system and external microphones, then test with the phone alone. Android may be listening to a remote microphone in another room or a headset with a blocked input. Reconnect one device at a time to identify the route that fails.

If only one app fails, update it and test a normal text field rather than a password, payment or protected field. If work-profile apps alone fail, contact the administrator. Keep accessibility services in mind: Voice Access controls the interface with spoken commands and is not the same as Gboard dictation.

Improve recognition after it works

Speak at a normal pace, keep the microphone unobstructed and reduce competing sound. Dictate in short paragraphs, then review names, numbers, negation and punctuation. For an existing recording, do not play it into the keyboard; use a proper audio-to-text workflow that preserves the source for checking.

Voice output is always a draft. A human must verify it before a medical, legal, financial, employment or other consequential use. If other people’s speech would be captured, explain the purpose, obtain explicit agreement first and offer a fully equal no-recording/manual-notes alternative.

If the distinction between a live keyboard draft and a preserved source is unclear, review what transcription means. Choosing the correct workflow avoids trying to make Gboard perform a job it was not designed to do.

Use the smallest fix that works

The efficient order is: test another app, confirm Gboard, enable voice typing, restore microphone access, match the language, update and restart, clear cache, then consider a reset. Stop when the feature works. Changing several settings at once hides the cause and can create a second problem.

For consented in-person sessions that need a reviewable recording, Kuno provides a dedicated physical capture route. Keep manual notes equally available and verify every transcript or summary before use. See Kuno