X360 Mobile 0.6.2 Public Hotfix 1

X360 Mobile 0.6.2 Public Hotfix 1

This maintenance release hardens the Vulkan and Android runtime introduced in
0.6.2. It keeps the same public feature line and concentrates on conservative
driver compatibility, reusable caches, memory stability and correct platform
scheduling.

Vulkan compatibility and cache stability

• Added vulkan_extended_dynamic_state=auto|static|dynamic globally and per
  game. auto uses the faster Vulkan 1.3 path on capable Qualcomm and Mesa
  drivers, while proprietary Mali and Samsung/Xclipse drivers retain the
  established static path until their exact GPU and driver combination has
  been physically validated.
• Explicit dynamic mode still falls back safely when the complete required
  Vulkan functionality is unavailable. PanVK and other Mesa drivers are not
  confused with proprietary drivers from the same GPU vendor.
• Host pipeline descriptions are now isolated between static and dynamic
  modes. Vulkan binary caches are additionally separated by the driver's
  pipeline-cache identity and version, preventing incompatible data from being
  reused after a driver, mode or application update.
• Pipeline-cache writes are atomic and periodically checkpointed at safe
  points, so a crash is less likely to discard all compilation work from the
  current session. Guest shader translations remain shared where safe.
• When rebuilding is required, the launch flow now reports that cache
  verification or optimization is in progress rather than repeatedly reusing
  an incompatible cache.

Memory and Android runtime behavior

• Vulkan upload pages now remain reusable for the entire game session instead
  of being discarded after a fixed number of submissions. This avoids cyclic
  allocation and rebuilding during sustained gameplay.
• Upload memory is reduced only after a real Android memory-pressure signal,
  and only pages no longer used by the GPU are eligible. Normal backgrounding
  does not destroy the warm pool, while title shutdown still releases it.
• Android display hints now use the general interactive-content contract,
  apply once per Surface and are cleared when that Surface is released. Xbox
  guest timing remains at its established 60 Hz cadence.
• Android Performance Hint sessions now use android_adpf=auto|off|on.
  Existing boolean values migrate automatically. auto, the default, starts
  only with supported APIs, valid Android thread identities and a measurable
  command-processor workload; any platform error returns to normal scheduling
  for the remainder of the session without repeated retries.

Validation and conservative defaults

• Automated JVM, native ARM64, lint, Debug and Release packaging gates passed.
• The deterministic extended-state hardware probe passed on Ayn Odin3,
  Adreno 830 and the proprietary Qualcomm system driver in automatic dynamic
  mode, covering triangle, line and point topology plus culling and winding.
• Proprietary Mali and Xclipse remain on the static compatibility path by
  default. This release does not claim those devices fixed until their exact
  GPU and driver revisions complete physical game testing.
• No game-specific settings, imported Turnip package or user cache is deleted
  solely because another driver or rendering mode is selected.

Package

• Package: emu.x360mobile.com.
• Version: 0.6.2-public.hotfix.1 (versionCode 6029001).
• Public artifact: x360-mobile-0.6.2-public.hotfix.1.apk.
• Channel: Public maintenance release; it is not a GitHub prerelease.
• The APK uses the established X360 Mobile Release signing identity, stripped
  ARM64 native libraries and APK Signature Scheme v3 with a local v4 sidecar.

Online compatibility-report submission remains temporarily disabled while
that service is redesigned. X360 Mobile is experimental software, is not
affiliated with Microsoft or Xbox, does not support piracy and must be used
only with games and content the user legally owns.