Markus RambossekandClaude Opus 5
4de3064f71
TB330FU (A15/SDK35) and CPH2747 (A16/SDK36) both re-run on the AGP 9.2 / Gradle 9.6 / Kotlin 2.2.10 / JDK 25 / targetSdk 36 toolchain. Every probe on both devices keeps the verdict it had on the previous build (tablet vs build-4, phone vs build-3), so the upgrade changed no observed capability. Dual-path Shizuku executor now confirmed on the current toolchain on both: phone exec_path=UserService, tablet exec_path=newProcess fallback, both 7/7. Collection-loop gotchas recorded in build-status.md, found while driving the phone over USB: - icmp.ping6's verdict is topology-dependent, not build-dependent. A run with only 2 networks up reported UNSUPPORTED; with cellular present it is the expected "echo reply on cellular only". Always read it against link.snapshot's network_count from the same report. - The Shizuku permission dialog times out after 30 s and the probe logs "permission not granted" at ~30027 ms. Grant it before starting a run. - uiautomator dump can report a stale idle state right after a tap; the exported JSON's durationMs values are the ground truth for completion. CLAUDE.md's collection loop is updated — over USB the run is fully driveable via am start / input tap / run-as cat, no manual export needed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Echolot Capability Prober
A throwaway diagnostic app that runs the borderline no-root operations from the Echolot feasibility matrix on a real device and reports what actually works on that Android build. Its job is to turn "should work / needs verification" spec notes into observed facts before the production app hardens around them. Several probes naturally evolve into the tier-detection code the real app needs anyway.
Package / appId: app.echo_lot.prober (derived from the echo-lot.app domain; hyphen → underscore
because Android application IDs and Java packages cannot contain hyphens).
What it probes
| Probe | Question it answers | Expected result |
|---|---|---|
link.snapshot |
What does LinkProperties expose per active network? |
SUPPORTED |
icmp.ping4 / icmp.ping6 |
Does the unprivileged ICMP datagram socket work? | SUPPORTED (no root needed) |
sockopt.matrix |
Are IP_TTL, IP_TOS, IP_RECVERR, IP_MTU_DISCOVER accepted? | SUPPORTED / PARTIAL |
trace.errqueue_reachable |
Is errqueue traceroute reachable from the Os API? | likely PARTIAL → needs a small native shim |
multinetwork.request_and_bind |
Can we hold + bind Wi-Fi / cellular / ethernet concurrently? | SUPPORTED for links present now |
local.mdns_discover |
Does multicast reception / mDNS work with a MulticastLock? | SUPPORTED |
peer.ble_advertise |
Can this chipset advertise BLE (peer-mode channel)? | device-dependent |
shizuku.command_battery |
Does the Shizuku shell tier return neighbor table, RA routes, DHCP logs? | SUPPORTED if Shizuku running |
Each result carries a verdict (SUPPORTED / PARTIAL / UNSUPPORTED / INCONCLUSIVE / ERROR), a one-line summary, and raw evidence (sockopt return codes, addresses, timings, and the actual dump excerpts from the Shizuku commands — capturing the per-device format the real parsers must handle). Export the whole run as JSON with the Export button and share it anywhere.
Building
Needs Android Studio (Koala or newer) or a local Android SDK; this repo was scaffolded without network access to Google's Maven, so dependencies download on your first local build.
# Point the build at your SDK (or let Android Studio create local.properties):
echo "sdk.dir=/path/to/Android/sdk" > local.properties
./gradlew :app:assembleDebug
./gradlew :app:installDebug # with a device/emulator attached
The debug APK lands in app/build/outputs/apk/debug/.
Using the Shizuku tier
- Install Shizuku and start it via wireless ADB pairing (no root).
- Launch the prober, tap Run all probes. The Shizuku probe requests permission on first use.
- If Shizuku isn't running the probe reports INCONCLUSIVE (everything else still runs).
Notes / known gaps
- Errqueue traceroute (
MSG_ERRQUEUErecvmsg + cmsg parse) is expected to need a native C-over-JNI shim; this prober only confirms the sockopts + call-path availability. Wiring the shim is the next spike if the verdict is PARTIAL. - Multi-network probe can only bind transports physically present at run time. To exercise USB ethernet, attach an adapter first.
- BLE advertising support is genuinely chipset-dependent; a UNSUPPORTED here is a real finding.
License
GPL-3.0-or-later, like the rest of the Echolot code — see ../LICENSE. The specs in
../docs/ are CC-BY-4.0.
Relationship to the specs
Result IDs mirror the measurement-schema.md test-type registry where one exists, and the JSON
report shape is a stripped-down cousin of the full measurement document. The specs live in
../docs/ — feature-catalog-and-feasibility.md, measurement-schema.md,
probe-protocol.md.