[HTML payload içeriği buraya]
31.4 C
Jakarta
Wednesday, May 13, 2026

Android 16 QPR2 Beta 2 is Right here



Android 16 QPR2 has launched Platform Stability as we speak with Beta 2! That implies that the API floor is locked, and the app-facing behaviors are ultimate, so you may incorporate them into your apps and reap the benefits of our newest platform improvements.

New within the QPR2 Beta

At this later stage within the improvement cycle, we’re centered on the important work of readying the platform for launch. Listed below are the few impactful adjustments we need to spotlight:

Testing developer verification

To higher defend 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 via 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 comprises new APIs that help developer verification throughout set up, together with a brand new adb command to allow you to drive a verification consequence for testing functions.

adb shell pm set-developer-verification-result

Through the use of 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 can be delayed for many apps for 3 hours to assist stop OTP hijacking. The RECEIVE_SMS broadcast can be withheld and sms supplier database queries can be filtered. The SMS can be accessible to those apps after the three hour delay.

Sure apps such because the default SMS, assistant, and dialer apps, together with related system companion, system apps, and so forth can 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. Verify to guarantee that your adaptive icon works nicely 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’ll be able to anticipate decreased CPU utilization from rubbish assortment, a smoother person expertise with much less jank, and improved battery effectivity.

Native step monitoring and expanded train knowledge in Well being Join

Well being Join now routinely tracks steps utilizing the system’s sensors. In case your app has the READ_STEPS permission, this knowledge can be accessible from the “android” bundle. Not solely does this simplify the code wanted to do step monitoring, it is extra energy environment friendly as nicely.

Additionally, the ExerciseSegment and ExerciseSession knowledge sorts have been up to date. Now you can file and browse weight, set index, and Charge of Perceived Exertion (RPE) for train segments. Since Well being Join is up to date independently of the platform, checking for characteristic availability earlier than writing the info will guarantee compatibility with the present native model of Well being Join.

// Verify if the expanded train options can be found
val newFieldsAvailable = healthConnectClient.options.getFeatureStatus(
    HealthConnectFeatures.FEATURE_EXPANDED_EXERCISE_RECORD
) == HealthConnectFeatures.FEATURE_STATUS_AVAILABLE

val phase = ExerciseSegment(
    //...
    // Conditionally add the brand new knowledge 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 supplied outdoors of our typical once-yearly timeline. In contrast to the key platform launch (Android 16) in 2025-Q2 that included habits adjustments that impression app compatibility, the adjustments on this launch are largely additive and designed to reduce the necessity for added app testing.

Android 16 SDK release cadence

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
}

You may also use the Construct.getMinorSdkVersion() methodology 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 check 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 habits adjustments, they can’t be used within the uses-sdk manifest attributes.

Get began with the Android 16 QPR2 beta

You’ll be able to enroll any supported Pixel system to get this and future Android Beta updates over-the-air. In the event you don’t have a Pixel system, you may use the 64-bit system photos with the Android Emulator in Android Studio.  In case you are already within the Android Beta program, you’ll be provided an over-the-air replace to Beta 2. We’ll replace the system photos and SDK recurrently all through the Android 16 QPR2 launch cycle.

In case you are within the Canary program and want to enter the Beta program, you will want to wipe your system and manually flash it to the beta launch.

For the most effective improvement expertise with Android 16 QPR2, we suggest that you just use the newest Canary model of Android Studio Narwhal Function Drop.

We’re in search of your suggestions so please report points and submit characteristic requests on the suggestions web page. The sooner we get your suggestions, the extra we are able to embrace in our work on the ultimate launch. Thanks for serving to to form the way forward for the Android platform.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles