You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Callers hear their voice echo if I take/make calls using Apple Watch

I'm having a bit of an annoying issue with using my Apple Watch for telephone calls and wondered if anyone has experienced the same issue?


When I either receive or make a call from my Apple Watch (which is a Series 2 running the latest software). The person I am talking to, tells me that they can hear an echo of what they have just said, and this then makes it difficult for them to hear what I am saying.


I have also spoke to someone via a landline, and they tell me that the echo is there too.


The weird thing is. While I am on a telephone call and the person on the other end mentions about the echo, if I then hand the call off on to my iPhone (iPhone 7 Plus with iOS 10.3 installed) the person tells me the echo has gone.


I was wondering if anyone has been able to get to the bottom of this issue?


I cannot really say how long this issue has been going on, apart from it wasn't there when I got the Apple Watch back in December.

iMac, macOS Sierra (10.12), iMac 27in Late 2012 Fusion Drive

Posted on Mar 31, 2017 2:28 PM

Reply
78 replies

May 18, 2017 11:26 AM in response to pnw44i

pnw44i wrote:


My local store reccommended I send it in for service, so I did. I just recieved an email this morning stating they couldn't find anything wrong with it and it is being sent back as-is.


Thier failure to recognize the problem is frustrating. I wanted to buy another Series 2 as a Mother's Day gift but this experience kept me from making that purchase.


If Apple can say that there is nothing wrong with the actual Watch, then the only other thing that controls the Watch is the software, so the issue has to be the software.

May 18, 2017 11:38 AM in response to Acer2384

Acer2384 wrote:


So I take Apple is still not recognizing the issue? I was really hoping that the new OS was going to fix this issue. I am going to stay on 3.1.3 until its reported the issue was resolved. Its a shame that only a few of us are experiencing this issue. I wonder if it has to do with the batch of watches ours came from or the OS is mainly at fault.


Has anyone gone to their local Apple store to see if anyone there is experiencing the same issue? I'm thinking of going to the store this weekend to ask.


The best thing that the people who are suffering the issue can do is to report the issue to Apple by submitting a feedback report on the link I've mentioned earlier. I too wish I'd stopped on 3.1.3


If the issue had been there since day one, then yes perhaps the Watch could have been faulty. But I know 100 percent that when I got my Apple Watch back in December last year, the issue was not there and it only appeared after I'd updated to 3.2, so it had to be a software bug that was introduced with 3.2, as the software is the only thing that has changed. I haven't even installed any different apps on to my Apple Watch eother from Decembe, so it's not like it's a recently installed app that could have caused it.


I know it's a busy time of year for Apple, but its no excuse for leaving software bugs in software.

May 18, 2017 12:44 PM in response to tal1971

I called apple support and spoke to a senior advisor again to see if the issue is being looked at. Long story short, it is on their report regarding this issue but they do not know if/when an update will come to correct this. Its not widespread but they have accounted for many cases of the issue.


I told him that many others are experiencing the same issue and that a few have tried to upgrade to the most recent OS but nothing is fixed. He said to stay on the 3.1.3, due to not currently having any problems, and just refer back to the thread/forum once a new update comes about.

May 18, 2017 1:29 PM in response to Acer2384

Acer2384 wrote:


I called apple support and spoke to a senior advisor again to see if the issue is being looked at. Long story short, it is on their report regarding this issue but they do not know if/when an update will come to correct this. Its not widespread but they have accounted for many cases of the issue.


I told him that many others are experiencing the same issue and that a few have tried to upgrade to the most recent OS but nothing is fixed. He said to stay on the 3.1.3, due to not currently having any problems, and just refer back to the thread/forum once a new update comes about.


It's a pity Apple don't give us the option to roll back to an earlier software version, for when things like this happen 😠

Encouraging somewhat to know that tech support are aware of the issue, but not that encouraging to not have any timescale of when/if the issue will be fixed.


I think Apple will be working on WatchOS 4, and as such will be paying lesser attention to WatchOS 3. Hopefully if all else fails, WatchOS 4 will fix it.

May 18, 2017 2:18 PM in response to tal1971

I used another Series 2 with OS 3.2.2 today at the Apple Store paired to my (same) phone to experiment. It worked just fine with no complaints from callers.


I will try pairing the watch that AppleCare returns to me with another phone in the household. If it still doesn't work I will be sending it back to AppleCare until I receive a product that works. This is what the gentleman at the Genius Bar recommended I do moving forward.

May 21, 2017 12:15 AM in response to pnw44i

pnw44i wrote:


Unfortunately we had further discussions and updates this morning and they were removed by an admin. More people chimed in and there was discussion about different iPhone models that had been tried.


That would have been useful, pity they got deleted as we might have been able to see if there were a pattern.

May 21, 2017 6:11 AM in response to tal1971

I have reached out to the apple care senior advisor I was working with (provided him with diagnostics from my Watch) and I have not gotten a reply. This is extremely frustrating. I was very hopeful a fix would have been in the last update. The sales woman at the store was not having a problem with her series 1 one Watch and the 3.2.2 update so I don't know if it's hardware with the series 2, software, or a combination of the two.

May 22, 2017 12:16 AM in response to Vegasmichele

Vegasmichele wrote:


I Have been to the store and am on my third series 2 watch....had the problem with all three after updating to 3.2.2. sales woman with a series 1 Does not have the problem with the 3.2.2 update. At least that's what she told me.


Thanks that's very helpful 🙂


It will be interesting to know if anyone with a Series 1 or even the original Apple Watch suffers from the echo issue with 3.2.2.

May 26, 2017 9:40 AM in response to MrsSpooky

I think we all have called and used the link to submit the issue. It is frustrating however I was lucky enough to be within my return period that I exchanged it for another one. Still using the 3.1.3 os. I would highly recommend for those who can exchange the Watch to do so and hope the ew Watch will have the old software.


Last time I spoke with tech , they had it noted in their system as this being an issue. What I don't get is that some users are experiencing this issue while others are not. That gets me thinking that it might be the Watch?? Although users with the original Apple Watch are showing signs as well. Frustrating!

May 26, 2017 7:12 PM in response to tal1971

I just purchased mine yesterday and am getting this issue too. I'm on the latest software, I don't THINK I was getting the problem when I got it, before I upgraded, but I'm not sure (no one said anything to me about echoing yesterday when I was on the phone and had the old software). I called Apple and talked to a senior advisor and they are forwarding the issue to the engineering department. They took a bunch of screenshots and info from me and I have a follow-up call scheduled for Thursday next week, hopefully they have an answer then.

May 27, 2017 1:03 AM in response to katymorris

katymorris wrote:


I just purchased mine yesterday and am getting this issue too. I'm on the latest software, I don't THINK I was getting the problem when I got it, before I upgraded, but I'm not sure (no one said anything to me about echoing yesterday when I was on the phone and had the old software). I called Apple and talked to a senior advisor and they are forwarding the issue to the engineering department. They took a bunch of screenshots and info from me and I have a follow-up call scheduled for Thursday next week, hopefully they have an answer then.


On my S2 Apple Watch, my problem wasn't there before WatchOS 3.2. So I would think that if your newly purchased Apple Watch didn't have the issue when you first got it, it would have had WatchOS 3.1.3 on it.


I suspect it is a software bug introduced with WatchOS 3.2. Hopefully the more people who get in touch with Apple with the issue/submit feedback to them via the link I posted earlier. The sooner the bug will be found and fixed.

Callers hear their voice echo if I take/make calls using Apple Watch

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.