We are coming across multiple reports of an Android Download Manager bug that removes downloaded files if a user moves them to a different folder on the same device.

The Google support forums have hundreds of reports dating back to 2017/8 where users of various Android smartphones – not just Google Pixels – have been complaining about what was seen as a Google Photos bug.

At the time, it was reported that photos would mysteriously disappear from the device as long as one moved them from the Downloads folder to any other folder on the same device.

Android-Download-Manager-bug
(Source)

The issue still persists years down the line, with a Nexus 6P, Galaxy S10, and other device users reporting the same problem not long ago.

I just had the same issue on a Nexus 6P. Moved over 100 files, irreplaceable photos and videos and all are gone. This is the first time Google has let me down that I’m aware of, but it’s a pretty big hit.
Source

Same issue here, Galaxy S10; Moved photos & videos from Internal Storage to SD Card, roughly 75% of the files are now either corrupt (a small amount of them) or missing entirely (the important ones).
Source

This also just happened to me! Lost 4000 pictures.
Source

According to a recent discovery, this issue is reportedly linked to the Android Download Manager and not the Google Photos app as earlier thought. This claim has been put forward by a Redditor who has also filed a bug report with Google issue tracker.

Apparently, the Android Download Manager app has a function known as cleanOrphans. Any file saved in the Downloads folder and then later moved to a different folder on the same handset is marked by the Download Manager as orphaned.

Huawei Nexus 6P
Huawei Nexus 6P users are also affected

These orphaned files get deleted when the device automatically enters the doze mode idle maintenance window. This, essentially, is how you keep losing the files you move from the Downloads folder to a different folder.

Although a bug report has been submitted to Google, this isn’t the first time. Matter of fact, a patch was submitted back in 2018 and despite later closing automatically, it was never merged.

Hopefully, Google will follow this issue closely this time around and fix it once and for all. We will let you know when the bug-fixing update arrives.

PiunikaWeb started as purely an investigative tech journalism website with main focus on ‘breaking’ or ‘exclusive’ news. In no time, our stories got picked up by the likes of Forbes, Foxnews, Gizmodo, TechCrunch, Engadget, The Verge, Macrumors, and many others. Want to know more about us? Head here.

Hillary Keverenge
2107 Posts

Tech has been my playground for over a decade. While the Android journey began early, it truly took flight with the revolutionary Lollipop update. Since then, it's been a parade of Android devices (with a sprinkle of iOS), culminating in a mostly happy marriage with Google's smart home ecosystem. Expect insightful articles and explorations of the ever-evolving world of Android and Google products coupled with occasional rants on the Nest smart home ecosystem.

Next article View Article

[Updated] Instagram crashing on all Android phones, but there are workarounds

Here's the crux of the article in video form: New updates are being added at the bottom of this story……. Original story from (June 5, 2018) follows: We're...
Jul 10, 2023 6 Min Read