# Universal ReVanced Manager for Android app patching > Universal ReVanced Manager combines ReVanced and Morphe patch bundles, APK management, signing, batch jobs, and automatic repatching in one Android application. It fits experienced Android users who need more control than a basic patcher provides. **Jman-Github/Universal-ReVanced-Manager** — 💊 Android manager for ReVanced and Morphe with third-party patch bundles, batch and automatic repatching, advanced installers, APK tools, and deep customization. - Repository: https://github.com/Jman-Github/Universal-ReVanced-Manager - Stars: 1,369 · Forks: 50 - Language: Kotlin - License: GPL-3.0 - Published: 2026-10-16 · Updated: 2026-10-16 · Language: en - Canonical page: https://hysenlabs.com/projects/jman-github-universal-revanced-manager ## What Universal ReVanced Manager Changes Universal ReVanced Manager, also called URV, addresses app patching on Android for users who need more than selecting a preset and producing one modified APK. It supports both ReVanced `.rvp` bundles and Morphe `.mpp` bundles in one manager. It can begin with installed apps, local files, manager-downloaded APKs, downloader plugins, supported helper apps, and split archives such as `.apkm`, `.apks`, and `.xapk`. The project serves two overlapping groups. ReVanced users can manage patch selections, bundle versions, patch options, and saved configurations. Morphe users can apply the corresponding patch ecosystem without switching to a separate manager. Android users who repeatedly update or customize an app are also relevant because URV adds saved apps, patch profiles, batch queues, and optional automatic repatching. This is not a generic APK editor. Its scope centers on patch bundles and the surrounding installation and file-management workflow. A user who only needs to inspect an APK, change basic metadata, or install an existing build may find the application unnecessarily demanding. The feature set assumes that the user understands APK inputs and output signing rather than treating every file operation as a one-click conversion. ## Patch Bundles, Profiles, and Patching Queues A patch bundle contains patches that URV applies to a selected APK. Users can add compatible local or remote bundles, including repository and release-based sources. A built-in bundle catalog supports searching, supported-app inspection, and direct import. Remote bundles can be checked and downloaded, with controls for stable or pre-release channels, per-bundle updates, and forced redownloads. Patch selection can be changed globally or for each bundle. URV documents undo and redo, filters for new patches, option-value inspection, and access to recommended or other supported bundle versions. Before a patching operation, the application presents a confirmation view containing selected bundles, patches, options, and relevant configuration. Profiles retain selected patches, option values, target version, APK or split source, installer choice, signature workflow, and auto-install behavior. A batch job can contain multiple apps with separate configuration, queue reordering, cancellation, progress, results, and install-all behavior. Automatic repatching applies only to apps that a user opts into and is configurable by interval, charging requirement, notifications, and optional Shizuku or Shevery installation. Retaining the original APK or split archive allows a later patch operation to reuse that source, which is important for recurring updates. ## Split APKs, Signing, and Installation Paths URV treats split applications as a first-class source rather than treating an `.xapk` or `.apks` file as a single ordinary APK. The documented preparation flow can select modules and remove unused language resources, density resources, and native libraries through cleanup filters. The patcher diagnostics include split and native-library state, which gives users a way to inspect why a particular operation failed. Signing is also part of the patching profile. The application can use its manager keystore, import a compatible keystore, or skip signing where the workflow supports it. It also has a signature metadata option that can clone metadata from the original signed input into the final patched APK. That choice can be stored for saved apps, profiles, batch jobs, and automatic repatching. Installation supports rooted and non-rooted workflows. Automatic installation can optionally use Shizuku or Shevery, while diagnostics can report app, runtime, device, selected patch, split, and failure information. ## APK Utilities and Saved App Management Beyond patching, the project includes standalone APK utilities and controls around files that patching generates. The README lists backups, storage controls, signature and keystore tools, detailed logs, and live resource graphs for memory, CPU, and storage I/O during a patch operation. Logs can be exported with failure and runtime information, which is more useful than a single success or error message when a bundle fails against a particular APK. Downloader plugins add another input path. The documentation says compatible plugins can be installed, updated, configured, trusted or revoked, and removed from the manager. This creates an extensible boundary, but it also means that the effective source and update path depend on a plugin being compatible with the installed URV environment. ## Runtimes and a More Demanding Workflow URV bundles current ReVanced and Morphe patching runtimes and also documents support for a ReVanced v21 runtime plugin. The plugin can come from a local APK or GitHub source, with settings for trust, update channel, installed version, and stored plugin files. This separation allows the manager to select a compatible runtime, but it adds a versioning and trust decision to an already broad workflow. The feature set addresses several recurring problems: acquiring an APK, selecting patches, handling split packages, applying signing rules, installing the result, and repeating the process after bundle changes. The cost of that coverage is a larger configuration surface. A user may need to understand bundle metadata, target app versions, split modules, native libraries, keystores, installer privileges, and runtime compatibility before a patch is dependable. URV also documents deep customization. The v1.9.0 release dated 2026-10-04 is the latest listed stable release, with v1.9.0-dev.2 and v1.9.0-dev.1 appearing as development releases. ## Installation Evidence and Maintenance Boundaries The repository contains Gradle wrapper files, including `gradlew` and `gradlew.bat`, along with Kotlin-oriented project directories and build files. The documented starting point is the project repository and its release information. The repository is not archived. Its last push was on 2026-10-11, which is recent, and the release list includes v1.9.0 from 2026-10-04. These facts indicate recent repository activity, but they do not establish compatibility with every Android device or patch bundle. The license is GPL-3.0. That matters when distributing modified versions or incorporating the project into another product, although determining specific obligations requires reviewing the license text and applicable law. Contributors should inspect `LICENSE` and the repository's contribution documentation rather than relying on the feature summary. ## Conclusion Universal ReVanced Manager is appropriate for Android users who already work with APKs and need explicit control over patch bundles, split archives, signing, diagnostics, and repeated repatching. It is a poor fit for someone who expects a documented one-command installation or an automatic way to bypass app restrictions. Before adoption, verify the available release for the Android device, confirm that the intended patches support the app version and patching mode, and review the repository's GPL-3.0 license implications. ## FAQ ### Does Universal ReVanced Manager support both ReVanced and Morphe? Yes. The README says URV supports ReVanced `.rvp` and Morphe `.mpp` patch bundles in the same manager, with built-in runtimes for both ecosystems. ### Can Universal ReVanced Manager patch split APK archives? The README lists `.apkm`, `.apks`, `.xapk`, and compatible split archives as supported sources. Users can select modules and apply cleanup filters for languages, densities, and native libraries. ### Does Universal ReVanced Manager support automatic repatching? Yes, for opted-in saved apps. The README describes configurable intervals, charging requirements, notifications, source retention, and optional Shizuku or Shevery installation. ## Sources - [Issues](https://github.com/Jman-Github/Universal-ReVanced-Manager/issues) - [Jman-Github/Universal-ReVanced-Manager on GitHub](https://github.com/Jman-Github/Universal-ReVanced-Manager) - [License: GPL-3.0](https://github.com/Jman-Github/Universal-ReVanced-Manager/blob/main/LICENSE) - [README](https://github.com/Jman-Github/Universal-ReVanced-Manager/blob/main/README.md) - [Releases](https://github.com/Jman-Github/Universal-ReVanced-Manager/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/jman-github-universal-revanced-manager