I'm seeing an I/O error when syncing to a KitKat SD card
Unfortunately, Google made SD cards read-only in KitKat, except for a small area.
There are four choices at this point.
  1. Sync to the internal memory.
  2. Wait on Android "L" and a Cheetah Sync update to support "L".
  3. Sync to sdcard/Android/data/com.jrtstudio.SyncFolders folder on the SD card.
  4. Root your device and use the following app to fix up the SD card. https://play.google.com/store/apps/details?id=nextapp.sdfix

I'm having trouble connecting to my computer. What should I do?
Assuming your computer and Android device are connected to the same network, connection problems are usually a firewall problem. Click on the Help button and then choose "PC Connection Help" to view our firewall configuration recommendations

What operating systems does Cheetah Sync support?
Cheetah Sync supports Windows XP and higher and Mac OS 10.5 and higher. Just download the proper installer for your computer.

If I select "Ignore Sub Directories", will they be deleted if I select "Sync Deletes"?
No. If you select ignore sub directories, they will be ignored on both sides of a sync.

What does the option "Deep File Compare" mean?
When the app starts a sync, it needs to compare any files you have on your computer to the files you have on your Android. By default, the app checks the file size and the modified date, but for maximum accuracy it might be necessary to calculate a file hash. Most users should not need to turn this option on, especially because it can slow down your sync considerably, but it is an option for maximum accuracy.

What's a collision policy?
When syncing files, the app needs to decide what to do when the source folder (eg. your computer) has a different version of a file than the target folder (eg. your Android). A collision policy tells the app which file to keep in this scenario. For example, if you select "Newer", then if the modified time of the source file is later than the modified time of the target file, the newer file will be copied

What is a conflict file?
When conflict files are enabled, then in the case of a file collision, a copy will be made of the file that would have been overwritten. For example, if your collision policy is "Newer", and you are syncing a file called "oasis.jpg", then if the file already exists on the target and is older than the source file, the app automatically renames it to "oasis (older).jpg" for you. The idea behind this option is to protect against accidentally losing files that would have otherwise been overwritten.

How do I report a bug?
Just send us an email at [email protected].