Android 17 Features: What's New and What Breaks for Your App

What Are the New Android 17 Features?

Google's Android 17 features page lists Handoff, the contact picker, Encrypted Client Hello, new ProfilingManager triggers and hybrid APK signing among the new APIs.

AppFunctions and App Bubbles come from the release post, which also makes Android development Compose-first. View components in android.widget and View-based Jetpack libraries such as Fragments, RecyclerView and ViewPager are now in maintenance mode, and all new APIs, libraries and guidance target Jetpack Compose.

Which Android 17 Changes Affect Every App?

These changes apply as soon as your app runs on Android 17, whatever its targetSdkVersion, per Google's behavior changes for all apps page.

Run this pass first. Users on Android 17 already hit these changes with the build you have in the store.

The memory limit is the change most likely to pass for a random crash in your reports. Log the exit reason on the next launch so a limiter kill is labeled as one:

val activityManager = getSystemService(ActivityManager::class.java)
activityManager.getHistoricalProcessExitReasons(packageName, 0, 5)
    .filter { info ->
        info.reason == ApplicationExitInfo.REASON_OTHER &&
            info.description?.contains("MemoryLimiter:AnonSwap") == true
    }
    .forEach { info ->
        Log.w("MemoryLimiter", "Killed at " + info.timestamp + ", PSS " + info.pss + " KB")
    }

Add these to the same regression pass:

• CameraX version - the release post says to update CameraX to 1.5.2 or 1.6.0+ to avoid a crash tied to a new dynamic range mode on Android 17 devices.
• Activity recreation - Google's guide to handle configuration changes says that starting with Android 17, activities no longer restart by default for keyboard, navigation, touchscreen, color mode and desk-mode UI changes and receive onConfigurationChanged() instead. An app that needs a full restart must opt in with android:recreateOnConfigChanges. Neither behavior changes page lists it, so check it in both passes.

What Breaks When You Target Android 17 (API 37)?

Raising targetSdkVersion to 37 switches on the changes for apps targeting Android 17 or higher, listed on Google's Android 17 behavior changes page.

Several of them surface as exceptions or process crashes rather than visible UI bugs, so read device logs alongside screenshots.

The resizability row takes the most manual time: unfold the device, rotate it, and drag the app into a floating window on each screen. The guide to testing foldable phones covers the posture and app continuity cases that go with it.

How to Test API 37 Changes Before Raising targetSdkVersion

Google's Android 17 migration guide splits the work into two phases: make the app compatible with Android 17 without changing targetSdkVersion, then update targetSdkVersion to target Android 17. For a debuggable app, its compatibility toggles let you test targeted changes without changing targetSdkVersion and manage them with adb commands.

# List every compatibility change on the device and how it is gated
adb shell dumpsys platform_compat

# Turn on the API 37 large-screen resizability rule for your debug build
adb shell am compat enable UNIVERSAL_RESIZABLE_BY_DEFAULT com.example.app

# Return the change to its default state
adb shell am compat reset UNIVERSAL_RESIZABLE_BY_DEFAULT com.example.app

• Debuggable builds - Google's compatibility framework tools page requires a debuggable build variant, and on a public release build of Android only changes gated by targetSdkVersion can be toggled. The same page explains the dumpsys output: enableAfterTargetSdk is one below the target level that switches a change on, and toggling a change kills the app so the override applies at once.
• The resizability flag - Google's resizability guidance says you can test the large-screen rule by enabling the UNIVERSAL_RESIZABLE_BY_DEFAULT compat flag.
• Logcat confirmation - the CompatibilityChangeReporter tag logs each reported change ID once per process, so force-stop and relaunch the app to see every change it hits.
• Non-SDK access - the migration guide asks you to watch logcat for non-SDK API warnings and to call StrictMode detectNonSdkApiUsage(), which catches the MessageQueue reflection that breaks at API 37.
• On TestMu AI - live app sessions on real devices include an ADB shell that accepts am compat enable, dumpsys, getprop and pm clear on public devices, per the real device ADB shell docs. am compat reset and Google's am memory-limiter commands need a private device, where the full am command set is available.

Which Android 17 Devices Can You Test on TestMu AI?

At the time of writing, the public list of real devices on TestMu AI shows these Android 17 entries, and each one is offered for both live and automated testing:

Older Pixel models are listed on several OS builds. The Pixel 9, for example, is listed on both Android 16 and Android 17, so one device model gives you an Android 16 baseline and an Android 17 run on the same hardware.

• Real devices only - the Android emulator online covers Android 4.1 through 16, so Android 17 runs happen on physical Pixels and foldables.
• Session artifacts - every real device cloud session records video, device logs, network logs, and CPU and memory data, which is where a memory-limiter kill or a silently failed audio call shows up.
• Automated runs - App Automation runs Appium, Espresso, XCUITest, Maestro and Mobilewright suites in parallel on 10,000+ real Android and iOS devices. If you are upgrading Appium in the same cycle, read what's new in Appium 4 first.
• Device planning - an Android app testing device matrix weights Android 17 against the versions your users still run, so the new OS gets a share of runs rather than the whole budget.

Android 17 QPR1 and the Changes Coming Next

Android 17 QPR1 reached Pixel devices with the September 2026 Feature Drop, per 9to5Google.

Google's QPR1 release notes say the QPR updates do not include app-impacting API changes, and that QPR1 reached Platform Stability with new capabilities you can adopt from its API diff report.

Your API 37 test plan carries over to QPR1 unchanged. These items set the next round of work:

• Android 18 URI grants - starting in Android 18, the system stops granting URI permissions automatically for ACTION_SEND, ACTION_SEND_MULTIPLE and ACTION_IMAGE_CAPTURE intents, so add FLAG_GRANT_READ_URI_PERMISSION now, plus the write flag for image capture.
• Cleartext traffic - Google plans to deprecate usesCleartextTraffic, so move cleartext exceptions into a network security configuration file.
• Google Play deadline - since August 31, 2026, new apps and app updates must target API 36, with extensions available to November 1, 2026, per Google Play's target API level requirements, which list no API 37 requirement yet.

StrictMode already flags the Android 18 URI grant change in debug builds:

val policy = StrictMode.VmPolicy.Builder()
    .detectImplicitUriPermissionGrant()
    .penaltyLog()
    .build()
StrictMode.setVmPolicy(policy)

Getting Started With Android 17 Testing

Run your current store build, unchanged, on an Android 17 Pixel and a Galaxy Z Fold8 first; that run covers every row in the all-apps table. Then build a debuggable variant, switch on API 37 changes one at a time with am compat enable, and raise targetSdkVersion to 37 once that pass is clean.

To automate the same checks, follow getting started with Espresso testing and select the Android 17 devices on TestMu AI for your next build.