We are very happy to announce that today we released a new update for Cheetah Sync, version 1.5.0!
Why is this exciting? Mainly because in prior versions of Cheetah Sync, the "Sync Deletes" option was unavailable for two-way syncs; so anytime you deleted a file from either your computer or Android under a two-way sync directory, the "missing" file was automatically re-copied back. In order to delete a file on both your Android and computer, you had to delete it on both the computer and the Android, which was quite inconvenient.
No longer. With Cheetah Sync 1.5.0, the app "remembers" the files that you synced during your last two-way sync, and knows if you've added files or deleted them, so if you turn on Sync Deletes for your two-way sync jobs, when you delete files on your Android, they will be automatically deleted on your computer (or vice versa).
This new version of Cheetah Sync also manages file and folder renames with ease. Just rename a file or folder on your computer, and your next sync will automatically rename the file for you on your Android (or vice versa).
Because of the large amount of development required to add Two-Way Sync Deletes, you must have purchased the Premium upgrade via an in-app purchase in order to turn on Sync Deletes for two-way syncs. We believe that true two-way syncing is well worth the investment for our customers that require this advanced feature. The premium upgrade also allows the creation of unlimited sync jobs and disables in-app advertisements.
We hope everyone enjoys this great new feature!
iSyncr License Error With MTP
This post is meant to help customers that are having issues with licensing on Android 3.0 and later.
First, make sure you are using iSyncr 2.6.3 or later. This version of iSyncr reduces the chance of seeing this error. If you are using iSyncr 2.6.3 or later, read-on.
Background (Optional): Starting in Android 3.0, Android devices use "MTP" instead of "Mass Storage" for sending files over USB. This is an improvement in security and file integrity. However, it is not a speed improvement and it does have more software behind it that has to be maintained. As a result, sometimes customers see a "license missing" error from iSyncr. This a result of Android's MTP implementation not being seasoned yet. We have filed bugs with the Android Open Source Project about this (early in 2011).
First, make sure you are using iSyncr 2.6.3 or later. This version of iSyncr reduces the chance of seeing this error. If you are using iSyncr 2.6.3 or later, read-on.
Background (Optional): Starting in Android 3.0, Android devices use "MTP" instead of "Mass Storage" for sending files over USB. This is an improvement in security and file integrity. However, it is not a speed improvement and it does have more software behind it that has to be maintained. As a result, sometimes customers see a "license missing" error from iSyncr. This a result of Android's MTP implementation not being seasoned yet. We have filed bugs with the Android Open Source Project about this (early in 2011).
Cyanogenmod 7 Note
To all those using Cyanogenmod 7 with iSyncr, the storage areas are reversed. Where you see "Internal Storage", iSyncr will write to the SD Card. Where you see "SD Card", iSyncr will write to the "Internal Storage". If your device only has internal memory or an SD card, just ignore this message. :-)
How To Sync Google Music Back To iTunes Using iSyncr
Today November, 17, 2011, I spent some time trying to figure out how to sync music back to iTunes that you "pin" to your phone in the new Google Music app. I have nothing against cloud streaming services, but iTunes has tons of options that I'd like to keep using. As such, I want to get the music I purchased out of Google Music and into iTunes. I doubt I'll be the only person looking to do so.
After some research, here is what I found.
The files from Google Music are stored with a ".nomedia" file. This file tells the Android OS, "No other music player would be interested in this". It was this way through the beta, but I'm very surprised that Google is dead set on keeping music you purchased locked into their music app. They know it is far from the best ones available and I thought the motto went something like "Don't be Evil". Weren't they in a tussle with Facebook because you could get your info out of it easily?
Moving on from the ".nomedia" file. We can also see the files are named "1201.mp3". I thought, OK, they are just making sure if you have two songs with the same name, they won't have any conflicts, right? Maybe. However, try to read the ID3 tag off of one of these files. Turns out they've stripped them of all information. Google Music has stored all of this info in a private database inside the app. That sucks.
So, yes. You can use iSyncr to sync these mp3 files into iTunes, but it wouldn't be terribly useful. You would have to manually add all of the song information after listening to it. Hopefully Google opens up the Music API, or at least doesn't take steps to make sure you have to use their player to play pinned files. A moderately decent intern could reverse these changes to the music app in a day.
-Justin
After some research, here is what I found.
The files from Google Music are stored with a ".nomedia" file. This file tells the Android OS, "No other music player would be interested in this". It was this way through the beta, but I'm very surprised that Google is dead set on keeping music you purchased locked into their music app. They know it is far from the best ones available and I thought the motto went something like "Don't be Evil". Weren't they in a tussle with Facebook because you could get your info out of it easily?
Moving on from the ".nomedia" file. We can also see the files are named "1201.mp3". I thought, OK, they are just making sure if you have two songs with the same name, they won't have any conflicts, right? Maybe. However, try to read the ID3 tag off of one of these files. Turns out they've stripped them of all information. Google Music has stored all of this info in a private database inside the app. That sucks.
So, yes. You can use iSyncr to sync these mp3 files into iTunes, but it wouldn't be terribly useful. You would have to manually add all of the song information after listening to it. Hopefully Google opens up the Music API, or at least doesn't take steps to make sure you have to use their player to play pinned files. A moderately decent intern could reverse these changes to the music app in a day.
-Justin
iSyncr - Honeycomb And Later Tutorial
iSyncr is an application that will help you sync songs from iTunes to your Android device. This tutorial is meant for people with Honeycomb tablets (Android 3.0) OR Ice Cream Sandwich devices (Android 4.0). If you have an Android device using Android 2.3 or earlier, please use the iSyncr for PC or iSyncr for Mac tutorial.
1.) Download iSyncr for PC from the Android Market or the Amazon Appstore or download iSyncr for Mac from the Android Market or the Amazon Appstore.
2.) Open iSyncr on your Android device after it is installed
3.) Press "OK" when the license is successfully installed
![](http://4.bp.blogspot.com/-X-blUIyFMgE/TrA2uhUrdCI/AAAAAAAAD-Q/axV2s_tq2xc/s1600/better-device-2011-11-01-133328.png")
1.) Download iSyncr for PC from the Android Market or the Amazon Appstore or download iSyncr for Mac from the Android Market or the Amazon Appstore.2.) Open iSyncr on your Android device after it is installed
3.) Press "OK" when the license is successfully installed
Cheetah Sync for Mac 1.20 Issues
Hi all,
I just found out that we have a major issue in Cheetah Sync 1.2.0 for Mac users. Basically we added some code to check for invalid characters in Mac filenames to either abort the sync, or skip the files in question (if you set the option in the Sync Job). But this code appears to be broken, marking files as invalid which should not be.
I will be fixing this bug ASAP, and hopefully we can release 1.2.1 with the fix very soon. Extremely sorry for the inconvenience in the meantime.
Cheers,
Hexar
UPDATE:
This issue has now been fixed. If you are using Cheetah Sync on a Mac, please update to version 1.2.1 in the Android Market.
I just found out that we have a major issue in Cheetah Sync 1.2.0 for Mac users. Basically we added some code to check for invalid characters in Mac filenames to either abort the sync, or skip the files in question (if you set the option in the Sync Job). But this code appears to be broken, marking files as invalid which should not be.
I will be fixing this bug ASAP, and hopefully we can release 1.2.1 with the fix very soon. Extremely sorry for the inconvenience in the meantime.
Cheers,
Hexar
UPDATE:
This issue has now been fixed. If you are using Cheetah Sync on a Mac, please update to version 1.2.1 in the Android Market.
iSyncr WiFi 1.5.0 Released
We are happy to announce a new update for iSyncr WiFi! Here are some of the changes we've made in this revision:
We hope that our users will find this new UI fresh and appealing =)
Mac Illegal Characters Bugfix
It's unfortunate that we didn't find out about this issue and fix it sooner. Basically, there are several filename characters which are valid on Mac OS X, but are not valid on the Android filesystem. Namely, the following characters: "/\*?<>|
For this reason, we added some code to remove / replace these characters when syncing tracks to your Android device.
Android 1.6 Crash Fixed
Some users running Android 1.6 were experiencing crashes due to a bug in our notification service code. This has been fixed =)
Major UI Overhaul
We spent a significant amount of time and effort in this release trying to improve the overall look and feel of the UI, as demonstrated by some of the following screenshots:
We hope that our users will find this new UI fresh and appealing =)
Subscribe to:
Posts (Atom)