This is my personal fork for testing purposes.
I'm not creating any official releases.
This repository mainly exists to communicate what is going on on my side.
It's basically a snapshot of my local repository.
I usually push branches when the work of a day is done.
But don't expect any stable code here. No guaranties for anything. Especially it is not meant to generate apps from it.
The layout of this repo should be seen combined with the NeoApplications repo.
Then it basically looks like this:
main ... rc ... experimental
I maintain a queue of commits in my local repository. Those are in flux, they are often rebased, sorted and squashed or even thrown away.
This work is (force) pushed from time to time to the experimental branch (in a somehow "final" state for a section of work).
Between main and experimental you find the rc branch.
More matured commits, that don't change often any more, are moved down to this branch.
It is meant as containing the candidates to be integrate into main soon.
This isn't pushed to main, because there is a chance that they still change as the result of testing.
If this branch is considered as stable, I usually simply fast forward the main branch to rc.
I intentionally left out the main branch in this repo, because it would never been guarantied to be up to date.
Instead use both the official and this repo together to get a complete picture from my POV.
--- the original README begins here ---
Neo Backup (formerly OAndBackupX) is a fork of the famous OAndBackup with the aim to bring OAndBackup to 202X and part of Neo Applications suite. For now the app is already fully rewritten, coming up would be making it robust and adding some lengthily planned features which could ease the backup/restore workflow with any device. Therefore all types of contribution are always welcome.
Now on functionality of our App:
- It requires root and allows you to backup individual apps and their data.
- Both backup and restore of individual programs one at a time and batch backup and restore of multiple programs are supported.
- Restoring system apps should be possible without requiring a reboot afterwards.
- Backups can be scheduled with no limit on the number of individual schedules and there is the possibility of creating custom lists from the list of installed apps.
And here's the project's FAQ.
A Stance: I stand with Ukraine, as I stood and still stand with Yemen, Syria, Afghanistan, Myanmar, Sudan, Columbia, Somalia, Hong Kong (not China) and everywhere human beings are being oppressed by bigger states and/or local ************s.
A combination with your favourite sync solution (e.g. Syncthing, Nextcloud...) keeping an encrypted copy of your apps and their data on your server or "stable" device could bring a lot of benefits and save you a lot of work while changing ROMs or just cleaning your mobile device.
You can join either our Telegram or Matrix groups to make suggestions, ask questions, receive news, or just chat.
Our Code of Conduct applies to the communication in the community same as for all contributors.
If enabled the data backup will be encrypted with AES256 based on a password you can set in the settings, which you'll have to use when you want to restore the data. This way you can store your backups more securely, worrying less about their readability.
Version 5.0.0 uses new encryption, new databases, fixes most of reported bugs in 4.0.0 and boost the performance to something near the 3.2.0's. With that said, it's incompatible with the older versions.
Version 4.0.0 marks a full overhaul of the app structure and thus breaks compatibility with previous versions.
Till the version 0.9.3 there's been no structural change in how the app handles backup/restore. So you could use that version to restore the old backups, then move to the newest version and renew your backups so that they'll stay compatible as long as the logic of the app doesn't radically change.
if you have some kotlin and android knowledge and like to contribute to the project, see our Taiga.io project here to see what is still needed to be done, where a help could be needed or if you'd like to fix one of the issues.
The communication and each contribution in the project community should follow our Code of Conduct.
OAndBackupX is built with gradle, for that you need the android sdk.
OAndBackupX is licensed under the GNU's Affero GPL v3.
App's icon is based on an Icon made by Catalin Fertu from www.flaticon.com
All new icons in 7.0.0 based on CC0 icons found on SVG Repo. A huge thanks for the project's maintainers.
Jens Stein for his unbelievably valuable work on OAndBackup.
Nils, Martin and DL for their active contribution to the project.
Oliver Pepperell for his contribution to the new anniversary design.
Open-Source libs: FastAdapter, RootBeer, NumberPicker, Apache Commons.
The Translations are now being hosted by Weblate.org.
Before that, translations were done analog/offline by those great people:
Kostas Giapis, Urnyx05, Atrate, Tuchit, Linsui, scrubjay55, Antyradek, Ninja1998, elea11.
I, myself acknowledge the role of the donations to motivate the work on FOSS projects, but in the state of how dynamic everything around my FOSS-contributions is, I would prefer to not take donations for now (the same answer as the last years). Nevertheless this project wouldn't have the accessibility it has without translations, which you the community drive and for which Weblate provides a platform. That's why I would suggest you to consider donating to Weblate.
Thanks to Tuta for the premium account.
Antonios Hazim & Harald Gutsche