3 ms·

This is not the same functionality that Nextcloud provides though. This is one time upload of manually selected files, not ongoing passive sync of an entire dir

by Macha 1y ago

This is not the same functionality that Nextcloud provides though. This is one time upload of manually selected files, not ongoing passive sync of an entire directory tree.

tadfisher 1y ago
Ongoing sync is still possible through ACTION_OPEN_DOCUMENT_TREE [0], and using ContentResolver.takePersistableUriPermission [1] to maintain long-lived access to that directory. Enumerating files is slow but that is not a major concern when the use-case is a background sync, and you can drop down to ContentResolver APIs to reduce the number of IPC calls when enumerating. [0]: https://developer.android.com/training/data-storage/shared/documents-files#grant-access-directory https://developer.android.com/training/data-storage/shared/d... [1]: https://developer.android.com/reference/android/content/ContentResolver#takePersistableUriPermission(android.net.Uri,%20int) https://developer.android.com/reference/android/content/Cont...
- apitman 1y ago
  > Enumerating files is slow but that is not a major concern when the use-case is a background sync Slow means it's probably burning a lot of CPU, and that is a problem for background tasks, especially on mobile.
  - tadfisher 1y ago
    No, the call is going through ContentProvider, which happens over Binder IPC, which entails context switching and other I/O overhead. Compared to local file operations (java.io and friends) this is massive; compared to anything else your device does, it's not a big deal at all, and it's not CPU-bound.
izacus 1y ago
The same picker has the functionality of allowing access to a full directory.