The Fourth Beta of Android 17

Android 17 has reached beta 4, the final scheduled beta of this launch cycle, a essential milestone for app compatibility and platform stability. Whether or not you are fine-tuning your app’s consumer expertise, guaranteeing easy edge-to-edge rendering, or leveraging the latest APIs, Beta 4 supplies the near-final atmosphere you’ll want to be testing with.

Get your apps, libraries, instruments, and recreation engines prepared!

For those who develop an Android SDK, library, instrument, or recreation engine, it’s vital to organize any needed updates now to stop your downstream app and recreation builders from being blocked by compatibility points and permit them to focus on the newest SDK options. Please let your downstream builders know if updates are wanted to completely help Android 17.

Testing entails putting in your manufacturing app or a take a look at app making use of your library or engine utilizing Google Play or different means onto a tool or emulator operating Android 17 Beta 4. Work by way of all of your app’s flows and search for useful or UI points. Every launch of Android accommodates platform adjustments that enhance privateness, safety, and total consumer expertise; evaluation the app impacting conduct adjustments for apps operating on and concentrating on Android 17 to focus your testing, together with the next:

• Resizability on giant screens: When you goal Android 17, you’ll be able to not decide out of sustaining orientation, resizability and facet ratio constraints on giant screens.
• Dynamic code loading: In case your app targets Android 17 or increased, the Safer Dynamic Code Loading (DCL) safety launched in Android 14 for DEX and JAR recordsdata now extends to native libraries. All native recordsdata loaded utilizing System.load() should be marked as read-only. In any other case, the system throws UnsatisfiedLinkError.
• Allow CT by default: Certificates transparency (CT) is enabled by default. (On Android 16, CT is on the market however apps needed to decide in.)
• Native community protections: Apps concentrating on Android 17 or increased have native community entry blocked by default. Change to utilizing privateness preserving pickers if attainable, and use the brand new ACCESS_LOCAL_NETWORK permission for broad, persistent entry.
• Background audio hardening: Beginning in Android 17, the audio framework enforces restrictions on background audio interactions together with audio playback, audio focus requests, and quantity change APIs. Based mostly in your suggestions, we’ve made some adjustments since beta 2, together with targetSDK gating while-in-use FGS enforcement and exempting alarm audio. Full particulars out there in up to date steering.

App reminiscence limits

Android is introducing app reminiscence limits primarily based on the machine’s whole RAM to create a extra steady and deterministic atmosphere on your functions and Android customers. In Android 17, limits are set conservatively to determine system baselines, concentrating on excessive reminiscence leaks and different outliers earlier than they set off system-wide instability leading to UI stuttering, increased battery drain, and apps being killed. Whereas we anticipate minimal affect on the overwhelming majority of app periods, we suggest the following reminiscence greatest practices, together with establishing a baseline for reminiscence.

Within the present implementation, getDescription in ApplicationExitInfo will include the string “MemoryLimiter” in case your app was impacted. You too can use trigger-based profiling with TRIGGER_TYPE_ANOMALY to get heap dumps which can be collected when the reminiscence restrict is hit.

The LeakCanary job within the Android Studio Profiler

That can assist you discover reminiscence leaks, Android Studio Panda provides LeakCanary integration straight within the Android Studio Profiler as a devoted job, contextualized throughout the IDE and absolutely built-in along with your supply code.

A lighter reminiscence footprint interprets on to smoother efficiency, longer battery life, and a premium expertise throughout all type elements. Let’s construct a sooner, extra dependable future for the Android ecosystem collectively!

Profiling triggers for app anomalies

Android introduces an on-device anomaly detection service that screens for resource-intensive behaviors and potential compatibility regressions. Built-in with ProfilingManager, this service permits your app to obtain profiling artifacts triggered by particular system-detected occasions.

Use the TRIGGER_TYPE_ANOMALY set off to detect system efficiency points resembling extreme binder calls and extreme reminiscence utilization. When an app breaches OS-defined reminiscence limits, the anomaly set off permits builders to obtain app-specific heap dumps to assist establish and repair reminiscence points. Moreover, for extreme binder spam, the anomaly set off supplies a stack sampling profile on binder transactions.

This API callback happens previous to any system imposed enforcements. For instance, it may well assist builders gather debug knowledge earlier than the app is terminated by the system due exceeding reminiscence limits. To know methods to use the set off take a look at our documentation on set off primarily based profiling.

val profilingManager = applicationContext.getSystemService(ProfilingManager::class.java)
val triggers = ArrayList<ProfilingTrigger>()  
triggers.add(ProfilingTrigger.Builder(
             ProfilingTrigger.TRIGGER_TYPE_ANOMALY))
val mainExecutor: Executor = Executors.newSingleThreadExecutor()
val resultCallback = Client<ProfilingResult> { profilingResult ->
    if (profilingResult.errorCode != ProfilingResult.ERROR_NONE) {
        // add profile outcome to server for additional evaluation          
        setupProfileUploadWorker(profilingResult.resultFilePath)
    } 
}
profilingManager.registerForAllProfilingResults(mainExecutor, resultCallback)
profilingManager.addProfilingTriggers(triggers)

Publish-Quantum Cryptography (PQC) in Android Keystore

Android Keystore added help for the NIST-standardized ML-DSA (Module-Lattice-Based mostly Digital Signature Algorithm). On supported units, you’ll be able to generate ML-DSA keys and use them to supply quantum-safe signatures, completely within the machine’s safe {hardware}. Android Keystore exposes the ML-DSA-65 and ML-DSA-87 algorithm variants by way of the usual Java Cryptographic Structure APIs: KeyPairGenerator, KeyFactory, and Signature. For additional particulars, see our developer documentation.

KeyPairGenerator generator = KeyPairGenerator.getInstance(
        “ML-DSA-65”, "AndroidKeyStore");
generator.initialize(
        new KeyGenParameterSpec.Builder(
                “my-key-alias”,
                KeyProperties.PURPOSE_SIGN | KeyProperties.PURPOSE_VERIFY)
        .construct());
KeyPair keyPair = generator.generateKeyPair();

Get began with Android 17

You’ll be able to enroll any supported Pixel machine to get this and future Android Beta updates over-the-air. For those who don’t have a Pixel machine, you’ll be able to use the 64-bit system photographs with the Android Emulator in Android Studio.

If you’re presently within the Android Beta program, you may be supplied an over-the-air replace to Beta 4. Proceed to 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.

For the perfect improvement expertise with Android 17, we suggest that you just use the newest preview of Android Studio (Panda). When you’re arrange, listed below are among the issues you need to do:

• Compile in opposition to the brand new SDK, take a look at in CI environments, and report any points in our tracker on the suggestions web page.
• Check your present app for compatibility, study whether or not your app is affected by adjustments in Android 17, and set up your app onto a tool or emulator operating Android 17 and extensively take a look at it.

We’ll replace the preview/beta system photographs and SDK usually all through the Android 17 launch cycle. When you’ve put in a beta construct, you’ll robotically get future updates over-the-air for all later previews and Betas. For full data, go to the Android 17 developer web site.

Be part of the dialog

Your suggestions stays our most useful asset. Whether or not you’re an early adopter on the Canary channel or an app developer testing on Beta 4, take into account becoming a member of our communities and submitting suggestions. We’re listening.