Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Dieses Thema wurde archiviert. Bitte stellen Sie eine neue Frage, wenn Sie Hilfe benötigen.

Downloaded images appear in different directory until Google Photos detects it

  • 1 Antwort
  • 1 hat dieses Problem
  • 12 Aufrufe
  • Letzte Antwort von EE

EE
EE
more options

Hello,

When I download an image from Firefox 83.1 on Android 10, it says it is in the directory path `/document/primary:Download/`, and the time is displayed as the current time in UTC, as shown in the first picture. This prevents the image from showing up properly in my phone's gallery.

However, when Google Photos detects the image, the directory changed to the proper `/storage/emulated/0/Download/` and the timestamp is the correct time I downloaded the image in my timezone. The image shows up in the proper location in my timezone.

I've tried disabling extensions and clearing data, same issue. Also tested with Beta and Nightly, both have this issue.

Hello, When I download an image from Firefox 83.1 on Android 10, it says it is in the directory path `/document/primary:Download/`, and the time is displayed as the current time in UTC, as shown in the first picture. This prevents the image from showing up properly in my phone's gallery. However, when Google Photos detects the image, the directory changed to the proper `/storage/emulated/0/Download/` and the timestamp is the correct time I downloaded the image in my timezone. The image shows up in the proper location in my timezone. I've tried disabling extensions and clearing data, same issue. Also tested with Beta and Nightly, both have this issue.
Angefügte Screenshots

Alle Antworten (1)

EE
EE Fragesteller
more options

Also to note, version 82 and 83 have this problem but 81 does not.