Facing microphone issues in the latest teams-for-linux version '1.4.1'

[emailstorbala]

Describe the bug
When using the latest version of 'teams-for-linux', the microphone audio is malfunctioning.

To Reproduce
Steps:

1. Upgrade to latest version 1.4.1
2. Connect the teams and try a meeting with a separate microphone device.
3. The other meeting persons are receiving an echo/distorted voices.

Expected behavior
Clear audio should be received by other recipients.

Screenshots
Since Audio is the issue, screenshot is not applicable.

**
Laptop: Thinkpad T470
OS: Debian 12 (Testing)
DE: KDE/Wayland

Additional context
Tried multiple times joining the same meeting. Restarted Teams also. No impact.

Only after going back to the older version of teams-for-linux '1.3.26', the issue is getting resolved.

[emailstorbala]

Now I am facing the same issue in 1.3.26 version also.

[fran-penedo]

I can confirm the issue in 1.3.26 and 1.4.1.1, @emailstorbala please reopen.

[SlavikZ]

The same issue for me. Meeting participants are complaining about the echo from me.

[pacoarribas]

Same issue, with Thinkpad T490, Dell Latitude, Pop! OS

[IsmaelMartinez]

Can you check if this is the same issue using the web browser? Sound issues normally are related to system configuration and/or MS changes.

[IsmaelMartinez]

Otherwise, can you check if using the disableAutogain option does the trick?

https://github.com/IsmaelMartinez/teams-for-linux/blob/develop/app/config/README.md

[sisco70]

Same issue. Ubuntu 22.04 LTS. Teams for Linux version 1.4.1.

The meeting participants heard an echo. I closed Teams for Linux, connected to the meeting from Chrome, and everything settled down. I did not make any changes to the audio configuration.

I have not yet been able to try version 1.4.2

[fran-penedo]

In Chromium, the issue was present for a while yesterday but works correctly now. The disableAutogain workaround fixes the issue.

[Mushoz]

I am facing the exact same issue. It was very difficult for our customer to follow me in our Teams meeting. I am using the browser version for now to work around this issue.

[IsmaelMartinez]

Did you try the disable autogain?

[sisco70]

I just made a voice call with version 1.4.2 and there were no Echo problems, without having to change the flag autogain.

I don't have meetings today to test (in case it behaves differently)

[gpcmol]

I also had the same issue. My (unproven) guess is that after the update to 1.4.1 (last Friday on my Lubuntu OS/computer), teams (or chrome) adjusted the microphone to 100%.
After some fiddling, I put it to 24% and my collegues are nice to me again.

[Danipiario]

Same issue for me, even with disableAutogain flag.
I've tried version 1.4.1, 1.4.2 and also 1.4.3 from edge channel with no luck.
It seems to be releated to Microsoft Teams New version.
Unfortunately the issue is still present with teams on browser for me

[IsmaelMartinez]

sorry to hear that. unfortunately if it is also happening in the browser, then is a MS issue. Fortunately, they got 100s more developers than us.

[dha4171]

I too get the echo with the app and with the browser. I just tested the disableAutogain and it seems to work now. First call was always ok. Subsequent calls would have the echo. I will definitely be using it more tomorrow and will report back.

[gpcmol]

After I posted the screenshot above, I thought the issue was resolved, but it seems that the echo is back unfortunately

[gpcmol]

https://answers.microsoft.com/en-us/msteams/forum/all/people-can-hear-an-echo-when-using-teams-so-not/52cbda27-6494-47a4-904b-51db20345a76?page=5

[Danipiario]

I reinstall the snap and today it's working

[IsmaelMartinez]

I will put the 'won't fix' tag but leave it open in case there is any workaround that can be shared. Unfortunately this looks like a MS issue.

[emailstorbala]

I am using version 1.4.2 (teams-for-linux) from yesterday with the flag '--disableAutogain'. Its working without issue till today morning.

Today there was an update 1.4.3 (with some wayland screen sharing rework). This brought in a new issue while sharing the desktop. During desktop sharing, the audio is completely distorted/ too much echo. This is tested with and without the flag '--disableAutogain'.

Now I have reverted back to version 1.4.2 with the flag '--disableAutogain' and its back to normal.

CC: @IsmaelMartinez

[emailstorbala]

After I posted the screenshot above, I thought the issue was resolved, but it seems that the echo is back unfortunately

@gpcmol If we don't set --disableAutogain, the microphone volume automatically raising to max/full.( atleast < 1.4.2). In 1.4.3, with --disableAutogain, it works good without screen sharing.

[IsmaelMartinez]

Can you try removing the cache? I would be surprised at the desktop sharing changes affecting this, as I don't think we share the device sound.

[gpcmol]

@emailstorbala I did the same now and the echo is gone (for how long ;)?)
My settings are:
1.4.2
--disableAutogain
input device on 24% (volume control Lubuntu)
teams Device settings: Noise suppression = High

[tsadan]

I looks like in 1.4.3 another input device starts, when starting to share a screen:
Input device without sharing:

Input devices right after start to share:

With that second input enabled, meeting paticipiants do hear echos. When the second input device is muted in PA volume control, sound is ok.
Can the start of the second input device be avoided somehow ?

[IsmaelMartinez]

I wonder if that screensharing is trying to share your computer audio... it should not do that by default but that is my guess.

[tsadan]

At least that was not actively configured by me, I wouldn't even know how to.
That happened after updating to 1.4.3. Could that be related to the rework of wayland support ?

[enzy]

The issue occurs for me when I start a screen share. From that point, others hear me twice (like an echo).
Wayland session.

[tsadan]

As I read here, the wayland screenshare part has been reworked. Maybe now there are more sources grabed than needed, not only the "screen" but more like audio devices.

[IsmaelMartinez]

aye, just waiting for 1.4.4 to be properly tested then we can do a pre-release of 1.4.5 with the hopefully fix.

[tsadan]

@IsmaelMartinez What do you think about removing the "wontfix" label, as it is (at least from what I read) confirmed to be related to wayland displaysharing and is about to be fixed by @herbiejhopkins ?

[IsmaelMartinez]

this might be fixed under https://github.com/IsmaelMartinez/teams-for-linux/releases/tag/v1.4.5

Closing as this should be fix. Do ask to be re-open if the 1.4.5 doesn't fix this issue.

[MonstrousOgre]

I was facing the issue while screen sharing yesterday. It seems to be fixed after I updated to 1.4.5

[damien-louis]

Thanks @IsmaelMartinez. Do you know when v1.4.5 will be released?

[jijojosephk]

@damien-louis 1.4.6 is just released. flatpak version is being built and gonna be available soon.

[jijojosephk]

publish fails seems like a problem with flathub.

flatpak run --command=flat-manager-client org.flatpak.Builder purge https://hub.flathub.org/api/v1/build/79008
 in dir /var/lib/buildbot-master/master/workers/MasterWorker8/publish/build (timeout 1200 secs)
 watching logfiles {}
 argv: [b'flatpak', b'run', b'--command=flat-manager-client', b'org.flatpak.Builder', b'purge', b'https://hub.flathub.org/api/v1/build/79008']
 using PTY: True
Purging build https://hub.flathub.org/api/v1/build/79008
Api call to https://hub.flathub.org/api/v1/build/79008/purge failed with status 400, details: {'error-type': 'generic-error', 'message': "Can't prune build while in use", 'status': 400}
program finished with exit code 1
elapsedTime=0.349693

[jijojosephk]

[jijojosephk]

It appears that there's a new permission workflow added to the flathub builds. There was a recent change in permission to flatpak manifest which needs to be approved by admins. @bbhtt would do it.

flathub/com.github.IsmaelMartinez.teams_for_linux#83 (comment)

[jijojosephk]

[IsmaelMartinez]

I think they just approved