Apple watch S4 call failed

it was working, no problem, before the WatchOS upgrade from 5.x to 6.x

In dev language it’s called a “regression”.

I can’t see a good technical reason for this bug not to be fixed.

Let’s wait and see what happens

Facts are: the bug is STILL present. After lots of updates since WatchOS 6 and lots of months (8!) After hours at the phone with apple support, after sending them lots of diagnostic files. My last call with apple support was today: “yes we know about the issue... maybe the next update will fix it”. Unacceptable answer after 8 months! Sorry to say that, but this is a huge shame. The bug isn’t a minor bug. It impacts on the mainly functions of our apple watches. Since 8 months we don’t have solutions. We don’t have apologies. Nothing. Time for a class action, I think. Anyone here has different solutions? How can we enforce our rights?

yeah I know how you feel, I have the same watch and mine is doing the same call failed but I'm resetting mine now but back to iOS 5 for the watch thanks to all my backups I've made regularly so I will let you know if it works. It sounds like a bug in the actual software that apple have released but it needs addressing typical Apple for you

Right! It’s a SHAME. Yesterday. I’ve called the support, after months without solutions (this huge bug that make our devices useless is present since Watchos 6, more than EIGHT MONTHS!). The answer was the same: we are aware about the issue, please wait the next Ios/WatchOS update. It’s clear apple will NEVER fix the issue, who cares now about old iPhoneS SE!?? I feel cheated. A brand who speaks about equality, rights, justice... trampled on MY right. What can we really do!?

Based on my experience WatchOs 6 and iOS 13 have an heavy impact on my iPhone SE battery. At least this is not an issue on the Apple Watch 4 side. And yes, the Siri/Bluetooth/calls-drop issue still persists. After 9 month. In the total silence from apple

Aleeekoi wrote:

Hi Kevin,

how do you unlock your watch using iphone device?

Thank you

HI there, it’s very convenient in general to have your phone unlocking the Watch but it won’t make any difference with your Watch bluetooth issues.

Go into the Watch app on your phone, choose “Code“ and scroll down to “unlock with iPhone“ and enable the switch. Done.

Please note I have had this enabled since the early days and the Siri issue remains.

Note to all: as for today, WatchOS 6.2.5 and iOS 13.4.1 the bug is still there.

Hope this helps

/P

Ehm... yes! As you can see here and on other similar threads about this bug it isn’t Just “my” case. It’s spread. “Unfortunately” not too much widespread to get apple to resolve it quickly. 10 months are passed. A shame

So what causes this problem in the first place?

Turned my watch off and on... No problem

Turned my iPhone off and on... No problem

Took my iPhone out of bluetooth range of the watch... No problem

Turned my WiFi (router) off and back on... Problem returned! Then did the "fix" and the problem again disappeared.

So, does this problem reappear when leaving the range of a WiFi connection? I dunno...got tired of testing. Hey, I'm retired now. I don't get paid to do this kind of stuff anymore. Let some hotshot Apple techie earn his pay.

Ok. Here’s my last update. I had a call today with apple support. After then months and list of updates (since WatchOS 6 and iOS 13) The ultimate answer is: “yes, we are aware of the issue. Sorry. You can try an exchange with a new iPhone at your local Apple store”. I was dazed! Yes I understood well: I have to take my Original iPhone SE to my local Apple store, They’ll value it (it’s about 50 euros). I pay my extra 500euros and I’ll have a brand new iPhone SE and -above all- my all devices functioning again!

Yes. I feel cheated by apple. As customer. As visually impaired . . As Human being . I’ll digg into it.

[Edited by Moderator]

Ergosum wrote:

Please, try also the official twitter support, could be another way…

When I was reading this forum, I also searched for this issue on Twitter. And I found some reports. For example on user said there:

"@AppleSupport I’m facing problem in Apple Watch series 5. I’m not able to pick calls and dial fro watch. Please help me out".

And here is what Apple Support answered:

"Help has arrived! Can you tell us more about what happens when you try to place a call using your Apple Watch? To confirm, are you still able to make and receive calls normally with your iPhone?"

And here is what I answered to Apple Support:

"Can you tell us more"

Are you kidding me? Do you ever read your own forums?"

And I gave a link to this topic.

Hi Ergosum,

1) No, clearly not. But I'll make sure to continue testing in the coming days. I'll let you know. I must say that with previous iOS and WatchOS updates it didn't take me long to reproduce the issue.

2) Interesting. So presumably, in your case, even quickly after these upgrades the issue appears again? That would suggest that WatchOS 6.2.8 doesn't bring any improvement but iOS 14 pb does. Perhaps you could try updating to iOS14 public beta too? I was hesitant to update to a public beta version as I haven't ever done so before and didn't want to take any risks with the phone I use daily. But as many people were posting good experiences in updating I decided to do so and so far I'm happy with it.

Best regards,

Mark

I have the same issue (series 4 + iPhone 8; latest iOs). The problem was reported to Apple already 5 month ago and I have uploaded Gigabytes of log-files together with the support team...and imagine: nothing happened until now!

"Our engineers work on your problem"...come on!

To me it seems like there is an issue whenever Wifi-Calling is involved (even if only activated on the iPhone).

I have checked virtually any different setup (different Wifi, different iPhone, etc.) the problem remains.

Is that how apple treats customers? Is that the premium service they advertise?

Any possibility for compensation?

I would have guessed that the phone functionality is one of THE key features of this (super expensive) watch?!

[Edited by Moderator]

I have the same problem, unpair and reset works. next day call fails.

Just a thought but can everybody with this problem make sure you report it to Apple Support, if people don’t report it the it reduces the chances of Apple doing anything about it.