Android: MainActivity launcher, game thread and AndroidPlayer lifecycle #255

Current State

The desktop launcher is Main(string[]) + Host.CreateDefaultBuilder, blocking in window.Run() on the main thread; Escape quits; Application.Quit cancels a token. Android owns the UI thread and destroys the surface on pause.

Tasks

• MainActivity template in the brick's launcher directory, hosting a SurfaceView
• Dedicated game thread running the player loop; AndroidPlayer is instantiated by the launcher, not through GamePlayers.Find
• Pause/resume map to ticking pause and surface lost/restored
• Back button: configurable quit or input event; Application.Quit calls finish()
• Immersive fullscreen; OapRuntimeKey.Set for encrypted packages

Acceptance Criteria

• The lifecycle runbook (Android: milestone 1 device runbook #262) passes on the Galaxy S24 FE

Related

• Android plan task B2 · seniority Sr · local-only on feat/android-platform until .NET 11 GA and CI support
• Depends on: Android: CoreCLR net11.0-android prototype with Vulkan, Skia, packaged content and lifecycle #235, Graphics: surface loss and restore in the renderer #246, Android: org.mass4.turian.android brick and AndroidBuildPlatform #254
• Platform roadmap: Platform roadmap research: Steam Deck, Android, iOS, Web #100