)]}'
{
  "commit": "b6787f2ee535338bb96df0ab8ad70a9f82760a25",
  "tree": "3ee86e968edcbce4bc241e19c882cc13f3e89d07",
  "parents": [
    "7e8cbfc2bc3ea2334c38db7fd2b6a1e17eefcac6"
  ],
  "author": {
    "name": "Christopher Tate",
    "email": "ctate@google.com",
    "time": "Thu Jul 02 17:40:45 2009 -0700"
  },
  "committer": {
    "name": "Christopher Tate",
    "email": "ctate@google.com",
    "time": "Mon Jul 06 11:49:49 2009 -0700"
  },
  "message": "Hold a wakelock during backup/restore/clear operations\n\nWe need to make sure we stay alive for the duration of a backup or (especially)\nrestore operation.  The existing Handler-based timing system was simply not\nproperly functional, so it\u0027s been retooled to use a repeating alarm delivering a\nbroastcast PendingIntent to our registered receiver.\n\nWe acquire a partial wake lock in the broadcast receiver [i.e. while the Alarm\nManager is holding one for the duration of broadcast delivery] and pass the\nwakelock object to the backup thread, which eventually releases it when it\u0027s\nfinsihed operations.  A similar pattern is used for the threads handling restore\nand clear.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7977d1f33b15dafb682144410acf48878142c967",
      "old_mode": 33188,
      "old_path": "services/java/com/android/server/BackupManagerService.java",
      "new_id": "e47d853809bb453ec3e4f481276b4fccbfc09a76",
      "new_mode": 33188,
      "new_path": "services/java/com/android/server/BackupManagerService.java"
    }
  ]
}