An entire module was missing from the APK. The app died with ClassNotFoundException for app.echo_lot.protocol.EnrollmentLink while the build was green, the module's jar was correct, and :app:dependencies listed it on debugRuntimeClasspath — its code simply never reached AGP's intermediates. The cause was a poisoned Gradle build cache entry, which is why nothing obvious fixed it: clean, rm -rf */build and --rerun-tasks all leave the build cache alone. Only --no-build-cache did. Every app build made in this session shipped without core-protocol, so enrolment, sign-in and upload would all have crashed identically; several hours of "the tap does nothing" were this, misread as a UI problem. CLAUDE.md now carries the symptom, the fix, and the verification — grepping the dex for a string literal only that module defines, because grepping for a class *name* proves nothing: callers carry the name as a reference whether or not the class is packaged. That false check is what let me believe an earlier rebuild had fixed it. Also: the enrolment dialog compared the stored endpoint against the link's public URL, so re-enrolling with the same server announced itself as a move to a different one. Those are deliberately different strings now that discovery exists; the comparison uses the public name on both sides. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Echolot app
The production Android client (spec). Native Kotlin + Jetpack Compose. Multi-module; built bottom-up from a verifiable protocol spine.
Modules
| Module | Type | Status |
|---|---|---|
core-protocol |
pure Kotlin/JVM | done — client half of probe-protocol.md, verified live against the server |
core-measurement |
pure Kotlin/JVM | planned — measurement-schema.md types |
core-probe |
Android lib | planned — app-tier probes, ported from echolot-prober |
core-shizuku |
Android lib | planned — dual-path executor (UserService + newProcess fallback) |
app |
Android app | planned — Compose UI |
core-protocol is deliberately Android-free so it builds and unit-tests on any JDK (no Android
SDK) and can run integration tests against a live server.
core-protocol
Implements the control plane (SPKI-pinned enrollment/profile/sessions via HttpsURLConnection —
Android-API-1 compatible, hostname verification off because trust is the pin), the HKDF-SHA256
session-key schedule, and the binary ELT1 UDP data plane (HMAC gate, ECHO + observation block,
MTU probe) — byte-compatible with the Go server.
./gradlew :core-protocol:test # unit tests (crypto vectors, wire round-trip)
scripts/test-fmr.sh # live end-to-end test against the deployed server
test-fmr.sh mints an enrollment token over SSH, enrolls via the public control plane, computes
the SPKI pin from the served cert, and runs LiveServerTest — proving the client speaks the wire
protocol to the real server (enroll → profile → session → echo+observation → MTU → observations).
The live test self-skips when ECHOLOT_LIVE_* env vars are absent, so unit runs and CI stay green
offline.