How laynz28/ytvancedx works
Project type & purpose
• This is a multi-module Android application plus a companion CLI tool, designed to produce and integrate “patches” into Google’s YouTube APK. The two primary modules are:
• vanced-patches-rvx: a Kotlin/Java CLI (command-line) application that reads patch definitions (fingerprints, bytecode/resource transforms, JSON metadata) and generates patch artifacts.
• vanced-integrations-rvx: an Android Gradle module (Java/Kotlin) that takes the original YouTube and YouTube Music APKs plus the generated patch artifacts, applies integrations (SponsorBlock, ReturnYouTubeDislike, swipe controls, UI tweaks, MicroG support, etc.), and builds final modded APKs.
• GitHub Actions drive CI (build/test) and releases.
High-level system components
• Developer environment (IDE/Terminal)
• GitHub repository (.github workflows, issue templates, funding)
• CI/CD: GitHub Actions → build CLI, build Android artifacts, publish to GitHub Releases
• vanced-patches-rvx (CLI)
• vanced-integrations-rvx (Android app + integrations)
• Upstream YouTube APKs (input binaries)
• External APIs/services:
• SponsorBlock API
• ReturnYouTubeDislike API
• MicroG authentication endpoints
• Output: patched YouTube APKs published as GitHub releases
Relationships & data flow
1. Developer commits code → pushes to GitHub
2. GitHub Actions workflow “android.yml” / “release.yml” triggers:
a. Build vanced-patches-rvx CLI (Gradle/Kotlin)
b. CLI reads patches.json + fingerprint/source directories → generates patch JARs/metadata
c. Build vanced-integrations-rvx (Android Gradle):
– Inputs: original YouTube APK (base.apk), generated patch JARs, resource overlays, integration code
– Applies all patch transforms via the CLI or ReVanced Core library
– Produces final modded APK(s)
d. Test artifacts on emulator/connected devices (optional)
e. Package and publish APK(s) + SHA sums to GitHub Releases
3. End users download microG APK + patched YouTube APK
Architectural patterns & design principles
• Modular separation:
• CLI module (patch generator) has no Android dependencies
• Android integration module depends on patch artifacts only as inputs
• Single pipeline for reproducible builds (infrastructure-as-code via GitHub Actions)
• Clear layering: patch definitions → patch generation → integration → final product
• Use of Gradle multi-project structure for isolated builds and dependency management