(In reply to comment #4) > Either way, a new PIM Manager API is needed for suspend/resume. See the > proposal for SuspendSync()/ResumeSync()/"status = suspended" in bug #70950 > comment #1. Is that okay? I went ahead and implemented the API by suspending the local database side of the sync. The Bluetooth transfer continues, we still need a new API to also suspend that. Note that I added a "bool" return code to Suspend/ResumeSync(): Returns true if and only the suspend state changed, otherwise false.