Handle binder transaction failures in CalendarSyncAdapter
* Created a facility for handling the newly implemented
TransactionTooLargeException that the framework can throw if
we send a too-large batch of data to a content provider.
* For now, we're just using this with CalendarSyncAdapter,
which is where we've seen problems in the past, and in
the referenced bug.
* The test account hits the exception, and then appars to
successfully finish syncing the calendar
3 files changed