Travel conversation guide

Check microphone access before repeating a translation

If a voice input does not start, check the selected input mode and the app’s microphone permission. Then test with one short, fictional sentence in a quiet place.

Android release in preparation

Quick Translate and experimental Live Interpreter are the current foundation. This website will link to the official Google Play listing when it is public. Product previews and examples are illustrative.

See launch status →

Identify the symptom first

SymptomFirst checkKeep separate
No recording startsIs the voice mode available and selected?Feature availability versus permission.
Permission prompt appearsRead which app is asking and whyAn operating system prompt versus an app error.
Recording starts but captures nothingMicrophone access and chosen input devicePermission versus audio routing.
Words appear incorrectlySource language, noise and turn lengthSpeech recognition versus microphone access.

A missing or disabled voice mode is not automatically a permissions problem. The feature may depend on the product, version or connection; check its current help information instead of repeatedly granting unrelated access.

Review the app permission

Google’s Android instructions describe opening Settings, Apps, selecting the app, then Permissions to review an individual permission. Device menus and available permission choices vary. Find Microphone and choose the option appropriate for your use. Review any system-wide microphone control if your device provides one.

Grant access only to the app you intended to use. If a browser page is doing the recording, the browser’s site permission can also matter. An allowed permission does not prove that a microphone, network connection or translation service is functioning.

Use a controlled first test

  • Move to a quiet place and use a fictional sentence.
  • Disconnect a headset briefly if you are unsure which microphone is active.
  • Check the input language and start one short turn.
  • Look for a visible transcript or recording indication.
  • If the input works, add your usual headset and repeat the same test.

Do not shout or repeat private information while troubleshooting. If the transcript is wrong despite a clear recording, use the background noise guide or type the key detail.

Revisit access after testing

If you no longer use a voice mode, review its permission again. Permission settings are one part of privacy, alongside the service’s stated retention and history behaviour. See the privacy preparation guide. This checklist does not establish Pocket’s current provider or deployed audio behaviour.

Sources and scope

Practical examples and checklists on this page are editorial exercises, not recordings, measured app results or claims about a currently released feature.

Help us improve Pocket’s website

Allow Google Analytics and Ahrefs Web Analytics to measure visits to Pocket’s website? Google also measures scrolling, outbound links and tool activity. You can decline and change your choice below at any time.

What is measured

With your permission, Google receives website activity and browser/device information. Ahrefs receives page visits and browser/device information, and uses IP addresses to estimate location. This measurement excludes URL query strings, fragments, form contents, email addresses and app conversations. Ahrefs does not receive referring URLs. Advertising personalization is disabled. Google Analytics cookies last up to 90 days; Ahrefs uses no analytics cookies. Your choice is saved on this device for 180 days. Provider privacy information: Google and Ahrefs. Contact Pocket support with website data questions.