-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change allowBackup to true #1222
Comments
I don't really understand your concerns about encryption, but I believe you have good reasons. So my use case here is I need to move the app with its data to another device. I would be more than happy if there is any alternative method to do so (I don't have root). |
It might make sense for aTox to have an export format that other clients (and aTox) can implement for imports. Moving between clients and devices is an important use case, and it would be nice to keep chat history and client settings around. There are some common settings (the ones in Tox core options) and client-specific ones. Probably the first step towards that is formulating a data schema for the export. |
Yeah, I'd happily enable only-local backup if that was possible, but
There was some work towards exporting (but not importing) aTox-bits in a JSON format in #1076, but there's no documented schema or anything yet, and it also includes a bunch of aTox internals that probably should be dealt with differently longer-term. If we can come up with a nice schema for these things I'd happily adopt it as an export/import format. |
Is it possible to make a function to archive/restore the app data as a tar/zip? |
Currently it is set to
android:allowBackup=false
which makes backup impossible without root. Backup and restore could be done without root if change it totrue
.The text was updated successfully, but these errors were encountered: