Android 16 QPR2 has launched Platform Stability right this moment with Beta 2! That signifies that the API floor is locked, and the app-facing behaviors are remaining, so you may incorporate them into your apps and make the most of our newest platform improvements.
New within the QPR2 Beta
At this later stage within the improvement cycle, we’re targeted on the important work of readying the platform for launch. Listed here are the few impactful modifications we wish to spotlight:
Testing developer verification
To higher shield Android customers from repeat offenders, Android is introducing developer verification, a brand new requirement to make app set up safer by stopping the unfold of malware and scams. Beginning in September 2026 and in particular areas, Android would require apps to be registered by verified builders to be put in on licensed Android units, with an exception made for installs made by means of the Android Debug Bridge (ADB).
As a developer, you’re free to put in apps with out verification by utilizing ADB, so you may proceed to check apps that aren’t meant or not but able to distribute to the broader client inhabitants.
For apps that allow user-initiated set up of app packages, Android 16 QPR2 Beta 2 incorporates new APIs that help developer verification throughout set up, together with a brand new adb command to allow you to pressure a verification end result for testing functions.
adb shell pm set-developer-verification-result
By utilizing this command, (see adb shell pm assist for full particulars) now you can simulate verification failures. This lets you perceive the end-to-end person expertise for each profitable and unsuccessful verification, so you may put together accordingly earlier than enforcement begins.
We encourage all builders who distribute apps on licensed Android units to join early entry to prepare and keep up to date.
SMS OTP Safety
The supply of messages containing an SMS retriever hash will likely be delayed for many apps for 3 hours to assist stop OTP hijacking. The RECEIVE_SMS broadcast will likely be withheld and sms supplier database queries will likely be filtered. The SMS will likely be accessible to those apps after the three hour delay.
Sure apps such because the default SMS, assistant, and dialer apps, together with linked gadget companion, system apps, and many others will likely be exempt from this delay, and apps can proceed to make use of the SMS retriever API to entry messages meant for them in a well timed method.
Customized app icon shapes
Android 16 QPR2 permits customers to pick out from an inventory of icon shapes that apply to all app icons and folder previews. Examine to make it possible for your adaptive icon works properly with any form the person selects.
Extra environment friendly rubbish assortment
The Android Runtime (ART) now features a Generational Concurrent Mark-Compact (CMC) Rubbish Collector in Android 16 QPR2 that focuses assortment efforts on newly allotted objects, which usually tend to be rubbish. You possibly can count on lowered CPU utilization from rubbish assortment, a smoother person expertise with much less jank, and improved battery effectivity.
Native step monitoring and expanded train information in Well being Join
Well being Join now routinely tracks steps utilizing the gadget’s sensors. In case your app has the READ_STEPS permission, this information will likely be accessible from the “android” package deal. Not solely does this simplify the code wanted to do step monitoring, it is extra energy environment friendly as properly.
Additionally, the ExerciseSegment and ExerciseSession information varieties have been up to date. Now you can document and browse weight, set index, and Price of Perceived Exertion (RPE) for train segments. Since Well being Join is up to date independently of the platform, checking for function availability earlier than writing the info will guarantee compatibility with the present native model of Well being Join.
// Examine if the expanded train options can be found val newFieldsAvailable = healthConnectClient.options.getFeatureStatus( HealthConnectFeatures.FEATURE_EXPANDED_EXERCISE_RECORD ) == HealthConnectFeatures.FEATURE_STATUS_AVAILABLE val section = ExerciseSegment( //... // Conditionally add the brand new information fields weight = if (newFieldsAvailable) Mass.fromKilograms(50.0) else null, setIndex = if (newFieldsAvailable) 1 else null, rateOfPerceivedExertion = if (newFieldsAvailable) 7.0f else null )
A minor SDK model
QPR2 marks the primary Android launch with a minor SDK model permitting us to extra quickly innovate with new platform APIs offered exterior of our traditional once-yearly timeline. Not like the foremost platform launch (Android 16) in 2025-Q2 that included conduct modifications that impression app compatibility, the modifications on this launch are largely additive and designed to reduce the necessity for added app testing.
Your app can safely name the brand new APIs on units the place they’re accessible by utilizing SDK_INT_FULL and the respective worth from the VERSION_CODES_FULL enumeration.
if (Construct.VERSION.SDK_INT_FULL >= Construct.VERSION_CODES_FULL.BAKLAVA_1) { // Name new APIs from the Android 16 QPR2 launch }
It’s also possible to use the Construct.getMinorSdkVersion() technique to get simply the minor SDK model quantity.
val minorSdkVersion = Construct.getMinorSdkVersion(VERSION_CODES_FULL.BAKLAVA)
The unique VERSION_CODES enumeration can nonetheless be used to match towards the SDK_INT enumeration for APIs declared in non minor releases.
if (Construct.VERSION.SDK_INT >= Construct.VERSION_CODES.BAKLAVA) { // Name new APIs from the Android 16 launch }
Since minor releases aren’t meant to have breaking conduct modifications, they can’t be used within the uses-sdk manifest attributes.
Get began with the Android 16 QPR2 beta
You possibly can enroll any supported Pixel gadget to get this and future Android Beta updates over-the-air. In the event you don’t have a Pixel gadget, you may use the 64-bit system pictures with the Android Emulator in Android Studio. If you’re already within the Android Beta program, you can be provided an over-the-air replace to Beta 2. We’ll replace the system pictures and SDK often all through the Android 16 QPR2 launch cycle.
If you’re within the Canary program and want to enter the Beta program, you have to to wipe your gadget and manually flash it to the beta launch.
For the very best improvement expertise with Android 16 QPR2, we suggest that you simply use the most recent Canary model of Android Studio Narwhal Characteristic Drop.
We’re searching for your suggestions so please report points and submit function requests on the suggestions web page. The sooner we get your suggestions, the extra we will embrace in our work on the ultimate launch. Thanks for serving to to form the way forward for the Android platform.