Sorry - I was out of the office for a while. I'm surprised nobody else jumped in to help.
Your original post included a nice log of the crash. Searching for "has died" turns up: I/ActivityManager( 260): Process com.google.process.gapps (pid 609) has died. So that tells you that process 609 was the one that crashed. Searching backwards from there for 609 gives: E/AndroidRuntime( 609): FATAL EXCEPTION: SyncAdapterThread-1 E/AndroidRuntime( 609): java.lang.IllegalArgumentException: Invalid column _count E/AndroidRuntime( 609): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:166) E/AndroidRuntime( 609): at android.database.DatabaseUtils.readExceptionFromParcel(DatabaseUtils.java:136) E/AndroidRuntime( 609): at android.content.ContentProviderProxy.query(ContentProviderNative.java:358) E/AndroidRuntime( 609): at android.content.ContentProviderClient.query(ContentProviderClient.java:50) E/AndroidRuntime( 609): at com.google.android.syncadapters.contacts.ContactsSyncAdapter.getCount(ContactsSyncAdapter.java:678) E/AndroidRuntime( 609): at com.google.android.syncadapters.contacts.ContactsSyncAdapter.processLocalChanges(ContactsSyncAdapter.java:721) E/AndroidRuntime( 609): at com.google.android.syncadapters.contacts.ContactsSyncAdapter.innerPerformSync(ContactsSyncAdapter.java:321) E/AndroidRuntime( 609): at com.google.android.syncadapters.contacts.ContactsSyncAdapter.onPerformLoggedSync(ContactsSyncAdapter.java:180) E/AndroidRuntime( 609): at com.google.android.common.LoggingThreadedSyncAdapter.onPerformSync(LoggingThreadedSyncAdapter.java:33) E/AndroidRuntime( 609): at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:247) Going backwards from there shows some Contact DB queries and references to a TypeBContactsWidget. Is that your code? R On Wed, Aug 22, 2012 at 1:12 AM, Maheswar Martha <[email protected]>wrote: > Hi Robert, > > Thanks for the reply. > > No, we have not flashed a different version or replaced with older version > of GAPPS. > To confirm this we erased all the data by factory reset and then loaded > the fresh software(APPS and MODEM builds). > But, still the problem is reproducible. The bug report is attached here. > > I searched the android frameworks code for this "sorry..." message, but > not found source location. > Do you have any idea about the source code from where we do pop up this > "sorry,process > com.google.process.gapps has stopped" message? > > The real problem we are facing no crash logs when the message popup. Do > you suggest any method to debug this kind of problems? > > If you need any information , please let me know. > We will be waiting for your response. > > Thanks, > Maheswar Martha > > > On Thursday, August 16, 2012 9:28:13 PM UTC+5:30, Robert Greenwalt wrote: > >> Have you done anything to the device like flash a different version or >> accept an OTA update? >> >> This often happens when you go backwards to a previous version because we >> support database upgrades but not downgrades. >> >> A good idea in these cases is to use adb to capture a bugreport and see >> what crashed. >> >> >> On Tue, Aug 14, 2012 at 5:52 AM, Maheswar Martha <[email protected]>wrote: >> >>> Hi, >>> >>> Below abnormal tip is popping up while performing sync of gmail/google+. >>> >>> "sorry,process com.google.process.gapps has stopped" ( See the attached >>> image) >>> >>> Problem reproduction procedure: >>> >>> "sorry,process com.google.process.gapps has stopped >>> >>> >>> We didn’t get any crash logs like tombstones or traces.txt. >>> >>> The only traces observed in logcat(find the logcat log in the >>> attachment):****** >>> >>> ** ** >>> >>> I/ActivityManager( 260): Process com.google.process.gapps (pid 609) has >>> died.**** >>> >>> ** ** >>> >>> I/ActivityManager( 260): Kill com.google.android.youtube (pid 3167): >>> provider com.google.android.gsf.**settings.**GoogleSettingsProvider in >>> dying process com.google.process.gapps >>> >>> >>> >>> 1. What could be reason for the problem? >>> >>> 2. Do we have any fixes for this issue? If yes, can you provide the fix >>> details. >>> >>> 3. any workaround? >>> >>> >>> >>> Thanks in advance. >>> >>> >>> >>> /Maheswar Martha >>> >>> >>> >>> >>> >>> ** ** >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Android Developers" group. >>> To post to this group, send email to android-d...@**googlegroups.com >>> >>> To unsubscribe from this group, send email to >>> android-developers+**[email protected] >>> For more options, visit this group at >>> http://groups.google.com/**group/android-developers?hl=en<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 > -- 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
