Hi Brian, You are exactly right on both accounts: a second row with the IM information needs to be added to the raw contact to "own" the presence dot; and yes there should be an example. :-)
Cheers, - Dmitri On Thu, Mar 11, 2010 at 9:46 AM, brian <[email protected]> wrote: > As far as I can tell, in order to provide PRESENCE, a 3rd party > provider needs to populate the following > fields:PROTOCOL,CUSTOM_PROTOCOL,IM_HANDLE,IM_ACCOUNT > > At the same time there is a note on DATA_ID: > "If this field is not specified, the provider will attempt to find a > data row that matches the PROTOCOL (or CUSTOM_PROTOCOL) and IM_HANDLE > columns." > So in order to populate presence, a 2nd data row should be populated? > > It would be useful to have an example of a 3rd party sync provider > that implemented PRESENCE,STATUS and the population of the dependent > IM fields... > > > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
