Files / More / Modification Timestamp

[SyncoveryLG]

I have a job that is copying files from a Windows PC to a USB attached Android phone.

In Files / More the "Copied Files Receive Current System Time as Modification Timestamp" setting is not checked.

The destination file ends up with the current system datetime as the Date Modified.

I have tried enabling "Copied Files Receive Current System Time as Modification Timestamp" and running the job, and it sets Date Modified to the current system datetime, but when I disable it for the next test it has no effect. Date Modified still gets current.

Is there a different setting I should be looking at?

To clarify I'd like the target file to end up with the same Date Modified value as the source file.

[tobias]

Hello,
some devices may not allow preserving the timestamps.

I don't think there's much we can do if that is the case.

You can make sure you have a recent Syncovery version (current is 11.15.3) to get the latest fixes.

I'll make some fresh tests here also.

[SyncoveryLG]

Yes, I have discovered the limitations on this little journey. I ended up enabling developer mode on the phone and installing ADB on the windows PC, the wrote a powershell script to do the actual file copy and use "adb shell touch" to set the modified datetime to the same as the source.

This is mostly a one time copy versus something I need to automate so this approach will work for me. I just tried to take the shortcut and save some time by giving it a try in Syncovery.