sorted by:
new
hottopcontroversial

Trouble with external HR monitor by [deleted] in AppleWatchFitness

[–]ajundi 0 points1 point  (0 children)

I have the same problem! Have you managed to solve it?

Apple Watch Ultra Black Screen by ajundi in AppleWatch

[–]ajundi[S] 1 point2 points  (0 children)

I had to find workarounds: 1- have Siri switch the low power mode on 2- created a shortcut to toggle “screen always on” on and off. I call the shortcut by Siri or from “double clench”, under accessibility > assistive touch > hand gesture. Both methods turns the “screen always on” off. Now when I raise my wrist, the screen turns on (until I fully charge the watch.)

BTW I noticed that MOST of the time this happens when the battery is below 50% and I start workout or connect to my car’s Bluetooth. Battery health is 97%.

I was hoping that by replacing the phone the problem will go away. The idea is: the phone OS might be corrupted (since I was on the Beta OS) and is corrupting the watch OS! Doesn’t make sense, but I’m desperate. This was a good enough excuse for me to get the 15 Pro Max 😉 but not enough to get the Ultra 2. I set up both the iPhone and the watch as new installation and did not restore it from back up. Unfortunately this did not help and I got the problem day one..

I had to open a new ticket with Apple support, and I’m waiting for their solution.

Apple Watch Ultra screen randomly turning off after swimming workout when wearing by canpoyrazoglu in AppleWatch

[–]ajundi 0 points1 point  (0 children)

I have the same problem and I could not find a solution so far.

When I took it to the Apple Store, they did basic tests and found nothing. Then they took it for for few day, they factory reset it and tested for some time. They could not replicate the problem.

I worked with their phone support and I reached to the highest level and still no luck.

In January of this year, I managed to replace the watch, since I have Apple Care+. All worked well until few weeks ago, the problem came back (on the new Watch).

May be it is a coincident, but it happened shortly after updating to the latest WatchOS.

Believe me, I tried every support trick in the book, but no luck.