
AntiSplit M
AntiSplit M is an open-source Android utility designed to merge split APK formats (APKS, XAPK, APKM) into a single, regular APK file. It utilizes the merge utilities from REAndroid APKEditor to automate the consolidation process and resolve common installation issues.Key Specifications
| Category | Details |
|---|---|
| Minimum OS | Android 4.4+ (Version 2.x), Android 1.6+ (Version 1.x) |
| Core Engine | REAndroid APKEditor |
| Design Language | Material You (Version 2.x) |
| License | Open Source |
Technical Features & Advantages
- Manifest Optimization: Unlike similar tools (e.g., AntiSplit G2), this app automatically removes split-specific metadata from
AndroidManifest.xml. This prevents "App not installed" errors caused by residual split information in non-split APKs. - Merge Capabilities: Supports merging of APKS, XAPK, and APKM formats into a standalone APK.
- Integrated App Picker: Includes a menu to select and merge split APKs already installed on the device.
- Multiple File Support: Ability to select and process multiple files simultaneously.
Usage Methods
- System Share: Share a split APK file and select AntiSplit M from the share menu.
- File Association: Open the file directly and select AntiSplit M from the "Open with" options.
- Internal Picker: Launch the app and use the internal file picker.
- Note: If XAPK files are not selectable, rename the extension to .ZIP or extract and select the internal APKs.
Version History & Changelog
| Version | Updates |
|---|---|
| 2.x | Implementation of Material You design; support for Android 4.4+. |
| 1.x | Legacy support for Android 1.6+. |
| Latest Fixes | Restored multi-file selection; fixed processing interruptions during screen rotation with system theme active; resolved black screen issues during split selection dialog; fixed persistent error reporting on sequential multi-file tasks. |
| New Additions | Added Slovak translation; added theme description toast messages on long-press of the theme button. |
Technical Notes
- Signing: Merged APKs must be signed before installation (unless using Core ρá†ch). If further modifications are planned, signing should occur after the final edits.
- Verification: Some applications employ signature verification or integrity checks that may cause crashes if the merged APK signature does not match the original.