After updating sdk to com.azure.android:azure-communication-calling:2.15.0 Call agent creation can take 30 seconds, failing incoming calls

Hello @Jonathan Volij ,

Thank you for posting your question on Microsoft Q&A.

This issue recognized performance regression in com.azure.android:azure-communication-calling:2.15.0, impacting call agent initialization times on certain Android OEM devices, particularly Xiaomi, Oppo, and some Samsung models.

With SDK 2.15.0, Microsoft addressed a 16 KB memory alignment issue affecting hardware-accelerated audio and video buffers on some devices.

However, the update introduced lazy initialization of internal native libraries and media engine configuration, which may result in delays of up to 20–30 seconds on devices with specific vendor customizations, such as Xiaomi MIUI power optimization or restricted background threads.

Initialize the SDK early

// Run as early as possible, e.g., in Application.onCreate()
val callClient = CallClient()
callClient.createCallAgent(context, credential, options) { ... }

Reuse the initialized agent instead of creating a new one when a call is received.

Disable MIUI battery optimization: Advise users to turn off “Battery Saver” or “MIUI Optimizations” for your app (Settings > Apps > Your app > Battery > No restrictions).

Temporarily roll back: Versions 2.14.1 or earlier do not exhibit this latency issue. Consider using 2.14.1 until Microsoft provides a fix, anticipated in 2.15.1 or 2.16.x (currently under internal review).

Could you please share the details which I've asked in private message that will help us to investigate more on this case.

Hello @Jonathan Volij ,

I Just want to know whether the comment above addressed your issue. If you need any further help, please let us know. We’re here to support you.

I modified the battery optimization setting and it didn't fix the issue.We will wait for the fix

We noticed this on a Samsung device as well

Hello @Jonathan Volij ,
Thanks for the update and below are some advanced troubleshooting and mitigation strategies to address the long delays you're experiencing with CallClient.createCallAgent(...) in SDK 2.15.0 on certain Android OEM devices.

Enable Verbose Native & Debug Logging : Enable verbose tracing to pinpoint which initialization steps are taking the most time. Use the SDK’s logging APIs and then call CallClient.getDebugInfo() after agent creation. Match timestamps of native library loads, media engine initialization, and network-handshake phases.

Pre-warm Native & Media Engine Layers : Since lazy initialization causes delays, you can simulate a lightweight “dry run” on app start to force lib loading:

1. Early in Application.onCreate() or a background Service, invoke a dummy createCallAgent.
2. Dispose it immediately once thenAccept returns.
3. Reuse it for real calls. This preloads native stacks ahead of real call-time, easing latency. Although unorthodox, it's a practical workaround given the OEM throttling behavior.

Validate Network & Token Latency: Long timeouts in agent creation may stem from network issues (DNS/TCP handshake) or slow token refresh.

• Capture and measure:
  • Time to fetch ACS token
  • DNS resolution delay
  • SYN/ACK for initial calls to ACS endpoints
• Consider injecting custom DNS (Cloudflare, Google) or pre-resolving endpoints to reduce delay. This is recommended in the ACS troubleshooting guide for slow call-setup

Refine App-Level Threading & Performance: MIUI and other OEM OS variants may throttle thread initialization:

• Offscreen, prioritize initialization on a foreground thread with elevated OS priority.
  • Use HandlerThread with high priority.
• Place CPU-heavy tasks (like native engine init) in excluded paths:
  • Consider temporarily whitelisting the process from MIUI’s battery/sleep manager.
  • Formal Android PowerManager APIs may help (REQUEST_IGNORE_BATTERY_OPTIMIZATIONS).

Confirm or Adjust Memory Alignment: Although AMD-like 16 KB buffer alignment fix is essential, test whether disabling/hacking this aspect is viable short-term for select devices:

• Compile a custom AAR reverting to 4 KB alignment on Xiaomi/Oppo/Samsung builds.
• Defer upgrading for those users until 2.15.1 or 2.16.x ships. This is more advanced but allows testing to isolate the root cause.

Reference:

https://learn.microsoft.com/en-us/azure/communication-services/concepts/voice-video-calling/calling-sdk-features?source=recommendations

https://learn.microsoft.com/en-us/azure/communication-services/resources/troubleshooting/voice-video-calling/call-setup-issues/failed-to-create-call-agent

Kindly let us know if the above comment helps or you need further assistance on this issue.

Please "upvote" if the information helped you. This will help us and others in the community as well.