commit 79e725a9924f47b08fceec34192edfe3d3f89d44
author Marc Blank <mblank@google.com> Thu Oct 15 12:11:39 2009 -0700
committer Marc Blank <mblank@google.com> Thu Oct 22 14:49:26 2009 -0700
tree ce928347f4e36678ed0233040aaba05554f693f2
parent 5bd8d6f8310305bce81071ade6ebdb42dbed6b72

Handle moreAvailable true w/o changes (#2189704) DO NOT MERGE

* An Exchange log from Moto has shown sync behavior in which moreAvailable
  is set to true even though there are no changes in the sync response
  (i.e. the SyncKey is unchanged)
* This leads to long-lived looping which impacts battery life
* The fix is to recognize the behavior and prevent looping by
  setting moreAvailable = false

Change-Id: Icf45efbc24331c874c820b7b177e39b16df445d8

src/com/android/exchange/adapter/AbstractSyncParser.java

diff --git a/src/com/android/exchange/adapter/AbstractSyncParser.java b/src/com/android/exchange/adapter/AbstractSyncParser.java
index c913af4..4c73fd8 100644
--- a/src/com/android/exchange/adapter/AbstractSyncParser.java
+++ b/src/com/android/exchange/adapter/AbstractSyncParser.java
@@ -140,7 +140,10 @@
                     mAdapter.setSyncKey(newKey, true);
                     cv.put(MailboxColumns.SYNC_KEY, newKey);
                     mailboxUpdated = true;
-                }
+                } else if (moreAvailable) {
+                    userLog("!! SyncKey hasn't changed, setting moreAvailable = false");
+                    moreAvailable = false;
+                } 
                 // If we were pushing (i.e. auto-start), now we'll become ping-triggered
                 if (mMailbox.mSyncInterval == Mailbox.CHECK_INTERVAL_PUSH) {
                     mMailbox.mSyncInterval = Mailbox.CHECK_INTERVAL_PING;