bright-tools/androidphotobackup

Android application to perform over-the-air encrypted backups of photos to cloud services

androidphotobackup's Issues

Check internet connectivity status before starting main backup

If there's no internet connectivity, no point starting.

Could also check at other points within the process and abort if connection has gone away?

Update backup service to retrieve file list

Service should retrieve the list of files stored on the remote server in one go rather than individually checking files. This should sheep up the process as well as reducing API calls to the network server.

Wifi Sleep

Backing up over WiFi can be interrupted if Android sleeps the WiFi connection. Should establish a WiFi lock when using it as the transport.

Photos re-uploaded after time-zone or DST change

It was observed that after change to DST, photos were being re-uploaded due to the fact that the timestamp appeared to have changed by 1 hour.

e.g. originally uploaded file:

20150314_155612.jpg.1426348572.zip

file re-uploaded after DST change:

20150314_155612.jpg.1426344972.zip

The photos in question were stored on an external SD card.

File checking does not work with >1000 photos

The 'search' method if the DropBox API has a limitation which means that it will not return more than 1000 entries see here. This means that in the case that the target folder has more than 1000 files, the app will not receive all the filenames and hence will believe that various files need to be uploaded again, even though they already exist on DropBox, just weren't returned by the API call.

Tags are too long

As of a recent Android Studio update, an error is being flagged that the Log tags in various classes are too long.

handleFiles does not correctly handle directory creation failure

in PhotoBackupService::handleFiles(), the second call to mExistingFiles.containsKey() erroneously uses bucketName as the parameter rather than bucketTargetDir and also inverts the result. This means that in the case that there is a top-level directory specified in the configuration the condition will always evaluate to true (meaning that failure to create the directory will be missed). In the case that there is no top-level directory specified, successful creation of the directory will result in an erroneous error indicating that the directory could not be created.

Upgrade to Dropbox Api v2

Api v1, as used by the current app is being deprecated.

Behaviour when drop-box quota is exceeded is unknown

Behaviour / handling of drop-box refusing upload due to lack of quota has not been checked

Support API V23 permissions system

The permissions system was tweaked at API 23. Project should be updated to support this.

Backup service can be unexpectedly killed in low memory situation

When memory becomes low, Android may kill the backup service, resulting in the backup not completing. This seems pretty undesirable behaviour from the user's perspective.

Dropbox file limit

Fixing issue #10 means that the file limit in a single directory has increased from 1k to 25k for the DropBox back-end, however this still means that in the case that the file limit is reached, the sync behaviour will not work correctly (see issue #10).

Clear notification after selection

Selecting the notification and starting the log display activity should clear the notification

Switch to OneDrive SDK

Currently the project uses LiveSDK for Android which is now replaced by Onedrive SDK for Android