XayahSuSuSu/Android-DataBackup: root first, consented port, and a tag that stopped in 2025

Root is the first requirement, with three implementations named

The first feature bullet is also the precondition. Root is required, and the readme names the three implementations it works with: Magisk, KernelSU and APatch, each linked to its own project. That list is the compatibility statement in practice, because an unrooted device has no way in, and a rooted device running something outside those three is outside what is claimed here. The description sets the floor at Android 7.0 and newer, and the code is Kotlin. Multi-user support appears as its own bullet right after the root requirement, which matters on a phone split into several user profiles. Cloud backup is named as a feature too, though the readme says nothing about which services it targets.

The application is a port of someone else's script, made with consent

The overview credits its origin in plain terms. DataBackup is based on speed-backup, the `backup_script` repository, by an author identified as CoolApk with a handle that ends in TEL, and the readme adds that the application was born with the consent of the author, alongside a claim that the original script has been acclaimed since it was written. That lineage is the detail worth pausing on. This is not a rewrite of a dead project but a port of a live script, licensed GPL-3.0, with the permission of the person who owns it. The script repository remains the place where the shell approach is documented.

source/ and source-next/ sit side by side in the tree

The repository layout carries two source trees rather than one, `source/` and `source-next/`, which is the kind of arrangement that says a rewrite is in flight or that variants are maintained in parallel. Alongside them sit `build/`, `dex/`, `docs/` and `fastlane/`, the last being the release tooling used to push to app stores. A `.gitmodules` file is present, so at least one dependency arrives as a submodule rather than as a vendored directory, and `.github/` holds the workflow configuration. Nothing in the readme explains which source tree produces the published APK, so that mapping has to come from the repository itself or from the changelog.

The last release tag is over a year older than the last commit

The release record and the commit record disagree. The newest tags are 2.0.12 from 2025-09-20, 2.0.11 from 2025-08-21 and 2.0.10 from 2025-08-10, three patch releases inside six weeks of each other last year. The repository was pushed to on 2026-10-25, which means work has continued for roughly a year without a new version number. The project is not archived, so this is active work that has not been cut, and `CHANGELOG.md` at the root is where the difference between the two records would show up. Anyone installing from the releases page is therefore installing code from 2025, not code from the current default branch.

Two F-Droid channels and a raw APK share one package name

Distribution is simple and the naming tells you where it lands. The readme links an IzzyOnDroid APK and an F-Droid package, both under `com.xayah.databackup.foss`, and then offers the APK from the releases page as the alternative. The `.foss` suffix marks the build intended for free software repositories, which is where a project that lists GPL-3.0 as its licence belongs. The Telegram links split into a channel and a chat, `dabackupchannel` and `databackupchat`, so announcements and discussion are separated. Translation runs through a Weblate instance, and the homepage is a GitHub Pages site at DataBackupOfficial.github.io rather than a custom domain.

The feature list deliberately ends in an ellipsis

Read the bullet list as written and it stops mid-thought. Root support, multi-user support, cloud, 100% data integrity, fast, easy, and then a bullet whose entire content is an ellipsis. Two of those are unfalsifiable claims rather than descriptions, which tells you the list is a summary written for the repository front page rather than a specification. The consequence for a reader is that the real inventory sits elsewhere: the usage section is one line, telling you to see the documentation site. Nothing in the readme explains what is backed up, where cloud backups go, or what the integrity claim is measured against.

Support is three payment links and no policy page

Asking for help is presented as sponsorship rather than as an issue tracker. The readme asks readers to sponsor the project and links PayPal and Afdian, with a Buy Me a Coffee link present but commented out, so that route is currently inactive. Combined with the two Telegram links and the Weblate instance, the picture is a single maintainer running a volunteer project with community help concentrated in translation and discussion. There is no bug tracker link in the readme, though the GitHub repository has 192 open issues. The top-level entries hold no code of conduct, no security policy and no contributing guide, only `.github/`, `.gitignore`, `.gitmodules`, the changelog, the licence, the readme, and the source and build directories.

Editorial conclusion

This app fits an Android user on 7.0 or newer who already has root, and who can read the documentation site before trusting a backup. It does not fit anyone without root, on a device whose root implementation is not one of the three named, or looking for a release cadence, because the newest tag predates a year of commits. Before trusting it with a device, confirm the root method, read the docs site rather than the readme, and check what CHANGELOG.md says has changed since 2.0.12.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Project website
3. README
4. Releases
5. XayahSuSuSu/Android-DataBackup on GitHub