Buggy Behavior When Copying Files from Android Phone
Posted: 10 Oct 2025 00:42
Hi, I've had this issue in both official and beta versions of XYplorer, and I still have no idea what causes it: Copying an occupied folder from my phone's internal storage to the desktop causes the phone's directory in XY to change and become unavailable until I completely exit and restart XY. I can't be sure whether this is actually a bug, but I have not found any other case quite like mine on the forums. The phone is a Galaxy S22 Ultra, connected via USB. XYplorer 28.00.0200, Windows 11 23H2, screen scaling 100%.
For context, I need to copy all the photos I take each day via the Timestamp Camera app, so that folder is what I attempt to copy to the desktop from my phone's internal storage. The copy operation itself is usually successful, however as soon as the operation is completed, the portable device address somehow changes and becomes unavailable; no amount of refreshing within XY will bring my phone back into view. In Windows Explorer, the device never disappears at all and presents no issue copying any files/folders. I have to completely exit and restart XY to get it to see my phone again.
From my testing, it seems that there is a cap of 7 individual photos that I can copy from within the Timestamp Camera folder without issue; if I try with 8 photos, the phone directory changes and becomes unavailable. When trying to copy the occupied Timestamp Camera folder itself, the cap seems to be only 5 photos; if I try with 6 photos in the folder, the phone directory changes and becomes unavailable. I can't explain the difference or the reason for these caps, but the issue does not occur when using WE to copy. Screenshots of the process below, with 35 photos inside the folder in this instance.
I'm hoping for some help finding whatever option I must have set incorrectly, or at least verifying if this is indeed a bug. I have tried changing various combinations of options under auto-refresh, custom copy, and other areas in XY, with no success. Please let me know how I can help narrow this down. Thanks for your time and help.
Before copy: After successful copy, location unavailable: If I refresh the window before exiting XY, the address for the portable device changes, now suggesting it is within my XYplorer install folder: XY with location unavailable, device still visible in WE: After restarting XY:
For context, I need to copy all the photos I take each day via the Timestamp Camera app, so that folder is what I attempt to copy to the desktop from my phone's internal storage. The copy operation itself is usually successful, however as soon as the operation is completed, the portable device address somehow changes and becomes unavailable; no amount of refreshing within XY will bring my phone back into view. In Windows Explorer, the device never disappears at all and presents no issue copying any files/folders. I have to completely exit and restart XY to get it to see my phone again.
From my testing, it seems that there is a cap of 7 individual photos that I can copy from within the Timestamp Camera folder without issue; if I try with 8 photos, the phone directory changes and becomes unavailable. When trying to copy the occupied Timestamp Camera folder itself, the cap seems to be only 5 photos; if I try with 6 photos in the folder, the phone directory changes and becomes unavailable. I can't explain the difference or the reason for these caps, but the issue does not occur when using WE to copy. Screenshots of the process below, with 35 photos inside the folder in this instance.
I'm hoping for some help finding whatever option I must have set incorrectly, or at least verifying if this is indeed a bug. I have tried changing various combinations of options under auto-refresh, custom copy, and other areas in XY, with no success. Please let me know how I can help narrow this down. Thanks for your time and help.
Before copy: After successful copy, location unavailable: If I refresh the window before exiting XY, the address for the portable device changes, now suggesting it is within my XYplorer install folder: XY with location unavailable, device still visible in WE: After restarting XY:
