Galaxy Tab S11 Window Insets & Display Metrics

Metrics

Dimensions

Logical Size: 1204.71 × 752.94 dp
Resolution: 2560 × 1600 px
Aspect Ratio: 8:5
sw600dp: Yes
Physical Density: 274 ppi
Android Density: 340 dpi
Scale: 2.13×

What does sw600dp mean?

“sw” means smallest width. Android's sw600dp resource qualifier applies when the app's smallest available width is at least 600 dp. The Yes/No value here compares the selected display's shorter measured logical dimension with 600 dp; exactly 600 dp counts as Yes.

Safe Area Insets

Top: 30.12 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

With the keyboard hidden, Compose's WindowInsets.safeDrawing and a View's systemBars() or displayCutout() insets resolve to these values.Compose · Views guide →

Display Cutout Bounds

Android reported no display cutout here. Any camera shown in the official artwork is not a measured exclusion, so its edge distances are not shown.Cutout measurement limits →

Corner Radii · Landscape

Top Left: 13.18 dp
Top Right: 13.18 dp
Bottom Right: 13.18 dp
Bottom Left: 13.18 dp

Use in development Preview spec, size class, AVD, adb

Compose Preview

Kotlin

// Galaxy Tab S11 · 3-button · ROTATION_90 (captured 2026-09-29)
@Preview(device = "spec:width=2560px,height=1600px,dpi=340,cutout=none,navigation=buttons")
@Composable
fun TabS11Preview() {
    // Your screen here
}

Kotlin

// Galaxy Tab S11 · 3-button · ROTATION_90 (captured 2026-09-29)
@Preview(device = "spec:width=2560px,height=1600px,dpi=340,cutout=none,navigation=buttons")
@Composable
fun TabS11Preview() {
    // Your screen here
}

Size and density match this capture exactly. Compose Preview draws its own generic system bars and cutout, not One UI's: check layouts against the measured insets above.

Window Size Class

Window: 1204.71 × 752.94 dp
Width / Height: Expanded (Large) / Medium

ROTATION_0Medium / Expanded
752.94 × 1204.71 dp
ROTATION_90Expanded (Large) / Medium
1204.71 × 752.94 dp
ROTATION_180Medium / Expanded
752.94 × 1204.71 dp
ROTATION_270Expanded (Large) / Medium
1204.71 × 752.94 dp

From WindowMetrics' maximum window in each capture (breakpoints: width 600 / 840 dp, height 480 / 900 dp; Large ≥ 1200 dp). Rotations without a capture are never derived by swapping width and height.

Emulator

Screen from this capture and the official diagonal; other hardware entries are emulator defaults. Import in Device Manager › Create Virtual Device › Import Hardware Profiles.

Shell

# Galaxy Tab S11 · 3-button · ROTATION_90 (captured 2026-09-29)
adb shell wm size 1600x2560
adb shell wm density 340
adb shell cmd overlay enable-exclusive --category com.android.internal.systemui.navbar.threebutton
adb shell cmd overlay disable com.android.internal.display.cutout.emulation.hole
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1

# Restore the emulator's defaults
adb shell wm size reset
adb shell wm density reset
adb shell cmd overlay enable-exclusive --category com.android.internal.systemui.navbar.gestural
adb shell cmd overlay disable com.android.internal.display.cutout.emulation.hole
adb shell settings put system user_rotation 0
adb shell settings put system accelerometer_rotation 1

Shell

# Galaxy Tab S11 · 3-button · ROTATION_90 (captured 2026-09-29)
adb shell wm size 1600x2560
adb shell wm density 340
adb shell cmd overlay enable-exclusive --category com.android.internal.systemui.navbar.threebutton
adb shell cmd overlay disable com.android.internal.display.cutout.emulation.hole
adb shell settings put system accelerometer_rotation 0
adb shell settings put system user_rotation 1

# Restore the emulator's defaults
adb shell wm size reset
adb shell wm density reset
adb shell cmd overlay enable-exclusive --category com.android.internal.systemui.navbar.gestural
adb shell cmd overlay disable com.android.internal.display.cutout.emulation.hole
adb shell settings put system user_rotation 0
adb shell settings put system accelerometer_rotation 1

Runs your app at this capture's window size and density in the selected navigation mode and rotation; open your app first, since a portrait-locked launcher keeps the display upright. The cutout is AOSP's generic punch hole and the system bars stay the emulator's own, so the measured insets above are not reproduced.

Official Samsung emulator skins ↗

Android details & sources All insets, test fixture, captures

Featured on RTL ↗

Samsung lists this model on Remote Test Lab. Live reservation slots have not been checked.

Checked 2026-09-25 · Measured selection

System Bars · 3-button

Top: 30.12 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

Display Cutout Insets

Top: 0 dp
Bottom: 0 dp
Left: 0 dp
Right: 0 dp

Status Bars

Top: 30.12 dp
Bottom: 0 dp
Left: 0 dp
Right: 0 dp

Navigation Bars

Top: 0 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

System Gestures

Top: 30.12 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

Mandatory System Gestures

Top: 30.12 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

Tappable Element

Top: 30.12 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

Test fixture · WindowInsetsCompat

Exact px of this capture for JVM UI tests (Robolectric, Paparazzi, Roborazzi).

Measured On

One UI: 8.5
Android: 16

Galaxy Tab S11 · Main · Captured landscape.

Samsung RTL Korea/Gumi, SM-X730_KR1, build BP4A.251205.006.X730XXS7BZG3. Four separate display rotations in both navigation modes, 340 dpi and font scale 1. Probe labels this non-foldable display 'phone'; model and dimensions identify the tablet main screen. Gesture mode is confirmed by Settings and configNavBarInteractionMode=2; its inset-only heuristic reports threeButton because the taskbar retains a tappable bottom inset.

measuredInsetsProbe 1.6.0 on Samsung RTL Galaxy Tab S11 main (SM-X730), landscape-1, threeButton · checked 2026-09-29
officialSamsung Galaxy Tab S11 specifications · checked 2026-09-25

How these values are measured →