Check the actual applicability conditions
Google’s adaptive-app guide describes API level 36 behaviour on displays with smallest width at least 600dp. It names tablets, inner displays of large foldables and desktop windowing among the affected settings. This is a density-independent size condition, not a simple count of physical pixels.
The guide lists exceptions, including smaller displays, games identified through the application category and a user choosing the app’s default aspect-ratio behaviour. A phone’s outer display and the same foldable’s inner screen can therefore require separate observations.
Separate the video shape from the application window
The documented overrides concern app orientation, aspect-ratio constraints and resizability. They do not say every movie should be stretched to fill the new window. Preserve the content’s intended geometry while the surrounding controls adapt to the available space.
Record whether the issue is an app window rotating, controls overlapping, a button becoming unreachable or the video itself being cropped. These are different defects. A correct resize of the app does not certify that its player layout handles the new width and height correctly.
Use the documented transition rather than an old lock assumption
Google documents a temporary API36 opt-out property for restricted resizability and warns that the opt-out is removed for API37 targeting. Its current guide also cautions that the property does not itself lock orientation or prevent rotation on large displays.
Do not present adding that property as a permanent guarantee to keep every tablet portrait-only. Review the current compatibility behaviour and make the app adapt. Keep any manufacturer or user override in the reproduction conditions rather than assuming the manifest is the only authority.
Test state and controls across the size change
Google’s readiness guidance calls for reachable scrolling content, responsive layouts and preserved state during configuration changes. For a player, a useful proposed check records the selected media, playback position and visible controls before rotation or resizing, then verifies them afterwards.
No app or emulator was run for this article. The procedure identifies a platform transition and meaningful observations; it does not certify a particular IPTV app. A support note should name the target SDK, device/display context and exact failed layout, making a developer fix more specific than disabling rotation everywhere.
Sources and scope
Scope notes distinguish published documentation, supplied information and editorial methods. They do not report a hands-on service test.
- Android: orientation and resizability — Primary current body: API36/sw600dp scope, exceptions, temporary opt-out limits and readiness checklist.
- Android: targeted API36 behaviour — Official indexed default large-screen restriction overrides; no emulator execution or app compatibility claim.
