Repository navigation
MVP: six collectors, local config, own disk queue, wake_policy (#2) - #7
Conversation
New module app/ (the spike stays in spike/): - collectors: battery, power, boot, network, device, thermal; each on/off with its own interval - config: built-in defaults plus a local JSON file (file, share sheet, QR text, adb broadcast); shows each value's source - own file queue (from the spike): one OTLP/HTTP protobuf body per file, size cap and max age - one foreground service; wake_policy never | when_charging | always, default when_charging - no app.installation.id; OpenTelemetry pinned to 1.66.0 with enforcedPlatform - unit tests, CI (build + unit tests + lint), release workflow for a signed APK Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… race, disk-full crash - Wi-Fi: Android hides networkId without location permission, so 'connected' comes from the network transports and the supplicant state - sender: do not follow redirects; drop a file only on 400/413/415/422, keep it and stop on any other answer - service: no alarm or wake lock from a tick that runs while the service stops - boot record and config save: catch IO errors instead of crashing - tools/vm_report.py: gaps split by charger/battery, screen share, process starts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… body) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Test on a OnePlus Nord CE 2 Lite (Android 12), 2026-11-13A second real phone, next to the planned HyperOS test.
Start. The config import by adb broadcast worked. The broadcast could not start the service from the background ( 1 h on the charger, screen off (13:05:43 → 14:06:29 UTC): So the check "no gap over 120 s for 1 h on the charger" passes on this phone. OnePlus delays the exact alarm. The app calls Network cut. The phone was unplugged, and adb (so the path to the receiver) was gone for about 20 min. The readings waited in the queue and arrived in order when the path came back. No process restart. On battery with
Bug: battery current. |
…rt tests Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
No gap over 120 s on the charger with when_charging; the app holds no wake lock between readings. Lists the phone settings changed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The MVP of #2: a new
app/module (the spike stays inspike/).What it does
/data), thermal. Each on/off with its own interval (default 60 s). Names, types and units: README table.wake_policynever|when_charging(default) |always. Waking: an exact alarm (setExactAndAllowWhileIdle) and a short wake lock per reading; without the exact-alarm permission, a partial wake lock between readings. Not waking: a plain timer, no alarm, no wake lock.adb shell am broadcast(protected by theDUMPpermission). The screen shows each value with its source.app.installation.id; no SSID/BSSID. OpenTelemetry held at 1.66.0 withenforcedPlatform. The app builds the OTLP bodies itself (SDK data classes + the OTLP marshalers), without opentelemetry-android: its disk buffer is not used, and this keeps each point at the time of its reading and stops a collector that is turned off at once.lintVitalRelease. Release workflow: signed APK on av*tag (docs/release.md); the signing secrets are set.Tests
docs/mvp-tests.md(emulator, Android 15, 2026-11-13): a query for each collector, collector off,wake_policyon battery and on the charger (dumpsys power,dumpsys alarm), the 30 min network cut with an app restart in it (largest gap 60 s, no reading lost), config import by file, share sheet and adb. 37 unit tests.Waiting for the follow-up (a job on 2026-11-14): the 1 h charger test and the 24 h test on a Redmi Note 12S on HyperOS 2 (the install needs a tap at the phone), then the merge, the
v0.1.0release, and the results here.Phone settings changed
None yet. The follow-up will set, for this app only and with the owner's OK: Autostart on, Battery saver "No restrictions", Alarms & reminders allowed. It lists them here so they can be undone.
Reviews
A correctness review found 4 bugs plus one more in the second pass; all fixed (Wi-Fi "connected" without location permission, queue loss on 3xx/401/404/415, an alarm or wake lock after stop, a crash loop on a full disk). A privacy review found nothing.
🤖 Generated with Claude Code