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

Automatic photo upload does not work #225

Open
SeniorSpielbergo opened this issue Aug 14, 2020 · 14 comments
Open

Automatic photo upload does not work #225

SeniorSpielbergo opened this issue Aug 14, 2020 · 14 comments
Milestone

Comments

@SeniorSpielbergo
Copy link

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.

@SailReal
Copy link
Member

Thanks for your feedback.
The log file could be indeed a help. Would be awesome if you could send it to us: https://community.cryptomator.org/t/how-do-i-enable-debug-mode-on-android/66

@SailReal SailReal added the state:awaiting-response We need further input from the issue author label Aug 14, 2020
@SeniorSpielbergo
Copy link
Author

Thanks for your quick reply!
Please find attached the corresponding logs in logs.zip. I left the whole history in the logs, but I guess that probably only the latest entries (i.e., for 2020-08-17) are relevant.
Also please note that I have disabled the battery optimization for cryptomator already a while back. I was suspecting that this was the cause for this issue and also saw a remark in another bug report relating to the auto upload feature. So I guess this possibility can be ruled out.

@no-response no-response bot removed the state:awaiting-response We need further input from the issue author label Aug 17, 2020
@SailReal
Copy link
Member

SailReal commented Aug 17, 2020

Thanks for the log file.

I'm missing something like this in the log:

...
2020-08-17 09:36:40.090 12325-12325/org.cryptomator I/PhotosContentJob: Job started!
2020-08-17 09:36:40.101 12325-12325/org.cryptomator I/PhotoContentJob: Added file to UploadList
2020-08-17 09:36:40.101 12325-12325/org.cryptomator D/PhotoContentJob: Added file to UploadList /storage/emulated/0/DCIM/Camera/IMG_20200817_093619.jpg (if debug mode enabled)
2020-08-17 09:36:40.104 12325-12325/org.cryptomator I/PhotosContentJob: Job rescheduled!
...

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.

@SeniorSpielbergo
Copy link
Author

Okay, thanks for letting me know. If you need further information or I can support you in any way, please let me know.

@cy2201
Copy link

cy2201 commented Sep 9, 2020

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.

@SailReal
Copy link
Member

SailReal commented Sep 9, 2020

@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.
Therefore I first delete the pictures locally and then start the upload. Such scenarios have to be considered for the automatic upload and have to be configurable via settings.

@stale

This comment has been minimized.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Nov 29, 2020
@SeniorSpielbergo
Copy link
Author

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.

@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Nov 30, 2020
@THuppke
Copy link

THuppke commented Feb 14, 2021

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:

  • (Vault is open)
  • Activated the debug log
  • Switched to the camera app
  • Took a photo
  • Switched back to Cryptomator
  • Locked the vault
  • Unlocked the vault again
  • No new images detected by Cryptomator

logs.zip

@SailReal
Copy link
Member

SailReal commented Feb 15, 2021

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

  1. Go to Settings-->More camera controls...-->Enable Use Storage Access Framework-->Select the SD Card, maybe a Picture folder but doesn't matter, apply with USE THIS FOLDER
  2. Create pictures
  3. Do the same but switch to internal storage, again using Settings-->More camera controls...-->Save location--> select internal storage and apply with USE THIS FOLDER
  4. Provide the log file

In the best case it should look something like this:

intern:
I/PhotoContentJob: Job started!
I/PhotoContentJob: Added file to UploadList
D/PhotoContentJob: Added file to UploadList /storage/emulated/0/Pictures/IMG_20210215_151105.jpg
I/PhotoContentJob: Job rescheduled!
I/PhotoContentJob: Service is destroyed
I/PhotoContentJob: Job started!
I/PhotoContentJob: Added file to UploadList
D/PhotoContentJob: Added file to UploadList /storage/emulated/0/Pictures/IMG_20210215_151139.jpg
I/PhotoContentJob: Job rescheduled!
I/PhotoContentJob: Service is destroyed

------------------------------------------------------------------------

extern:
I/PhotoContentJob: Job started!
I/PhotoContentJob: Added file to UploadList
D/PhotoContentJob: Added file to UploadList /storage/120A-4105/Pictures/IMG_20210215_151231.jpg
I/PhotoContentJob: Job rescheduled!
I/PhotoContentJob: Service is destroyed
I/PhotoContentJob: Job started!
I/PhotoContentJob: Added file to UploadList
D/PhotoContentJob: Added file to UploadList /storage/120A-4105/Pictures/IMG_20210215_151258.jpg
I/PhotoContentJob: Job rescheduled!
I/PhotoContentJob: Service is destroyed

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.

@THuppke
Copy link

THuppke commented Feb 15, 2021

Thanks for the quick response!
I followed your instructions from the last comment, but it does not seem to make a difference whether the Photos to the SD card or to the internal storage.

Here are the logs
logs.zip.

The behavior is different however, if I set Open Camera to save them to /storage/emulated/0/WhatsApp/Media/WhatsAppImages.

Then it suddenly works
logs.zip

@stale

This comment has been minimized.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Jun 26, 2021
@SeniorSpielbergo
Copy link
Author

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.

@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Jun 28, 2021
@stale

This comment was marked as outdated.

@stale stale bot added the state:stale Issues without any activity that will be closed automatically label Apr 18, 2022
@SailReal SailReal added this to the Backlog milestone Apr 19, 2022
@stale stale bot removed the state:stale Issues without any activity that will be closed automatically label Apr 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants