{"id":432132,"date":"2025-09-17T21:49:13","date_gmt":"2025-09-17T21:49:13","guid":{"rendered":"https:\/\/www.europesays.com\/uk\/432132\/"},"modified":"2025-09-17T21:49:13","modified_gmt":"2025-09-17T21:49:13","slug":"heres-every-new-feature-for-pixels-in-android-16-qpr2-beta-2","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/uk\/432132\/","title":{"rendered":"Here&#8217;s every new feature for Pixels in Android 16 QPR2 Beta 2"},"content":{"rendered":"<p><img class=\"e_3g\" decoding=\"async\" loading=\"eager\"  title=\"Photo of Android 16 QPR2 Beta 2 logo on a Pixel phone\"  alt=\"Photo of Android 16 QPR2 Beta 2 logo on a Pixel phone\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/Photo-of-Android-16-QPR2-Beta-2-logo-on-a-Pixel-phone.jpg\"\/><\/p>\n<p>Mishaal Rahman \/ Android Authority<\/p>\n<p>In less than three months, Google will roll out the second quarterly release of <a href=\"https:\/\/www.androidauthority.com\/android-16-features-3484159\/\" target=\"_blank\" rel=\"noopener\">Android 16<\/a> to Pixel devices, bringing major new features like an expanded dark theme, auto-themed app icons, an HDR\/SDR brightness slider, and more. While Google previewed many of these features in last month\u2019s QPR2 Beta 1 release, the beta program is far from over.<\/p>\n<p>Earlier today, Google rolled out <a href=\"https:\/\/www.androidauthority.com\/android-16-qpr2-beta-2-release-3598233\/\" target=\"_blank\" rel=\"noopener\">Android 16 QPR2 Beta 2<\/a> to supported Pixel devices. It\u2019s the second of three releases in the QPR2 beta program, and while it doesn\u2019t bring as many new features as <a href=\"https:\/\/www.androidauthority.com\/android-16-qpr2-beta-1-features-3586944\/\" target=\"_blank\" rel=\"noopener\">Android 16 QPR2 Beta 1<\/a>, it includes a few exciting changes. We installed Android 16 QPR2 Beta 2 on our Pixel devices to find out what\u2019s new, so keep reading if you\u2019re wondering whether it\u2019s worth installing the beta on your own Pixel or waiting for the stable release in December!<\/p>\n<p>Icon shape customization<\/p>\n<p>In Android 16 QPR2 Beta 2, you can now change the shape of app icons on the home screen. When you open the Wallpaper &amp; Style app and tap the Icons option in the Home Screen tab, you\u2019ll find five shape options: the default circle shape, a square, four-sided cookie, seven-sided cookie, and arch.<\/p>\n<p><img class=\"e_3g\" decoding=\"async\" loading=\"lazy\"  title=\"Icon shapes for Pixels in August 2025 Android Canary release\"  alt=\"Icon shapes for Pixels in August 2025 Android Canary release\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/Icon-shapes-for-Pixels-in-August-2025-Android-Canary-release.jpg\"\/><\/p>\n<p>Mishaal Rahman \/ Android Authority<\/p>\n<p>Google first introduced this icon shape customization feature in the <a href=\"https:\/\/www.androidauthority.com\/android-canary-august-3589690\/\" target=\"_blank\" rel=\"noopener\">2508 Android Canary release<\/a>, but since the Canary track is its own, separate release channel, we weren\u2019t sure when the feature would make its way to users in the stable channel. Now that it\u2019s live in QPR2 Beta 2, we expect the icon shape options to be available in December\u2019s stable Android 16 QPR2 release.<\/p>\n<p>Step tracking in Health Connect<\/p>\n<p>When Google launched <a href=\"https:\/\/www.androidauthority.com\/google-health-connect-app-3234491\/\" target=\"_blank\" rel=\"noopener\">Health Connect<\/a> back in 2022, it was designed as a central hub for all your health and fitness data. Apps would contribute data to Health Connect, which would store that data in a secure, local database. Other apps could then pull that same data, add it to their own databases, and analyze that data. The idea was for Health Connect to simplify data sharing between health and fitness apps instead of tracking data of its own.<\/p>\n<p><img class=\"e_3g\" decoding=\"async\" loading=\"lazy\"  title=\"Step tracking banner in Health Connect\"  alt=\"Step tracking banner in Health Connect\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/Step-tracking-banner-in-Health-Connect-scaled.png\"\/><img class=\"e_3g\" decoding=\"async\" loading=\"lazy\"  title=\"Health Connect notification about step tracking\"  alt=\"Health Connect notification about step tracking\" src=\"https:\/\/www.europesays.com\/uk\/wp-content\/uploads\/2025\/09\/Health-Connect-notification-about-step-tracking-scaled.png\"\/><\/p>\n<p>Well, it seems Google wants to make Health Connect do more. In Android 16 QPR2 Beta 2, Health Connect now tracks your steps using your phone. When you open the app, you\u2019ll be met by a banner that reads, \u201cSteps tracked on your phone will appear in Health Connect. Steps tracked by this device are now stored in Health Connect for connected apps to access.\u201d<\/p>\n<p>Other changes<\/p>\n<ul>\n<li><strong>A way to test Android\u2019s new developer verification requirements<\/strong>\n<ul>\n<li>Google recently announced that Android will block the <a href=\"https:\/\/www.androidauthority.com\/android-developer-verification-requirements-3590911\/\" target=\"_blank\" rel=\"noopener\">installation of apps from unverified developers<\/a> next year. Android 16 QPR2 Beta 2 add a <a href=\"https:\/\/developer.android.com\/reference\/android\/content\/pm\/PackageInstaller#EXTRA_DEVELOPER_VERIFICATION_FAILURE_REASON\" target=\"_blank\" rel=\"noopener\">new API<\/a> that lets developers of apps that support package installation to see if installation failed due to developer verification checks. Developers can also use a new ADB command in QPR2 Beta 2 (adb shell pm set-developer-verification-result) to simulate a verification outcome for testing purposes. Google also confirmed today that <a href=\"https:\/\/www.androidauthority.com\/how-android-sideloading-restrictions-may-work-3595355\/\" target=\"_blank\" rel=\"noopener\">ADB installation will bypass<\/a> Android\u2019s new developer verification checks.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Protection from SMS OTP hijacking<\/strong>\n<ul>\n<li>To protect users from malicious apps that steal OTPs from SMS, Android 16 QPR2 Beta 2 now withholds the RECEIVE_SMS broadcast and filters SMS provider database queries for three hours after an SMS containing a retriever hash has been received.<\/li>\n<\/ul>\n<\/li>\n<li><strong>More efficient garbage collection<\/strong>\n<ul>\n<li>The Android Runtime (ART) has a new \u201cGenerational Concurrent Mark-Compact (CMC) Garbage Collector\u201d that Google says \u201cfocuses collection efforts on newly allocated objects, which are more likely to be garbage.\u201d The company says to \u201cexpect reduced CPU usage from garbage collection, a smoother user experience with less jank, and improved battery efficiency.\u201d<\/li>\n<\/ul>\n<\/li>\n<li><strong>Expanded exercise data in Health Connect<\/strong>\n<ul>\n<li>The ExerciseSegment and ExerciseSession data types have been updated so apps can now \u201crecord and read weight, set index, and Rate of Perceived Exertion (RPE) for exercise segments.\u201d<\/li>\n<\/ul>\n<\/li>\n<li><strong>Minor SDK version bump<\/strong>\n<ul>\n<li>The SDK version for Android 16 QPR2 is 36.1, reflecting its status as a minor release with new developer APIs but no new app-facing system behaviors.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>This article will be updated as we find more information on Android 16 QPR2 Beta 2. Check back later for more details!<\/p>\n<p>Thank you for being part of our community. Read our\u00a0<a class=\"c-link\" href=\"https:\/\/www.androidauthority.com\/android-authority-comment-policy\/\" target=\"_blank\" rel=\"noopener noreferrer\" data-stringify-link=\"https:\/\/www.androidauthority.com\/android-authority-comment-policy\/\" data-sk=\"tooltip_parent\">Comment Policy<\/a> before posting.<\/p>\n","protected":false},"excerpt":{"rendered":"Mishaal Rahman \/ Android Authority In less than three months, Google will roll out the second quarterly release&hellip;\n","protected":false},"author":2,"featured_media":432133,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7],"tags":[2239,2240,53,16,15],"class_list":{"0":"post-432132","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-android-16","9":"tag-authority-insights","10":"tag-technology","11":"tag-uk","12":"tag-united-kingdom"},"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@uk\/115221847497006829","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/432132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/comments?post=432132"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/posts\/432132\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media\/432133"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/media?parent=432132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/categories?post=432132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/uk\/wp-json\/wp\/v2\/tags?post=432132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}