Why the mandatory Google Sign in?
To setup your Swift Backup account
To encrypt some sensitive backup files (eg. Calls/SMS) by default without any user input
To sync backup files in your Google Drive (If enabled)
To sync your Swift Backup app settings in cloud
To verify purchases and activate premium
To reduce/diminish financial damages caused by pirated/modded apk users (Modded apk's cannot use our paid servers)
Note that all backup files, whether local backups or synced backups, are tied to a specific Google account. You cannot use the backup files of one Google Account with another.
What personal details do you receive and store when I sign in with Google in your app?
Your email address, name and a link to your profile picture all of which is used to be shown in the app.
Can I use one Google account to sign in the app and upload backups to Google Drive of another account?
You can only use Google Drive of the Google account with which you signed in the app. You simply need to sign in the app with the Google account with which you want to sync your backups to Drive.
Will my premium plan work with the other Google account?
Yes. You can use any Google account to sign in the app and still use premium features if the purchasing Google account is signed in Play Store.
Which app parts should I backup / restore?
This is completely up to the user. Most apps work fine when restored with App + Split APKs and Data. It can take some trial and error in deciding which parts need to be selected during backup/restore for apps you specifically use. Each app part is briefly explained below.
App + Split APKs: Many apps (Eg. Airbnb, Facebook and many more) are now downloaded from Play Store as multiple apks and not just one single apk. There is a main apk and then smaller split apks. Both the main apk and split apks are required for the app to work. These apks can be found in /data/app/ folder.
Data: The usual app data that stores your app settings, login info, etc. Data for an app can be found in /data/data/ folder.
Ext. Data (External Data) : Mostly media files stored in /Android/data/ folders in Internal Storage or removable sdcard. Some apps/games may still store 'Data' here. Note that Swift Backup currently DOES NOT backup external data on removable sdcard.
Expansion: Some games (or even apps) have large .obb files due to a huge number of resources. These .obb files are called expansions.
Is Android 10/Q supported?
Yes. Most of the things should work the same way as they did on Android 9/P except for WiFi networks restoring due to restricted WiFi APIs.
WiFi networks restoring on Android 10
APIs for adding WiFi networks are no longer available for non-platform apps targeting Android 10. This means that batch restoring (Restore all) button will not be shown in Swift Backup. Instead, the user should click on the backed up WiFi item icon, and click 'Restore'. This will copy the password to clipboard and bring up the new WiFi selection popup introduced in Android 10. Select the WiFi network in this dialog and paste the password to connect with the network.
Is removable sdcard supported?
Using removable Sdcard as backup location is an experimental feature in Swift Backup (Go to Settings > Swift Labs). As such, you use this feature at your own risk. We recommend you use your sdcard as Adoptable Storage if possible.
Keep in mind the limitations of using an sdcard:
Uninstalling Swift Backup will WIPE the backup folder on the sdcard
Backup/Restore will be considerably slow in contrast with your device's internal storage depending on your sdcard read/write speed
1. Will my backup files on Sdcard be deleted if I install a new custom ROM?
No, the only way backup files on sdcard will be deleted is if you uninstall Swift Backup.
2. Why don't you use the DocumentsProvider API to access sdcard?
File reading from USB and sdcards require us to use a whole different framework (aka Documents API) which has been poorly implemented by Google. For eg. Reading apk file properties directly is impossible with that framework without copying the file to our app folder. There are other issues as well. We don't want to use root for such similar simple actions which are faster and easier with the conventional and proven Files API.
3. Can I use a custom location for /SwiftBackup folder on the Sdcard?
No. Any other location apart from /Android/data/... folder will need to be accessed using the DocumentsProvider API which we can't use due to the above mentioned reasons.
What about USB-OTG support?
USB drives are not supported for the same reasons as Sdcard. And unlike the sdcard which are partially supported as Android System allows apps to store files in /Android/data/ folder on the sdcard using normal Files API, we cannot do the same with USB drives.
In case you need to wipe your device completely, you can use a file manager app to copy /SwiftBackup folder from your device storage to a USB drive or Sdcard.
I can't see restored messages in Google Messages app!!?
This is a Google Messages issue. For some reason it doesn't read the updated messages in android's SMS database. To solve this: Clear cache/data of Google Messages or Reinstall Google Messages.