mrambossekandClaude Opus 5 416b783647 app: lay the server facts out in real columns
The block was rendered as one padded string, which only lines up in a
monospaced font — and the monospace never took, so the values sat at
ragged offsets and the point of the list was lost. Padding text to fake a
table makes the layout depend on a typeface decision made elsewhere.

It is a label column of fixed width and a value column that takes the
rest, so the addresses align whatever the font does and a long value wraps
inside its own column instead of under the labels. The capability list
goes back to plain comma-separated text: hand-wrapping it at three per
line was working around the same missing alignment.

Placement too. The facts now sit under the "Check server" button that
fetches them, rather than among the input fields, and the sentence
explaining the endpoint sits directly under the URL field it describes —
it had ended up orphaned between the two, reading as a comment on nothing.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-02 08:24:00 +02:00

echolot — measure, don't guess

Echolot

Free software for detecting and debugging local network issues from an Android phone — built for people who actually know what a neighbor table is.

Most "wifi analyzer" apps show you signal bars. Echolot aims at the layer where home and office networks actually break: duplicate DHCP servers, broken IPv6 RAs, MTU black holes, NAT64 weirdness, multicast that dies at the AP, DNS that answers differently than it should. It records what it observed, separates observation from interpretation, and exports the whole run so you can argue with it later.

Status: pre-release. The capability prober runs on real hardware; the production app and the probe server are not built yet.

Repository layout

docs/              design docs — the contract for everything below
echolot-prober/    capability prober: validates the no-root feasibility matrix on real devices

The Go probe server and the production app land here as siblings.

Design docs

The three specs are draft-complete and reviewed; treat them as the contract.

Doc What it defines
docs/feature-catalog-and-feasibility.md Full feature list + the no-root feasibility matrix
docs/measurement-schema.md Archived/exportable measurement JSON (observation vs finding, two-clock rule, anonymization)
docs/probe-protocol.md Client↔server wire protocol (pinned TLS control plane, binary UDP data plane, STUN, canary DNS)
docs/build-status.md Running log of decisions and next steps

Privilege tiers

Every result records which tier produced it:

  • app — no root, no special setup. The bulk of the functionality.
  • shizuku — ADB-shell privileges via wireless pairing, no root. Shipped in v1.
  • root — future optional module.

Licensing

Part License Why
All code (app, prober, server) GPL-3.0-or-later The value here is the platform-API research; copyleft keeps derivative apps free
docs/ (the specs) CC-BY-4.0 A wire protocol and a measurement format should be implementable by anyone, without license anxiety

Full texts: LICENSE (GPLv3) and docs/LICENSE (CC BY 4.0). Sources carry SPDX-License-Identifier headers.

If you want to build a compatible server or client, the protocol and schema docs are deliberately permissive — go ahead.

Building

See echolot-prober/README.md. Short version, from echolot-prober/:

echo "sdk.dir=/path/to/Android/sdk" > local.properties
./gradlew :app:assembleDebug
S
Description
No description provided
Readme GPL-3.0
1.3 MiB
2026-08-02 14:58:41 +02:00
Languages
Kotlin 61.6%
Go 36.2%
HTML 1%
Shell 0.5%
Python 0.4%
Other 0.2%