Beta 7.1
| Release date | October 16, 2026 |
| Builds | CP41.260831.019 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-10-05 |
| Google Play services | 26.28.33 |
Beta 7
| Release date | October 9, 2026 |
| Builds | CP41.260831.016 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-10-05 |
| Google Play services | 26.28.33 |
Beta 6.1
| Release date | September 29, 2026 |
| Builds | CP41.260831.007.A3 CP41.260831.011 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-08-05 |
| Google Play services | 26.28.33 |
Beta 6
| Release date | September 24, 2026 |
| Builds | CP41.260831.007 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-08-05 |
| Google Play services | 26.28.33 |
Beta 5
| Release date | September 15, 2026 |
| Builds | CP41.260828.004.A8 CP41.260828.005.A6 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-08-05 |
| Google Play services | 26.28.33 |
Beta 4
| Release date | August 28, 2026 |
| Builds | CP41.260814.003.A2 CP41.260814.003.B1 CP41.260814.003.C2 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-08-05 |
| Google Play services | 26.28.33 |
Beta 3
| Release date | August 14, 2026 |
| Builds | CP41.260731.005.A2 CP41.260731.005.B1 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-08-05 |
| Google Play services | 26.26.34 |
Beta 2
| Release date | August 3, 2026 |
| Builds | CP41.260717.006 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-07-05 |
| Google Play services | 26.24.35 |
Beta 1
| Release date | July 20, 2026 |
| Builds | CP41.260701.005 |
| Emulator support | x86 (64-bit), ARM (v8-A) |
| Security patch level | 2026-07-05 |
| Google Play services | 26.23.34 |
Android 17 QPR 2 Beta 7.1 (October 2026)
Building on the initial release of Android 17, we continue to update the platform with fixes and improvements that are then rolled out to supported devices. These releases happen on a quarterly cadence through Quarterly Platform Releases (QPRs), which are delivered both to AOSP and to Google Pixel devices as part of Feature Drops.
Although these updates don't include app-impacting API changes, we provide images of the latest QPR beta builds so you can test your app with these builds as needed (for example, if there are upcoming features that might impact the user experience of your app).
Android 17 QPR2 includes a minor SDK release. This incremental update has no planned behavior changes, minimizing the need for compatibility testing. You can the current SDK changes in the API diff report.
Hardening against call forwarding fraud
Android 17 QPR2 introduces new security restrictions on programmatic call
forwarding to protect users from fraud. The system now parses and selectively
restricts call-forwarding USSD codes (such as *21#) executed using the
TelephonyManager.sendUssdRequest() API.
- API Restriction: The
sendUssdRequest()API is no longer accessible for call-forwarding codes using only theCALL_PHONEpermission. Standard apps attempting to execute these codes in the background will be blocked and receive aUSSD_ERROR_NOT_ALLOWEDcallback. - System Confirmation: To combat social engineering scams, users manually dialing call-forwarding codes in the system dialer will now see a new OS-level confirmation dialog before the command is executed.
- Non-Call Forwarding USSD: Non-call forwarding enabling USSD requests (such as mobile money transfers and account checks) are unaffected by this change.
- Mitigation: If your app is affected, verify that it handles the
USSD_ERROR_NOT_ALLOWEDfailure callback gracefully. For apps requiring call-forwarding setup that don't qualify for an exempted role, migrate your flow to use theACTION_DIALintent to pre-fill the dialer, allowing the user to manually confirm the action.
Optimized delivery of self-broadcasts
在搭载 Android 17 QPR2 或更高版本的设备上，Android 会更高效地传递自我广播，以改善系统运行状况。自我广播是一种广播（例如，使用 sendBroadcast() 发送的广播），其所有接收器（无论是在上下文中注册还是在清单中声明）都在发送广播的同一进程中运行。如果有任何接收器在其他进程中运行，则该广播不是自广播。系统会将自我广播交回给发送进程，由发送进程在主线程上将其递送给自己的接收器。这可以防止应用通过重复向自身发送广播来使自身在后台运行。此变更适用于所有应用，无论其 targetSdkVersion 为何。
此项变更会通过以下方式影响您的应用：
发送自我广播不会提高进程的重要性，也不会阻止缓存的进程被冻结。
如果您的进程已缓存并冻结，则其发送的自广播会等待进程解冻，例如，当用户返回应用或应用的另一个组件启动时。
尚未传送的自广播会保留在进程的内存中。如果系统在消息传递之前终止进程，消息就会丢失，并且不会重新传递。
如果广播的接收器位于其他进程（包括同一应用的其他进程），或者广播是代表其他应用发送的（例如通过 PendingIntent），或者广播是发送给其他用户个人资料，则不受影响。
确保您的应用不依赖于自广播在后台执行工作。请勿将自广播用作计时器或保持连接机制。如需调度后台工作，请使用 WorkManager；对于必须在特定时间执行的工作，请使用 AlarmManager。 对于进程内通信，请使用直接调用（例如回调或 Kotlin flow），而不是广播。
Known issue in Beta 7.1
Pixel 11 Pro Fold users may have to re-enroll Face Unlock for it to function properly.
Top Issues fixed in Beta 7.1 (October 2026)
- Severe UI stuttering and multi-second freezes (Issue #571186734)
Top Issues fixed in Beta 7 (October 2026)
- Excessive battery drain during idle states when Flip to Shh prevents the device from entering deep sleep. (Issue #560036427, Issue #569079944)
- HTTPS downloads fail immediately when initiated through the system DownloadManager. (Issue #562833711)
Top Issues fixed in Beta 6 (September 2026)
- A visual regression causing letterboxed content to leak through the status bar during activity transitions. (Issue #493438057)
- The screensaver displays a blank screen while charging. (Issue #516262713, Issue #526560397)
- Unexpected device reboots on Pixel 9 Pro Fold when initializing the camera viewfinder in third-party applications. (Issue #555960820, Issue #558564487, Issue #554763027, Issue #559421409)
- Locked applications could not be dismissed using swipe gestures in Recents. (Issue #555579953)
- A system kernel crash causing devices to unexpectedly reboot when third-party applications requested simultaneous camera and microphone access during biometric identity verification. (Issue #557712189)
- An issue that caused device crashes, reboots, or hangs when scrolling. (Issue #559054323)
Top Issues fixed in Beta 5 (September 2026)
- Changing a Bluetooth device type in settings failed to update its icon visually. (Issue #516071134)
- A system stability issue that caused unexpected device reboots during continuous UI scrolling in media-heavy applications. (Issue #544291113)
- Pressing hardware volume buttons while casting media prevented the system volume slider UI from displaying. (Issue #548145018)
- Fixed a text-rendering issue that caused unexpected background highlights to appear when typing in search fields, and resolved a navigation routing issue that prevented Private Space from unlocking correctly. (Issue #548285596)
- Enhanced HDR mode remained enabled despite being turned off in user settings. (Issue #547457910)
- Launching Google Wallet via the power button shortcut caused the touchscreen to become unresponsive. (Issue #549758084)
- Camera crashes during panorama processing. (Issue #551069625)
- Bluetooth audio experiences noise and distortion after completing or answering a call. (Issue #541684282)
Top Issues fixed in Beta 4 (August 2026)
- Enabling the "render apps below the cutout area" developer setting caused a transparent status bar on the launcher after exiting fullscreen video playback. (Issue #295747911)
- A thermal management issue that caused devices to overheat and unexpectedly reboot during use. (Issue #437116407)
- An issue preventing screen mirroring to external USB-C XR glasses. (Issue #439269938)
- Gesture navigation became unresponsive when rendering apps below the display cutout. (Issue #441378954)
- The 80% battery limit optimization caused excessive charge times during the final 2% threshold. (Issue #477009501, Issue #476803337)
- A launcher UI issue where searching for apps in the app drawer failed to process text input. (Issue #505157934, Issue #527921034, Issue #530531588, Issue #537704656)
- Invoking the power menu via hardware buttons caused a missing background blur effect behind the navigation bar. (Issue #537202501)
- An issue where phone call audio defaulted to the phone speaker instead of connected Bluetooth devices. (Issue #537908014, Issue #541501134, Issue #541772860, Issue #545047074)
- A Recents app switcher rendering bug where the first task card could intermittently freeze and visually clip behind other apps during horizontal scrolling. (Issue #530484511, Issue #505564040, Issue #545574713, Issue #551022006)
- An audio service resource lock triggered during screen recording that prevented microphone usage across apps and input methods like Gboard and Gemini until a device restart. (Issue #538229807)
- A System UI visual inconsistency where turning off the screen from the home screen triggered a plain fade instead of the power-button screen-off animation. (Issue #541261786)
- A low-contrast rendering issue in dark mode where the connected Wi-Fi settings cog icon was barely visible. (Issue #536320341)
- Enabling 3D mode on connected smart glasses resulted in a blank screen. (Issue #536628506)
- A User Interface issue that prevented the notification bar from being pulled all the way down. (Issue #539244095, Issue #547801203, Issue #547017781, Issue #546896889, Issue #547163658, Issue #547281675)
- An issue where WebGL applications could freeze or crash the browser process when combining shadow maps with vertex color attributes by resolving an invalid memory read in the PowerVR GPU driver's texture state processing. (Issue #541322087)
- Low-light Face Unlock failures bypassed Fingerprint Unlock and forced PIN entry. (Issue #547597971, Issue #545329611, Issue #541723970)
Top Issues fixed in Beta 3 (August 2026)
- Opening the notification shade and Quick Settings menu caused visual corruption and an unexpected device restart. (Issue #535249652, Issue #543124160)
- The Device Health and Support tool erroneously displayed false battery capacity degradation warnings to users. (Issue #535421490, Issue #538943170, Issue #535504630)
Top Issues fixed in Beta 1 (July 2026)
- Bluetooth re-pairing fails silently following a remote bond loss. (Issue #412524057)
- Media player controls briefly flashed on the lock screen upon waking the device despite the app's notifications being disabled. (Issue #484607701)
- A system crash causing Pixel devices to unexpectedly reboot when invoking Gemini. (Issue #505750489)
- Initiating a drag-and-drop gesture with multiple fingers caused the source application to stop receiving subsequent touch events. (Issue #516836306)
- Notifications randomly became invisible in the notification shade until a system restart. (Issue #526139207, Issue #522657034)
- ML-DSA key generation fails with an exception when using the "NONE" string digest instead of the class constant. (Issue #525612735)
- An issue in AccessibilityNodeInfo.toString() where window bounds were incorrectly logged using screen bounds, which caused misleading accessibility debugging data. (Issue #520428442)
- Window-level UI blur effects failed to render and the "Allow window-level blurs" developer toggle reset after rebooting. (Issue #527376569)