sync'ing to android - over USB-C cable.
deletions don't happen, and sometimes copying is abysmal.
I realize it is not a syncovery issue,from reading prior posts. but any suggestions as to how to improve copying to android (as i copy my keepass and other encrypted ID files to the phone,from desktop, the main repository, for when i travel)
thanks
sync to ANDROID, revisited
Re: sync to ANDROID, revisited
To sync between Windows OS and Android OS devices reliably, quickly, efficiently you need sync software to run on both sides (Windows OS and Android OS device) at the same time. This allows to build file lists for comparison and perform file operations (copy, move, delete, rename) natively and fast.
For instance, to sync between 2 remote Windows OS devices, Syncovery has its optional Syncovery Remote Service feature, which runs a service on remote Windows OS machine to allow for fast file comparison and file operations.
To achieve fast and reliable performance in Android OS, Syncovery needs to develop a client/service for Android OS.
Until Syncovery is available in Android OS, I'm using Syncthing to sync between Windows OS and Android OS devices.
You run Syncthing on Windows OS device and Android OS device at the same time.
Syncthing devices communicate over WiFi or internet rather than USB cable.
For instance, to sync between 2 remote Windows OS devices, Syncovery has its optional Syncovery Remote Service feature, which runs a service on remote Windows OS machine to allow for fast file comparison and file operations.
To achieve fast and reliable performance in Android OS, Syncovery needs to develop a client/service for Android OS.
Until Syncovery is available in Android OS, I'm using Syncthing to sync between Windows OS and Android OS devices.
You run Syncthing on Windows OS device and Android OS device at the same time.
Syncthing devices communicate over WiFi or internet rather than USB cable.
Last edited by Shaipetit on Sun Nov 08, 2026 12:55 am, edited 1 time in total.
-
Contractor5Prepays9
- Posts: 101
- Joined: Wed Sep 23, 2020 10:38 pm
Re: sync to ANDROID, revisited
thanks for reply.
if that is the case, then why is that not needed when i sync from my home computer to network computer, or laptop computer? syncovery is only running on one (source) device.
thanks
is it because it is android on destination?
if that is the case, then why is that not needed when i sync from my home computer to network computer, or laptop computer? syncovery is only running on one (source) device.
thanks
is it because it is android on destination?
Re: sync to ANDROID, revisited
It's because MTP (Media Transfer Protocol) is used to connect your android OS device with your computer via USB cable.
It has to do with the interface/protocol that Syncovery uses to access the remote Android device.
To access your android OS device attached to your computer via USB cable, Syncovery uses MTP.
MTP is considered to be slow, prone to hanging during large transfers, unrefined.
It's not Syncovery's fault that MTP's performance is poor.
Syncovery accesses your other non Android OS computers using different protocols that perform better than MTP: Server Message Block (SMB), FTP, WebDAV, SFTP. These protocols are faster and more reliable than MTP. Even when using these protocols, Syncovery can speed things up further, for instance speed up the “Building File List” phase, by running a dedicated Syncovery service on the remote machine that runs locally on the remote machine and therefore bypasses the need to use the above mentioned protocols.
If you want to use Syncovery to sync your Android devices with your computers, you need to bypass MTP.
You can setup FTP or SFTP server on your Android device to allow Syncovery to access your Android device using FTP or SFTP protocols instead of MTP.
FTP or SFTP server will require Wifi or internet connection between devices.
Alternatively, you run Syncthing on Android and non Android devices that you want to sync.
By using Syncthing between Android device and computer over Wifi/Internet you don't need to use MTP.
MTP is the problem.
In order for Syncovery to sync reliably with Android device via USB cable, Syncovery should do the sync using ADB (Android Debug Bridge) instead of MTP.
It has to do with the interface/protocol that Syncovery uses to access the remote Android device.
To access your android OS device attached to your computer via USB cable, Syncovery uses MTP.
MTP is considered to be slow, prone to hanging during large transfers, unrefined.
It's not Syncovery's fault that MTP's performance is poor.
Syncovery accesses your other non Android OS computers using different protocols that perform better than MTP: Server Message Block (SMB), FTP, WebDAV, SFTP. These protocols are faster and more reliable than MTP. Even when using these protocols, Syncovery can speed things up further, for instance speed up the “Building File List” phase, by running a dedicated Syncovery service on the remote machine that runs locally on the remote machine and therefore bypasses the need to use the above mentioned protocols.
If you want to use Syncovery to sync your Android devices with your computers, you need to bypass MTP.
You can setup FTP or SFTP server on your Android device to allow Syncovery to access your Android device using FTP or SFTP protocols instead of MTP.
FTP or SFTP server will require Wifi or internet connection between devices.
Alternatively, you run Syncthing on Android and non Android devices that you want to sync.
By using Syncthing between Android device and computer over Wifi/Internet you don't need to use MTP.
MTP is the problem.
In order for Syncovery to sync reliably with Android device via USB cable, Syncovery should do the sync using ADB (Android Debug Bridge) instead of MTP.
-
Contractor5Prepays9
- Posts: 101
- Joined: Wed Sep 23, 2020 10:38 pm
Re: sync to ANDROID, revisited
thanks very much, that helps clarify this.
i may try syncthing, i dont do a lot of sync'ing to the phone, i sync som e encryptd wallet files (with xecrets program, a successor/offshoot to axcrypt),
thanks again
i may try syncthing, i dont do a lot of sync'ing to the phone, i sync som e encryptd wallet files (with xecrets program, a successor/offshoot to axcrypt),
thanks again
Re: sync to ANDROID, revisited
If you don't need to sync frequently with your Android device, then you could simply manually run any FTP or SFTP server Android app (not client app) on your Android device and connect to your Android device using Syncovery via FTP or SFTP. Ensure that both your devices are on the same LAN to avoid issues with port forwarding. This way, you bypass USB cable based MTP with FTP or SFTP server app running on your Android device and use already familiar Syncovery to do the sync.
If you use Syncthing on both devices, Syncthing will use its own protocols to bypass MTP and port forwarding issues.
Syncthing will also handle the sync part itself.
Syncthing can run 24/7 and do live sync as soon as files change or you can run Syncthing manually only.
Some people do use Syncthing specifically for keepass sync.
However, using Syncthing and Syncovery for different sync tasks means that you're now using 2 different programs to sync your files.
If you use Syncthing on both devices, Syncthing will use its own protocols to bypass MTP and port forwarding issues.
Syncthing will also handle the sync part itself.
Syncthing can run 24/7 and do live sync as soon as files change or you can run Syncthing manually only.
Some people do use Syncthing specifically for keepass sync.
However, using Syncthing and Syncovery for different sync tasks means that you're now using 2 different programs to sync your files.
-
Contractor5Prepays9
- Posts: 101
- Joined: Wed Sep 23, 2020 10:38 pm
Re: sync to ANDROID, revisited
thanks.
i may try the ftp server option.
it is not a lot of files that i have concerns with, but would like a simple way.
thanks again !
i may try the ftp server option.
it is not a lot of files that i have concerns with, but would like a simple way.
thanks again !