Before this update, activating Touch Lock on Pixel Watches running Wear OS 4 or the initial Wear OS 5 would disable the touchscreen. This prevented accidental inputs from stray touches or water droplets, which was useful during activities like exercise or in wet environments.
Crucially, while the touch capability was off, the rotating crown remained active. Users could still scroll down to view Quick Settings (checking battery, connections) or scroll up to browse incoming notifications, all without needing to touch the display itself.

Turning Touch Lock on and off on a Pixel Watch. | Image credit — 9to5Google
The new behavior in Wear OS 5.1
Following the update to Wear OS 5.1, enabling Touch Lock now disables both the touchscreen and the rotating crown. With Touch Lock active, the screen ignores taps, and the crown no longer responds to rotation. The only interaction possible is a two-second long-press of the crown, which deactivates the lock entirely.This modification has drawn criticism from some users. One pointed out the convenience of the older system, especially for checking notifications with the crown while showering, a scenario where using the touchscreen is impractical.This specific change arrives alongside the rollout of Wear OS 5 and its subsequent point releases like 5.1. Wear OS 5 itself focused on larger improvements, including battery life optimizations and new developer tools. Small usability tweaks in updates like 5.1 are common but, as seen here, can sometimes have a noticeable impact on the daily user experience, especially compared to competitors like Apple Watch or Samsung Galaxy Watch which have their own screen lock nuances.
Currently, it’s not certain if Google intended to disable crown functionality with Touch Lock or if it’s an unintentional bug in Wear OS 5.1. The company hasn’t updated the official support documentation for Touch Lock to reflect this change. Users affected by this are hoping for clarification or a fix in a future software update, possibly in the next monthly patch cycle if it’s deemed a bug.
Disabling all physical input methods when Touch Lock is on seems somewhat counterintuitive for a device designed for quick glances. Limiting interaction options, even when trying to prevent accidental input, can reduce the watch’s convenience in certain situations. We await Google’s clarification on whether this is the new standard behavior.