foldersync chokes on large files

[Michael]

Hi,

Frustrated as I've spent a lot of time debugging, but feel like I'm stuck now.

Trying to sync via SFTP (FTP behaves quite similarly..) on a local network to a samsung galaxy s4 device, NOT rooted.  What seems to happen is during the upload of the large file, the phone (excuse me, not an android expert) goes to sleep?  disables wifi?  breaks the TCP connection?

It seems to be connected with pressing the 'sleep' button on the phone.

Here's what has been happening:

Looking at sftp server logs, we can get 2000 requests in on the transfer reliably.  Sometimes it will continue to 5800.  It never completes.  It hits a point where it just stops transferring, sits a while doing nothing, and then the log says "debug1: read eof"; forced close; written ~128mb.  Shortly after, the session is reopened and the partial file is deleted, and the sync attempt fails with the error "File transfer failed ... Unexpected server response null"

I've tried #*0011# , menu, wifi, and disable wifi power save mode; this doesn't fix it, although it slightly changed it, but it still hung.

------

however, as I was typing this, I noticed that the same file is over 45% synced on an autostarted sync..  (24000 parts and counting).  Basically it just started working..

Is this a known issue with the galaxy s4 device series?  As I type this, I'm surprised as this is the first correct full sync I've ever had.

[Michael]

I think I should clarify.  2 devices are syncing to this sftp server (which is a basic centos 6 install).  Identical methodology, syncing the pictures directory only.

1 (galaxy s4 active) succeeds intermittently, maybe 1 out of 4 times.

1 (galaxy s4) succeeded for the first time only yesterday, and I can't be sure if it is the change to wifi power mgmt at a baseband level that induced this, or not... (It was syncing pictures, seemingly, but would always die when it hit a 550 mb file).

Now the second device, after its first ever successful sync, is more broken than before.  It does nothing but fail after 20 seconds and report "The socket is EOF".  Reboots of client and server don't change this, and independent connections (as well as server logs) via sftp prove the server works.

I want to like this software.  You have singlehandedly put together the most flexible set of design paradigms for a general purpose sync tool.  But it literally fails at its most basic task; and if this can't be resolved I'm going to have to look elsewhere.  I understand it is hard to make money at $3 per app.. why not charge more.. a lot more.. but deliver a supported working app?  I would pay $20 for this without a second thought, if it just worked.

[Anders]

Have you tried the legacy for mode for SFTP?

You could also try seeing the support webpage for info on creating and sending a log file.

[Michael]

thanks, will try that (i did send in a support log.  curious to see what you make of this constant "EOF" error).

I noticed that this server wasn't configured right -- firewall and selinux were at defaults, which were sometimes blocking ftp.  once I fixed that, ftp seems to work reliably.  That isn't ideal but will at least suffice.

If that becomes stable and I can rule out the phone os/hw/baseband, i'll go back to sftp and see if legacy mode makes it stable.

can you elaborate a bit as to what "legacy mode" is?  why did you switch methodologies?  

[Anders Carlsen]

Legacy mode is just another SFTP library that is used. Is not worse or better, but perhaps compatible with some SFTP servers the primary one isn't.