If live call translation is not working, first determine whether the translation control is missing, the call has no translated audio, or the translation is wrong or delayed. Those symptoms have different causes. Missing controls usually point to device, software, region, call-app, or language support. Silent translation usually points to audio routing, permissions, or an undownloaded language pack. Poor translation is more often caused by the wrong language direction, overlapping speech, noise, or long sentences.
If your phone does not support built-in call translation, you are not out of options. A browser-to-phone service can translate a call before it reaches an eligible regular landline or mobile number. The person you call answers normally and does not need a compatible iPhone, Pixel, Galaxy device, or translation app.
Start with this two-minute diagnosis
Use the symptom you see to choose the first fix instead of changing every setting at once.
| What you see | Most likely cause | First thing to try |
|---|---|---|
| No translation button anywhere | Unsupported device, old software, unavailable region, or unsupported call app | Check the device-specific requirements below and install the latest supported update |
| Translation exists in messages but not phone calls | Text translation and call translation are separate features | Confirm that your exact phone supports translation inside its Phone app |
| Your language is missing | The language pair is unsupported or its model is not downloaded | Download both languages and check the current official support list |
| Translation starts but you hear nothing | Media volume, Bluetooth routing, speaker selection, or a missing model | Raise in-call and media volume, disconnect Bluetooth, and retry on the phone speaker |
| Only one person is translated | Languages are reversed, one microphone is not captured, or people are talking over each other | Re-select who speaks each language and take turns speaking |
| Translation is slow or inaccurate | Noise, long sentences, names, numbers, weak connectivity, or simultaneous speech | Move somewhere quiet and use one short sentence at a time |
| Native translation is unavailable | The device or language pair is outside the supported set | Use browser live translation to call an eligible regular phone number |
Before troubleshooting software, make one ordinary call without translation. If the microphone, speaker, carrier connection, or internet calling path already fails, translation cannot repair the underlying call. Use the browser microphone test if you are calling from the web.
Fix Live Translation on iPhone
Apple's Live Translation is not the same feature across Messages, FaceTime, and the Phone app. An iPhone may translate text messages while lacking translated audio for ordinary phone calls, or it may support FaceTime captions for a language pair that is unavailable in Phone.
Apple currently says phone-call Live Translation requires Apple Intelligence and is available only for supported models, languages, and regions. Apple's Apple Intelligence requirements list iPhone 15 Pro models and iPhone 16 models or later. Its Live Translation guide lists the language availability separately for Messages, FaceTime, Phone, and AirPods.
If the Live Translation button is missing
- Confirm the iPhone model. An iPhone that can install the current iOS release does not automatically support Apple Intelligence.
- Update iOS. Install the newest version offered for the device, then restart it.
- Turn on Apple Intelligence. Open Settings > Apple Intelligence & Siri and confirm it is enabled.
- Match the device and Siri languages. Apple notes that Apple Intelligence availability depends on supported language and region settings.
- Download both translation languages. Open the relevant translation settings before the call and wait for each model to finish downloading.
- Start a one-to-one call in Apple's Phone app. During the call, open the More menu and look for Live Translation. Group calls and third-party call paths may behave differently.
If Messages translates correctly but Phone does not show the control, do not keep reinstalling language packs blindly. Recheck the Phone-specific language list and your iPhone's Apple Intelligence compatibility.
If iPhone translation starts but has no sound
- Raise both the in-call volume and media volume while translation is active.
- Disconnect AirPods, hearing devices, car audio, or another Bluetooth route and retry on the iPhone speaker.
- Confirm the call is not muted and the other person can hear your untranslated voice.
- Stop Live Translation, switch both languages, switch them back, and start again.
- Delete and redownload the affected language model if the problem happens only with one language.
Apple notes that model output can vary, so confirm critical numbers and names instead of assuming the transcript is exact.
Fix Voice Translate on Google Pixel
Do not confuse Pixel's broad Live Translate tools with Voice Translate for ordinary calls. A Pixel may translate chats, captions, or media without supporting two-way translated speech inside the Phone app.
Google's current Voice Translate documentation says the call feature is available on Pixel 10 and later, including Pixel 10 Pro Fold. It translates between English and a defined set of supported languages; some languages are not available on every model. Google's separate Pixel translation overview covers chat, media, captions, and other translation features, which is why seeing Live Translate elsewhere does not prove that Voice Translate is available during a call.
If Voice Translate is missing
- Confirm that the phone is a supported Pixel model.
- Update Android, the Phone app, and system components through Google Play.
- Open Phone > Settings > Voice translate and turn the feature on.
- Select the language you speak and download the other person's language.
- Start a call, tap Call Assist, then choose Voice translate.
If you have an older Pixel, there may be nothing broken. The phone can support translated captions or messages while the call-specific feature remains unavailable.
If Pixel selects the wrong language
Voice Translate can suggest a language when it detects speech. For a planned call, set both languages manually before the conversation begins. If the speakers switch languages mid-call, stop and select the new pair instead of expecting every code-switch to be recognized correctly.
Fix Live Translate on Samsung Galaxy
Samsung's Live Translate depends on the exact Galaxy model, One UI version, region, language pack, and calling app. Samsung's current Live Translate support page says the feature is available on select Galaxy phones and tablets running supported software. It also lists the current languages and explains that some third-party calling apps are supported.
If Call assist or Live Translate is missing
- Update the phone to the newest supported version of One UI.
- Open Settings > Galaxy AI > Call assist > Live translate.
- Turn Live Translate on and download the two required language packs.
- Open Samsung's Phone app, place a call, then tap Call assist > Live translate.
- If the control still does not appear, check Samsung's support page for the exact model and region rather than assuming every Galaxy phone includes Galaxy AI.
If it works in Samsung Phone but not another app
Third-party app support is a separate compatibility layer. Confirm that the app appears under Live translate in other apps, enable it there, and update the app. A feature working in Samsung Phone does not guarantee that every voice or video calling app exposes the same audio path.
Samsung also warns that only one person should use Live Translate at a time. If both sides enable separate translation systems, each system may capture and retranslate the other's synthetic voice, producing loops, delays, or nonsense. Pick one translation path for the call.
Fix silent, one-way, or delayed translation on any device
Once the feature appears and starts, use a controlled test to separate an audio problem from a language problem.
Run a clean audio test
- Turn off Bluetooth and use the phone speaker or a wired headset.
- Move to a quiet room and disable speakerphone if it creates echo.
- Confirm that an ordinary untranslated call works both ways.
- Start translation with a common supported language pair.
- Say one short sentence, then pause until the other person hears it.
- Ask for one short reply, then wait for the translated result.
If that works, reconnect accessories one at a time. The first change that breaks the call identifies the likely route or compatibility problem.
Speak for the translation system, not for a meeting transcript
Real-time speech translation has to recognize speech, translate it, and produce text or audio before the conversation can continue. Help it by:
- using short, complete sentences;
- letting one person finish before the other starts;
- spelling names and reference codes;
- reading phone numbers in grouped digits, then confirming them;
- avoiding speakerphone echo, loud music, and road noise;
- repeating important details in a different way rather than only louder;
- keeping slang, jokes, and idioms out of high-stakes instructions.
For an address, reservation number, price, or appointment time, use a closed-loop confirmation: “I have Tuesday, July 28 at 3:30 p.m. Is that correct?” A visible transcript is useful, but agreement from the other person is the real check.
The browser fallback when native translation is unavailable
Built-in translation is convenient when the device, language pair, region, and Phone app all line up. When they do not, Localcall live translation moves the translation into the browser calling path.
You call from a supported browser to an eligible regular landline or mobile number. The other person answers a normal phone call; they do not need Localcall, an app, a recent smartphone, or internet access. This makes the browser route useful when:
- your iPhone does not support Apple Intelligence;
- your Pixel is older than the models that support Voice Translate;
- your Galaxy model, region, or call app does not expose Live Translate;
- the person you need to call uses a landline or basic mobile phone;
- you are calling from a laptop, tablet, or Wi-Fi-only device;
- you need one calling workflow across different devices.
How to place a translated browser call
- Open the Localcall dialer in a supported browser.
- Enter the complete international phone number.
- Use the phone number validator if you are unsure about the country code or format.
- Select live translation and choose the language you speak and the language the recipient speaks.
- Review the displayed rate. You can estimate a longer conversation with the call cost calculator.
- Allow microphone access, place the call, and use short alternating sentences.
Localcall is outbound-only and does not support every number type or destination. It is not an emergency-calling service. Check the exact number and displayed rate before dialing.
For a category-level comparison of native, carrier, mobile-app, browser, and enterprise options, see the best AI translation calling apps in 2026. If you need conversation preparation rather than technical troubleshooting, use the guide to calling someone who does not speak your language.
When to stop troubleshooting
Switch methods when the current path fails a requirement it cannot change.
| Your requirement | Best next move |
|---|---|
| Built-in translation on a supported recent phone | Finish the device, software, language-pack, and audio checks |
| A language pair the native feature does not support | Use another supported translation path or a qualified interpreter |
| Calling an ordinary phone number from an unsupported device | Use browser-to-phone live translation |
| A legal, medical, financial, immigration, or other high-stakes conversation | Use professional language assistance when accuracy or policy requires it |
| An emergency call | Use an official local emergency-calling method, not Localcall |
The fastest fix is often recognizing that “live translation” is not one universal phone feature. Apple, Google, and Samsung each separate devices, languages, regions, apps, and call types differently. Diagnose the missing layer once; then either repair it or choose a calling path that does not depend on it.