The "Flip to Shhh" feature, designed to silence notifications when a Pixel phone is placed face down, is currently malfunctioning for some users. Reports indicate that the feature is either unavailable or generates an error message when users attempt to enable it.
The issue spans multiple Pixel models, from the Pixel 7 to the Pixel 10. Users have described various scenarios leading to the problem, including changes to Advanced Protection settings, launcher preferences, or even after a factory reset. Attempts to re-enable the feature consistently result in a "can't turn on flip to shhh" error.
The problem is attributed to a server-side issue involving conflicting versions of the Digital Wellbeing application. While some users temporarily resolved the issue by forcing an update to the Digital Wellbeing app via the Google Play Store, the fix has not been permanent for everyone, with the problem reappearing for some.
Despite reports surfacing weeks ago, a permanent solution has not been provided. The exact reason why the Digital Wellbeing service is causing this disruption with updates remains unclear. This bug occurs as Google introduces the Pixel 11 series with a similar feature called HiLight, though the current issue is not believed to be related to new hardware.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
Google Pixel users from Pixel 7 to Pixel 10 models are reporting that the "Flip to Shhh" feature, which silences notifications when the phone is placed face down, is no longer working or available. The issue appears to be related to conflicting Digital Wellbeing versions, with no definitive fix currently available.