MobileCode v0.1.76 (official APK withdrawn)

MobileCode v0.1.76

Release type: pre-release patch.

Distribution notice (2026-08-07): the official mobilecode-v0.1.76.apk
asset was withdrawn after post-build review found that the old public build
workflow supplied runtime service credentials as Dart compile definitions.
The remaining explicitly named debug-signed APK is QA-only. No credential
value is recorded here; affected provider credentials should be rotated at
their providers. Use v0.1.77 or later for public distribution.

Scope

• Require a mobilecore.local v2 protocol handshake before MobileCore model control or inference.
• Fail closed with protocol_missing, protocol_invalid, protocol_unsupported, or service_mismatch instead of sending control requests to an incompatible loopback service.
• Confirm the requested model remains active before every local inference request.
• Give local inference at least three minutes and convert transport timeouts to a typed, redacted inference_timeout failure.
• On timeout or explicit Agent pause, call MobileCore's authenticated inference-cancel endpoint so native decoding does not continue after the client stops waiting.
• Use the last measured local decode rate to cap the next response budget on very slow or constrained runtimes.
• Surface MobileCore's runtime_busy result when another request owns the shared llama context.
• Preserve the v0.1.75 one-task cloud approval boundary: declining cloud inference stays local or fails closed, and does not grant Phone Use, login, payment, or ordering authority.
• Keep prompts, media, credentials, and generated content out of protocol and cancellation evidence.

Acceptance gates

• MobileCore 0.1.4-rc4 publishes the exact protocol name, major/minor, and supported client-major range from /health.
• Client tests prove incompatible protocols cannot reach model-control or chat endpoints.
• A clean Android pureRelease APK reports 0.1.76 (66) and pairs with MobileCore 0.1.4-rc4 on the emulator.
• The paired emulator completes one real local text request; its measured latency is emulator evidence only.
• Release assets identify signing status. Emulator pairing does not satisfy physical-device thermal, low-memory, background-recovery, controlled-account, or 30-task gates.

Published verification

• Android workflow 31128209900 completed source analysis, release signing, APK build, version consistency, artifact upload, and GitHub Release upload from merge commit 0860190.
• A fresh download of mobilecode-v0.1.76.apk is 33,053,383 bytes with SHA-256 52c53c26d51d6335588a443fd3f84f9a36ed9ac093de79a4238a23b2ff3ead31 and reports 0.1.76+66.
• The official APK verifies with APK Signature Scheme v2 and the MobileCode release certificate (CN=MobileCode, O=Harzva), not the Android Debug certificate.
• After removing the differently signed QA build, the official APK installed on an Android 16 ARM64 emulator, cold-launched through the microphone permission sheet, resumed MainActivity, and completed a real TuiMa Local request with the exact answer OK without a crash, ANR, OOM, or SIGABRT marker.
• The separate mobilecode-v0.1.76-debug-signed-qa.apk remains explicitly labeled QA evidence and has SHA-256 4c0592cf7e0c1fd45145e3eaced74f405c5fe6fa96f72e7dcbd83a9657a8da11.