Acer2384 wrote:
Question...Has anyone sent in their watch to be analyzed by Apple? I would do so but I'm still running 3.1.3 after trade in.
I was at target the other day and asked an associate if they were having the same issue as reported here. She said no, that she was running the latest software and did not have this issue.
Can it be the Watch at this point? If it was a software issue, wouldn't Apple have made it a priority to fix? I mean it seems like only a few are having this issue.
I would advise you to keep your watch on 3.1.3 until its mentioned on this thread that Apple has fixed this software bug.
I know people on this thread have got their Apple Watch replaced and the replacement had 3.1.3 on it and the echo issue was not there. Once they had updated to 3.2, the echo issue returned, showing that it is a software bug introduced with 3.2.
I know it was mentioned that some people who did not have the Series 2 Apple Watch, didn't suffer this echo issue, so perhaps the associate doesn't have an Series 2.
If it were the watch, the echo issue would have been there since new. I and others have had the Series 2 since just after launch and they did not have the echo. I know personally that I done around 2 or 3 software updates on my watch prior to the 3.2 update. All the software updates I performed (before 3.2) did not introduce the echo issue. I think perhaps the software bug is something to do with the hardware that's in the Series 2 (but I hasten to add not a fault with the hardware) and the software that is in 3.2.
Apple seem more interested/busy at this time, with other software etc (the announced iOS 11, WatchOS 4, MacOS High Sierra and other new products in the pipeline).
The echo issue has been reported to Apple and they are indeed aware of it. Perhaps with WatchOS 4, they might be a fix. It would be interesting to know if WatchOS 4 does fix the issue, but the only people who have access to WatchOS 4 at this time are developers and they are not allowed to disclose any information about the software if I correct.
Its a real pity that Apple do not allow us to rollback to an earlier version of the Watch software, thus solving the issue.