Broken audio/echo with Telecom API 16.3.0.81 on Galaxy A3/Android 9

[syntcom]

Hello,

first of all: I know the info text under the API button in the settings and the problems with the API.

Just like to inform you and hope it helps you with finding a workaround for these issues, because Samsung devices are very common and it is so sad, that it just doesn't work properly.

When I go out, depending on if I use a headset or get into the car (with bluetooth audio) I have to go into the app settings and turn the Telecom API on or off. This is not feasible and results into many broken calls.

The problem:
Telecom API off and no headset connected, In Wifi and 4G: Audio is good, or expected behavior
Telecom API off and headset (wired or bluetooth) connected, In Wifi and 4G: Audio is good, buttons on the headset not working like expected
Telecom API on and no headset (wired or bluetooth) connected, In Wifi and 4G: My audio is normal, but the counterpart has an annyoing echo and the voice is low (not useable)
Telecom API on and headset (wired or bluetooth) connected, In Wifi and 4G: My audio is normal, but the counterpart has an annyoing echo and the voice is low (not useable), Buttons on the headset work like expected

There must be a way to fix the audio or change the way it behaves depending on if a headset device is detected or not.

Thank you,
Michael

 

[JohnS_3CX]

Hi Michael,

We can control which API we use (and you can too from the toggle) but we cannot control what the API itself does.

The reason is simple (and somewhat sad) that each Android phone manufacturer can customize the way their phone behaves. This means that the same API will behave differently on say a Samsung VS a LG phone. Since we can only talk to the API, we cannot always control the behavior AFTER the API and this means you will not get a consistent experience across all phones, and even across all Android versions (i.e 8,9,10).

You will notice the same deal outside of the world of 3CX, when using various bluetooth headsets on various Android phones - they just don't always behave the same. I hope this clears things up, and I also hope that in the future there will be a more "common" behavior, but such is the world of Android