Optional Android startup diagnostic — v2.2-test412

This is a diagnostic prerelease, not a fix for the remaining Android startup crashes. The stable release remains v2.2.

The ordinary Java diagnostic screen opens before SDL or the native launcher is loaded. It can retrieve Android's available historical exit records for ReKHCoM's own processes, including a native crash trace when Android retained one. Records can be absent, expired or from an earlier build; the report says when data is unavailable. Local validation used an isolated API34 emulator and does not establish a fix or compatibility on a physical S22 Ultra, Moto Edge60 or Android16.

Optional test

1. Install ReKHCoM-v2.2-test412-startup-diagnostic.apk over the existing app. Do not uninstall or clear app data.
2. On the diagnostic screen, choose Open launcher once. If it closes, reopen ReKHCoM to return to the diagnostic screen.
3. Choose Refresh report, then Share report to save or share its ZIP. Copy summary is available if sharing is inconvenient. Review crash details before posting; attach only information you are comfortable making public to the relevant issue.
4. To return to normal play, install the stable v2.2 APK over this diagnostic variant. No uninstall or app-data reset is required.

The package ID, signing certificate and versionCode are the same as stable v2.2, allowing that return without a downgrade or deleting saves. The version name identifies this diagnostic variant. All eight native libraries and bundled assets are byte-identical to the published v2.2 APK; only the Java diagnostic entry screen, manifest and packaging differ. Network access is disabled in this variant; use the stable APK for normal network features.

Report scope and privacy

The collector reads this application's own Android exit records, not global device logs. It does not collect ROMs, saves, accounts or configuration files, request global diagnostic permissions, or upload anything automatically. Up to eight process records, a bounded summary and available raw crash traces are included. Native crash traces remain binary protobuf files, rather than being decoded as text. Android may retain historical entries from previous builds.

Each Share creates an immutable, uniquely named ZIP with a read-only grant. Only the selected recipient receives that grant. At most eight share snapshots are retained in the app cache; older links can expire. Refreshing the private report does not change a previously shared snapshot.

APK SHA256:
28847519552dd22f904eb2645e7388a101214d1096d19e6796d201dca1363bae

Implementation and validation: PR437. This test does not close #412 or #374 and does not modify the immutable stable v2.2 downloads.