Your Phone calls unusable due to too much echo

My issue is the person on the other end is getting the echo not me.  My end is fine but everybody gets the echo on their end.  No idea what that's about.

Hi,

I have the same problem. My Samsung S10e is paired with my Win10 Pro 2004 via bluetooth and good quality USB, wired, headset plugged into Win10. When making phone calls using Your Phone, some users complain on echo on their end. On my end there is no echo. When called directly (using a mobile, without Win10, Your Phone, headset) no one complains about echo. 

I use the same set also for MS Teams, Jabber and Skype (on Win10) with no complains on echo.

Not sure whether this echo is caused by a mobile-to-laptop-over-bluetooth-connection or solely by Your Phone application or both. 

I can also see there is another post titled "Your Phone" in this forum, reporting echo on the other (call recipient's side) so it seems to happen to a few people, not just myself and Pino.

Thanks, Leszek

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.

I have a Samsung S10 phone connected to a Lenovo ThinkPad laptop via bluetooth and the Your Phone app in Windows 10 version 1909. When I make or receive calls everything sounds fine on my end but the other party complains of a loud echo of everything they say, however no echo when I talk. I would rather not connect by a cord. I move around the house quite a bit and want to have my hands free, so when I'm not at the computer I use a Bose headset connected via bluetooth to the same phone and there is no echo problem using it. If other people are having the same problem with other phones and computers it seems like a Windows 10 issue.