android-syncadapter

REST Server I created a Rails server that contains :users and associated :comments . It is used as a backend API for an Android client. The exchange format to load and store data at the server is JSON. Here are the relevant migrations. class CreateUsers < ActiveRecord::Migration def change create_table :users do |t| t.string :name t.timestamps end end end ... class CreateComments < ActiveRecord::Migration def change create_table :comments do |t| t.references :users t.string :subject t.text :message t.timestamps end end end All users have already been imported. Therefore, only read access is

I am implementing a syncadapter for an android app and would like to make the settings for the account available under the "Accounts & sync" menu. I have seen this done in the DropBox app(as shown below), but I have not been able to find documentation on how to do this. I have the accounted added, just want to add a link to the account settings in this menu. In your Android Manifest, you should have a section like this to define your account authenticator: <service android:name="AccountAuthenticatorService" android:exported="true" android:process=":auth"> <intent-filter> <action android:name=

I try to understand the Android synchronization logic. What I don't understand is the file syncadapter.xml contained in the Android SDK sample project SampleSyncAdapter . If you downloaded the SDK samples it should be in the following folder: SDK/android-sdk-PLATFORM/samples/android-VERSION/SampleSyncAdapter/res/xml/syncadapter.xml I read, the authority of a content provider should be a string or a reference to a resource. What exactly is the content authority and where is com.android.contacts ? Here is the content of the file (w/o license information and comments, API level 16). <sync-adapter

I recall reading about a broadcast receiver interface from the sync adapter or some ResultReceiver of sync progress events. Is there something built into the SyncAdapter pattern or is it home-grown? What works: The method suggested in a 2010 Google IO session, Developing Android REST client applications is to place columns into your ContentProvider as tags to indicate that a record is being fetched or placed or etc. This allows a per-row spinner (or other visual change) to be placed in your UI. You might do that through a custom CursorAdapter that drives a ListView. Your ContentProvider is on