Android on Tablets and Foldables: Why Orientation Locks Are Going Away

For years, an Android developer could add a line to an app saying "portrait only" and the app would stay upright, even on a tablet. That is ending. Beginning with Android 16, and with no escape route in Android 17, the system ignores orientation and resizability locks on large screens for apps that target those versions. The app simply fills the window, whatever its shape.

If your customers or staff use only ordinary phones, this will mostly pass you by. If any of them use a tablet, a foldable, a Chromebook or a phone connected to a monitor, read on. The details below come from Google's developer documentation as of November 2026.

What exactly changes

The rule applies to screens whose smallest width is 600dp or more. That covers tablets, the inner screens of large foldables and windows in desktop mode. Ordinary phones, flip phones and cover screens are below that line and unaffected. On those large screens, an app that targets the affected version has these settings ignored: fixed screen orientation, "not resizable", and minimum or maximum aspect ratio. The app becomes resizable, can run in split-screen, and rotates with the device.

There are three exceptions. Games, identified by their app category, are exempt. Users can choose to run a specific app in its default behaviour from the device's aspect ratio settings. And small screens are not covered at all.

The timeline: Android 16 first, Android 17 for good

• Android 16 (API 36): the restriction applies to apps targeting API 36. Google provides a temporary opt-out, a manifest property that can be set for the whole app or for one screen.
• Android 17 (API 37): the opt-out is removed. An app targeting API 37 cannot avoid the behaviour.

The link with Google Play matters. Since 31 August 2026, new apps and updates must target API 36, so any update you publish now is subject to the Android 16 behaviour on tablets unless the opt-out is set. Google has announced no Play deadline for targeting API 37 as of 3 November 2026, which means the opt-out can buy time but not forever. Our posts on Android 16 and Android 17 cover the surrounding changes.

What breaks in phone-only layouts

Google lists three common failures, and they match what we see when phone designs meet wide windows.

• Stretched screens. A login form or a list built for a 360dp-wide phone is suddenly 1,200dp wide: buttons become huge bars, and text lines run too long to read.
• Camera previews. Scanning and photo features can look stretched, rotated or cropped, because the code assumed a fixed link between the camera sensor and the screen direction. Barcode scanners in stock and billing apps are the usual victims.
• Lost input. Rotating or resizing recreates the screen by default. If the app does not save its state, half-typed forms and scroll positions vanish.

Who should care, honestly

If your app is a phone-only tool for delivery staff, with no tablet use at all, treat this as a low priority and a simple test. It becomes a real item for: a shop or restaurant billing app on a counter tablet; a classroom or training app, where tablets are normal; kiosks; and any app that plays video. A video lesson player like the one in the Android app we built for Brave Mom Naturals is exactly the sort of screen worth checking on a tablet, since people often watch lessons on larger devices.

A word on state and testing budgets

Most of the cost of this change is testing, not coding. A single layout fix is quick; checking every screen at three window sizes in two orientations is what takes the time. Ask for the test to be done screen by screen from a list, and ask to see screenshots of the tablet result before you approve the release.

How to adapt

1. Ask your developer to turn on Google's compatibility flag for universal resizing on a test device, which shows the new behaviour before you target it.
2. Test on tablet and foldable emulators in Android Studio, in both orientations and in split-screen.
3. Cap the width of forms and text so they stay readable on wide screens.
4. Use window size classes to switch between a one-column phone layout and a two-pane layout with a list beside its details.
5. Save screen state so rotation does not wipe user input.
6. Re-test every camera and scanning feature.
7. Use the Android 16 opt-out only as a short bridge while the work is scheduled.

Apps written in Jetpack Compose adapt more easily, because layouts are built as flexible functions rather than fixed files. VS Tech Builders builds new Android apps this way, and native Android development is where we do most of our work. If you would like an existing app tested on a tablet, contact us.

Sources

Checked on 3 November 2026. Technology changes quickly; always confirm details with the official source before you act on them.

• App orientation, aspect ratio, and resizability — Android Developers
• Restrictions on orientation and resizability are ignored (Android 17) — Android Developers
• Behavior changes: Apps targeting Android 16 or higher — Android Developers
• Target API level requirements for Google Play apps — Play Console Help

Frequently asked questions

Does this change affect apps on normal phones?

No. The change applies only to screens with a smallest width of 600dp or more, such as tablets, the inner displays of large foldables and desktop windows. Ordinary phones, flip phones and cover screens fall below that threshold, so a portrait-locked phone app behaves as before on them.

Can I still lock my app to portrait on tablets?

Only temporarily. For apps targeting Android 16 (API 36), Google provides a manifest property that opts out of the new behaviour. That opt-out does not apply to apps targeting Android 17 (API 37), and Google gives no way around the change there. Games and users who choose the app's default behaviour are exempt.

Does Google Play force me to target Android 17?

Not as of 3 November 2026. Play requires new apps and updates to target Android 16 (API 36) since 31 August 2026, and Google has announced no deadline for API 37. That means the orientation opt-out remains available for now, but planning the layout work early avoids a rushed release later.

How do I test whether my app will break on tablets?

Use the tablet and foldable emulators in Android Studio, and ask your developer to enable the universal resizable compatibility flag on a test device. Rotate the screen, resize the window and open split-screen. Pay special attention to camera previews, forms with typed input and any screen using a fixed width.