irisandClaude Fable 5.1 8750ff90cb Build the phone's APK as a signed release, and say so in the render report ...

The phone has been running the debug build: build-apk.sh assembled it, and
nothing in the app or its report said which build a frame time came from.
A debuggable build runs Compose at a fraction of release speed, so the
tuning so far was measured against the wrong number. On the emulator, the
same fixture and gestures: measure 1.4ms mean / 14.7ms worst on debug,
0.8ms / 6.6ms on release.

build-apk.sh now assembles the release variant, signed with a key it
generates once under ~/.config/ai-app (beside the pinned CA, outside any
checkout). The report's header names the build. The one native library is
declared kept-with-symbols so packaging stops warning about an NDK the
build does not need.

Also: ui-sandbox.sh keep now keeps the config too. The server appends
spawned sessions and enrolled tokens to it, so regenerating it left the
transcripts on disk and the registry empty.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

2026-09-02 05:21:30 -04:00

..

src/main

Build the phone's APK as a signed release, and say so in the render report

2026-09-02 05:21:30 -04:00

build.gradle.kts

Build the phone's APK as a signed release, and say so in the render report

2026-09-02 05:21:30 -04:00