Skip to content

Validate EdgeGenBench on an Android 16 KB runtime - #51

Merged
triasha72 merged 2 commits into
mainfrom
evidence/android-16kb-runtime
Aug 27, 2026
Merged

Validate EdgeGenBench on an Android 16 KB runtime#51
triasha72 merged 2 commits into
mainfrom
evidence/android-16kb-runtime

Conversation

@triasha72

Copy link
Copy Markdown
Owner

Summary

  • run EdgeGenBench v0.1.7 through the Kotlin/JNI/reference path on an Android 15 API 35 ARM64 emulator reporting PAGE_SIZE=16384
  • retain ten cold-launch evidence runs with logcat, launch, memory, thermal, CSV, and screenshot artifacts
  • verify every machine-readable result reports runtime_page_size_bytes=16384, zero preprocessing/output drift, the reference backend, and disabled fallback
  • fix the repeated-profile collector to match the stable v0.1.7 backend log and wait for benchmark_json before retaining each run
  • promote the portfolio lane from runtime-pending to validated_16kb_emulator_runtime

Verification

  • zipalign -c -P 16 -v 4 app-debug.apk: passed
  • arm64-v8a and x86_64 ELF PT_LOAD alignment: 0x4000
  • Android runtime: adb shell getconf PAGE_SIZE16384
  • ten of ten retained logcat files contain runtime_page_size_bytes=16384
  • five portfolio acceptance tests passed
  • repository-wide Ruff format and lint passed
  • Android lint, JVM tests, native builds, and APK assembly passed

Claim boundary

This closes the Android 16 KB runtime-compatibility gap for the reference APK/JNI path. It is emulator compatibility evidence, not physical-device performance, Qualcomm QNN APK placement, thermal, energy, or power evidence. The supported-Snapdragon APK run and calibrated power measurement remain hardware-only gaps.

@triasha72
triasha72 merged commit 245ac2f into main Aug 27, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant