Andotp: Streamline backup and restore

[hydrian]

Enhancement

Right now if you want to restore a file it has to be in the Download directory unless you enable 'Ask for Filename' is enable for both restores and backups.

1. I think 'Ask for Filename' should always be enabled for restore. This is also to confirm that the application is importing the expected file. _Implemented in 34ac28189c3dd2ed287e43c19a3707cc1929f303._
2. Backups should have time stamped filename enabled by default. This help with versioning and if we enable more frequent updates like in #46, it is easier to overwrite a backup that could be needed if the filename is static. If a user needs a constant filename, they can disable time stamps explicitly. _Implemented in 78f9463f93176a23a1b41b52101d76b38c822231._
3. One touch backups: Once the backup methodology is configured, backups should be one click and done. This is where backups should have 'Ask for Filename' disabled. As you can see, 1 and 3 conflict with each other. _Already works if "Ask for filename" is disabled and a backup password is set in the settings._
4. When a backup file is generated, it should show a transient overlay dialog with the file name and path.
   This is for confirmation that backup completed and info on what the file name is.

[flocke]

Thanks for your suggestions, I agree with all of them and will implement them when I find more time to spend on andOTP. Refactoring the whole backup code has been on my todo list for a while now, just not very high up :wink:

[skorokithakis]

Not only one-touch, but andOTP should automatically write a backup whenever any of the services is changed. For example, if I add a new service, or rename a service, or something like that, it should write a new, automatic backup with the date in the filename. That way we can't forget to back up, and syncing will ensure we always have the latest data backed up.