JimmyTheSaint

Members
  • Posts

    306
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by JimmyTheSaint

  1. My Windows and Linux devices all updated and synced with no problems.
  2. I monitor battery usage closely. With auto sleep turned off, I've seen no change in power consumption.
  3. For that lingering tooltip, I get rid of it by opening the window in the same spot, go to the Devices tab, and then mouse over the folder names until it pops up a new one. The old, lingering label disappears, and then if you move the cursor along a safe path out past the app's window, the new tooltip will disappear, too.
  4. When you updated your Samsung phone to KitKat, your phone lost the ability for its apps to write to external storage: 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/ So you now get that error. You can fix this by rooting your phone and installing the Xposed module HandleExternalStorage, or by flashing the CyanogenMod 11 ROM.
  5. Eleven hours later, and the fix is still working. But I just want to add that the same files the Linux devices kept adding back are now being added back by my Note 2. It's not overwriting because the originals have moved. So when the Note 2 adds them back, I delete them. On each round, the number of files it adds back become fewer and fewer, and now it's down to one. This is the same behavior I saw on my Linux boxes before the fix. Meanwhile, my S4 hasn't shown any problems.
  6. OK, I've started btsync on both Linux boxes with all debug information enabled. When one dies, I'll post here. I guess the best way to provide those large files will be via a sync folder. I should mention that when I restarted the Linux clients, they began overwriting new with old, as expected. What's more, if I copy the newer versions on top of the older versions, this time one of the Linux clients just keeps re-overwriting them. When I simply delete the clobbered files (planning to add them back later from saved copies), that same Linux box just keeps adding them back. about 15 minutes later: One of my Windows clients just crashed. In all the time I've been using btsync, I've never seen it crash on a Windows client. I selected the option to send crash info to the developers. After restarting it, it syncs without overwriting any new with old, but also I haven't been changing any synced files because of this problem. about 30 minutes later: One Linux client's btsync stopped running, but there is no core in the bin directory. I PM'ed you log location info.
  7. I've started a thread about this in the troubleshooting forum at http://forum.bittorrent.com/topic/28911-linux-processes-stop-running-then-overwrite-new-with-old-when-restarted/
  8. btsync stopped running on both of my Linux boxes within 20 minutes of starting them and syncing. This has happened a couple of times. Before I manually restart them and restore overwritten files, what diagnostic info do you want, exactly? There's nothing relevant to the btsync process in /var/log/messages. And bin/.sync/sync.log doesn't show anything unseemly. It just ends after a bunch of "incoming connection" entries, which is 6 minutes after the last file's piece was completed.
  9. crap, btsync just stopped running on both Linux boxes within 20 minutes of starting them and syncing. Before I manually restart them and restore overwritten files, what diagnostic info do you want, exactly? There's nothing relevant to the btsync process in /var/log/messages. And bin/.sync/sync.log doesn't show anything unseemly. It just ends after a bunch of "incoming connection" entries, which is 6 minutes after the last file's piece was completed.
  10. OK, then there are no cores. Please say specifically the name of the log file you mean, which I assume is in /var/log somewhere? And I always have all peers online 24/7, except perhaps for one of the Windows laptops. In the time since my last post, I updated the systems on both my Synology boxes via their update apps, which means there's a clean shutdown and restart. I then restarted btsync manually, as usual. On the first device, no issues. When I did the second device after the first one had fully synced, it overwrote several files with their older versions. Each file was one that had been touched in the couple of hours preceding. I did make sure that no files on any peer were touched while the Linux boxes were updating their systems. So it looks like a version of the Linux reboot issue that has appeared before for some people.
  11. I posted at http://forum.bittorrent.com/topic/28275-android-442-dont-have-permission-to-write-to-this-folder/#entry80608 about a new Xposed module that's supposed to enable apps to write to external storage with KitKat. Since you've flashed a custom ROM, I would think you'd have no problem installing the Xposed framework and seeing if this app fixes your problem: http://repo.xposed.info/module/de.defim.apk.handleexternalstorage More info at http://forum.xda-developers.com/showthread.php?t=2693521
  12. Where does the btsync process dump core? If it's in the directory where the bin is located, then there's no core. I've forgotten many details of Unix because so much runs automatically these days. By "data destruction" I always mean old-overwrites-new, so I'll make sure to specify that in the future. By the way: on one Linux device, I'd restore the file from the archive, and then the same device would overwrite it with an older version in about 50% of the cases, without an observable pattern. When I manually copied the file over a second time, the change "took." Also, I observed at some point that my Note 2 was no longer listed as a peer on other devices. That's my backup phone which just stays at home on WiFi without me ever operating it. I checked the phone, and there was no FC or notice of any kind. When I restarted BitTorrent Sync, several of the same files as above were overwritten by older versions. Maybe I made a mistake or forgot something somewhere, but now that this is happening, I'll watch more closely.
  13. Same thing just happened on my other Linux client. I have no clue what suddenly happens to the btsync process. Any suggestion of what diagnostic information to collect and how to collect it in case it happens again?
  14. If the latest SlimROM is Kit Kat, then it's going to have the problem where the app can't write to just any location it wants to.
  15. No logs or core dumps. My server shows it's been up for 14 straight days, so it wasn't a server reboot. The app must have crashed somehow. The re-started app overwrote all files that were changed on other clients past a certain time with its older versions of those files. Presumably, that certain time was when the app must have crashed, which was about twelve hours before I discovered it. So I was saved a lot more work than if I'd gone days without noticing it.
  16. As with previous versions, when my Galaxy S4 is on 3G data and Auto-sleep is enabled, the phone still never syncs. If I launch the BitTorrentSync app, it will eventually sync, and if the phone moves onto a WiFi network, it will sync with Auto-sleep as expected. With auto-sleep disabled, the phone always syncs fine on WiFi and data. Can anyone else verify whether or not their Android phone syncs when on mobile data with Auto-sleep enabled?
  17. At some point, 1.3.67 stopped running on one of my Linux clients, I don't know why. When I manually restarted btsync, I had a lot of data destruction where old overwrote new. It took about 30 minutes working with the history file to sort everything out. But I'm concerned that this will happen again when the Linux client restarts, possibly after it crashes. And then, the longer it takes before you notice it needs a restart, the more painful the restore session will be.
  18. There is a new Xposed module for Android that will allow any app to write to external storage called HandleExternalStorage: http://repo.xposed.info/module/de.defim.apk.handleexternalstorage If you're new to Xposed, your phone needs to be rooted. I use lots of Xposed modules. Information on the Xposed framework is at: http://forum.xda-developers.com/showthread.php?t=1574401
  19. With the version update, I'm going back to test the Android sleep function to see if it's now totally glitch free. I want to make sure about the expected functionality. While my phone's BTS is set to sleep and wake every 30 minutes, if I make a change to a file by opening it directly with some other app, will BTS Android detect and sync that change within 30 minutes? Or are we expected to open the file from within the BTS app's file browser? I've only made one test so far: I opened a text file via a shortcut I have programmed into my phone, and then altered and saved the file. 45 minutes later, the changes still hadn't been synced to any other peer. When I opened the same file from within the BTS app and altered it, it synced immediately, but that's me manually waking up BTS rather than it waking itself within the 30-minute period to detect and sync the changes on its own, automatically. Before I do more tests, what's the expected behavior here?
  20. The March 11 nightly of CyanogenMod 11 for S4 (i9500) is reported to have fixed the storage problem for 4.4.2. I like CM on my Note 2, and I've been waiting for quite a while to get 4.4 on my S4 with CM 11. I won't be flashing it for several days, but if anyone can report on how it works with BitTorrent Sync on your S4, please post.
  21. Yes, that's what I mean. With auto sleep on at 15 or 30 minutes, about once per day I was experiencing things like old versions overwriting new versions, phantom Android sync files, and other small annoyances that couldn't really be predicted or traced. I think I mentioned it on the boards here somewhere, but because of the lack of diagnostic info, I couldn't raise a specific, reproducible problem on these forums. All I know is that for the past six weeks with auto sleep turned off and my phones syncing 24/7 (they're always on a network), I haven't had a single problem. But without auto sleep, my phone consumes 20% battery per hour. With auto sleep, it's 5%. Carrying a spare battery with a Samsung phone is a total no-brainer, otherwise using the battery this way for the sake of persistent two-way sync wouldn't be possible.
  22. Yes, I'm saying the fix worked. In addition, as I mentioned in another thread, I stopped using Android sleep because I was experiencing too many unpredictable glitches. With sleep turned off, I've been 100% glitch free for several weeks. I'm hoping that the recent "peer come online" fix will also prevent the anomalies that happen when a sleeping Android peer wakes up. I'll try Android sleep again at the next update to the Android version.
  23. No wait time to install a new release.