JimmyTheSaint

Can you verify that you used the Xposed module called "HandleExternalStorage"? If so, you might also try getting help at the module's xda forum at: http://forum.xda-developers.com/xposed/modules/app-handleexternalstorage-t2693521 What device are you using? CM 11.0 on my S4 and Note 2 allows writing to the external SD card without needing an Xposed module.

While your Android device is online and set to Auto Sleep, does it continue to sync as expected? In other words, are your Android device's files never more than 30 minutes or so out of sync, and your other devices' files never more than 30 minutes or so out of sync with what's on the Android device? By "30 minutes or so," I mean reasonably close to whatever sync period you've chosen. If Auto Sleep works consistently for you, please post your device, Android version, and if you were using WiFi or mobile data.

1.3.21.0 still has the same problem: Auto Sleep stops syncing relatively soon. As far as I can tell, within a few hours at most, my phone will stop syncing changes made by other clients. Many hours later, I can see that the phone's version is that many hours behind what's been synced on all the non-Android peers. The reverse doesn't seem to be true: when I make a change on the phone via a third party app, BitTorrent Sync seems to notice within the Auto Sleep period. But I haven't systematically taken notes on the behavior. I just know that it stops syncing within a few sleep periods. It's possible that it syncs again much (8 or more hours) later. In fact, I haven't yet seen anyone on the forums state definitively that Auto Sleep worked with a reasonable degree of consistency for them.

I don't think simply rooting is enough. You either need to flash a capable ROM or try the Xposed module HandleExternalStorage.

The Kit Kat external storage issue is being discussed at this thread: http://forum.bittorrent.com/topic/28275-android-442-dont-have-permission-to-write-to-this-folder/

I strongly prefer the previous Linux UI's ability to display the sync state of everything in one view. In the new interface, we have to click on the links under "Connected devices" to get this info, and can only see info on one shared folder at a time. I suggest making it an expandable link. That way, users could modelessly monitor at a glance precisely the stuff they want to monitor and unexpand links when they want a cleaner look. This new modeful UI is too claustrophobic.

My debug log is in C:\Users\<UserName>\AppData\Roaming\BitTorrent Sync\sync.log

I've tried them all, and the one I've found that suits me best is Jota Text Editor: http://www.appbrain.com/app/jota-text-editor/jp.sblo.pandora.jota I think several others will work fine; it's a matter of the kind of user interface you want. I open text files inside sync folders from my file browser (Solid Explorer), and they open in Jota. Right after I save, they sync in the expected way. With Dropbox, I frequently had 20-second latency opening even the smallest text files on my phone, probably due to the location of Dropbox's servers far from my networks. Even a file opened a minute ago would take 30 seconds to re-open. Real dealbreaker there, that and the whole Snowden thing.

As of March, 2011, applications have to belong to the media_rw group to modify the contents of an SD card. To gain access to this group, a permission called WRITE_MEDIA_STORAGE was added. See: http://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/

Auto-sleep will sleep the app and wake it up for a short period after the Auto-sleep time is up to see if there's anything to sync and sync it. Yes, it's verified to save quite a lot of battery. While the app is sleeping, it won't show in any of the sync peers, but it will show for the short time it's awake, though you might not be looking at just the right time. Are you certain that it's only syncing when you launch it manually? You can test by altering a file, waiting past the sleep period (default is 30 minutes), and then seeing if the Android device has picked up the change.

Do you have Auto-sleep on or off? If off, does your Android device appear in other sync peers' "Devices" tab?

http://forum.bittorrent.com/topic/29448-how-to-make-it-save-on-sd-card-in-44/

If you're willing to root your device, you can use the Xposed module HandleExternalStorage. I preferred flashing a different 4.4.2 ROM that doesn't have the external storage limitation.

I just noticed that my S4 is consuming battery at less than 12%/hr without using Auto sleep. It was more than 20%/hr in previous versions. I don't know when that change happened or if it's a permanent imrovement. I just know that for the past 3 hours, my S4 reports 10-12%/hr at each of several data points.

1.3.20: still no sync with Auto sleep while on 3G data.

I've heard that when you remove an app on 4.4.2, its home folder gets deleted automatically. I can't test that, but will the BitTorrentSync app's home folder--and the user's data--get deleted if they uninstall?

CPU usage is back to normal on my Linux NAS's.

I just rolled back my other Linux NAS to 1.3.77 the same way as I did the previous one, and it synced without any new files getting overwritten. I wonder why sometimes restarting on Linux is OK, and other times not. Meanwhile, this one is showing 20-30% CPU so far, but the other one stays right around 10%.

I'm now seeing heavy CPU usage on my Linux NAS's. They were at a constant 50-70%, so I restarted btsync on both. One now hovers at 18-23%, but the other continues at 70-80%, and it's the backup NAS with less load on it. I haven't been tracking the CPU usage, so I'm not sure when the problem returned. But as I reported in this thread: http://forum.bittorrent.com/topic/21884-is-20-45-linux-nas-cpu-usage-too-high/ 1.1.70 had pretty much solved the problem by providing 11-13% CPU usage, and that's why I haven't been paying attention to it for seven months. But it's got my attention now. EDIT: I just tried reverting one of the servers to 1.3.77, and it ovterwrote about 100 newer files with their older versions. Is there a clean way to shut down the Linux process and downgrade? The 1.3.77 version is still running between 20-50%, and I'm dreading re-upgrading it. EDIT (later): at this point, 1.3.77 is down under 10% CPU.

A thread with "latest build" in the title is always a sticky in the top area of this forum. At the top of that thread, the dev will post a link to the current download versions. For Synology, you can find out what kind of CPU your NAS has by browsing to: http://forum.synology.com/wiki/index.php/What_kind_of_CPU_does_my_NAS_have

If your S4 has been updated to KitKat (4.4.2), then you're experiencing a limitation that's new with KitKat, and your problemis unrelated to this old thread. See, for example: http://forum.bittorrent.com/topic/28275-android-442-dont-have-permission-to-write-to-this-folder/ and complete info at: http://www.androidpolice.com/2014/02/17/external-blues-google-has-brought-big-changes-to-sd-cards-in-kitkat-and-even-samsung-may-be-implementing-them/

Right, I forgot about the debug logs. I just sent them in case there's still something useful there. In my note, I mentioned losing sync, but I forgot to mention that the problem only happens when using auto sleep.

Bad auto sleep news update: I noticed at one point that my S4 had gone about four hours without syncing. I had moved between WiFi and 3G a few times. A couple of times, I manually launched the app and watched it find devices online, so I assumed it synced at those times, but it turned out files didn't get updated. I simply couldn't get it to sync, and at one point the app appeared frozen, so I had to manually kill it. When I later checked history on another computer, I saw that the S4 had been overwriting new with old with the one file that had been seeing activity during the test period. That's basically what was happening to me with 1.2.x versions--anomalies--which I totally cured by turning auto sleep off and living with 20% per hour battery consumption. I could live with a lagging sync problem; I mean if the phone lost sync sometimes, but in a way that you could reliably fix by manually launching the app, then that would make it possible to keep testing. But anomalies are a dealbreaker, and I've had to shut off auto sleep again. Here's a logcat that only covers the last twenty minutes because I don't know what's limiting the period of my system's logcats: https://db.tt/F7yL8Jo9 Anyone reading the logcat should know that at one point, as I mentioned, I killed the app with a utility, which is probably captured by the logcat. As for power-savings, I was seeing less than expected. In 1.2.x versions, I reported a baseline battery consumption of 5-7% per hour. This time I was seeing 10-12% per hour, but I was only spot-checking between times of busy phone usage, so I wouldn't try to conclude anything about auto sleep's power consumption.

yeah, maybe: root your phone and try the Xposed module HandleExternalStorage.

My S4's been syncing with Auto sleep on 3G for a couple of hours now, no problem. By the way, when I change a file on the phone via another app, it seems to always get synced before the Auto sleep period is finished.