1. 13 Aug, 2016 14 commits
  2. 21 Jul, 2016 1 commit
  3. 08 Jun, 2016 2 commits
  4. 05 Jun, 2016 1 commit
  5. 04 Jun, 2016 1 commit
  6. 03 Jun, 2016 2 commits
  7. 22 May, 2016 1 commit
  8. 21 May, 2016 1 commit
  9. 04 May, 2016 2 commits
  10. 19 Mar, 2016 1 commit
  11. 17 Mar, 2016 1 commit
  12. 25 Feb, 2016 1 commit
  13. 19 Feb, 2016 2 commits
    • Justin Klaassen's avatar
      Merge remote-tracking branch 'goog/ub-deskclock-dazzle_nyc' into nyc-dev · 2c535e27
      Justin Klaassen authored
      * goog/ub-deskclock-dazzle_nyc: (122 commits)
        Add android.support.design proguard flags
        Use ACTION_LOCKED_BOOT_COMPLETED on API 24+ - DO NOT MERGE
        Teach DeskClock about file-based encryption. - DO NOT MERGE
        Refactoring SharedPreferences to common location. - DO NOT MERGE
        Use AppCompat's imageButtonStyle attribute - DO NOT MERGE
        Use SimpleItemAnimator - DO NOT MERGE
        Bump version to 4.5.0 - DO NOT MERGE
        Do not assume current stopwatch lap has positive duration
        Avoid IndexOutOfBounds when deleting timer - DO NOT MERGE
        Fix snooze event tracking
        Rebuild notifications after app upgrade
        Fire timers as scheduled after app upgrade
        Create AlarmObserverPreL in onCreate
        Handle deleted timers gracefully
        Fix alarm not firing in memory-pressure situations
        Promote TimerService to the foreground while expired timers exist
        Match firing alarms for SEARCH_MODE == alarm.next
        Fix alarm icon cut off in 1x4 digital widget on nexus 5
        Import translations. DO NOT MERGE
        Attempt to avoid early death of AlarmService
        ...
      
      Change-Id: I422291e92ca76a901aba0d192749789916495711
      2c535e27
    • Justin Klaassen's avatar
      Add android.support.design proguard flags · 4a90936e
      Justin Klaassen authored
      Change-Id: Ib56c2edf4f37eaf90b442e0e2c4342046fe839c1
      (cherry picked from commit 581aa2ea)
      4a90936e
  14. 17 Feb, 2016 4 commits
  15. 16 Feb, 2016 3 commits
  16. 13 Feb, 2016 1 commit
    • James Lemieux's avatar
      Do not assume current stopwatch lap has positive duration · f8e562f6
      James Lemieux authored
      Bug: 27171498
      
      After a device reboot the realtime clock is reset. Because of this, the
      app is notified of the BOOT_COMPLETE and resets the stopwatch.
      There exists about a 10 second window of opportunity before the
      BOOT_COMPLETE broadcast in which the app may be opened and
      the realtime clock information may be used to compute stopwatch
      laptimes which would be negative. This case is now handled gracefully
      rather than crashing on a sanity check.
      
      Change-Id: I0eb4da0a9a55b5abc8d6abaa5a2e046821d39a2e
      f8e562f6
  17. 08 Feb, 2016 1 commit
  18. 04 Feb, 2016 1 commit