Solved 3CX Android App Crash: Yealink "Video First" calls on Android 16 QPR 3 & 17 Beta

[t.quitsch]

Hello everyone,

We are using 3CX Version 20 Update 8 on Debian and have identified a reproducible issue with video calls on Android devices.

Environment:

3CX Server: Version 20 Update 8 (Debian)

3CX Android App: Version 20.6.0.20 (Version 5.5 Build 20)

Android devices: Google Pixel 8 with Android 16 QPR 3 and a test device with Android 17 Beta 3

Caller device: Yealink T58V with CAM50

Cross-check: iOS extensions (work without issues)

Error Description & Reproduction:

Scenario A (Option “Video First”):

Call from the Yealink T58V (Video First enabled) to the Android extension.

The Android app rings.

As soon as the call is answered on the Android device, the 3CX app crashes immediately.

Scenario B (Option “Video Optional”):

Call from Yealink T58V (Video Optional) to the Android extension.

The call is answered on the Android device.

The call connects and audio works, but the Android app does not send a camera image (black screen).

Additional information:
A test update of the Android smartphone to the latest Android 17 Beta 3 did not change anything; the behavior (crash or black screen) remains exactly the same. A cross-check with an iOS extension in the same setup works perfectly smoothly (video and audio present on both sides).

There appears to be a compatibility issue with SIP video negotiation or access to the camera encoder in the new Android versions.

 

[ThomB_3CX]

@t.quitsch thanks for the feedback. We're looking into it

​

 

[t.quitsch]

Hello everyone,

A quick update from me: The latest Android 17 beta is now available. Since the official release of Android 17 is expected soon, time is of the essence—as soon as the system is officially rolled out, all Android users with current devices will suddenly face this issue.

Is there any new information or an update from the development team regarding this issue?

In addition, I’ve gathered new insights this week that show the underlying API issue actually begins with Android 16 (since the last Google Feature Drop).

On Android 16, the app doesn’t crash completely, but during a regular voice call, there’s a noticeable delay of about 1 second before the audio connection is established. The log clearly shows that during this time, the app is forced to perform a fallback of the audio system.

I hope this information helps the developers further narrow down the problem in time for the final Android 17 rollout (presumably by permanently disabling OpenSL in favor of AAudio).

 

[ThomB_3CX]

Hi there, after some investigations, it looks like this issue is coming directly from Google on their Pixel devices.
We found a few tickets already opened and also testing internally, not all Pixel devices are effected.

We are looking to make a fix from our side for this

 

[t.quitsch]

Hi @ThomB_3CX
Is there any news on this yet?
We're already in the QPR1 beta program.
This is the preview version of the first feature drop for Android 17, and several tickets related to VoIP and audio have been resolved in this version.
If you already have a new version of the app, feel free to send it to me as an APK or APKM so I can test it.

 

[ThomB_3CX]

@t.quitsch repied to you privately via Pm

 

[t.quitsch]

I reactivated video calls at our company today, and I can confirm that the issue has been resolved.
Thank you very much for the fix.