A PRACTICAL NOTE · Troubleshooting

How to apply this guide

Check the Android device and primary Gboard languages before assuming a new phone lacks the feature.

Start with

Note the primary Android language and the primary Gboard language as displayed. In a scratch note, check whether ordinary keyboard voice input starts.

Check before you finish

If the desired language requires different primary settings, check ordinary voice input and review the result manually. Revert temporary language changes that affect how other apps work for you.

Evidence to keep: Record the expected sentence, actual result, microphone, language, model and app build before changing settings. This page’s key limit is: Check the Android device and primary Gboard languages before assuming a new phone lacks the feature.

Start here

Google’s troubleshooting guidance says Advanced voice typing needs matching primary device and Gboard languages. A normal microphone icon can still appear when advanced controls are unavailable.

Record the starting settings

Note the primary Android language and the primary Gboard language as displayed. In a scratch note, check whether ordinary keyboard voice input starts.

Test a matching supported language

Temporarily align both primary languages on a language your device supports for Advanced voice typing. Follow Gboard’s own Voice typing settings and start a fresh test in an editable field.

Keep the setup you need

If the desired language requires different primary settings, check ordinary voice input and review the result manually. Revert temporary language changes that affect how other apps work for you.

Keep exploring