I deavticivated AGC in the Mic settings and it worked for me
Your Phone calls unusable due to too much echo
I have setup Your Phone on my PC and Phone Companion on my phone (Nokia 7.1) - both devices have latest software and are fully patched.
While I can make and receive phone calls via the Your Phone app on the PC (and they sound fine at my end) the other parties all complain of excessive echo so that I need to conduct the call on the phone.
My mic and speaker settings are the same as I use for Skype, Zoom, Hangouts, etc. - how do I trouble shoot this?
Is it possibly caused by the mic / speakers on the phone remaining active during the call?
Thanks
Pino
Windows for home | Windows 10 | Connect Phone and PC
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
76 additional answers
Sort by: Newest
-
Anonymous
2021-02-20T10:59:10+00:00 What I think is "Your Phone" App is sharing all computer sounds with the caller. I mean what you are hearing from the computer, all of it is being shared with the caller, and I mean all of it, including the voice of the caller. Caller is hearing everything you hear, including his/her voice, causing an echo on the caller side.
Just an option to disable sharing of computer sounds with the call could be a quick and dirty fix.
-
Anonymous
2021-02-03T00:40:05+00:00 I came to the same conclusion.
John
-
Anonymous
2021-02-02T23:28:26+00:00 I did a bit of testing with this issue. Normally my phone will mute my mic when anything is coming from the speakers (this is standard phone functionality to avoid echoes). The Your Phone app isn't doing that. So my mic picks up what I'm hearing as I'm hearing it, and sends it back to the other person on the line.
I think this is an old problem, pertaining to the basic functionality of phones. And it has a solution but Msft just didn't implement it (yet), or it's not working for me.
-
Anonymous
2020-12-23T18:28:40+00:00 The issue has multiple variables. I'd suggest to the Your Phone developers: Allow users to control how audio is handled. Here's a prime example per Skype:
Frankly, please—please just steal this from Skype. It solves all the issues from a usability standpoint. The fact we have an app that handles calls (in any capacity) but doesn't allow us to set custom Microphone, Speaker, and Secondary Ringer options is simply absurd. (The Secondary Ringer/"Also ring on" option is agreat way to utilize the typically terrible speakers that are built into devices like monitors.) I've always had this gripe and it's now long overdue to air it.
As for the actual issue, I believe it has a lot to do with not having control over these options. For instance, when I have the settings as shown below (which works great in everything from Skype, to Teams, to Hangouts, to Zoom), there's rarely an issue if at all. This suggests that the controls these apps have over the handling of audio routing for their specific uses is preferable to however Your Phone handles it.
I'll also point out that, for the Your Phone app, it has never mattered how I set up my default audio options for Recording, because it always uses my "Desktop Microphone" as the default microphone regardless. As of this post, I have the latest Bluetooth available for desktop computers with the latest drivers (and no drivers have ever improved this situation). The only "workaround" to this issue is to make the "Headset Microphone" the Default Device and Default Communications Device. To me it's clear indication of a routing issue.
The fact is, while this app is handy and has it's conveniences, it's poorly thought out from the standpoint of a person who uses their phone to actually make calls. If the issues were simply due to Bluetooth latency, I could deal with that, but there's a systemic problem here that needs to be addressed.
It's my firm belief that once users are provided with these controls in the Your Phone app, we can start to remove the app itself from the problem's equation and begin to narrow it down to bad drivers or even bad hardware.