Unison for Android
Too dated. Does not work on newer versions of Android.
Tool doesn't give information on which port unison s listening and which user I have to make use when connecting.
This doesn't do anything but take you to the paid app download page.
Requires root
The "Lost connection with the server" error means unison is having trouble using ssh to contact the server. In my case I had my own ssh executable I was trying to use, and SELinux was preventing applications installed in /data (including unison) from running system apps. Moving the unison executables into /system/xbin fixed it. Configuring SELinux to let unison run ssh also would have worked, and so would using socket mode with a unison server. The lost connection error is very generic - it just means something went wrong using ssh to run unison on the server. I diagnosed it by setting unison's sshcmd to a script I wrote to run env and echo $*. The idea was to see the environment variables and command line parameters ssh was seeing, duplicate it manually, and where it failed. But my script wasn't called, which pointed to SELinux being the problem. Now that it's fixed, unison is working very well.
Pfff. No help from the developer. Any other 2-way sync software to sync a large home?
Simply doesn't work. I get the unhelpful lost connection message every time, with no clue how to fix it.
Works just as well as the computer version: perfectly. Every bit as fast and efficient.
Excellent job.
I so appreciate being able to sync with my laptop.
Thank you for making this app :)
Just the app I was always looking for.
Simply doesn't work. I get the unhelpful lost connection message every time, with no clue how to fix it.
Works just as well as the computer version: perfectly. Every bit as fast and efficient.
Excellent job.
I so appreciate being able to sync with my laptop.
Thank you for making this app :)
Just the app I was always looking for.
by C####:
The "Lost connection with the server" error means unison is having trouble using ssh to contact the server. In my case I had my own ssh executable I was trying to use, and SELinux was preventing applications installed in /data (including unison) from running system apps. Moving the unison executables into /system/xbin fixed it. Configuring SELinux to let unison run ssh also would have worked, and so would using socket mode with a unison server. The lost connection error is very generic - it just means something went wrong using ssh to run unison on the server. I diagnosed it by setting unison's sshcmd to a script I wrote to run env and echo $*. The idea was to see the environment variables and command line parameters ssh was seeing, duplicate it manually, and where it failed. But my script wasn't called, which pointed to SELinux being the problem. Now that it's fixed, unison is working very well.