• Content Count

  • Joined

  • Last visited

About heymoe

  • Rank
    New User
  1. 2 folders per mobile device is the bare minimum. Add in save game data (1 directory per game) or other apps that store their pictures folders outside of the system default pictures directory. Heck the pictures directory doesn't even contain the directory that the camera on the device stores it's photos in. A single mobile device can blow the 10 folder limit on a PC easily.
  2. I was reading the recent reviews on the Mobile Android app and found that Sync's support people were responding to complaints about the 10 folder limit with: "Dear XXXX, note that 10 folders limit is not applied to Sync for mobile. Sync Support Team." or "Dear XXXX, note that limitation of 10 folders is only applied to desktop computers. Sync Team." I know a few people in this thread has mentioned how it's easy to exceed the 10 folder limit on a mobile device because you can't merge all the folders you want to sync under one folder because each apps expects to find their files in a specific location thus you have to create a separate Sync folders for each App you want to sync data for which can eat up your 10 folder limit quickly. I personally run into this issue too. Based on the responses above by the Sync team, it sounds like you can create more than 10 folders on a mobile device without having to upgrade to Pro BUT even if this is true, I'm not syncing my mobile device to another mobile device but to my PC which is limited to 10 folders thus having unlimited folders on a mobile device for free is still useless unless you pay for Pro on the PC. I also see this whole unlimited folders for free on mobile and not PC as a big WTF! but that could just be me. To me a nice compromise that the Sync team could do is only apply the 10 folder limit to Sync folders created using the new v2.x Sync folder format while allowing unlimited number of Sync folders using the v1.4x Sync folder format. It sounds like (I haven't verified myself) that the v2.x apps are backward compatible with the v1.4x folder format and you can create new v1.4x folders via the v2.x apps so they would just have to update their license code to check for total # of v2.x Sync folders instead of all Sync folders which I'd like to think would be a quick change but I'm not a developer nor do I know what their code looks like. I think that would go a long way to making a lot of people happy again and would be a legitimate way for them to keep their promise of not removing any v1.4x features. Granted this might be a somewhat short term "fix" being that I'm sure they will want to eventually stop supporting the v1.4x format from a code bloat point of view. Sure they made a promise to not remove any features from v2.x that were in v1.4x but I doubt they will make the same promise for v3.x. As such I still feel, like many others, that a re-evaluation of their pricing model still needs to get done. A non-subscription option for at least personal / home users would be nice as in pay once for a major version with updates (security) then an upgrade price for the next major release if we feel the need to upgrade. Any ways, that's my feedback
  3. Just an update: It would seem that BTSync v1.3.94 has corrected non-stop flood of UDP packets to the IP of a shutdown client. Based on my packet capture after updating my Windows and Linux server to v1.3.94, the UDP traffic continues for about 1 mins after I shutdown my Android client and then stops. My Android device is now able to stay in deep sleep mode while connected to WiFi thus my battery drain is back to reasonable levels. Thanks!
  4. I'm currently using BTSync to sync photos and other files on my mobile android devices to my Windows laptop and a home server running Linux. I'm running BTSync v1.3.93 on the Windows laptop and Linux server and v1.3.20 on Android. I noticed that my battery life on my Android device was really bad when I was connected to my home WiFi network due to excessive wlan_rx_wake wake locks. Basically these wake locks keep my Android device from going into deep sleep / low battery consumption mode. If I disconnected from WiFi and went back to 4G the wake locks stopped and battery drain would go back to more reasonable levels. Doing some packet sniffing I found that BTSync on my laptop and home server were sending UDP packets to the IP of my Android device even though BTSync on my Android device was not running. I confirmed that if I shutdown BTSync on my laptop and home server that these UDP packets would stop. Once these UDP packets stopped, the number of wlan_rx_wake wake locks went down significantly and my Android device was able to stay in deep sleep mode. The WiFI network (bridged) and the Lan network that my laptop and home server are connected to are on the same subnet. I noticed that if I changed the IP of my Android device while BTSync was running on my laptop and home server that my Android device would stop receiving these UDP packets but I could see from the packet sniffing that my laptop and home server were still trying to send those packets to the old IP. If I start BTSync on my Android device on this New IP, let things sync up and then shut it down again, the UDP packets from my laptop and home server start hitting the new IP. My guess is that BTSync on my laptop and home server are just trying to reconnect with my Android device even though I turned BTSync off on that device but it seems that this constant "hey are you there now" UDP packets are keeping my Android device awake because it has to respond to any packet directed to its IP (not broadcast). The main Android device I've been testing this with is an LG G2 running Android 4.4.2. Any thoughts on this?