On November 10, 2026, Google began rolling out Android 17 QPR2, the quarterly update to Android 17, to supported Pixel devices. Together with the "November Pixel Drop" announced the same day, it adds features such as letting users manually change screen brightness that an app has set, and temporary permission for app installation sources. However, the official release of QPR2 does not mean every announced feature is available right away. Nearby audio broadcasting remains in preview, and for app lock, only an API has been added; it has not yet been enabled on Pixel devices. When reading the published overview of Android 17 QPR2 features, it is necessary to distinguish between features that are already usable and those that depend on app support or future OS updates.
Not every feature is available in the stable release
Android 17 QPR2 includes officially provided features, preview-stage features, additions to developer APIs, and preparation for changes to be introduced in the next OS. The status and conditions of each feature as Google described them at the time of the November 2026 release are summarized below.
| Change | Status at QPR2 release | Conditions / future plans |
|---|---|---|
| Manual adjustment of app-set screen brightness | Available | Returns to normal brightness control when you leave the app |
| Voice broadcast | Preview | Requires an Auracast-compatible receiving device |
| App lock | Launcher API added | Not yet enabled in Pixel's QPR2 |
| MANAGE_CONTACTS | New permission added | For apps that need broad access to contacts |
| Write restrictions on WRITE_CONTACTS | Future change | Applies to apps targeting the next Android release planned for 2027 |
This breakdown clearly separates the addition of an API from users actually being able to use a feature. App lock, for example, has a developer API in place but is not enabled as a user-facing feature in Pixel's QPR2. The poster of the feature overview explained in a reply that it can be tried from QPR3 Beta 3, but no official launch date has been given.
The target devices also deserve attention. Android 17 QPR2 is delivered first to supported Pixel devices, and availability on other manufacturers' devices depends on each maker's update plans. The November Pixel Drop announced by Google is scheduled to roll out over several weeks starting November 10, but that is not a deadline for QPR2 to reach all devices.
Manual brightness adjustment arrives, along with audio broadcasting via Auracast
Apps that display boarding passes or QR codes sometimes set the screen to maximum brightness to make them easier to scan. Previously, while an app was controlling brightness, users could sometimes not change it manually even by using the Quick Settings slider. In Android 17 QPR2, users can adjust brightness even in this state. The change is temporary, however: brightness returns to normal control when you leave the app or go back to the home screen.
Appearance customization has also been expanded. In "Wallpaper & style," hue can be adjusted with a slider, and color intensity can be chosen from four levels: "Neutral," "Soft," "Bright," and "Bold." With compatible wallpaper collections, the wallpaper's appearance can also switch to match the system's light and dark modes. Not all wallpapers support automatic switching, however.
Status bar display settings can now be changed in more detail. For notification icons, you can choose from "Show all," "Show priority only," and "Hide." Even if you choose to show all, only as many icons as fit in the available space in the status bar will actually appear. The battery percentage and the mute and vibrate icons can also be shown or hidden individually.
On the audio side, "Voice broadcast," which uses the Bluetooth audio-sharing technology Auracast, has been added as a preview feature. Audio picked up by the phone's built-in microphone or a wired headset microphone can be broadcast to nearby Auracast-compatible earbuds, hearing devices, compatible Android devices, and more. Broadcasting can be started from Quick Settings, and participants can be restricted by setting a password. The receiving side must also support Auracast, so not every ordinary Bluetooth earbud can be used.
Public Auracast broadcasts can be joined using a QR code or NFC, and a new "Audio streams" Quick Settings tile has been added. Separately, Bluetooth volume control has been improved. According to Google, it addresses a bug in which the volume suddenly jumped to maximum when Gemini was invoked or when the audio type changed. On devices that support Absolute Volume, the volume is raised smoothly when audio switches, and unnecessary external volume commands issued midway are discarded. This fix targets specific switching behavior and does not eliminate every volume discrepancy that occurs with Bluetooth devices.
"Just this once" app installation permission and stronger in-call safeguards
Android 17 QPR2 changes permission management when installing APKs from browsers or file manager apps. Previously, if the source app lacked permission, users had to go to the settings screen. In QPR2, they can choose "Just this once," "Always allow," or "Deny" directly from a system dialog. If you choose "Just this once," the permission automatically expires when the installation session ends, so you can install an app without granting ongoing permission.
What is granted here is the permission for apps such as browsers and file managers that provide the APK to install apps. It is not a mechanism that certifies the safety of the APK itself. With this change, users no longer need to go back to settings after installation to revoke the permission, and can choose whether to grant the installation source ongoing permission.
On the privacy side, a new logging feature has been added to "Private Compute Core," which protects on-device machine learning processing. It lets users record and review data that they have permitted to be sent outside the Private Compute Core. Logging can be turned on from the privacy dashboard: "Limited" stores summaries for up to 72 hours, while "Detailed" stores detailed raw data for up to 12 hours. Because detailed logs may contain sensitive information, users choose between summaries kept for longer and more detailed information kept for a shorter period. It is not, however, a feature for auditing all AI communications in one place.
Protections against phone scams have also been strengthened. While you are on a call with someone not in your contacts, the action of newly enabling developer options is blocked. This is intended to prevent a scammer from instructing the user during a call to change settings that reduce the device's security. If developer options were already enabled before the call, however, this does not automatically disable them.
Restrictions have also been placed on USSD codes, which send instructions to the telephone network. According to the Android 17 QPR2 release notes, ordinary apps holding only the CALL_PHONE permission can no longer run call-forwarding USSD codes in the background. Also, when a user enters a call-forwarding code directly in the system dialer, the OS shows a confirmation screen before executing it. USSD codes other than call forwarding, such as balance inquiries, are outside the scope of this restriction. The change is meant to prevent unintended call-forwarding settings and is not a mechanism to prevent phone fraud in general.
New contacts permission added; write restrictions begin in 2027
Android 17 QPR2 adds a new permission for managing contacts, "MANAGE_CONTACTS." However, writing under the existing "WRITE_CONTACTS" permission is not restricted immediately. According to the migration plan published by Google, write restrictions on WRITE_CONTACTS will apply starting with apps that target the next Android release planned for 2027. Apps targeting older OS versions keep the existing behavior, so simply updating the OS will not make every contact-saving feature stop working.
The new MANAGE_CONTACTS permission is intended for apps whose main function is managing contacts and that need broad access. Examples include apps that continuously sync contacts with corporate or cloud service accounts, and apps that back up and restore large numbers of contacts in bulk. On the other hand, for something as simple as saving a single contact from a chat app, Google recommends using an intent that opens the system's standard contact editing screen. The design distinguishes one-off saves and edits that a user initiates from processing in which an app continuously manages many contacts.
Having a custom-designed contact editing screen alone does not satisfy the conditions for using the MANAGE_CONTACTS permission. Also, standardized editing screens that can be shared across apps will not be in place until the next OS, so not everything is complete at the time of QPR2. Declarations in Google Play Console and compliance with related policies are likewise planned to target the next OS in 2027 and later. Rather than simply swapping permission names, developers need to review which operations among saving, editing, and syncing contacts truly require broad access.
Background processing changes regardless of an app's target OS
One point developers need to watch is a change in the behavior of "self-addressed broadcasts" sent and received within an app. These are cases where the broadcast's sender and all of its receivers are in the same process. Even within the same app, it does not apply if the receivers include one running in a different process. Because this change applies regardless of the OS version an app targets, apps developed for older versions of Android also need to be tested.
In Android 17 QPR2, sending a self-addressed broadcast can no longer keep a background process from going dormant. If the process is dormant, undelivered broadcasts are held until the process resumes. However, because undelivered broadcasts are kept in the process's memory, they are lost if the process is terminated before delivery and are not redelivered. As a result, designs that use self-addressed broadcasts as a substitute for timers or to keep an app running in the background are affected. Google recommends using WorkManager and similar tools for background processing, and callbacks and the like for communication within the same process.
Elsewhere, on foldable devices, a control handle has been added at the top of the app screen, allowing users to switch between full-screen and split-screen display and to move bubbles. The Linux Terminal has also changed: while the virtual machine is running, its home directory can be accessed directly from Android's file screen. The need to manually move files handled on the Android side to /mnt/shared, as before, goes away. This feature is available only while the virtual machine is running.
While improving everyday operation, Android 17 QPR2 also brings changes to permission management related to security and privacy, and to apps' background behavior. Some of the added features, however, require Auracast-compatible devices or are not yet enabled on Pixel devices, so what is available varies by usage environment. For developers, preparing for the contacts permission change planned for 2027 is important, but so is handling the self-addressed broadcast behavior change that applies as soon as devices update to QPR2. As user devices and peripherals gain support and developers update their apps, the features added this time should become usable in a wider range of environments.