Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Phase 9 exit: the doctor's report over the corpus, and a bundle, HUD and trace from a device

Open
  • Is something wrong?
#296 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
android, kotlin
Domain
mobile, observability, performance

Research direction

Start with PRD.md Part 4 (Phase 9 exit criterion) and the corpus register that check runs over the deliberately broken manifests. The committed doctor report needs every pathology, its severity grade, and the doctor's output, including the entries it correctly reported nothing for. The device parts need a real device session, a bundle exported and checked against every redaction rule, a HUD capture, and a devicelab Perfetto trace. Done means the report, bundle, HUD evidence and trace are committed and ./gradlew assemble check passes.

Written by the indexing model from the issue text.

Description

need-device ready-for-agent

Parent

#284

What to build

PRD.md Part 4's Phase 9 exit criterion, and the parts of this phase that only a device can answer.

The criterion itself — "the doctor correctly identifies each pathology in a curated set of deliberately broken manifests" — is met under check by the corpus register, with no device involved. What this ticket adds is the committed report: the doctor run over the whole curated set, every pathology beside what the doctor said about it, so that the claim is readable rather than merely green. devicelab measures and does not assert, and the same applies here: the verdict goes into a committed report.

On the device:

  • A bundle from a real session, exported off the device and read back, from a session that really loaded over a real network with a real device's codecs and protection — the one place the redaction rules meet data that was never synthetic.
  • The HUD on the demo, shown while playing, with its numbers moving.
  • A Perfetto capture showing SuperPlayer's phases beside MediaCodec's.

Say what the emulator could not show, and name the device that did.

Acceptance criteria

  • A report over the curated corpus is committed: every pathology, every severity grade, and what the doctor reported for it, including the entries it correctly reported nothing for
  • A bundle captured from a real device is committed with the run, and inspected against every redaction rule
  • The HUD is shown on a device, with evidence
  • A Perfetto capture from devicelab shows SuperPlayer's phases, committed with the run
  • The report names the device, and says which criteria the emulator could not answer
  • ./gradlew assemble check passes

Blocked by

  • #290
  • #292
  • #293
  • #294
Dominant language
Kotlin
Stars
1
Forks
0
Avg merge
1h 20m
Merged PRs (30d)
172

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ramesh130/superplayer

All issues in ramesh130/superplayer

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.