Galaxy Tab A9 Plus Window Insets & Display Metrics

Metrics

Dimensions

Logical Size: 1280 × 800 dp
Resolution: 1920 × 1200 px
Aspect Ratio: 8:5
sw600dp: Yes
Physical Density: 226 ppi
Android Density: 240 dpi
Scale: 1.5×

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: 24 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.33 dp
Top Right: 13.33 dp
Bottom Right: 13.33 dp
Bottom Left: 13.33 dp

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

Compose Preview

Kotlin

// Galaxy Tab A9 Plus · 3-button · ROTATION_90 (captured 2026-09-25)
@Preview(device = "spec:width=1920px,height=1200px,dpi=240,cutout=none,navigation=buttons")
@Composable
fun TabA9PlusPreview() {
    // Your screen here
}

Kotlin

// Galaxy Tab A9 Plus · 3-button · ROTATION_90 (captured 2026-09-25)
@Preview(device = "spec:width=1920px,height=1200px,dpi=240,cutout=none,navigation=buttons")
@Composable
fun TabA9PlusPreview() {
    // 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: 1280 × 800 dp
Width / Height: Expanded (Large) / Medium

ROTATION_0Medium / Expanded
800 × 1280 dp
ROTATION_90Expanded (Large) / Medium
1280 × 800 dp
ROTATION_180Medium / Expanded
800 × 1280 dp
ROTATION_270Expanded (Large) / Medium
1280 × 800 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 A9 Plus · 3-button · ROTATION_90 (captured 2026-09-25)
adb shell wm size 1200x1920
adb shell wm density 240
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 A9 Plus · 3-button · ROTATION_90 (captured 2026-09-25)
adb shell wm size 1200x1920
adb shell wm density 240
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

RTL status unverified ↗

The full RTL device catalog could not be checked. This does not mean the model is unsupported.

Checked 2026-09-25 · Measured selection

System Bars · 3-button

Top: 24 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: 24 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: 24 dp
Bottom: 48 dp
Left: 0 dp
Right: 0 dp

Mandatory System Gestures

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

Tappable Element

Top: 24 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: 6.1
Android: 14

Galaxy Tab A9 Plus · Main · Captured landscape.

Samsung RTL Galaxy Tab A9+ 5G (SM-X216B), build UP1A.231005.007.X216BXXS3CXG1. Main display landscape, rotation 1, full-screen 1920×1200 px, 240 dpi and font scale 1.1. InsetsProbe's non-foldable Phone label is classified as the tablet main display from model and skin-matching dimensions. Gesture mode is confirmed by Settings/config_navBarInteractionMode=2 and left/right system gesture insets, although the inset-only heuristic reports threeButton because tappableElement includes the bottom system bar. Both modes report the same 48 dp bottom system-bar inset; keep these observed values without inferring a mode error from inset size. Font scale is non-default and preserved as captured.

measuredInsetsProbe 1.3.0 on Samsung RTL Galaxy Tab A9+ 5G main (SM-X216B), threeButton · checked 2026-09-25
officialSamsung Galaxy Tab A9+ 5G specifications · checked 2026-09-25

How these values are measured →