[peiikai]

Follow-up to #614, from play-testing the Android build in the emulator. Desktop builds are unchanged; everything here is Android only except one rename.

• No on-screen keyboard when the menu opens. The menu turns text input on while it is open, so its fields take typing. On Android that also brings up the on-screen keyboard, which covers half the screen and takes the hardware keyboard's keys. There, text input is now on only while something takes text: a focused text field in the menu, or the game's name entry.
• No crash going into the game. That check asked ImGui for its IO between the start screen and the game, when there is no ImGui context, and aborted. It now asks only while there is one.
• No crash at a start sent to the background. A surface lost while the swapchain was being made stopped the app with a FATAL. The surface is now made again there too, as during play, or the swapchain waits for the window to come back.
• Debug switches on Android. The activity copies any LARECOMP_* extra of its launch into the environment, e.g. adb shell am start -n com.lasrecomp.android/com.lasrecomp.LASRecompActivity --es LARECOMP_LOG_SKIPS 1.
• docs/android.md covers the switches, and why the emulator can't draw the game world: its Vulkan goes through gfxstream and MoltenVK, whose shader translation to Metal fails ("call to 'fmin' is ambiguous"). A phone's GPU compiles the shaders directly.

Tested on the arm64 Android 15 emulator:

• keyboard play works, and F1 opens the menu without the on-screen keyboard
• Play goes into the game with no crash (Marin and Tarin's house, 60 fps, saves work)

The Mac build compiles.

🤖 Generated with Claude Code