Apple watch S4 call failed

I think what's really been bothering me lately is how much my iPhone/Watch/Airpods experience has been fraught with problems over the last year and while I was thinking maybe the "It just works" mantra wasn't it what it used to be, it just turns out that it's my setup that's the real issue.

I used to be out mid-walk and tried to move my Airpods from being connected to my iPhone to my Apple Watch and my Apple Watch would consistently complain about the Airpods not being in range, which is a lie because they were in my ears. It was probably this ongoing issue.

That's on top of a stack of other minor annoyances over the months that would have likely been solved if I wasn't using an iPhone SE. How irritating.

Ok. The issue with iPhone SE and related accessories connected via BT like Apple Watch AirPods ecc it’s acclarated, We all already know. Very well. Also apple knows it. Since 10 months. I was wondering: what about Covid api and apps that rely on BT connections?! Should I trust a device whose Os/firmware has been ruined by a software update? Can apple still ignore the bug, even in a case like this? (it’s about health). Time for apple to take care to this issue, I think. A serious issue.

All absolutely true. But in case you hadn't noticed, Apple's primary concern is with sucking every cent from every person's wallet. Leaving bugs unaddressed helps with that by coercing customers to replace their equipment.

I think you're onto something here. Calls were failing immediately, unlocked iphone XS MAX and the call worked on my watch. Locked the phone and it worked on my watch. Now to wait a while and see if I can make a call with phone locked.

Can anyone confirm whether this issue has been addressed with the iOS14 beta on iPhone SE (1st generation)?

iOS13 rendered my Apple Watch nearly useless and it's been that way for close to a year now. The fact that a bug that compromises functionality so severely has remained unaddressed for so long is mind boggling for a company that is so well resourced and known for its attention to detail. I refuse to "upgrade" my devices to fix this issue.

This entire experience has destroyed any enthusiasm I had for the Apple Watch - so much so that I intend to replace it with a regular analogue time piece once this one dies.

I'm surprised there isn't more noise about this on the internet. I would have thought there would be more people with this iPhone / Apple Watch model and OS combination having issues - obviously not enough for Apple to address it or take complaints seriously. They're obviously too busy making sure the "new" widgets feature in iOS14 works properly.

Much has changed over the past 10 years. Although they have a well deserved reputation for charging a premium prices, they also provided premium quality. The lightning connector is an excellent example of changing to improve the product. It has many features far superior to the previous connector, pre-dating USB-C by many years. The MagSafe plug was an outstanding improvement, as power connector breakage was the number one failure of all notebook computers, and still is.

It shouldn’t take a genius to understand the true reasons the headphone jack was removed, and it had nothing to do with leaving old technology behind or saving space inside devices. There was a great deal to be gained by pushing millions of users to an expensive and unnecessary wireless alternative. But the undeniable proof that quality is no longer an objective can be found in the abandonment of the MagSafe plug.

So the reason a critical software bug—unique to an older device—has been left to fester for so long should be obvious.

I couldn’t agree more. Your post, Crisb90, is “THE” post. The best resumé of this case. Even if apple will solve this with iOS 14 I’ll firmly ask for compensation. I can’t believe a brand like Apple has left us one entire year with a bug like this (I’ve fully payed a premium device, after a software update I’m with a piece of plastic and aluminium). There’s more. As partially sight, I’m dazed that apple still ignore this Case. . I used to consider apple the best brand for his attention to accessibility. After this insane year I rethink my entire opinion about this. A real Shame. Seriously shame.

Has anyone tried a combination of watchOS 7 Beta and iOS 14 Beta? Does this shameful problem continue to be observed? I also have this problem (iPhone SE 1st gen and Apple Watch Nike Series 5). I read all 19 pages, and I share the indignation and frustration of the forum participants. The quantity of users who have checked in here with the same problem (over five hundreds for the moment) is impressive. I sent the report using the link that was given here earlier. I described the problem and also offered to calculate for them how much time has passed since the problem was registered, if they are not able to do it themselves.

thanks for sharing your experience. I also hope Watchos 7 will solve this HUGE issue. But I also hope Apple will consider a compensation. A whole year with our devices fully payed but more than halved on their main functions is a real shame an it’s unacceptable. Please, try also the official twitter support, could be another way....

It’s appreciable that users try to find workarounds. Sorry to say that but this trick didn’t solved the issue. Thanks anyway

we have to face it: the solutions has to come from Apple side, not customers. This is a bug. A huge, multi-bug. Apple is aware of the issue. We all firmly have to ask Apple for a final solution and (after 11 months and all these malfunctions) also for compensation.

Thank you, but I'm sorry, I didn't even try to do this, because for me it is obvious that changing mode from light to dark will in no way solve this problem. I saw different hints, but this one is really strange, and has nothing to do with whether the function works or not.

Of course it's an Apple bug, but Apple devices are brimming with bugs. iOS 13 is an unmitigated disaster. But with Steve Jobs no longer running the ship, the crew seems to have become complacent. Not to mention the ship is now heading toward ever greater profits instead of customer satisfaction as it used to. The only consolation, if it can be called that, is that Apple isn't as bad as their competition.

Hi Mark. Thanks for the news.

I hope iOS 14 will solve the issue... BUT:

1 are you sure does it work even after few days? Very often after updates the issues disappear, but after some attempts they appear again...

2 I’ve upgraded my devices to iOS 13.6 and WatchOS 6.2.8 and again, the issues are all still present (call drops, Siri unresponsive.. we all know).

if iOS 14 will solve it’s a good mews, but ios 14 will be officially out in September, ONE WHOLE YEAR after the issues appeared for the fist time. It’s not acceptable That apple has left us one year with our devices unusable.

Same here. Just today updated iPhone SE (2016) to iOS 13.6 and Apple Watch Nike Series 5 (no cellular) to watchOS 6.2.8.

I tried to accept and make a call (I disabled Wi-Fi on my iPhone and on my Watch). Everything worked perfectly. I tried again two hours later — again without complaints. I didn't want to write here right away, as time must pass. But since people are writing, I decided to report it too. I'll keep watching.

I checked again today several times over the course of a few hours. And so far, the problem has not returned.

Although, I should clarify that I don't use Apple Watch intensively and often turn it off (I put it in Power Reserve mode), since lately I rarely leave my apartment, and I don't wear it at home (I don't wear any of my watches at home, including two Casio watches). I will continue to observe.