Android call diagnosis · Updated 2026

WhatsApp calls not working on Android

When WhatsApp calls are not working on Android, match the failure to a cause before you reinstall the app. If calls never ring, microphone and camera can be the problem even when messages send. If calls start and drop, the network or VPN route usually is. This guide runs the checks in an order that avoids random toggling.

Test a call with FortVPN
  • Free on Android
  • No sign-up
  • Unlimited data

Read the signal, not the country

Three Android failure patterns and where to start

Each pattern points to a different fix. Picking the wrong one wastes time and makes you reinstall the app.

Call never reaches “Ringing”

Phone side first

The recipient never gets a ring. This can be a microphone permission, a WhatsApp background restriction, or a network issue on your side. Check permissions and background data before blaming the network.

Call connects, then drops after a second

Network or VPN route

A call that starts and then ends is usually a routing or bandwidth problem, not a blocked account. Switch to a different VPN server or a different network and retest once.

Voice works off Wi-Fi, fails on Wi-Fi

Wi-Fi limitation

If the same call connects on mobile data but not Wi-Fi, the Wi-Fi network is restricting voice traffic. Run the controlled Wi-Fi vs mobile data test below.

Not sure whether your network is the problem? Start from the VPN for WhatsApp guide to confirm the basics before changing phone settings, and run the Wi-Fi vs mobile data test if calls work on cellular data.

Fix WhatsApp calls on Android in this order

One test at a time, record the result, then move to the next step.

  1. 1

    Check WhatsApp service status, not the app

    Load a website and check status.whatsapp.com. An outage looks identical to a phone problem from inside the app. If the service is down, no setting or VPN will make the call connect.

  2. 2

    Grant microphone and camera access

    Open Android Settings → Apps → WhatsApp → Permissions and enable Microphone and Camera. On some builds, also check the camera under the same permission screen. A denied permission often leaves messages working.

  3. 3

    Switch back to mobile data and retest once

    Turn Wi-Fi off and place a short voice call. If it connects, the original Wi-Fi network was the problem. If it still fails, reconnect FortVPN and reopen WhatsApp before the next call.

  4. 4

    Reconnect VPN before opening WhatsApp

    Check the detailed WhatsApp VPN guide to place the call inside the tunnel. Use Fast Connect first, then one alternative server if the first route is congested.

Android causes that look like a network block

Change one setting, run one call, record the result. These often get skipped before a VPN is blamed.

Microphone permission

Symptom
Call connects but no one hears you
Fix
Settings → Apps → WhatsApp → Permissions → Microphone → Allow. Requires a phone restart for some Android builds.

Battery optimization

Symptom
Call drops after a few seconds or shows “Calling”
Fix
Settings → Apps → WhatsApp → Battery → Unrestricted. Background call handling is throttled on a restricted mode.

Background data

Symptom
Incoming calls and messages do not arrive while the app is closed
Fix
Settings → Apps → WhatsApp → Data usage → Background data → On. This is separate from the network restriction issue.

Do Not Disturb / call blocking

Symptom
Incoming WhatsApp calls do not alert
Fix
Check Do Not Disturb mode and any per-number block list. These are device behaviours, not WhatsApp bans.

Cleared app cache

Symptom
Call functions break or freeze after an update
Fix
Settings → Apps → WhatsApp → Storage → Clear cache, then reopen and place a single test call. Do not clear data unless you want to sign in again.

If calls fail only when the VPN is connected, read VPN connected but WhatsApp calls still fail. A VPN cannot repair permission, battery or radio problems.

What a call actually needs

The bandwidth bar, not a “block” verdict

WhatsApp adapts video resolution to your upload. A failed call can be a bandwidth problem long before it is a network restriction. Match your call type to the numbers below.

1:1 voice call
Upload
Minimum
~100 kbps
Good
≥ 0.5 Mbps
HD / large group
≥ 1 Mbps

Voice is the lowest bar. If a voice call still fails below ~100 kbps, the limit is usually the route, not the codec.

1:1 video call
Upload
Minimum
~500 kbps
Good
≥ 1 Mbps
HD / large group
≥ 2 Mbps upload

Video is bursty: it needs sustained upload, not just a fast speed test. A later fallback to voice is normal when upload dips.

Group call (≤ 8 people)
Upload
Minimum
~1 Mbps
Good
≥ 3 Mbps
HD / large group
≥ 5 Mbps upload

Group calls multiply the same stream to each participant. The weakest home upload link is the usual glass ceiling.

Group call (≤ 32 people)
Upload
Minimum
~2 Mbps
Good
≥ 5 Mbps
HD / large group
≥ 8 Mbps upload

Large group calls need a very stable path. Upload spikes from cloud backup often starve these calls first.

“Use less data for calls” is often the real culprit

Guides such as Sábio Advogados flag WhatsApp’s data-saver call mode as a top cause of pixelated or stuck video. It is frequently on by default, because it reduces audio and video bitrate to save bandwidth. If your call “connects” but looks or sounds bad, disable it before touching the VPN.

Android: WhatsApp ⋮ → Settings → Storage and data → Use less data for calls → OFF

If you are not sure whether your network or your phone is the limit, run the Wi-Fi vs mobile data A/B test to separate the two before changing any setting.

Blocked vs not blocked

Read the ticks before you blame a block

Most “it must be a block” calls are actually a network, permission or “Call unavailable” technical failure. Use these signals instead of a hunch.

Two grey ticks still appear on your message
Not a block

Two grey ticks mean delivered, which normally rules out a block. If calls still fail, the problem is usually network or device, not being blocked.

One grey tick, no profile photo, calls fail together
Blocked signal

A message stuck on one grey tick can mean delivery never happened. It is often an offline or blocked recipient. AirDroid notes a permanent single tick plus a missing photo is a stronger block signal, but it is still not proof.

“Call unavailable” after a split-second ring
Not a block

“Call unavailable” is a technical connection failure, not a rejection. MobileTrans lists regional VoIP restrictions, disabled permissions and active data savers as the usual causes, and symptom is a call that rings then drops immediately.

Focus / Do Not Disturb is on
Not a block

Focus and Do Not Disturb silence notifications; they do not block WhatsApp VoIP. A silenced call can ring on the recipient’s phone and they simply miss the prompt.

Truecaller / Hiya flags the number
Not a block

Spam-caller apps manage carrier calls. According to AirDroid, they normally do not block WhatsApp voice traffic, so do not treat a spam label as a WhatsApp block.

To confirm not blocked: two grey ticks, or two blue ticks when read receipts are on, means you are not blocked.

Still unsure: test with a second contact. A block is per-number, so a call that fails with everyone is a network or device problem.

WhatsApp calls on Android: questions

These cover the checks users ask about before reinstalling or switching networks.

Two parts of an Android phone matter here: the app’s network path and its system permissions. If messages and photos send but live calls fail, rule out a WhatsApp outage first, then check microphone permission, battery optimization and whether the phone is on a network that restricts VoIP calling. A VPN may help with the network part; it cannot grant microphone permission.

One ordered test beats reinstalling everything.

Install FortVPN on Android, connect before opening WhatsApp, and place a short voice call. If it fails, use the cause table above—no guaranteed-unblock promise.

Run the Android call test
Free downloadNo sign-upTap to connect