Since I received my Apple Ultra 2 watch the taptic time is not working as expected. My expectation is that when I double tap the watch face, I will get the appropriate taptic vibrations to let me know the current time. Well this sort of works. The problem is that the time is spoken before the taptic vibrations start. This defeats the purpose for me. I am in bed and do not want to wake my spouse. I double tap the watch and there is the time spoken, then the vibration starts. Why bother? I have had Apple watches since version 3 and have no problems with the taptic time. I checked in settings and the taptic time is turned on. Any help?
Comments
Rist up
Did you check to see if rist up is off, If I have my rist up VO will tell the time. If I am in bedd and my rist is on my leg it does not. If I put my rist near my heart VO will tell the time.
double tap bug
This happens to me ever since I upgraded my series 5 to WatchOS 10. I can't get the vibrations to happen consistently. I'm thinking something is up with the double tap having to be faster to register, so if you do it slower the watch thinks you're just tapping the screen and the time or whatever is on your watch face speaks. Don't know if that made sense lol.
There has been a similar bug on the phones with iOS 17 where double taps don't register in the same way. On the watch though, there's no setting to change the double tap time out, which some people here have said mitigates the problem. I haven't tried this on my iPhone though.
Triple tap?
For me, haptic time starts with a triple tap to the screen. Double tap just seems to speak the time.
not consistent at all.
I have wrist up turned off, always have had, and tripple-tap isn't doing haptic time anymore most of the time. Maybe next version.
double tap not working for taptic time on apple watch
In the past up until my latest purchase of the ultra 2 watch, the double tap worked as expected. I did turn off raise to speak and that did not make any difference. Tripple tap makes my watch do some things but not taptic time for sure. I thought it was me but it seems like it is a potential bug in the software. Anybody have anything else?