-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Drop instant uploads in favor of automatic (non-instant) camera uploads #2028
Comments
cc @michaelstingl , @jesmrec , @davigonz |
Renaming this feature sounds reasonable. I think it's easier to communicate with a broad audience, if we coordinate with the release of the iOS app, where it's also not really "instant". /cc @pmaier1 |
Ensuring 100% of photos are uploaded eventually is more important to me than 75% of photos being uploaded instantly and 25% being missed. The Dropbox camera auto upload feature worked perfectly before I switched to Owncloud, is it possible for you to do things the way they do? I have disabled the power saving for Nextcloud client in Android and the auto upload seems relatively reliable for now, but I'd rather have the 100% reliability that Dropbox offered. |
I think I would stick with the name but define it - keep in mind that the folder is called Instand Upload as well. And very much agree that 100% is most important. |
@janipewter Totally agree Coming back to the matter of choosing a name for this feature, from an user point of view, I would prefer something like "Camera uploads" , which is self explanatory and avoids entering in a discussion about wether uploads should be performed in 5 minutes, 10 or an hour.
@hodyroff If we keep the "instant uploads" name, where could we explain that uploads are not instant? In the app with a warning? In the app manual? IMHO, use the "Instant uploads" name could create misunderstandings, since users are going to expect that uploads start "instantly", i.e: as soon as the pictures or videos are taken. And about "Auto uploads" , it is too generic. Maybe some users that have taken part in other issues related to instant uploads want to give their opinion about the feature naming. What do you think? @janipewter , @jensd0e , @fishstew , @M0ses , @kigero CC / @michaelstingl @jesmrec @nasli |
@jesmrec Yes, I see your point and they should be named differently. The feature to upload a picture directly from the camera could be implemented by using a new button with the text "Upload from camera" that appears when pressing the floating action button. See this mockup I included here: #2027 (comment) On the other hand, the "Camera uploads" feature would continue appearing in the Settings app menu, like the previous "Instant uploads" |
I'd vote for "Camera uploads". Instant uploads Instant picture uploads Instant video uploads I'd just remove everything with "Instant/Instantly": Camera uploads Picture uploads Video uploads "Upload" just explains, what I'd want to happen: get my photos/videos uploaded to my ownCloud. :-) |
I will rather call it auto uploads, take into account that could be possible to upload pictures not just for the camera (at least for iOS) |
Since testing this feature has a certain complexity due to the great bunch of involved devices, we are going to include it in a beta version previous to the final 2.5.1 release. Follow up: #2063 CC / @michaelstingl @jesmrec |
Auto upload is working great for me. Thanks guys for all of your hard work. It would be nice if "upload failed" notifications could be removed once the files have uploaded successfully though. I take quite a lot of photos in places with bad/no network coverage so uploads fail quite often on the first attempt, but then successfully complete later on, and the "upload failed" notifications stays in the notification tray until I clear it manually. |
BUG (1) [FIXED]Steps to reproduce1.- Enable camera uploads for pictures/videos Current behaviourThe ownCloud app crashes Expected behaviourThe ownCloud app performs the upload properly Device & versionNexus 6P with Android 8 |
BUG (2) [FIXED]Steps to reproduce1.- Enable camera uploads for pictures/videos, setting as source folder one with a lot of files. Current behaviourThe screen keeps white during several seconds Expected behaviourThe files view appears faster Device & versionNexus 6P with Android 8 |
BUG (3) [FIXED]Steps to reproduce1.- Enable auto uploads for pictures/videos Current behaviourThe ownCloud app crashes Expected behaviourThe ownCloud app retries the upload properly Device & versionNexus 6P with Android 8 |
IMPROVEMENT (4)Steps to reproduce1.- Turn off wifi internet connection and turn on cellular one Current behaviourUpload is not retried Expected behaviourThe upload is retried, even with cellular internet connection Device & versionNexus 6P with Android 8 |
Ups, wrong button 😌 |
Hi all @M0ses, @houseofbugs, @bkraul, @smmilani and @jensd0e, @janipewter , @fishstew , @kigero, @d98ama , @erwinfolmer. We have just released the 2.5.1 beta version, which includes the new Camera uploads feature, that is replacing the previous Instant Uploads feature. To use it, you just have to select a camera folder and the pictures and videos contained there will be automatically uploaded to the folder you select in a period of 15 minutes at most, focusing on reliability instead of immediacy and avoiding battery draining caused by excessive checking of the folder. You can find this beta on Google Play Store and it will be on F-Droid too, in the next days. Try it out and give us your feedback by commenting in this issue, thank you so much! |
I have tested this using my Samsung Galaxy S8+ SM-G955U and the default camera app & sd card DCIM location ( /storage/B6BF-89F1/DCIM/Camera ). The upload is working about once every 5min or sometimes sooner. Thank you for getting this going and I will start following this post and testing on my S8+ :) |
Great news, thank you so much for your feedback, if you have any suggestion or question do not hesitate to ask us |
@davigonz - So one issue that I see and this has happened 2 times already since yesterdays post. I will run with just the Beta version installed for now and see if the issue clears up.... Owncloud Beta - V 2.5.1-beta. 1 |
Thank you for your feedback @sesipod but I think that the problem you describe is not related to camera uploads, can you please read the issue that @jensd0e included above (#2030) and see if the problem is the same? If so, add a comment there and if not, please open a new issue with the detailed steps and try to answer these questions:
Thanks |
This is random issue... I reinstall the app the only way I can login once the issue happens. Then use it to move a file or two around then close out of the app. At some point later it will loose my credentials ( I notice this because picture uploads will fail and I get a notification.) So I reopen the app put in my password (it still has the server and username filled in). The login page will go away like a successful login but push me right back to the login screen. No errors at all. |
It's important for you to know that the new Camera uploads feature, which is going to replace the previous Instant uploads feature, needs to be enabled and configured, even if you had previous Instant Uploads feature enabled since is not going to be handled in the same way for the app. SO, all the Instant Uploads configuration will be deleted after upgrading to 2.6.0, but you can easily enable the new Camera uploads feature and test it. |
Feature approved and finished. Let's enjoy the new camera uploads!!! |
This does not work on my Samsung S7 Edge with Oreo. Both from SD card nor internal memory |
Hello @ALL. Running into troubles with new phone and owncloud sync. Best regards. |
#From the feedback we got from #1829 and #1860, we know that we can't trust in the current implementation of instant uploads to grant that all the picture we'll be eventually uploaded.
At this moment we have tried all the things possible, in our knowledge, to upload the files "instantly", i.e: as soon as the pictures are taken.
We need to forget the idea of immediately and focus in reliability. Most of the feedback we have is from people that are much more concerned about having all there pictures effectively pushed to the server side than about the time needed to get it.
The problem of the current implementation is that the file observers we register for changes in the camera folder "live" in a background service that we try to keep alive forever. If that service is killed for any reason, the observers "die" and pictures are not detected anymore until the service is restarted. The restart is done when the app is opened again, or when the device is rebooted.
In the past, the death of the service didn't happen often. But from Android 4.4, Google is silently killing "immortal" services more and more often with each Android version. With Android 8 Google finally is documenting that services in background will not be allowed to live more than a limited time.
We need to go for a total rewrite of the detection of pictures, that will be based in the next key points:
There are many other details that be improved on the road, but these points address the reliability problem we have in the current implementation.
TASKS:
BUGS & IMPROVEMENTS
The text was updated successfully, but these errors were encountered: