Native Android app that assists MLBB Draft Mode players. Sprint 1A turns the previously working capture path into a real image-bearing foundation: frames carry pixels, geometry is tested, preprocessing validates before it renders, and a Vision Lab lets you place manual slot annotations and save calibration profiles.
Maintainer-reported device smoke: the Sprint 0 capture path and the Sprint 1A Vision Lab interaction behavior were used on a physical Android device and confirmed working. Device details, the exact build and test dates were not supplied, and the MediaProjection lifecycle matrix remains NOT RUN. See docs/TESTING_PHYSICAL_DEVICE.md and docs/VISION_TESTING.md.
- MediaProjection consent flow (
ActivityResultContracts.CreateScreenCaptureIntent) - Foreground service (
mediaProjectiontype) with persistent notification + Stop action - Frame acquisition at 2 FPS default, configurable 334–2000 ms (hard cap 3 FPS)
- Live frame preview in the debug screen, frame count / resolution / latency / timestamp
- Pause / resume, rotation & resize handling, clean resource teardown on stop/revoke
- Non-null frame contract:
FramePayload,OriginalFrame,ProcessedFrame,SlotImage - Rotation-aware geometry with round-trip tests (
FrameTransform) - Validated preprocessing with honest failure codes (
PreprocessingMath,PixelArrayFramePreprocessor,AndroidFramePreprocessor) - Manual slot annotations with stable ids, bounds/duplicate/overlap validation and a strict JSON codec
- Versioned calibration profiles: 1 % aspect-ratio tolerance, exact orientation match, unsupported-schema refusal, delete-as-escape-hatch
- Vision Lab tab: frame preview, freeze/resume, explicit processing, interactive annotation canvas, text slot editor, profile controls
- Hero recognition v0 (Sprint 1B, PR #3): hero catalog sync from public static data, explicit Identify action for the selected slot, ranked candidates with similarity scores, manual confirm/correct — accuracy on real game screens is not measured yet
- Capture notification with Stop and Pause (Sprint 1C): pausing keeps the latest valid frame, blocks new frames replacing it, keeps MediaProjection running, and the same Resume action recovers from pause or from a pinned frame; the notification reflects LIVE / PAUSED / FROZEN and never shows both actions
- App-only capture guidance (Sprint 1C): prefer Single app / app window → Mobile Legends (Android 14+ chooser); the captured window's visibility drives publication — MLBB hidden ⇒ the last valid game frame is kept, never DraftLens/shade/system UI; full-display capture remains the documented fallback (it may include the shade/system UI)
- Circular floating freeze button (Sprint 1C): one 52dp circular
TYPE_APPLICATION_OVERLAYbutton shown only while capture runs — tap toggles LIVE (green) / orange (paused or frozen), long-press-and-drag moves it, it snaps to a screen edge, position persists normalized in DataStore; notifications/in-app Freeze/Resume keep working without it; the overlay permission is requested only when you enable the button
Recommendation engine, counter/synergy/role scoring — and no recommendation overlays
(Sprint 1C ships exactly one capture-freeze overlay button, and nothing else).
ML hero recognition is Sprint 1B (PR #3). API sync, player profiling, builds.
The Vision Lab says "Detection: not implemented" — manual slots are calibration data,
never detections. See tasks/plan.md and docs/ARCHITECTURE.md.
Requires JDK 17 and Android SDK platform 35, build-tools 35.
./gradlew test # JVM unit tests
./gradlew lint # Android lint
./gradlew assembleDebug # produces app/build/outputs/apk/debug/*.apkGitHub Actions (.github/workflows/build.yml) runs exactly those steps on push/PR and uploads
the APK artifact. This authoring environment is aarch64 and the SDK's aapt2/build-tools are
x86_64-only, so nothing that touches resources can be assembled locally — the CI run is the
build of record. See docs/VISION_TESTING.md for exactly what ran.
- Install the APK from the
draftlens-debugCI artifact on a physical device (the emulator validates compilation, not MediaProjection reliability). - Open the app; the Debug Capture tab is first.
- Tap Start Capture → grant the system screen-capture consent dialog. When Android asks what to capture, prefer Single app / app window → Mobile Legends: Bang Bang (Android 14+); if that option is missing, choose Entire screen / full device display (it can capture the shade and system UI).
- Open Mobile Legends and wait for the draft screen you want to annotate.
- With MLBB on screen, tap the circular Floating freeze button (enable it on the capture screen first) to freeze the frame — or, if you never granted the overlay permission, pull down the notification shade and tap Pause (notifications must be enabled).
- Switch back to DraftLens → Vision Lab. Capture kept running; the Vision Lab shows the pinned MLBB frame instead of the DraftLens screen.
- Draw a slot rectangle, then run Identify hero on the frozen frame. Candidates are similarity scores, not probabilities — confirm or correct manually (the manual search is available in every recognition state).
- Tap Resume live capture in the notification, or Resume in the Vision Lab, to show live frames again. No second capture session is created.
- Press Process Frame to run the preprocessing engine on the selected frame.
- Save the annotations as a calibration profile; apply it later on a matching frame.
- Stop Capture, or the notification's Stop, or revoke consent in Settings to exercise teardown.
docs/ARCHITECTURE.md— module layout, state machine, data flow, Vision boundarydocs/VISION_ARCHITECTURE.md— Vision packages, ownership, processing rulesdocs/VISION_FRAME_CONTRACT.md— payload contract, ownership, original/processed/slot framesdocs/VISION_COORDINATES.md— normalized coordinates, rotation tables, crop semanticsdocs/VISION_LAB.md— user-facing controls, freeze behavior, slot editing, profile rulesdocs/VISION_TESTING.md— test inventory, CI gates, what was and was not rundocs/SCREEN_CAPTURE.md— MediaProjection lifecycle, Android 14+ rules, limitsdocs/DATA_SOURCES.md— Rone Arena vs MLBBDex audit (verified live 2026-11-04)docs/decisions/ADR-001-android-native.md— why native, single-module, and version pinsdocs/IMPLEMENTATION_REPORT.md— executed verification, limitations, next tasks