Android test for the launcher font crash found in the Moto report #374. This is a limited prerelease; stable Latest remains v2.2.
Five matching tombstones identify an unbuilt font atlas reaching ImGui::NewFrame. The test now builds and checks the atlas before drawing, keeps valid configured fonts, and retries once with ImGui's incorporated font if the configured fonts fail. If neither can be built, it reports a startup error and exits that graphical view cleanly. The particular failing font on the phone is not yet identified. The incorporated fallback can lose custom lettering and Japanese glyph coverage.
The same source also retains an existing valid game font if allocating its fitted replacement fails, and rejects failed FreeType/Web glyph uploads instead of treating them as ready. Original text resumes on the next frame in those upload paths; an already omitted glyph can be absent in the first failed frame. Those are separate sibling fixes, not evidence of the Moto's original cause.
The APK opens the Java entry first. Graphical launcher (optional) tests the repaired launcher; Play installed ROM can start the game directly using a validated existing ROM. Select ROM remains available. This variant does not force32 on a64-bit-only phone. It keeps the package ID, certificate and versionCode for installation over the current app without uninstalling or clearing saves. Networking is disabled in this temporary test; normal graphics acceleration selection and imported video quality are unchanged.
Local verification: the actual release-mode ImGui consumer reproduces the old invalid access and passes16 guarded cases across i686/x86_64, including a valid KHMenu control. Startup cleanup/error persistence passes44 controls; font replacement and glyph-upload guards pass12 and20 CPU controls. Both Android launcher ABIs and current EU/US/JP native components compiled. The exact APK signature, certificate, identity, native ABIs and225 asset/native member hashes were independently checked.
Android installation and runtime remain unverified locally: the emulator failed to boot before APK installation in three attempts. These were test-environment failures; no app failure was observed in those attempts. The result on the physical Moto and S22 still needs confirmation, and the issues remain open.
Source/tag:2dd3d01bafc071cf2959e27bc04ba762e24190ed. Native component provenance is recorded separately in BUILD-SOURCES.json. No ROM, save, private configuration, reporter trace or imported game media is included. Previous APKs/releases are preserved.