Syncovery Support Forum

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 ...

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 ...

Is there any way for this to not be treated as an error. Perhaps as just a warning?

I'm syncing some phone image files - example file:

Name: 20221221_201531.jpg
Date: 12/21/2022 8:15 PM
Date Taken: 12/21/2022 8:15 PM
Date Created: 4/14/2023 7:02 PM
Date Modified: 4/14/2023 7:02 PM

Somewhere along the path the Date Created and Date Modified attributes have been changed from their ...

This seems like something that shouldn't be too hard to do so I must be overlooking something.

I have a job I always want to run every hour but at 15 minutes after the hour:
00:15
01:15
02:15
...
23:15

I have it set to "Run Every" 1 Hours and then I "Specify Next Run" to be the upcoming one, so ...

More insight.

On Exact Mirror profiles I understand now that the database only gets created when I have:
"Comparison / More / Remember Results"
checked, even though "Binary comparison of Existing files when building the File List" to the left is not checked. I thought those two were related since ...

No databases in /volume1/@appdata/Syncovery/.Syncovery/Database either.
Pardon the rapid fire posts. Didn't see this one before.

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

So to summarize, the questions I have are:

Are those really long ".old.old.old.old." filenames normal?

Where should I expect to find ...

I also found the .old.old.old. pattern for /volume1/@appdata/Syncovery/CfgBackups/Syncovery.empty - see SyncoveryEmpty.jpg attachment.

Maybe that's normal and you'll tell me so. It just looks supsicious to me, especially on a 256 character boundary like that.

This may also explain quite a few things.
I looked in the /volume1/@appdata/Syncovery/Database folder and I only see two databases in there, even though I created 18 profiles. That leads me to a theory on the database issue.

I have two "flavors" of profiles on this NAS. Let's call them A and B ...

More logs on the various DB issues if that might help:

25-12-22 19:00:02: TTGSQLIniFile.OpenDatabase: /volume1/@appdata/Syncovery/Syncovery.cfg
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg data string count: 433
25-12-22 19:00:02: /volume1/@appdata/Syncovery/Syncovery.cfg entry ...