So, if I understand you correctly, even though the mdates on the mobile device end up being incorrect, Sync keeps track of the correct date for each file in its internal database and when a file changes (and thus gets a newer mtime), detects that and syncs it back to the PC, is that right?
If that is the case, I'd like to tell you that about a year ago, I tried to use BT Sync bidirectionally, and even though in the beginning everything seemed to work fine, shortly afterwards, I noticed that it was massively overwriting my files on the PC with ones from the phone, which haven't really changed, but have the later mtime because of the Sync. That indicates that sometimes this database scheme fails, and Sync begins to take those incorrect mdates at face value. I also lost some files on the PC that were newer versions, but were still overwritted by the older version from the mobile device. Fortunately, I have good backup habits, so I didn't lose a lot of data, but still, with pain in my heart, I had to stop using the very useful bidirection Sync capability. I really, really hope all this will get sorted out some time soon, as Sync's functionality is EXACTLY the solution I need for my situation...
I also realize that the biggest culprit here is Google, as it is totally inexcusable that after 7 years on the market, Android still can't handle something as simple and fundamental as setting a file's modification date.
Cheers,
Oleg.