-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
Automatic photo upload does not work #225
Comments
Thanks for your feedback. |
Thanks for your quick reply! |
Thanks for the log file. I'm missing something like this in the log:
It looks like new images are not being captured on your device for some reason. We have to think about how to find the cause of the problem. |
Okay, thanks for letting me know. If you need further information or I can support you in any way, please let me know. |
Auto upload works for me on Android 10, but I have to lock the vault and unlock it again after taking a photo. That's very annonying because my vault is always unlocked on my phone. In this way I have to unlock and lock my vault multiple times during the day. |
@qwertz22 yes, that's how it works until we implement #181 and how it is documented in https://docs.cryptomator.org/en/latest/android/settings/#automatic-photo-upload. It will probably mean that in the future you will have to specify in the settings when to upload (directly, x minutes after a new image is taken, ...). If the upload takes place immediately after creating/storing images, it can happen that images that you actually wanted to delete locally will end up in the cloud. For example if you have photographed a tree 15 times you might not want to persist all 15 images. |
This comment has been minimized.
This comment has been minimized.
Just to prevent this ticket from being closed automatically by the stale bot: The issue still exists and, thus, this ticket should not be closed. |
I'm also experiencing this issue for photos I take, even though they are not stored on the SD card. My Whatsapp images are synced automatically whenever I unlock the vault, but it would be great if that also worked for the photos I take myself. My photos are stored in /storage/emulated/0/DCIM/Camera. I'm running version Cryptomator 1.5.11 on Android 10 QKQ1.190828.002 with MIUI Global 12.0.3 Stable. Attached are the logs of the following events:
|
I tried to reproduce the problem but without success. Maybe indeed it has on some devices something to do with internal vs external storage. Could you please let the debug mode enabled, install open camera https://f-droid.org/en/packages/net.sourceforge.opencamera/ or https://f-droid.org/repo/net.sourceforge.opencamera_80.apk
In the best case it should look something like this:
If it is indeed only in the external storage that Cryptomator notices that images have been created on your device, I could imagine what the problem is and could very likely solve it. However, since I cannot reproduce it, I would like to know if this is actually the problem on your device. |
Thanks for the quick response! Here are the logs The behavior is different however, if I set Open Camera to save them to /storage/emulated/0/WhatsApp/Media/WhatsAppImages. Then it suddenly works |
This comment has been minimized.
This comment has been minimized.
Just to prevent this ticket from being closed automatically by the stale bot: The issue still exists and, thus, this ticket should not be closed. |
Basic Info
I'm using Android in version: 10, Security Patch July 2020
I'm running Cryptomator in version: 1.5.9
Description
I am trying to enable automatic photo upload for my android device using a vault on my Google Drive.
The photos in question are stored on an SD card when I take them.
To set up the auto photo upload, I selected the vault for upload and enabled "upload only using WiFi". After that I activated the auto upload. However, no upload started, even after locking and unlocking the selected vault. I also tried different orders for configuring the settings and kept the phone as well as the vault unlocked for longer periods.
As I am running out of options here, I guess this is a bug and I am more than happy to share any log files if required.
The text was updated successfully, but these errors were encountered: