Skip to content
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

Updating Sync Capabilities on Mobile #1677

Closed
5 of 6 tasks
MTRichards opened this issue May 17, 2016 · 11 comments
Closed
5 of 6 tasks

Updating Sync Capabilities on Mobile #1677

MTRichards opened this issue May 17, 2016 · 11 comments
Labels

Comments

@MTRichards
Copy link

MTRichards commented May 17, 2016

As an ownCloud user, I want to sync files to my mobile devices automatically so that I can have always the latest files available on my mobile platform

Acceptance Criteria:

  • Current “not granted offline” continues as currently implemented in iOS (tap on a file downloads, tap again downloads latest, changes are uploaded to server if found)
  • Current “not granted offline” in Android needs to be updated to meet user expectations:
  • tap on a file downloads
  • tap again downloads latest Automatic download for already downloaded file when file updated? #333
  • local changes are uploaded to server if found, without user interaction Grant that updates on files in the local ownCloud folder are automatically uploaded #1683
  • Current favorite functionality is renamed available offline
  • The available offline overlay icon is a download arrow with a bar underneath
  • Mobile sync error status is changed to red circle x from desktop
  • Successfully synced files are shown with a green check mark from desktop
  • Syncing files are shown with a circular blue arrow from desktop
  • File transfers in process are the same circular blue arrows from desktop

Android

iOS

@davivel
Copy link
Contributor

davivel commented May 23, 2016

Edited first comment to clarify pending changes

@jeremy447
Copy link

Great to see improvement on Sync Capabilities !
Can this #1437 be improve too please ?

Thanks !

@moscicki
Copy link

If a directory on mobile device is requested to be kept in sync with the server would that require regular polling and scanning of local mobile filesystem? What about the battery usage of mobile devices in this case? Is there an OS-provided mechanism to do it efficiently?

@helmo
Copy link

helmo commented May 25, 2016

@moscicki Linux has inotify for that, which android uses as FileObserver

@helmo helmo mentioned this issue May 25, 2016
@moscicki
Copy link

@helmo: what are the practical limits on Android for inotify? How many filesystem objects can one process watch?

@helmo
Copy link

helmo commented May 25, 2016

@moscicki I'm not sure

@davivel
Copy link
Contributor

davivel commented May 25, 2016

@moscicki , @helmo, these questions would be better placed in #1136 and / or #6.

And they are very good questions. Our current implementations of files being kept in sync extends FileObserver in the class FolderObserver. If I recall correctly, this is able to detect changes in all the subtree pending of the observed folder, so the total number of FileObserver shouldn't be a big deal, in theory.

There are other improvements we could address to control battery consumption (such as separating observation to detect a change from uploading that change) , and other problems / uncertainties that may affect the observers (they need to be kept watching indefinitely; the system might not like that). We'll talk about all this in more detail soon.

@davivel
Copy link
Contributor

davivel commented May 25, 2016

@moscicki , @Paviluf , @helmo , if you really want this get attention, take the chance of voting for it in owncloud/core#24684 (comment) . Let us see your hearts there!

@davivel
Copy link
Contributor

davivel commented Aug 3, 2016

Marked checkbox for #333, already merged, to be released soon: #1750

@davivel davivel added this to the backlog milestone Aug 4, 2016
@davivel davivel modified the milestones: 2.3.0, backlog Aug 12, 2016
@davivel
Copy link
Contributor

davivel commented Jan 16, 2017

Marked checkboxes for #1136 and owncloud/ios-legacy#463 , both of them released.

@davivel davivel modified the milestones: 2.4.0, 2.3.0 Mar 9, 2017
@davivel davivel modified the milestones: backlog, 2.4.0 Apr 11, 2017
@davivel
Copy link
Contributor

davivel commented Apr 11, 2017

Sorry, but we need to drop issues from milestone 2.4.0 to get it out next to OC 10 server.

This time we'll move topics to backlog instead of directly to next release, so that we can schedule 2.5.0 properly.

In this case, since there is a single independent issue pending to finish, I will label that and close this one.

@davivel davivel closed this as completed Apr 11, 2017
@davivel davivel removed this from the backlog milestone Apr 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

6 participants