By Google’s Pixel 11 series ships August 20 with Android 17 already installed, and if you ship an Android app, this is not a consumer story. Android 17 (API Level 37) introduces five breaking behavior changes, and the most consequential removes your ability to lock screen orientation on large screens entirely. The system ignores whatever you set. With Pixel 11 devices landing in a week and the broader Android 17 rollout coming this fall, the compliance clock is running.
The Big One: Mandatory Large-Screen Resizability
Starting with API level 37, on any device whose smallest width exceeds 600dp — tablets, foldables, most of the Pixel Fold lineup — the following attributes and method calls are simply ignored by the system:
android:screenOrientationin your manifestsetRequestedOrientation()at runtimeandroid:resizeableActivity="false"minAspectRatioandmaxAspectRatioconstraints
Games tagged with android:appCategory="game" and devices under 600dp are exempt. Everyone else: your orientation lock is gone on large screens.
The most common breakage is camera preview. If you’re using Camera2 directly and calculating orientation from screen dimensions, you’ll get a stretched or rotated preview on wide displays. Migrate to CameraX — it handles sensor orientation and display rotation automatically. For layouts, constrain fixed-width elements in Compose:
Column(
modifier = Modifier
.widthIn(max = 300.dp)
.fillMaxWidth()
.padding(16.dp)
)Add verticalScroll(rememberScrollState()) to scrollable columns to prevent buttons from going offscreen on unexpected aspect ratios. Also note that six configuration change types no longer trigger a full Activity restart in Android 17 — use onConfigurationChanged() or Compose’s declarative recomposition to handle size changes cleanly. For full migration guidance, Google’s official resizability migration guide covers camera fixes, emulator setup, and CI testing strategies.
The Google Play deadline for targeting API level 37 is August 2027. You have time, but not infinite time, and this change takes real engineering. Start now.
Two Changes That Will Catch You Off Guard
Certificate Transparency Is On By Default
Certificate Transparency was opt-in through Android 16. Starting with API 37, it is active by default. If your app connects to any TLS server using a privately issued certificate that has not been submitted to a public CT log — a corporate API, a staging environment behind a private CA, an on-premise deployment — that connection will fail silently. No warning. Just failure.
The fix is either to submit your certificates to a CT log or to configure exceptions in your Network Security Configuration. Either way, this is something your backend and security teams need to know about before you bump targetSdkVersion to 37.
Local Network Access Is Now Permissioned
Android 17 adds ACCESS_LOCAL_NETWORK, a new runtime permission. Apps targeting API 37 have local network access blocked by default. mDNS discovery, Chromecast integration, smart home device scanning — all of it requires the new permission. Declare it in your manifest, request it at runtime, and consider whether a privacy-preserving picker can handle the use case instead.
The Tensor G6 Is Worth Paying Attention To
The developer angle on Pixel 11 hardware matters. The Tensor G6’s TPU delivers 50% more compute than its predecessor, with Google claiming on-device AI tasks run 3.5 times faster at 3.5 times lower energy consumption. That is not a minor increment.
The practical implication: features that previously required a cloud round-trip are viable on-device on Pixel 11. The latest Gemini Nano model runs locally on Android 17 — offline, private, no API call. If you have been holding off on building ML-driven features because previous Tensor generations were too slow, the G6 changes that calculus. It also means users on Pixel 11 will expect snappier ML interactions than on Pixel 10 — apps relying on cloud inference for basic tasks will start feeling sluggish by comparison.
Three More Breaking Changes
Static final fields via reflection now throw. If any part of your code — or a testing framework you use — modifies static final fields through reflection, it will throw IllegalAccessException on API 37+. The long-standing workaround is gone. Replace it with proper dependency injection or updated mocking libraries that do not rely on reflection hacks.
SMS OTP access is delayed. Apps that read SMS directly and are not using the SMS Retriever API will find OTP messages held for three hours. Google is forcing the ecosystem toward declared, auditable flows. Migrate to the SMS Retriever API before targeting API 37.
Reflecting on MessageQueue private fields breaks. Android 17’s lock-free MessageQueue implementation has a different internal structure. If anything in your stack reflects on its private fields, that code needs to be removed.
What to Do Now
If you are not targeting API 37 yet, you have until August 2027 before Google Play requires it for new submissions. That deadline is real, and the large-screen compliance work is not a one-sprint fix for most apps. Audit your codebase for orientation locks and aspect ratio constraints now. Set up a Pixel Fold or tablet emulator in CI. And test your TLS connections against a staging environment before blindly bumping the target SDK. Google announced Pixel 11 yesterday — Android 17 is already shipping. The ecosystem catches up fast.
