Skip to content

Mobile benchmark 2.3 — one configuration per APK

Choose a tag to compare

@vinyteles vinyteles released this 05 Nov 18:04

One APK now runs exactly one model configuration on the same 120 frozen prompts. This replaces the five batch APKs with nine assignments for two-hour RTL reservations.

Download your assigned APK from the configuration table, install it, and tap Start / resume. Configurations 1 and 2 are the previously successful GPU paths; all five GPU configurations come before the four CPU configurations.

  • One required-model download and one expandable benchmark progress card per APK.
  • Android 12+ ARM64. Version 2.3 / version code 9. About 58 MB per APK, plus model weights and runtime caches.
  • All APKs update the same app and preserve models, answers and recovery data. Finish or stop before switching APKs.
  • Reports upload automatically: phone → upload relay → one public Hugging Face dataset per session. No participant HF token or account is required. Session index.
  • Legacy batch sessions retain their original labels; each new configuration gets its own upload session.
  • README times include 30 extra minutes per APK. Slow configurations may still require checkpoint/import/resume beyond one reservation. Gemma Q8 GPU remains conditional on available RAM.

All nine APKs passed signature, profile, label, architecture and fixture verification; Android regression and server suites passed. Validation details. These packaging and synthetic tests do not constitute new physical-phone performance measurements.

SHA256SUMS identifies the exact APK downloads.