Google appears to be quietly advancing a feature that Pixel users have been requesting for years: double-tap-to-lock. Originally spotted in an early Android 16 beta more than a year ago, the gesture was designed to let users turn off the display without pressing the power button. Now, newly updated strings in Android 17 QPR2 Beta 3 suggest Google has not only kept the feature alive but is actively expanding its functionality to include the home screen as well.

The double-tap-to-lock gesture is a staple on many custom Android skins and third-party launchers. It offers a convenient way to put the phone to sleep without reaching for a physical button, especially on larger devices where the power button may be awkwardly positioned. For Pixel phones, which have historically offered a clean, near-stock Android experience, the lack of this feature has been a long-standing omission. Third-party apps have filled the gap, but they often require accessibility permissions or workarounds that are not always reliable.

A feature in wait

Reports of Google developing a native double-tap-to-lock feature first surfaced in June 2025, when a code string appeared in Android 16 QPR1 Beta 1. That early version described the gesture as a way to double-tap an empty space on the lock screen to turn off the screen. At the time, it was unclear whether the feature would ever see a public release, as it remained dormant in subsequent builds. Some speculated that Google had shelved the idea, prioritizing other lock screen enhancements or facing technical hurdles with palm rejection and accidental taps.

Now, over a year later, the feature has resurfaced in Android 17 QPR2 Beta 3. This time, the evidence is more robust. The code not only contains the original string but also an updated version that includes the home screen. The new description reads: “Double tap an empty space on the home or lock screen to turn off the screen.” This subtle change suggests that Google is expanding the gesture’s scope, potentially making it more useful for users who often find themselves on their home screen and want to quickly shut off the display.

Dedicated settings and controls

In addition to the updated description, the latest beta includes strings that point to a dedicated settings page for the double-tap-to-sleep gesture. One string indicates that the system will offer a way to locate this settings page, while another references an option to enable or disable the feature when double-tapping an empty area on the lock or home screen. This implies that Google intends to give users granular control over the gesture, rather than forcing it on by default. It also suggests that the feature is further along in development than previously thought, as settings pages and toggles are typically added only when a feature is nearing completion.

The addition of a toggle is particularly important. Not all users will want double-tap-to-lock, especially those who frequently tap their screens or use cases that might inadvertently trigger the gesture. A dedicated setting would allow users to opt in or out based on their preferences. It also aligns with Android’s philosophy of user customization, offering accessibility while maintaining simplicity.

Why the delay?

Google’s slow rollout of this feature raises questions. The company has been working on it for over a year without a public release, which is unusual for such a seemingly simple gesture. Several factors could explain the delay. First, the feature must avoid conflicting with other gestures. Double-tapping an empty area of the screen could be misinterpreted as a tap on a widget or an icon, causing accidental actions. Google likely needs to ensure that the gesture is only activated in truly empty spaces, which requires careful touch detection and edge-case handling.

Second, the feature has implications for battery life and screen wake behavior. If a user double-taps the home screen to turn off the display, the phone must immediately enter a low-power state. This is straightforward in theory, but in practice, it requires coordination with the system UI and the launcher to ensure that the screen doesn’t flicker or delay. Third, Google may be tying this feature to broader Android 17 changes, such as a redesigned lock screen or new navigation gestures, which could push the release timeline.

Comparing with other phone makers

Double-tap-to-lock is not a new idea. Many Android OEMs have offered the gesture for years. Samsung, for example, allows users to double-tap the home screen or lock screen through its Good Lock module and One UI settings. Xiaomi, OnePlus, and Oppo all include similar options in their custom interfaces. Even stock Android’s “Screen lock” widget on older versions could be placed on the home screen to turn off the display with a single tap. However, a native, well-integrated double-tap gesture has been missing from Pixel devices, which is why this development is notable.

The implementation on Pixels could serve as a reference for future Android versions. If Google perfects this feature, it might eventually become part of the Android Open Source Project (AOSP), benefiting all Android devices. That would be a significant step for user convenience, especially as phones grow larger and physical buttons become less prominent in the design.

How it could work

Based on the code strings, the gesture would trigger when a user double-taps an empty area of the home or lock screen. On the lock screen, there are usually blank spaces between notifications and the clock, or along the edges. On the home screen, empty areas are common, especially with minimalist wallpaper setups or fewer app icons. The feature would require two consecutive taps with a short interval, likely similar to the double-tap-to-wake gesture that many phones already support. In fact, some Pixel devices have a double-tap-to-wake feature that allows users to wake the screen by tapping it twice. Adding the reverse — double-tap-to-sleep — would create a symmetrical and intuitive interaction.

One potential challenge is accidental activation. If a user habitually double-taps to wake the screen, they might inadvertently turn it off. To mitigate this, Google could restrict the double-tap-to-sleep gesture to the home screen only, or require that the screen is already unlocked and showing the launcher. The updated string includes both home and lock screen, so the company is clearly considering both scenarios. In practice, the lock screen might be less prone to accidental taps because it’s typically shown when the device is first picked up, whereas the home screen is a dynamic environment where users interact with apps.

What this means for Pixel users

For Pixel enthusiasts, the news is encouraging. It signals that Google is listening to user feedback and continuing to refine the Android experience. The feature, once released, would add a level of convenience that many users on other platforms already enjoy. It could also reduce wear and tear on the power button, which is a common failure point on older devices. Additionally, having a native implementation means better reliability and no need for third-party accessibility services, which can drain battery or cause privacy concerns.

The timeline remains uncertain. Since the strings appear in Android 17 QPR2 Beta 3, the feature could arrive in a future beta or as part of a feature drop. Google typically releases Pixel Feature Drops several times a year, and this could be a candidate for one of those updates. However, it’s also possible that the feature won’t make the cut and will be pushed to a later Android version. The fact that Google updated the strings, rather than removing them, suggests that the feature is alive and progressing.

A closer look at the code evidence

Teardowns of pre-release software often reveal features that never see the light of day. However, the presence of multiple new or updated strings is a strong indicator of active development. In this case, the strings include not only the summary text but also likely titles and descriptions for the settings page. Developers at Google are clearly investing time in polishing the user-facing text, which is usually one of the final steps before a feature is enabled by default. The reference to a “double_tap_screen_to_sleep” string family indicates that the feature has a formal name and is being integrated into the system settings architecture.

One string also hints at a preference or switch: something like “Double tap to sleep” with a summary that explains the gesture’s scope. This is typical of Android’s settings structure, where users can enable or disable specific gestures. For example, the existing “Double tap to check phone” and “Double tap to switch camera” gestures are located in the System settings under Gestures. It would make sense for double-tap-to-sleep to appear alongside these options, providing a consistent user experience.

Potential pitfalls and solutions

While the feature seems straightforward, there are potential pitfalls that Google may be addressing. One is the definition of an “empty” area. On the home screen, users often have widgets that span large portions of the display. The system must differentiate between a true empty space and a widget that is mostly blank. This can be determined by checking touch targets and activity boundaries. Similarly, on the lock screen, notifications could be mistaken for empty areas if they are not treated as interactive. The system will need to ensure that double-tapping a notification does not accidentally lock the phone, which would be frustrating.

Another concern is accessibility. Users with reduced motor skills might find double-tapping difficult, but they can simply disable the feature. Moreover, the gesture is not a replacement for the power button but an addition, so it doesn’t degrade accessibility for those who rely on the button.

Battery life is also a consideration. The feature itself should consume negligible power, as it only involves detecting touch events. However, if the phone is in a pocket and the screen is accidentally double-tapped, it could turn off the display unnecessarily, but that is no worse than what happens with existing gestures.

The road ahead

As Android 17 QPR2 Beta 3 continues to be tested, it is likely that more evidence of this feature will emerge. The official release of Android 17 QPR2 is expected later this year, and it might include the double-tap-to-lock gesture alongside other refinements. If not, a subsequent feature drop could deliver it. Either way, the fact that Google is updating strings suggests a commitment to seeing this through.

For now, Pixel users can only wait and hope that the feature will finally see the light of day. The idea of tapping twice to put a phone to sleep is appealingly simple, and it would be a welcome addition to the Pixel experience. With Google’s track record of iterative improvements, the final implementation could be both reliable and user-friendly, setting a new standard for other Android manufacturers to follow.

It’s also worth noting that the feature may be part of a broader effort to reduce reliance on physical buttons. As smartphones evolve toward seamless, buttonless designs, gestures like double-tap-to-lock will become increasingly important. Google has been experimenting with various touch and hold gestures in recent Android versions, and this could be one of many steps toward a more gesture-driven future. While a physical power button is unlikely to disappear soon, offering alternative ways to control the device is always a positive development.

Source: Android Authority News