You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug]: Orca Mobile is unusable in Samsung DeX (severe lag, stale rendering, non-responsive layout) #8592
Orca Mobile version: unknown (can be provided if needed)
Paired desktop/runtime version: v1.4.137
Details
Short summary
Orca Mobile becomes effectively unusable when launched in Samsung DeX desktop mode. The app has severe UI lag, parts of the interface fail to render or refresh, and the layout does not adapt to the desktop-sized/resizable DeX window.
How to reproduce
Install and pair Orca Mobile on a Samsung Android device.
Start Samsung DeX.
Launch Orca Mobile in a DeX window.
Open a project/worktree or terminal and try to navigate and interact with the UI.
Resize or maximize the app window.
Actual behavior
Interactions have major delays.
UI regions are blank, stale, or only partially redrawn.
The layout remains phone-oriented or otherwise fails to adapt to the wider DeX window.
Resizing/maximizing does not reliably trigger a correct re-layout/repaint.
Normal actions such as navigating worktrees, opening terminals, reading output, and typing are impractical or impossible.
Expected behavior
The UI should remain responsive in Samsung DeX.
Visible content should repaint correctly after navigation and window resizing.
The layout should adapt to the current DeX window dimensions and density.
Core mobile workflows should remain usable with keyboard and mouse in desktop mode.
Impact
Blocking for Samsung DeX usage: Orca launches, but it cannot be used productively in this mode.
Environment
Device: Samsung phone/tablet (exact model can be provided)
Orca Mobile detects size/configuration changes in DeX and recalculates its layout.
Maximizing, restoring, and resizing the window produces no blank or stale regions.
Scrolling, navigation, terminal rendering, and text input remain responsive.
The app is usable in both compact and maximized DeX window sizes.
Diagnostics that may help
I can provide the exact Samsung model, Android/One UI versions, Orca Mobile build number, screen recording, window resolution/scaling, and adb logcat/performance traces if the maintainers specify what is most useful.
Samsung DeX + Orca Mobile required. This host is macOS without a DeX-capable Android device/emulator pair for the described lag/stale rendering. Not labeling cannot_repro (env blocked).
Correction to my previous comment: the allowFontScaling explanation I gave is wrong, so please don't spend time on that path.
Measuring the screenshots properly gives a sharper picture. The three stat cards sit at a pitch of exactly 349px with 19px gaps, and statsRow declares gap: 10, so density is around 1.9. Each card is 54px tall, where its declared box (1px borders, 8px vertical padding, an 18pt value, a 2px margin, an 11pt label) should land near 110px at that density. The vertical padding does scale correctly at roughly 15px a side, which leaves about 20px for two text lines that need something like 70px.
Horizontal advance covers the other half. "Agents spawned" measures 127px wide, putting the rendered glyphs at about 11 x 1.9 px, so rasterization is scaling fine and only the line boxes are not.
That also rules out what I first suggested. heroTitle, statValue, statLabel and sectionHeading (app/index.tsx:1035, 1057, 1063, 1071) declare no lineHeight at all, RN grows the natural line height with fontScale, and there are no custom fonts since expo-font isn't a dependency. So fontScale on its own cannot clip these.
My CONTENT_MAX_WIDTH note was off too. That cap only applies when isWideLayout is true, and the same branch adds alignSelf: 'center' (app/index.tsx:719). The content is left-aligned with the stat row centred on x=768 of a 3840px window, so the cap isn't what leaves the right side empty.
I still have the device. If it helps I can shoot the same screen with DeX off at display size 3, and with DeX on at the default size, which should separate those two variables.
Additional reproduction: whole-app low-resolution rendering in Samsung DeX
I can reproduce this on an external monitor in Samsung DeX.
Scope: the entire app is affected—not only the terminal. Navigation, lists, buttons, body text, Chat UI, and terminal content all look blurred or low-resolution.
Relaunch test: fully quitting Orca Mobile after entering DeX and launching it again does not restore native-resolution rendering.
Expected: Orca should redraw at the current DeX window bounds and density, with crisp text and icons after launch, maximize/restore, and resize.
Actual: it looks as if a lower-resolution or phone-density surface is being scaled to the DeX window.
Environment currently confirmed from the host:
Desktop Orca version: 1.4.188
DeX path: Galaxy device → external monitor
The Galaxy model, Android / One UI version, Orca Mobile version, monitor / DeX resolution, connection type, and native DeX comparison capture are not available from the Mac host, so I am not guessing those values. I will add them when captured on the device.
Useful evidence for the follow-up will be:
a native DeX screenshot,
a close crop comparing Orca text/icons with Chrome or Samsung Settings,
a short recording covering launch, maximize/restore, and resize,
if needed, adb shell wm size and adb shell wm density.
The problem persists after a full app restart in DeX, so it is not limited to a stale surface immediately after switching display modes.
Closing as a duplicate of #18841, which has the root cause (display density mixing in DeX / freeform windows) and the in-flight fix in #20198. The whole-app low-resolution observation from this thread is carried over there.
Activity
nwparker commentedon Jul 27, 2026
Screenshot / recording needed
Samsung DeX: severe lag, stale rendering, non-responsive layout. Please attach:
This is hard to triage without visual evidence of the layout failure mode.
nwparker commentedon Jul 27, 2026
Repro attempt blocked (environment)
Samsung DeX + Orca Mobile required. This host is macOS without a DeX-capable Android device/emulator pair for the described lag/stale rendering. Not labeling
cannot_repro(env blocked).Chang-Jin-Lee commentedon Aug 22, 2026
Correction to my previous comment: the
allowFontScalingexplanation I gave is wrong, so please don't spend time on that path.Measuring the screenshots properly gives a sharper picture. The three stat cards sit at a pitch of exactly 349px with 19px gaps, and
statsRowdeclaresgap: 10, so density is around 1.9. Each card is 54px tall, where its declared box (1px borders, 8px vertical padding, an 18pt value, a 2px margin, an 11pt label) should land near 110px at that density. The vertical padding does scale correctly at roughly 15px a side, which leaves about 20px for two text lines that need something like 70px.Horizontal advance covers the other half. "Agents spawned" measures 127px wide, putting the rendered glyphs at about 11 x 1.9 px, so rasterization is scaling fine and only the line boxes are not.
That also rules out what I first suggested.
heroTitle,statValue,statLabelandsectionHeading(app/index.tsx:1035, 1057, 1063, 1071) declare nolineHeightat all, RN grows the natural line height with fontScale, and there are no custom fonts since expo-font isn't a dependency. So fontScale on its own cannot clip these.My
CONTENT_MAX_WIDTHnote was off too. That cap only applies whenisWideLayoutis true, and the same branch addsalignSelf: 'center'(app/index.tsx:719). The content is left-aligned with the stat row centred on x=768 of a 3840px window, so the cap isn't what leaves the right side empty.I still have the device. If it helps I can shoot the same screen with DeX off at display size 3, and with DeX on at the default size, which should separate those two variables.
lvuping commentedon Aug 24, 2026
Additional reproduction: whole-app low-resolution rendering in Samsung DeX
I can reproduce this on an external monitor in Samsung DeX.
Environment currently confirmed from the host:
The Galaxy model, Android / One UI version, Orca Mobile version, monitor / DeX resolution, connection type, and native DeX comparison capture are not available from the Mac host, so I am not guessing those values. I will add them when captured on the device.
Useful evidence for the follow-up will be:
adb shell wm sizeandadb shell wm density.The problem persists after a full app restart in DeX, so it is not limited to a stale surface immediately after switching display modes.
AmoabaKelvin commentedon Oct 28, 2026
Closing as a duplicate of #18841, which has the root cause (display density mixing in DeX / freeform windows) and the in-flight fix in #20198. The whole-app low-resolution observation from this thread is carried over there.