Skip to content

Rewrite the README as a short fork summary with screenshots - #64

Merged
trexx merged 10 commits into
masterfrom
docs/readme-rewrite
Sep 16, 2026
Merged

trexx merged 10 commits into
masterfrom
docs/readme-rewrite

Conversation

@trexx

@trexx trexx commented Sep 16, 2026

Copy link
Copy Markdown
Owner

What

Rewrites README.md from 462 lines of per-feature rationale to a 193-line summary of what the fork is, what it changes (a line or two per item), what it removed, and how to build and test it. Adds six screenshots under docs/screenshots/.

Why

The long-form README was hard to scan and had fallen behind — nothing on the GIP driver rework or Xbox-pad headphone audio, the rebuilt browse screen, the keystroke soft keyboard, the worst-frame/sparkline overlay or the build label, and OkHttp/BouncyCastle versions were stale. The rationale lives in the PR descriptions and commit messages.

Screenshots

Taken on the Shield TV (com.limelight.unofficial 12.1) streaming Steam from Sunshine, over adb: browse, settings, in-stream menu, special-keys and controllers submenus, and the performance overlay cropped to its own region. WebP q90, 232 KB total (776 KB as PNG/JPEG); GitHub renders WebP in READMEs.

Credits

Every upstream author, xow, summershrimp and backported-PR link from the old file is kept in the Credits section. Upstream's Play/Amazon/F-Droid links are dropped — they never pointed at this fork's builds — in favour of one link to moonlight-stream.org.

Latency / performance impact

None. Documentation and images only.

🤖 Generated with Claude Code

trexx and others added 10 commits September 16, 2026 18:23
The README had grown to 462 lines of per-feature rationale, and had still
fallen behind: nothing on the GIP driver rework or headphone audio through
Xbox pads, the rebuilt browse screen, the keystroke soft keyboard, or the
worst-frame and sparkline overlay, and the OkHttp and BouncyCastle versions
were stale. The detail lives in the PR descriptions and commit messages;
the README now says what the fork is, what it changes, in a line or two per
item, and what was removed, then how to build and test it. The credits block
keeps every upstream, xow and backported-PR link the old file had; the
upstream store links go, since they never pointed at this fork's builds.

Six screenshots under docs/screenshots/, taken on the Shield streaming
Steam from Sunshine: browse, settings, the in-stream menu and two of its
submenus, and the overlay cropped to its own region. WebP at q90, 232 KB
in total against 776 KB as PNG/JPEG, and GitHub renders WebP in a README.

Latency and performance impact: none. Documentation and images only; no
code, resources or build configuration change.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Focus on the rail so Add PC and Settings show their labels, and with Steam
still running on the host the tile carries its running badge, which the
earlier shot did not show.

Latency and performance impact: none, image only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Anything with Android 11 and an ARM CPU can run the build; naming the
Shield and the Homatics read as a device whitelist. The Amlogic decoder
line stays, since that is a decoder family the code checks by name.

Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Thirteen items in one paragraph read as a wall; one per line scans.

Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
HARDWARE_TESTING.md has recorded it as verified on hardware since
2026-08-24; the README caveat was stale on arrival.

Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The branch that moves the toolchain from 25 to 26 is in flight; the
README is being rewritten in parallel, so it states the version it will
be true for when both land rather than one that would be stale on merge.

Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Latency and performance impact: none, documentation only.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@trexx
trexx force-pushed the docs/readme-rewrite branch from 288a3fa to 4fd842e Compare September 16, 2026 16:24
@trexx
trexx marked this pull request as ready for review September 16, 2026 21:14
@trexx
trexx merged commit 72d170f into master Sep 16, 2026
2 checks passed
@trexx
trexx deleted the docs/readme-rewrite branch September 16, 2026 21:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant