I tried calling three different people from my FP2 on Telegram and all of them hear their voice echoing. I do not hear any echo, they do. I called them multiple times and for long calls.
The weird thing is:
Telegram calls work properly from the desktop application.
FP2 microphone works properly with normal calls and Skype (I do not use Whatsapp).
I could call via telegram without an echo using earphones (with the earphone integrated microphone)
So it does not seem to be an exclusively hardware nor an exclusively software issue, but rather a bad combination of the two.
I had the same issue with Signal a couple of weeks ago, but since then OpenWhisperSystems continuously releases updates which claim to decrease the echo (However, I haven’t tested it since then).
I don’t use Threema, but do you have the latest Threema version on your phone?
I do not use threema either. Apparently echo issues with telegram calls are rare (i do not know anyone else having them and I also asked on specific telegram groups) and I currently have the latest telegram release so it does not seem to be so much of a telegram issue…
Signal developers solved this issue by switching from hardware echo cancellation to software echo cancellation. This hardware mode seemed to be broken on Fairphone 2 (and numerous other phones), at least on Android 5.1. I actually never tried Signal with hardware echo cancellation on Android 6.0.
From this I assume that any app relying on Fairphone 2’s hardware echo cancellation will produce echo.
Which version of Telegram are you using? My contacts still hear themselves speak when I call them.
Both Telegram and Android are on the latest available version here.
I am on the latest telegram version, but for me this was solved some months ago. However I do not use this function often so I can only say the last times I used it I did not have this issue anymore.
That’s exactly the point. This is not limited to Telegram. Even Android’s native SIP client (integrated into the stock Phone app) suffers from this bug! The only workaround is using a headset.
Please vote for this bug in the bug tracker to give it more attention.