msmith979

Members
  • Posts

    2
  • Joined

  • Last visited

Posts posted by msmith979

  1. On 10/28/2016 at 7:13 AM, RomanZ said:

    @msmith979 Most likely possible, but it also depends on your android flavor. Your Folder A should be RW, your folder B should be RO, with sync all enabled, enabling overwriting of changed files. In worst case, your Android won't let Sync to adjust timestamps, although in this case Sync will keep internal record of real mtime.

    Thanks for the reply, but I am a little confused by it.  Let me try to be a little more clear on my part.  I'm currently running Android Marshmallow 6.0.1, stock from my provider.

    Folder A = Source folder on my PC

    Folder B = On my phone's microSD card. I wish Folder B to mirror all changes, if any, from Folder A.

    With that said, shouldn't Folder A be set to RO and Folder B set to RW?

    In my initial post, I only set up Folder A in my PC's Resilio Sync application.  From there, I used my phone to scan the QR code (either Folder A's RO or RW code) to initiate synchronization between the two devices.  In my phone's Sync app, I directed Folder A to transfer/update its contents to Folder B.  I also turned off selective sync.

    With the RO QR code, I believe new files/subdirectories in Folder A not present in Folder B were added to Folder B.  However, conflicting files (Folder A files on Folder B with newer timestamps) were not updated.  With the RW QR code, conflicting files were resolved by files with newer timestamps overwritting older counterparts.  However, subdirectories/files there were deleted from Folder A prior to sychronization were not deleted from Folder B and such conflicts were shown in Folder A after synchronization.

    For example, in Folder A:

    ├───Alternative and Rock
    │   ├───Built to Spill
    │   │   ├───Album 1
    │   │   └───Album 2

    will look like this after synchronization (from Folder A, artist directory renamed and Album 3 subdirectory deleted):

    ├───Alternative and Rock
    │   ├───Built to Spill
    │   │   ├───Album 1
    │   │   └───Album 2
    │   ├───Conflicted.Built TO Spill
    │   │   ├───Album 1
    │   │   ├───Album 2
    │   │   └───Album 3

    From your quote, are you suggesting that I setup both Folder A (on my PC) and Folder B (on my phone) and point them to their respective directories for proper bidirectional syncing? For example, on my PC, Folder A (RO) receives a link from my phone's Folder B; on my phone, Folder B (RW) receives the QR code from my PC's Folder A.  Will this establish that Folder B cannot update Folder A but any new or conflicting files from Folder A will be updated accordingly in Folder B?  Will this prevent the creation of "Conflicted.X" in Folder A?

     

    FYI: directory tree is 5525 lines long.

  2. On my PC, I have folder that contains all of my playlists and music I wish to sync to my android phone (Folder A).  Essentially, I desire the mirror that folder onto my phone (Folder B).  From time to time, I will add/subtract songs or update playlists from Folder A (both are automatically generated) and I wish that it such changes will be reflected onto Folder B.  However, the results have been underwhelming when syncing Folder A to Folder B, with Folder A as its source.  Under read only mode, Sync did not update files with newer timestamps (updated playlists or files with updated tags).  Under read+write mode, files with newer timestamps from Folder A replaced older files in Folder B (good!).  However, subdirectories in Folder B not found in Folder A remained and, when there was a conflict, the parent directory of older files in Folder B showed up in Folder A as "foo.Conflict" (bad).  So, at the end of the day, how can Sync be set up in a way that Folder B mirrors all of the updates and changes (additions and deletions) from Folder A?