Repository navigation
[Bug]: Device panel Portrait and Landscape actions are reversed on Android tablet emulators #20177
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included steps to reproduce and environment details.
Area
Device panel orientation controls (apps/server, Android).
Steps to reproduce
- Connect T3 Code to a Linux environment with an Android tablet emulator whose natural orientation is landscape.
- Open
medium_tabletin the Device panel. - Open the rotation menu and select Portrait.
- Select Landscape.
Expected behavior
Portrait produces a tall display. Landscape produces a wide display.
Actual behavior
The actions are reversed:
- Portrait produces landscape, 2560 × 1600.
- Landscape produces portrait, 1600 × 2560.
The app supports both orientations and renders correctly after rotation.
Impact
Minor bug. The requested orientation can be reached by selecting the opposite menu item.
Version or commit
T3 Code server: v0.1.0.
Environment
- Server host: Linux Mint
- Client: T3 Code on macOS
- Emulator:
medium_tablet, Android 15 / API 35, x86_64 - Natural display orientation: landscape
Investigation
DeviceActions.ts uses fixed accelerometer values for the requested orientations:
portrait: 0:9.81:0
landscape_left: 9.81:0:0
On this emulator, those values produce landscape and portrait respectively. Android reports its natural landscape rotation as ROTATION_0 and portrait as ROTATION_90.
This suggests the handler assumes a portrait-native device and needs to account for the emulator's natural orientation.
Screenshot
The rotation menu used to reproduce the issue:
Workaround
Select the opposite orientation from the menu.
Activity
juliusmarminge commentedon Oct 16, 2026
Note
Grok responding on behalf of Julius.
Confirmed on main. In
apps/server/src/device/DeviceActions.ts,setOrientationmaps each orientation to a fixed value and never checks the device's natural orientation:ANDROID_GRAVITY: portrait0:9.81:0, landscape_left9.81:0:0).cmd window user-rotation lockwith fixed rotations (ANDROID_ROTATION: portrait0, landscape_left1).Both tables assume the device is portrait-native. On a device whose natural orientation is landscape, like
medium_tablet, rotation0is landscape, so Portrait and Landscape come out swapped, which matches your report. Neither path looks up the natural orientation anywhere.Until this is fixed, picking the opposite menu item works.