TeamAmaze / TeamAmaze/AmazeFileManager
Back up and restore app data
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 6.4k
- Forks
- 1.7k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 1
Description
One of the features of ES File Explorer that tends to be overlooked is its ability to back up not only APK files from /data/app/package.name, but also the ability to back up and restore app data from /data/data/package.name. Amaze and ES already backs up APK files to user storage under the app's friendly name. ES File Explorer backs up the app data by copying the directory in data/data/package.name, compressing it into .zip format, and writing the zip file to user storage under the app's friendly name. This means you have two files: the app itself and its data. In a directory listing, it would look something like this.
SDMaid.apk
SDMaid.zip
Once the data is backed up, it can then be restored using the file manager. In ES File Explorer, the user has the option of installing the app without the data, installing the app with the data, or installing the data alone. My feature requests are below.
Feature 1: the ability to batch install apps. I don't know if Amaze has this feature, but in ES File Explorer you can install multiple apps just by selecting the desired apps, then tapping the menu option to install. You can also set the installation mode to be silent, meaning no dialog prompts for any apps installed using the file manager.
Feature 2: the ability to back up application data and restore that data upon command. This feature will only function with a rooted device. This is fairly self-explanatory, but the file manager should be able to pull application data, store it on user storage, restore the pulled data upon command, and have the app with its restored data work correctly afterward, as if the data were never touched.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the existing APK backup and installation flows, then determine how rooted storage access and app-data restoration are handled; done would require a defined scope and working support for the requested batch installation and app-data backup/restore behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100