"upload failed: HTTP 400 client sent an HTTP request to an HTTPS server" is a TLS listener rejecting cleartext, and the cleartext was ours: REPORT_UPLOAD_URL was http://89.185.109.150:443/report, which used to be the adb-beacon receiver holding 0.0.0.0:443 in plaintext. Disabling that receiver and giving 443 to echolot-server left this posting plain HTTP at a TLS port. Blanked rather than repointed. The endpoint existed so an unattended run could be collected without adb, and autorun reports are now read straight off the device with `run-as cat` — so it was buying nothing and emitting an alarming error for a debugging convenience. Deliberately not aimed at /v1/runs either: that is the consent-gated upload, and a debugging shortcut must not be able to satisfy it by accident. The message says what happened instead of implying something broke. 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.