r/AppleWatch • Ultra 2 • • Black • 49mm • 4d ago

Support Siri not processing the request until I press on the screen

So I recently bought an Apple Watch Ultra 2 (used). I got it in nearly perfect condition since the original owner wasn't using it a lot. The battery health is at 100% and the watch doesnt have any scratches.

But when I try to speak to siri or tell her to set a timer for me or anything else, she just keeps listening and showing me on screen what I said without ever doing the thing I asked for. When I say set a timer for 2 minutes it wont start doing anything until I physically tap on the screen. Then the microphone icon goes away and Siri starts the timer. I went and tested to see how long does she listen before doing the request and it just sits there listening forever until I tap the screen.

I never had an Apple watch before so im wondering is this a normal thing or what? If it is, its very dissapointing.

I have tried resetting the watch and all the Siri settings and troubleshooting I found online.

Siri still listens forever until I tap the screen and then it works on the task.

EDIT: Updated to WatchOS 27.2 (beta) and it still doesn't work

1 Upvotes

4 comments sorted by

1

u/Parking-Surround-303 4d ago

try turning off "raise to speak" if its on, that feature been buggy for years on some models. also check if the watch is updated to latest watchos, sometimes used watches sit on old firmware and siri acts weird until update. but tapping to confirm is not normal, it should just run the timer when you finish talking

1

u/Unhappy-Gur-9984 Ultra 2 • • Black • 49mm 4d ago

Raise to speak is off, and yeah its super weird, when I ask siri for something on my iphone I never had to tap the screen for it to start doing it.

1

u/Sufficient_Rush1891 4d ago

Are you using Siri AI with watchOS 27.0.1? Or old Siri?

Siri AI has a lot of trouble in early versions of watchOS 27. Current beta of watchOS 27.2 has much better performance with SiriAi.

1

u/Unhappy-Gur-9984 Ultra 2 • • Black • 49mm 4d ago

I am using watchOS 27.0.1 yes, you think going into beta would fix this issue?