ogrfnkl

New Members
  • Content Count

    5
  • Joined

  • Last visited

About ogrfnkl

  • Rank
    New User
  1. 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.
  2. Just to add -- exactly the same problem has occurred on stock Samsung Kitkat (on the Galaxy Note 10.1 2014 Edition) and on Cyanogenmod Lollipop and later Marshmallow (on the Samsung Galaxy S4). Which Android distros DO support the proper setting of mtime, then? I suspect that it has more to do with the fact that the creation date/time is not being set properly, and hence mtime fails, too. Does that sound correct to you?
  3. Hello, RomanZ, thanks for your reply. I am not sure, though, what you mean by the OS keeping the OLD mtime... The whole problem here is that after syncing, the files all end up having the timestamp from the time of the sync, and it is this NEW mtime that sticks around. Perhaps what you meant to say is that BT Sync attempts to set mtime to the OLD value (that of the SOURCE file), but the OS keeps the new mtime -- is that correct? If so, I suspect that Android does that simply because it won't tolerate mtime to be set to a lesser value than the creation time. Question: why can't BT Sync simply try to set both creation AND mtime on the target file to their source values? Isn't that the whole point of syncing files between devices in the first place -- making an exact copy of each file, and then propagating any changes based on the mtime value?
  4. When syncing from a Windows 10 PC to any Android device (I've tried it with both a Galaxy S4 phone and a Galaxy Note 10.1 2014 Edition, running on anything from Kitkat to Marshmallow), both the creation and the modification dates/times of destination files are set to the time of the sync. Thus, on the destination device, they immediately become newer than on source. This happens when syncing onto either the internal or the external SD card. Please help!
  5. Hello, I have been happily using Bittorrent sync to share a folder from a Windows 7 laptop to my Android phone (Galaxy S4) in read-only mode (i.e. changes can only be propagated from the laptop to the phone, not the other way around), and everything has been working just fine. Then, earlier today, I suddenly started getting the "Don't have permissions to write to the selected folder" error on the phone. When I disconnect the folder and then reconnect it, Bittorrent Sync tries to place it in a subfolder of the Bittorrent directory, and if I try to force it to go to the external SD card, where it's always been, I get the message "No access: Don't have permissions to write to selected folder. On external SD card it is allowed to write to app designated folders only. I thought I had already taken care of this type of problem right from the start, when I rooted this phone and then used the NextApp SD application to remove the external SD card use restriction, and it HAS worked just fine with BitTorrent Sync all along... until today... Anyone has any idea what's going on and how I can go back to using the same folder on my external SD card as before? Thanks!