-
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
Photos/Videos auto-sync stopped working #1795
Comments
Also reported at IRC as well as at central: https://central.owncloud.org/t/adroid-6-0-1-client-intant-uploads-not-working/2152?u=realrancor The user in IRC reported that using the "ocloud" client works again. That one seems to be a themed but quite outdated version 1.7.2 of the official app. |
For the record, I (that IRC user) just tried to uninstall and reinstall the client after removing the ocloud client and same results. Guess I'll stick to the ocloud client until this is fixed. |
I'm seeing the same here. owncloud android 2.1.1 HTC One M8 - Droid 6.0 It's not even getting as far as trying to upload, so server version not relevant. This has been working fine for years. |
I'm seeing the same. Galaxy S7 - Android 6.0.1. Have tried reinstalling client and also tride to switch from internal to sd and back without luck. |
Hi, everybody. The underlying implementation of instant uploads has changed to try to support more devices and camera apps, including Android 7. As an undesired side effect, you need to access the app settings and select the location where your camera app stores the pictures and videos in a new option called "Camera folder". The default value corresponds to the default location for Google Camera app (and others), but might not be yours. Please, try to set this folder and tell us if the pictures are still not captured. |
Thank you, @andykvakk . These pictures correspond to a configuration saving is SD card? What is your camera app? |
Yes, the images are stored on SD card (The samsung phone seems to map some internal memory as sd card, but the images shows up in /storage/3338-6339/DCIM/Camera. I use the standard Samsung APP v. 5.0.88. I will also do at test on my wifes Nexus 5 as soon as possible. |
Thanks a lot. I would expect no problem with Nexus 5, we tested with several of them, but any feedback is welcome. Please, could you try also with some other camera app in your device? I could suggest Open Camera - it's free, open source, and you can find it both in Google Play Store, F-Droid and maybe other stores. |
Testet open camera, changed the storage folder to same setting, but still no luck. Nothing happens in Owncloud client. Change to default settings in Open Camera and changed the folderpath in OC client, then it worked like it supposed to, the file got uploaded instantly. I wonder if this has something to do about the SD card folder. On my S7, the /sdcard is not the same as my SD card. I will test some more. New test with both camera apps pointing into same location (internal sd, /sdcard/DCIM/Camera). Only the pictures from Open Camera gets uploaded. If i change OpenCamera location to use my SDcard, /storage/3338-6339/DCIM/Camera the images is not uploaded instantly. My wifes Nexus 5 works like it should. |
In 'Open Camera', 'Settings' icon, 'More camera controls...', is the option 'Use Storage Access Framework' enabled? In that case, could you test with it disabled? |
Yes, it was enabled. Disabled it, but was not able to change to /storage/3338-6339/DCIM/Camera so i used /storage/emulated/0/DCIM/Camera, then it works from OpenCamera but still not from Samsungs app (which i also changed to same folder). This is strange. Now both camera apps store the images to same folder, but only images from OpenCamera gets uploaded. |
OK, thanks. This is the second time we watch this effect, and I also could confirm it on a Nexus 5. Samsung camera probably is using Storage Access Framework all the time. For some reason, files created with Definitely, we need to deal with this ASAP. |
Ok. Do feel free to contact me if you want me to test more. |
likewise. I have the same thing on Xperia 6.0.1 |
David A. Velasco said: "As an undesired side effect, you need to access the app settings and select the location where your camera app stores the pictures and videos in a new option called "Camera folder". The default value corresponds to the default location for Google Camera app (and others), but might not be yours." I have tried the various paths to get to the Camera folder, but none of them make any difference I'm afraid. |
I've also chosen to store images on the SD card (Sony Z3+ phone) |
I hope this is fixed soon (as in fixed, not asking users to do a bunch of workarounds). Older versions just worked without fiddling around with stuff. This is important owncloud to be easy to use for non-geeks. |
I'm having the same exact issues as andykvakk. No instant upload from my camera folder '/storage/FA8F-27EF/DCIM/Camera'. I'm using LG G5, Android 6.0.1, LG's "Camera" app 5.0.83. |
Could you check the fix in branch |
I will gladly test, but i'm not sure how to get the fix on my phone. I have found the branch, but should there be an . apk file? I don't have sdk or other build tools for android. |
No, @andykvakk , sorry. At the moment you need to know how to build the app from source code to test it. |
I was able to build android_2.1.1-debug.apk successfully, but it would not install :( any clue where to find install logs or how to figure out what went wrong? |
@johfeu, if the official Android app is installed in the same device, you will not be able to install a client build by yourself due to security rules. But don't uninstall your official app, please. Given the interest in this feature, let me prepare an APK that you all can test. |
Find a test APK in https://github.com/owncloud/android/blob/instant_upload_combined_solution/android_2.1.2-beta-debug.apk . It can be installed in your device without uninstalling your current ownCloud app, will appear as another app, ownCloudTest. You will need to allow APKs from "Unknown sources" in your device settings to install it. Then, disable instant uploads in your regular ownCloud app and start ownCloudTest as usually to enter your account details, enable instant uploads and give it a try. If instant uploads were working for you in version 2.1.0 you can ignore the "camera folder" option. |
Unfortunately i can't pinpoint what exactly triggered this either, i have the same issue with the stock camera folder on a Samsung S7. The .apk provided earlier seems to work tough. |
The proposed fix works for me (Samsung Galaxy S6 EDGE, android 6, samsung camera) |
The provided APK fixed the issue for me. My problem was the same as most reported above:
|
I confirm the test apk fixes the issue on LG G3 with stock camera app on external sd folder. Photos and videos not synchronized in the meantime seem to remain not synchronized, I guess I'll have to upload them manually. |
Same problem on my OnePlus 2 with their version of Android 6.0.1 When I try to choose the camera folder, the app tells me, the folder is empty - like any other folder I choose. The App seems not to see the pictures. |
@ctrlbru , sorry, you are right, you will need to upload those pictures manually from the list of files. @kaffeeringe , files are not listed in the 'Camera folder' option, only folders (we should improve that showing files as disabled elements). You should both files and folders from the uploader. Go to the list of files in the app, tap on the (+) button, then the top |
Same problem here, running version 2.1.1 of the client on a BQ M5 running Android 6.0.1. Nothing gets uploaded despite the right folder is set. For image/video backup from an Android phone, this is a pretty bad bug. |
I have a Galaxy Note 5 that was experiencing this issue and the test .apk is working on my phone now with the default camera app. Android 6.0.1 |
I have a Galazy Note 5 - Android 6.0.1. I use the default Samsung Camera app. My photos are not syncing with the Google Play app nor the Test .apk linked in this thread. I save my camera pics on the sdcard. In both apps, if I try to manually upload a file from the location: /storage/emulated/0/DCIM/Camera it works fine, I can see pics and upload them. When setting the InstaUpload settings, if I navigate back from the default directory, once I get down to /storage/ and click on emulated - it then lists there are no folders available in /storage/emulated. Also in the same dialog, when in the /storage directory, it lists the emualted directory's date as 12/31/2014 - which seems odd. |
Hey, |
The test APK restored automatic sync of photos stored to the internal memory on Xperia Z3 Compact with Android 6.0.1. |
Hey, when goming this fix in Google Play Store ? |
Very soon. We'll release a hot-fix version ASAP. Stay tuned. |
By the way, @janarzz , did you try the test APK? Did it work for you? |
The validation is in this status:
|
@OlivierS1, @kaffeeringe, @marchaase, could you please try to get to the camera folder through the paths |
The test app works fine with Huawei P8 Lite and Android 6.0 :) |
I am back on the playstore version. If I use the + button to try to upload a file, I can see pictures in all 3 When I use the instant upload directory chooser and the 2 new folders Let me know if you need any more info. On Sep 12, 2016 7:45 AM, "David A. Velasco" notifications@github.com
|
@marchaase With the test .APK file, set your folder path to /storage/emulated/0/DCIM/Camera then take a new picture after setting that folder path. We have the same phone and android version and it works just fine for me. I am experiencing the folders not displaying properly in the app navigator when trying to choose a new camera folder as well. It seems once I hit /storage/emulated/ the folders in there do not display properly, even on the test .apk file. All other folders seem to display just fine. As a test, I am using the Samsung default camera application. I set my camera folder to /storage/emulated/0/DCIM/Camera and to /sdcard/DCIM/Camera and all new pictures I take get uploaded correctly. |
I suspect Google update have changed folder permissions and ownerships causing this series of issues. |
Hey, |
Well, I'm not sure if was the Google update or was there before in Android 6, but the permissions of the folders are the key. In any case, please, take this into account: If instant uploads were working in your device with ownCloud Android app version 2.1.0, then you don't really need to care about the value of the 'Camera folder' option. That option is only required if you are using Android 7 or if instant uploads never worked for you before I'll add an ugly clarification to the option. Since we'd like to get the uploads fixed really fast, we'll make a fast release just that way. We can care about a better UI in settings in subsequent releases. |
That should do it. Updated the test APK in https://github.com/owncloud/android/blob/instant_upload_combined_solution/android_2.1.2-beta-debug.apk just in case anybody is curious. Added better filtering to prevent duplicated uploads. ETA for release: tomorrow. |
The feature with the last APK seems to be OK. Anyway, all the feedback you can give us will be helpful. Thanks everybody for your contributions. |
Thanks! I was having issues with Note 4 android 6.0.1 running oc 2.1.1 with the instant upload and the latest .apk worked. |
This is now merged and pushed to the Play Store, will be available as soon as Google processes the update, what usually takes not too much time. Thank you everybody for your help testing this, has been fundamental. |
Actual behaviour
Photos/Videos auto-sync doesn't work anymore, last succesfull sync was 2 days ago.
Uploads list is empty, no files to sync. They are new photos/videos to sync.
Expected behaviour
Photos/Videos should be auto synced to SofortUpload directory on Owncloud server.
Steps to reproduce
Can this problem be reproduced with the official owncloud server?
(url: https://demo.owncloud.org, user: test, password: test)
Environment data
Android version: 6.0.1
Device model: HTC M10
Stock or customized system: stock
ownCloud app version: 2.1.1
ownCloud server version:
Logs
Web server error log
ownCloud log (data/owncloud.log)
The text was updated successfully, but these errors were encountered: