Btsync Android Build 1.3.19

[RomanZ]

Hi all,

 

We've prepared build 1.3.19 for Android devices. Please see change list below. Build will be available on Google Playmarket shortly.

 

Android change list

- Fixed crash on folder view open

- Fixed crash on switch to 3G connection

- Fixed crash on app start

- Fixed LAN discovery issue

- Fixed issue with non-ability to get data over 3G after sleep

- UI cosmetic changes

[JimmyTheSaint]

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.

[RomanZ]

JimmyTheSaint,

 

What about power consumption? BTSync should not use a lot of battery if auto-sleep is working properly.

[JimmyTheSaint]

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.

[RomanZ]

Jimmy,

 

We'll need your debug logs ("Send feedback" in Android) to find what is happening. The file might get deleted as you killed the app.

 

Thanks!

[JimmyTheSaint]

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.

[suntear]

Hello I have been having an issue since upgrading to Android version 1.3.19 and Windows desktop version 1.3.77 and 1.3.80.  The Android client has issues seeing the Windows desktop client (both version 1.3.77 and 1.3.80) when on the LAN.  The folder properties is set to Search Lan, no other options.  This folder is to only sync when the Android client is on the LAN.  If I enable Use tracker server than Android client has no problem seeing Windows Desktop client.  I don't want to sync this folder when not on the LAN.  This only started happen since upgrading to 1.3.77 and still is a problem in 1.3.80.  

[dms2013]

Hello I have been having an issue since upgrading to Android version 1.3.19 and Windows desktop version 1.3.77 and 1.3.80. The Android client has issues seeing the Windows desktop client (both version 1.3.77 and 1.3.80) when on the LAN. The folder properties is set to Search Lan, no other options. This folder is to only sync when the Android client is on the LAN. If I enable Use tracker server than Android client has no problem seeing Windows Desktop client. I don't want to sync this folder when not on the LAN. This only started happen since upgrading to 1.3.77 and still is a problem in 1.3.80.

Do you have a Dlink router? I have the same issue, when I connected via addwrt netgear, problem was gone...

[suntear]

Do you have a Dlink router? I have the same issue, when I connected via addwrt netgear, problem was gone...

 

Nope don't have a dlink router.

[RomanZ]

Suntear,

 

Could you please check if your PC has several active NICs (including virtual adapters)? BTSync subscribes for multicast packets to only one of interfaces, this might be the root cause.

[suntear]

RomanZ I do have multiple virtual interfaces.  What is confusing is that on a fresh restart of the Windows clients, every client sees each other fine.  Eventually the Android client will stop seeing the other Windows client while the Windows client still sees each other.  You had mentioned an issue with Auto-Sleep function which I disabled and it started working again until I leave the house and come back at which point Android can't see the Windows clients, or over a long period of time (8 hours when i checked the Android client again).  The odd thing is that restarting the Android client does not fix the problem.  I have to restart the Windows clients then all clients talk to each other until I either leave the local LAN and come back or after an extended amount of time.  Since there is a new desktop version I will upgrade to that and see if the problem is correct.  Also I do have one share that has Use tracker server enabled and that share never has a problem even when the Search Lan only shares disappear.  If I had to take a wild guess I would be guessing that the LAN discovery process either on the Windows or Android side has a problem.  This never had this issue on BT sync 1.2.x code, only started with 1.3.77 and 1.3.80.

[Lujo]

Have had this problem for something like 2 months maybe through several desktop (ubuntu) / mobile (android) versions / updates.

 

A few days ago brand new install of ubuntu and btsync and nothing with mobile app still in notification list.

 

Went on mobile device and opened app from notification list. Wait for backup device to appear on mobile device. And desktop icon starts moving.

 

The secret is to have the app showing on the screen on the device to backup.

 

Battery-saver and sleep are not at fault unless they are broken.

Devices may disappear from app after dropped to background.

Desktop is not at fault as desktop works after app on mobile is opened from the background.

 

logcat lines (android 4.4.2 cyanogenmod official):

04-09 15:12:49.517 I/ActivityManager(478):   svcb  S    13925 kB: com.bittorrent.sync (12697) started-services04-09 15:12:50.329 I/ActivityManager(478): Process com.bittorrent.sync (pid 12697) has died.04-09 15:12:50.329 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 4000ms04-09 15:12:54.337 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=12777 uid=10101 gids={50101, 1006, 3003, 1028, 1015}04-09 15:12:58.595 I/ActivityManager(478): Process com.bittorrent.sync (pid 12777) has died.04-09 15:12:58.595 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 16000ms04-09 15:13:14.603 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=12868 uid=10101 gids={50101, 1006, 3003, 1028, 1015}04-09 15:13:38.056 I/ActivityManager(478): Process com.bittorrent.sync (pid 12868) has died.04-09 15:13:38.056 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 64000ms04-09 15:14:42.079 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=13028 uid=10101 gids={50101, 1006, 3003, 1028, 1015}04-09 15:15:11.009 I/ActivityManager(478): Process com.bittorrent.sync (pid 13028) has died.04-09 15:15:11.009 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 256000ms04-09 15:19:27.032 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=13607 uid=10101 gids={50101, 1006, 3003, 1028, 1015}04-09 15:19:41.946 I/ActivityManager(478): Process com.bittorrent.sync (pid 13607) has died.04-09 15:19:41.946 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 1024000ms04-09 15:36:45.970 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=14435 uid=10101 gids={50101, 1006, 3003, 1028, 1015}04-09 18:39:28.967 I/ActivityManager(478): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x30000000 cmp=com.bittorrent.sync/.ui.activity.StartActivity bnds=[72,115][792,210]} from pid -104-09 18:39:29.061 I/ActivityManager(478): START u0 {cmp=com.bittorrent.sync/.ui.activity.MainActivity} from pid 1443504-09 18:47:42.436 I/ActivityManager(478): START u0 {cmp=com.bittorrent.sync/.ui.activity.PreferencesActivity} from pid 1443504-09 18:53:02.232 I/ActivityManager(478): Process com.bittorrent.sync (pid 14435) has died.04-09 18:53:02.232 W/ActivityManager(478): Scheduling restart of crashed service com.bittorrent.sync/.service.CoreService in 1000ms04-09 18:53:03.264 I/ActivityManager(478): Start proc com.bittorrent.sync for service com.bittorrent.sync/.service.CoreService: pid=16871 uid=10101 gids={50101, 1006, 3003, 1028, 1015}**** Opened from notification area at this time. Testing for this post.****04-09 19:06:57.568 I/ActivityManager(478): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x30000000 cmp=com.bittorrent.sync/.ui.activity.StartActivity bnds=[72,220][792,315]} from pid -104-09 19:06:57.701 I/ActivityManager(16871): Timeline: Activity_launch_request id:com.bittorrent.sync time:39537489104-09 19:06:57.701 I/ActivityManager(478): START u0 {cmp=com.bittorrent.sync/.ui.activity.MainActivity} from pid 1687104-09 19:06:59.225 I/ActivityManager(478): Displayed com.bittorrent.sync/.ui.activity.MainActivity: +1s407ms (total +1s598ms)04-09 19:06:59.584 I/ActivityManager(478): Timeline: Activity_windows_visible id: ActivityRecord{423ede50 u0 com.bittorrent.sync/.ui.activity.MainActivity t558} time:39537677704-09 19:10:18.842 I/ActivityManager(478): Timeline: Activity_windows_visible id: ActivityRecord{423ede50 u0 com.bittorrent.sync/.ui.activity.MainActivity t558} time:395576035

Edited April 9, 2014 by Lujo

[Lujo]

Edit disappeared...

 

Some btsync log lines during same times as logcat log

[20140409 18:40:08.031] Incoming connection from 192.168.1.7:36348[20140409 18:40:30.353] Incoming connection from 192.168.1.7:36348[20140409 18:40:53.482] Incoming connection from 192.168.1.7:36348[20140409 18:41:16.084] Incoming connection from 192.168.1.7:36348[20140409 18:41:39.501] Incoming connection from 192.168.1.7:36348[20140409 18:42:02.216] Incoming connection from 192.168.1.7:36348[20140409 18:42:25.122] Incoming connection from 192.168.1.7:36348[20140409 18:42:48.346] Incoming connection from 192.168.1.7:36348[20140409 18:43:11.101] Incoming connection from 192.168.1.7:36348[20140409 18:43:34.402] Incoming connection from 192.168.1.7:36348[20140409 18:43:57.069] Incoming connection from 192.168.1.7:36348[20140409 18:44:20.386] Incoming connection from 192.168.1.7:36348[20140409 18:44:43.161] Incoming connection from 192.168.1.7:36348[20140409 18:45:06.236] Incoming connection from 192.168.1.7:36348[20140409 18:45:29.399] Incoming connection from 192.168.1.7:36348[20140409 18:45:52.372] Incoming connection from 192.168.1.7:36348[20140409 18:46:15.181] Incoming connection from 192.168.1.7:36348[20140409 18:46:38.041] Incoming connection from 192.168.1.7:36348[20140409 18:47:00.111] Incoming connection from 192.168.1.7:36348[20140409 18:47:22.288] Incoming connection from 192.168.1.7:36348[20140409 18:47:45.050] Incoming connection from 192.168.1.7:36348[20140409 18:48:08.019] Incoming connection from 192.168.1.7:36348[20140409 18:48:30.126] Incoming connection from 192.168.1.7:36348[20140409 18:48:53.017] Incoming connection from 192.168.1.7:36348[20140409 18:49:15.124] Incoming connection from 192.168.1.7:36348[20140409 18:49:36.086] UPnP: Device error "http://192.168.1.6:2869/upnphost/udhisapi.dll?content=uuid:*removed[20140409 18:49:38.486] Incoming connection from 192.168.1.7:36348[20140409 18:50:01.458] Incoming connection from 192.168.1.7:36348[20140409 18:50:24.367] Incoming connection from 192.168.1.7:36348[20140409 18:50:47.118] Incoming connection from 192.168.1.7:36348[20140409 18:51:10.049] Incoming connection from 192.168.1.7:36348[20140409 18:51:32.302] Incoming connection from 192.168.1.7:36348[20140409 18:51:57.229] Incoming connection from 192.168.1.7:36348[20140409 18:52:20.487] Incoming connection from 192.168.1.7:36348[20140409 18:52:43.275] Incoming connection from 192.168.1.7:36348[20140409 18:53:29.476] Incoming connection from 192.168.1.7:57574[20140409 18:53:29.478] Incoming connection from 192.168.1.7:36399[20140409 18:53:30.355] Incoming connection from 192.168.1.7:36399[20140409 18:53:53.098] Incoming connection from 192.168.1.7:36399[20140409 18:54:16.358] Incoming connection from 192.168.1.7:36399[20140409 18:54:39.580] Incoming connection from 192.168.1.7:36399[20140409 19:07:18.252] Incoming connection from 192.168.1.7:57574[20140409 19:07:18.254] Incoming connection from 192.168.1.7:36431[20140409 19:07:19.237] Incoming connection from 192.168.1.7:36431[20140409 19:07:32.448] Extension: ipv4:[*removed] for 'magnet (*removed)'[20140409 19:07:32.448] Got metadata size 90, pieces 1[20140409 19:07:32.452] Extension: ipv4:[*removed] for 'magnet (*removed)'[20140409 19:07:32.452] Got metadata size 70, pieces 1[20140409 19:07:32.479] Finished receiving metadata for *removed[20140409 19:07:32.520] Extension: ipv4:[*removed] for 'magnet (*removed)'[20140409 19:07:32.520] Got metadata size 68, pieces 1[20140409 19:07:32.520] Extension: ipv4:[*removed] for *removed[20140409 19:07:32.520] Finished receiving metadata for *removed

Edited April 9, 2014 by Lujo

[RomanZ]

suntear, Lujo,

 

The BTSync local discovery mechanism changed significantly between 1.2 and 1.3. In your case it looks like your Windows machines did not subscribe for multicast to appropriate NIC. I could advise to disable all the rest of virtual adapters as a test to see if it helps resolving your issue.

[suntear]

RomanZ,

 

I can try that but I am curious as to why on restart of the Windows client then Android client is able to see it until the Android client leaves the LAN and come back or after a long time time of being idle then it can't see the Windows client until I restart the Windows clients.  Also if it was binding on the wrong interface then why are the Windows client always able to see each other without issues.  Looking at the log for the Windows clients I see it using the correct LAN IP, what I can't see from the log is which interface its binding on.  If it was binding on the wrong nic then would it not use the wrong IP?

[Ethan]

With the new updates using the "download" icon is no longer necessary. I still have to manually start the app for sync to start. I hope it can be completely automatic one day.

Also, would it be possible to display an estimate space left somewhere based on the lowest amount of free storage in one of the clients sync folder?

[RomanZ]

Ethan,

Could you please elaborate? Which "Download icon" do you mean? Which OS refuses to start BTSync automatically? As for the second request - AFAIR there is such proposal in the wishlist.

 

suntear,

Let's take a closer look at your Android logs to see what is happening. When you come home and restart your Android - tap a feedback after it fails to see Win machines, agree to send logs.

[suntear]

RomanZ,

 

I have opened a case and sent logs to support.

 

https://syncapp.zend...m/requests/9504

[RomanZ]

Thanks!

[Ethan]

The android side doesn't sync automatically. I have to open the app, wait for it to find other online devices and then start syncing. I wish it would always do this by itself in the back

[JimmyTheSaint]

The android side doesn't sync automatically. I have to open the app, wait for it to find other online devices and then start syncing. I wish it would always do this by itself in the back

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

[Ethan]

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

Auto-sleep is on and the device appears on my windows machine, yup.

What exactly does auto-sleep do? Save battery I presume?

[JimmyTheSaint]

Auto-sleep is on and the device appears on my windows machine, yup.

What exactly does auto-sleep do? Save battery I presume?

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.

[Ethan]

I tried it and indeed, even after 30 mins, the phone app did not pick up a new file I had put into the btsync folder with my laptop. I had to manually start the app in order to sync again.

I hadn't realised it checks within time intervals. I guess I'm too used to Dropbox and Google where changes are updated instantly. This is actually a considerable advantage they have over btsync.

[Viewmax]

The android side doesn't sync automatically. I have to open the app, wait for it to find other online devices and then start syncing. I wish it would always do this by itself in the back

I have the same problem. On my Nexus 4, BTSync never works in background either with or without auto-sleep. I have to run the app on mobile for getting things synced...