From 357ba28b6a0d23389acc6876649e07a7844aa371 Mon Sep 17 00:00:00 2001 From: The412Banner Date: Sat, 19 Sep 2026 16:52:15 -0400 Subject: [PATCH] Let the session activity resize MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit It was declared non-resizable. On a foldable that means the system keeps a fixed-shape window across the fold and stretches it onto the other panel — the app never receives a size change, so the compositor's re-fit, the swapchain rebind and the letterboxing all had nothing to react to. Resizable, the window follows the panel and the picture keeps its shape with bars. --- app/src/main/AndroidManifest.xml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/app/src/main/AndroidManifest.xml b/app/src/main/AndroidManifest.xml index 1965f2cff..d0ab605e5 100644 --- a/app/src/main/AndroidManifest.xml +++ b/app/src/main/AndroidManifest.xml @@ -40,13 +40,18 @@ A session keeps a Surface, a compositor thread and a proot tree alive; a configuration change must not tear that down and rebuild it, so the activity handles them itself. Landscape only: gamescope is told one output size when it starts. + + Resizable, deliberately: a foldable opening or closing changes the window, and the + compositor re-fits the picture with bars. Declared non-resizable, the system keeps a + fixed-shape window instead and STRETCHES it onto the other panel — the app never sees a + size change, so nothing it does can help. -->