Need help fixing issues with the Zangi app

Apps
1

Is anyone else having problems with the Zangi app not working reliably on calls and messages? It used to run smoothly, but recently I’ve had dropped calls, delayed messages, and random logouts. I’ve tried reinstalling, updating, and checking my network, but nothing fixes it. Can someone share possible solutions, settings tweaks, or known compatibility issues so I can get the Zangi app stable again?

2

Yeah, Zangi has been flaky for me too the last few weeks. Here is what helped a bit:

  1. Check battery and background settings
    • On Android: Settings > Apps > Zangi > Battery > set to “Unrestricted” or “No optimization”
    • Allow “Run in background” and “Auto start” if your phone has it
    If the OS kills the app, you get random logouts and delayed messages.

  2. Lock the app in recents
    On some phones you need to “lock” Zangi in the recent apps screen so the system does not close it. Usually long press the app card and tap the lock icon.

  3. Turn off aggressive data saving
    • Disable Data Saver for Zangi
    • On Wi‑Fi, turn off any “Wi‑Fi power saving” or “adaptive connectivity” options.

  4. Reset network settings
    • Reset mobile and Wi‑Fi network settings in system options
    This fixed delayed messages for me when switching from Wi‑Fi to LTE.

  5. Try a different DNS
    Use Cloudflare 1.1.1.1 or Google 8.8.8.8. Zangi’s signaling sometimes struggles on weird ISP DNS setups. After I switched DNS, call setup time dropped from like 10–12 seconds to about 3–4.

  6. Check VPN and firewall apps
    • If you run VPN, proxy, or firewall apps like NetGuard, disable them and test
    • Some of them block UDP traffic, which kills VoIP quality.

  7. Log out and clear data the “hard” way
    • Log out inside Zangi
    • Force stop
    • Clear cache and app data
    • Log back in
    You said you reinstalled, but in some cases Google backup restores broken settings, so this manual reset helps.

  8. Test on another device and network
    • Install Zangi on a second phone with a different SIM or Wi‑Fi
    • If it runs fine there, your main phone setup is the issue
    • If it fails there too, problem is server side or account related.

  9. Check version and recent reviews
    Go to Play Store or App Store, sort reviews by newest, and see if others report the same stuff for the latest version. For me, version after mid‑December update started dropping calls a lot more.

  10. Send them logs
    In Zangi settings there is usually a “Send log” or “Report problem” option. Trigger it right after a dropped call or logout. Describe time, caller, network, and device model. Their support asked me for that and admitted to “temporary issues on some routes” between Europe and Middle East.

If none of this helps, I would keep Zangi only as backup and run a second app in parallel for important calls. At least until they push a new update and the recent Play Store reviews calm down.

3

Yeah, you’re not the only one. Zangi has been a bit of a clown show lately.

@himmelsjager already hit most of the usual suspects (battery, background, DNS, etc.), so I won’t repeat that checklist. A few different angles to try:

  1. Watch the pattern, not the individual crash
    Are the drops only when:
    • Calling cross‑country / cross‑region
    • Switching from Wi‑Fi to mobile data mid‑call
    • Screen is off for more than ~30–60 seconds
    If it’s tied to screen‑off or network switch, that screams app-side handling issues rather than your phone alone.

  2. Turn off “smart” / “adaptive” crap inside Zangi
    Dig through Zangi’s own settings:
    • Disable anything like “Low data mode,” “Adaptive call quality,” “Save bandwidth,” etc.
    Those can cause aggressive codec/connection renegotiation that manifests as dropped calls instead of just reduced quality.

  3. Try forcing a specific network path
    • If your mobile supports it, lock the phone to LTE/4G only (no “auto 5G/4G/3G”) and test.
    • On Wi‑Fi, try only 2.4 GHz or only 5 GHz instead of “smart connect.”
    Zangi is more sensitive than it should be to network handoffs, so reducing hops and band-switching can calm it down.

  4. Turn off Wi‑Fi calling & VoLTE temporarily
    On some carriers, VoLTE and Wi‑Fi Calling fight with OTT VoIP apps. Try:
    • Disable Wi‑Fi Calling in system settings.
    • If your carrier lets you, toggle VoLTE off just to test.
    If stability improves, the carrier’s SIP/IMS stack is stepping on Zangi’s traffic.

  5. Test “local only” calls
    Call someone on the same network and same region:
    • Both on Wi‑Fi, same ISP if possible
    • Or both on LTE on the same carrier
    If that’s solid but international / cross‑network calls stink, it is very likely Zangi’s routing / servers, not your setup.

  6. Create a throwaway account
    Sounds dumb, but:
    • Make a second Zangi account, log out of your main one, log into the new one.
    • Test calls and messages for a day.
    If this new account behaves much better, your main account may be flagged or stuck on some bad backend route. Their support never advertises that, but it happens.

  7. Check exact app version and roll back if possible
    Instead of just “latest version”:
    • Note the exact version number that is giving you trouble.
    • If you can sideload, try 1 or 2 versions older from a reputable APK mirror.
    If the older version runs fine on the same phone and network, you have your answer: regression on their side. I’d actually disagree with @himmelsjager a bit here: if a specific update broke it, jumping through tons of OS tweaks is just coping. The fix is on Zangi’s side.

  8. Watch system logs while calling (if you’re up for nerd mode)
    If you’re comfortable:
    • Use adb logcat on a PC while you make a Zangi call.
    • Look for repeated “socket”, “keepalive”, or “wakelock” errors right before the drop.
    That can tell you if Android is killing it or the app is just failing to maintain the connection. You don’t need to fully understand the logs; even screenshots can help if you send them to support.

  9. Compare with another VoIP app under identical conditions
    • Same contact
    • Same Wi‑Fi / same spot in the room
    • Same call duration
    If Telegram / Signal / WhatsApp work perfectly while Zangi dies, that’s more proof it’s not just “your network is bad” like support loves to say.

  10. Decide if it’s “primary app” material right now
    If you need reliable calling (work, family overseas, etc.), I’d honestly demote Zangi to backup for a bit and run another app in parallel. Flaky updates happen, but months of dropped calls is not worth it just because it “used to be good.”

If you can post:
• Phone model
• OS version
• Zangi version
• Network type (carrier, Wi‑Fi ISP)
someone here can probably tell you if it matches patterns others are seeing or if your setup is uniquely cursed.

4

Quick add-on from a troubleshooting angle, without rehashing what @mikeappsreviewer and @himmelsjager already covered.

1. Check if the problem is “session length” related

Zangi lately glitches on longer calls more than short ones.

  • Do 3–4 test calls: 1 minute, 5 minutes, 15+ minutes, same contact, same network.
  • If only longer calls die, that points to keepalive / NAT timeout on their side or your router.

If that’s the case, try:

  • On your router, disable any “SIP ALG” or “VoIP accelerator” option. Those often break third‑party VoIP like Zangi.
  • Shorten router idle timeout if possible, or enable “UDP timeout” tweaks if your firmware allows it.

2. Check router QoS and “gaming / streaming” modes

A lot of routers have QoS presets that unintentionally starve small UDP flows.

  • If you have QoS, create a rule to prioritize Zangi traffic (or prioritize VoIP/real‑time apps in general).
  • Temporarily disable “Gaming mode / Game accelerator / Streaming accelerator” and test.

If other VoIP apps (Telegram, Signal, WhatsApp, etc.) work fine with the same router settings, Zangi is just more fragile, but QoS can still help.

3. Profile the exact failure mode

Instead of just “call dropped” or “delayed messages,” look at:

  • Do you still hear the other side for a few seconds after they lose you, or is it simultaneous?
  • Do messages suddenly all arrive in a batch after a long silence?

If everything arrives in bursts, it is usually a stall in a single persistent connection. That again screams either:

  • Zangi’s signaling server issue for your region, or
  • Aggressive middlebox (carrier NAT or corporate firewall).

Testing the Zangi app on a completely different Wi‑Fi (friend’s house, cafe, or mobile hotspot from another carrier) is gold here. If behavior improves instantly, no phone tweak will fix your usual network.

4. About using Zangi as a “main” app right now

Given what you and others report:

Pros of using Zangi right now:

  • Still very good audio quality when it works.
  • Often lighter on data compared with some competitors.
  • Nice for people who want a smaller, less mainstream VoIP app.

Cons right now:

  • Call stability issues that seem to have worsened in recent updates.
  • Delayed messages when networks switch or on spotty Wi‑Fi.
  • Random logouts on some Android setups, which is a dealbreaker for primary messaging.
  • Less transparent communication from support about ongoing routing problems.

That “cons” list is why I would not rely on Zangi alone for mission‑critical calls until they push a clearly more stable build. Keep it on your phone, but pair it with at least one of the usual suspects (Telegram, Signal, WhatsApp, Viber, etc.) so you always have a fallback.

5. Where I slightly disagree with earlier advice

  • @himmelsjager focuses heavily on OS tweaks like battery and DNS. Those are absolutely worth trying, but if you notice the problems started right after a specific Zangi update and no other VoIP apps misbehave, I would not sink endless time into phone gymnastics. At that point, it is very likely a regression in the app.
  • @mikeappsreviewer mentioned rolling back versions, which is solid, but I’d only do that after confirming other apps are stable on the same network. Otherwise you end up chasing ghosts that belong to your router or ISP.

6. When to escalate and what to send Zangi support

If you decide to stick with Zangi:

  • Document 3 or 4 failed calls: exact time, both regions/countries, whether you were on Wi‑Fi or mobile, and approximate call duration before drop.
  • Mention that other VoIP apps are stable on the same network. This pushes them away from the generic “your network is bad” reply.
  • If you have logs from a test with another phone or another network, include that contrast.

If after an update or two the situation does not improve, I would keep Zangi installed for occasional use but mentally demote it to a secondary option and move your main calling/messaging flows to a more consistent app.