You always have to specify a content provider when implementing a SyncAdapter, but that’s not to say it actually has to do anything. I’ve written SyncAdapters that create accounts and integrate with the “Accounts & sync” framework in Android that don’t necessarily store their content in a standard provider. In your xml/syncadapter.xml: <sync-adapter xmlns:android=”http://schemas.android.com/apk/res/android” android:accountType=”com.company.app” … Read more
There are two basic methods you can use when making a SyncAdapter: Fill data into an existing ContentProvider. Create your own ContentProvider to store a new kind of data. The former is what’s going on in this example app. They have some website that has a list of contacts, and they want to store those … Read more
Calling requestSync() will only work on an {Account, ContentAuthority} pair that is known to the system. Your app needs to go through a number of steps to tell Android that you are capable of synchronizing a specific kind of content using a specific kind of account. It does this in the AndroidManifest. 1. Notify Android … Read more
I’ll try to answer all your questions by addressing the larger question: How can I sync data between a webserver and an android app? Syncing data between your webserver and an android app requires a couple of different components on your android device. Persistent Storage: This is how your phone actually stores the data it … Read more