Android 17 behavior changes: a checklist for target SDK 37
Short answer: Android 17 has two sets of behavior changes. Some apply to every app running on Android 17, whatever it targets, such as app memory limits, SMS OTP protection and background audio rules. Others start only when you target API level 37, such as the lock-free MessageQueue, the local network permission, certificate transparency by default and ignored orientation locks on large screens. Google Play has not yet announced a date for requiring API level 37; the current rule is API level 36 for new apps and updates since August 31, 2026.
Android 17 behavior changes at a glance
From Android Developers’ Android 17 behavior change pages, read 1 October 2026. «All apps» means every app running on Android 17; «Target 37» means apps targeting API level 37 or higher.
| Change | Applies to | In one line |
|---|---|---|
| App memory limits | All apps | Per-app limits by device RAM; over the limit means zRAM, then termination |
| SMS OTP protection | All apps; stricter at target 37 | OTP messages held back from most apps; use SMS Retriever or User Consent |
| usesCleartextTraffic deprecation plan | All apps | Move cleartext rules to a network security configuration |
| Background audio hardening | All apps; while-in-use rule at target 37 | Background playback, focus and volume need a visible activity or foreground service |
| Lock-free MessageQueue | Target 37 | Reflection on MessageQueue internals breaks; update Espresso and Robolectric |
| Static final fields unmodifiable | Target 37 | Reflection throws IllegalAccessException; JNI writes crash |
| Local network permission | Target 37 | Local network blocked without a system picker or ACCESS_LOCAL_NETWORK |
| Certificate transparency by default | Target 37 | HTTPS certificates must be in public CT logs unless opted out |
| Orientation and resizability ignored | Target 37 | No orientation lock or fixed aspect ratio on screens 600dp and wider |
Changes for every app on Android 17
These reach users as soon as their device updates, even if you never change your target SDK: app memory limits, SMS OTP protection and phone verification, the usesCleartextTraffic deprecation plan and background audio hardening. Google’s «all apps» page also lists restricted implicit URI grants, per-app keystore limits, blocked cross-profile loopback traffic, restoring default IME visibility after rotation, relative touchpad events during pointer capture and autonomous Bluetooth re-pairing.
Changes when you target API level 37
Raising targetSdk to 37 switches on: the lock-free MessageQueue and unmodifiable static final fields, the local network permission, certificate transparency by default and ignored orientation and resizability limits on large screens. Google’s «targeting Android 17» page also lists Encrypted Client Hello, hiding passwords from physical devices, activity security, safer native dynamic code loading, restricted PII fields and strict SQL checks in the contacts provider, the deprecation of setContentCaptureEnabled, a memory limit for widgets and consistent Bluetooth RFCOMM read() behavior.
When Google Play will require target SDK 37
Not announced yet. Since August 31, 2026, new apps and updates must target Android 16 (API level 36), with an extension available to November 1, 2026; the API 35 rule before it took effect on August 31, 2025. Details and exceptions for Wear OS, TV, XR and Automotive are in Google Play target API level. The Play policy deadlines on contacts, location and call log that fall in January 2027 are separate from the target API rule, see the Contact Picker and the location button.
Where Censuus fits
Keeping up with the platform keeps your app working; being found brings users to it. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.
Frequently asked questions
What are the main Android 17 behavior changes?
For all apps: app memory limits, SMS OTP protection, the usesCleartextTraffic deprecation plan and background audio hardening. For apps targeting API level 37: the lock-free MessageQueue, unmodifiable static final fields, the local network permission, certificate transparency by default and ignored orientation limits on large screens.
What API level is Android 17?
API level 37.
When does Google Play require target SDK 37?
Google has not announced a date yet. The current requirement, since August 31, 2026, is API level 36 for new apps and updates.
Do Android 17 changes affect my app if I don’t update targetSdk?
Some do. Memory limits, SMS OTP protection and background audio rules apply to every app running on Android 17; the others start only when you target API level 37.
Guides for app developers
- Google Play target API level requirements for 2026
- ADB Wi-Fi 2.0 wireless debugging
- The Android 17 location button and Google Play’s precise location rules
- Android 17 ignores orientation lock and resizability on large screens
- The Android 17 Handoff API
- Android Contact Picker and the new READ_CONTACTS rules
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.