iNPUTmice / Conversations

Conversations is an open source XMPP/Jabber client for Android

Home Page:https://conversations.im

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Echo issues with Fairphone 4

Greylinux opened this issue · comments

Hi ,

Sorry to add another Echo video call issue to your issues tab.
I have a Fairphone 4 which appears to have the same echo issue as other fairphone models. I believe it has something to do with the device having 3 mics and which one the app chooses to use during video calls, but I'm not entirely sure.
Fairphone have put out a fix for other proprietary apps such has whatsapp that apparently has fixed the issue for them , I have trialled using Jitsi which appears to not have the Echo issue.
If I call using just an audio call it doesn't cause an echo for the other user, so its specific to video calls only and the echo is heard by the otheer user, so its obviously my device.

I uderstand you dont have the device to trial a fix, so is it an option for me to fork your application and trial the fix my end to see if it works? I know you have added some devices to a black list could this be an option ?

For reference I am running /e/ OS (android 12) on Fairphone 4 calling a Oneplus 5, but video calling other devices has the same issue. Ive tested all 3 mics using Fairphones software for hardware testing and they work fine.
I am running through my own self hosted Snikket xmpp server and I have trialled the Snikket android app (fork of yours) and your app directly. If I video call from Dino to the Oneplus device there is no issue with Echo , So its definitely the Fairphone.

Thanks in advance for any advice you can give me.

The same thing happens when I call my parents, who recently got a Fairphone 4. However, it is not so much an echo (echo, echo, ...), but rather a feedback-like high-frequency interference. I use a headset, my parents do not.

It's just fixed on monocles chat (1.7.5) and a pull request is sent to conversations. Both apps should be fixed with the next update.

@Arne19 is that truly a fix or just a way to ignore it?