Google Still Building Android 17 App Lock as Beta 6 Strings Resurface

Android 17 App Lock is not dead. Code strings inside Android 17 QPR1 Beta 6, pushed on July 1, 2026 as build CP31.260618.005, show Google is rebuilding the feature for a Settings-based release with multi-app support and a possible biometric-only mode. Android Authority reporter Rita El Khoury surfaced those strings inside the QPR1 Beta 6 APK, the same day Google declared QPR1 had reached Platform Stability.

Pixel owners had been waiting for a native App Lock since Android Canary 2603 first surfaced an early version, only for later Canary builds to drop support without explanation. Beta 6 brings the strings back, with a Settings-driven setup, multi-app lock management, and a description that hints at disabling PIN entry. The teardown rates the chances of App Lock landing in the QPR1 stable release as low, which puts the next quarterly release forward as the realistic window.

What Beta 6 Actually Reveals

Google released Android 17 QPR1 Beta 6 on July 1, 2026 as build CP31.260618.005, and the same release pushed Android 17 QPR1 to Platform Stability. The QPR1 Beta 6 release notes for Pixel detail what landed in the changelog and confirm the API surface is locked. The bigger news for Pixel owners sits inside the same APK: new strings tied to the App Lock feature that was missing from the June stable build.

The strings sit inside a Settings promo dialog, with one title reading “You can now add app lock to multiple apps at once in Settings” and a description reading “Quickly add and manage app lock anytime. For extra security, you can also limit access to your apps by requiring only biometrics.” That language points to two distinct changes from the original Canary implementation: a move from the Pixel Launcher into Settings, and a hint at a future biometrics-only mode. The wording is identical to what Google’s translation team would push into a final release dialog, which is what makes the find worth treating as a signal rather than noise.

APK teardowns are educated guesses, not announcements, and the publication is explicit about that. Its standard teardown disclaimer notes that “such predicted features may not make it to a public release.” Even so, finding active strings inside a beta that has already hit Platform Stability is a stronger signal than seeing them in a Canary channel, and the new App Lock strings found in QPR1 Beta 6 walk through each string in detail.

How the App Lock Design Is Changing

The shift from Android Canary 2603 to QPR1 Beta 6 changes App Lock in three concrete ways. In Canary 2603, App Lock could only be set up through the Pixel Launcher, and only one app could be locked at a time. The QPR1 Beta 6 strings describe adding App Lock to multiple apps at once, directly inside Settings. That removes a clunky one-at-a-time flow that, while technically a one-time setup, still punished anyone who wanted to lock a handful of apps.

The second change is biometric. In Canary 2603, locked apps opened with biometrics or a PIN. The QPR1 Beta 6 description string tells users they can “require only biometrics,” which the teardown reads as a possible future option to disable PIN-based unlocking entirely. Skipping PIN entry at app lock removes a fallback path that can be shoulder-surfed. It also gives users who prefer fingerprint or face unlock a cleaner path into sensitive apps. The dialog’s “for extra security” framing matches the biometric-first push Google has shipped elsewhere in Android 17.

App Lock has bounced in and out of Google’s development channels for months. The short version of where things stand:

1. Android Canary 2603 surfaced a working App Lock that lived inside the Pixel Launcher.
2. Later Android Canary builds dropped App Lock support without explanation.
3. Android 17 stable shipped in June 2026 without any native App Lock feature.
4. Android 17 QPR1 Beta 6, pushed on July 1, 2026, brought new App Lock strings and reached Platform Stability.

Why QPR1 Stable Likely Misses It

Android Authority puts the odds bluntly: App Lock is not in QPR1 Beta 6, and there is a “low chance” the feature lands in the QPR1 stable release. Beta 6 hit Platform Stability on the same day, a milestone that locks the API surface so app developers can ship code without fearing further churn. Platform Stability does not mean every hidden feature inside the beta is finished. The absence of an actual App Lock toggle in Settings tells its own story about how far the work still has to go.

Google has used this exact pattern before with other Android 17 features. Foldable Gaming Mode arrived as an enabled Android 17 feature that Google said would be “available in the coming months” rather than at the June stable release. App Lock looks headed down a similar path, with the strings shipped first and the toggle arriving in a later quarterly release. QPR1 Beta 7 will be the next checkpoint for anyone watching the Settings app for an App Lock switch.

Where App Lock Sits in Android 17’s Privacy Story

App Lock fits inside a wider Android 17 privacy push that is already live on Pixel 6 and later devices. Google shipped the headline features in June alongside the stable release, and they lean hard on biometrics and tighter permission boundaries.

Find Hub’s Mark as Lost now accepts biometric authentication, not just a passcode, so a thief who learned the PIN cannot turn off device tracking. One-time precise location lets an app see a user’s exact position for a single session, with no repeat prompts. The Contacts Picker tool grants temporary, field-level access to selected contacts, replacing broad READ_CONTACTS grants. None of these features ship with App Lock, and that is exactly the gap Google appears to be filling.

• Android 17 stable release window: June 2026, for Pixel 6 and later devices
• QPR1 Beta 6 build: CP31.260618.005, released July 1, 2026
• Eligible devices for QPR1 Beta 6: 21 Pixel models from Pixel 6 through Pixel 10 series, including the Pixel Tablet and the Pixel 10 Pro Fold
• Lock method hint in QPR1 Beta 6 strings: biometrics only, with PIN unlock as the fallback
• Confirmed Android 17 stable features: App Bubbles, Screen Reactions, Contacts Picker, one-time precise location, Mark as Lost biometric

The description string frames App Lock as something to add for “extra security,” which puts it in the same biometric-driven family of features that shipped with Android 17 stable in June. That placement matches the Android 17 stable release and its feature lineup framing of Find Hub’s Mark as Lost and the one-time precise location prompt. App Lock extends the same biometric-first logic from system-level tools down to individual apps.

Foldable Gaming Mode, also enabled in Android 17 stable code, will be “available in the coming months,” per Google’s own language in the Android 17 release notes. App Lock is following the same behind-the-scenes build pattern, with strings shipped first and the toggle following later. The two features together signal that Android 17’s launch window included work Google was not yet ready to surface.

The Roadmap Beyond QPR1

The teardown methodology carries an explicit caveat, and it is worth stating plainly. APK teardowns surface work-in-progress code, and Google can change or remove any of it before a public release. The new strings describe a Settings-based App Lock with multi-app support and a biometrics-only mode, but they do not commit Google to a release date or a feature flag flip.

The next checkpoint for anyone watching for App Lock is QPR1 Beta 7. If the toggle does not appear there, QPR1 Beta 6 release notes and Platform Stability details indicate the next quarterly release becomes the next window. Until then, Pixel users who want per-app locks today are still pointed at third-party apps from the Play Store, the same workaround earlier App Lock notification privacy teardowns have suggested for Pixel owners waiting on Google’s native solution.

Google’s own strings say as much. The dialog title frames App Lock as something users can now “add,” language that only makes sense if the toggle is not yet live. That phrasing matches what the teardown already reported: App Lock is still in development, with no public toggle yet and no confirmed release date.

Frequently Asked Questions

When will App Lock arrive on Pixel phones?

Google has not announced a release date. Based on the Android 17 QPR1 Beta 6 teardown, App Lock is not in QPR1 Beta 6 and the publication rates the chance of it reaching QPR1 stable as low. The next quarterly release after QPR1 stable is the more realistic window.

Why wasn’t App Lock in Android 17 stable?

Android 17 stable shipped to Pixel 6 and later devices in June 2026 without a native App Lock feature, even though Android Canary 2603 had surfaced an early version. Later Android Canary builds removed App Lock support, and the work resurfaced as new code strings inside QPR1 Beta 6 on July 1, 2026.

How will the new App Lock differ from the Canary 2603 version?

The Canary 2603 build required users to add App Lock through the Pixel Launcher and supported only one app at a time. The QPR1 Beta 6 strings describe adding App Lock to multiple apps at once inside the Settings app, with a description that hints at a future option to require biometrics only and skip PIN entry.

Which Pixel devices will get App Lock?

The QPR1 Beta 6 update is available for the Pixel 6 series through the Pixel 10 series, including the Pixel Tablet. App Lock is not yet switchable on any of them, and the strings do not narrow the eligible list. Android 17 stable itself is rolling out to Pixel 6 and later devices.

Will App Lock support PIN unlock, or biometrics only?

Both, and possibly biometrics only as well. The QPR1 Beta 6 description string says “For extra security, you can also limit access to your apps by requiring only biometrics.” The teardown reads that as a possible future toggle to disable PIN-based unlocking entirely, on top of the existing biometrics or PIN option from Canary 2603.