| ff62e7fa903e3b6b11d0443543725c1351ab289d |
|
03-Dec-2016 |
James Lemieux <jplemieux@google.com> |
Refactor where SharedPreferences are built
Bug: 33251787
To enable easier testing, build and migrate SharedPreferences once
during Application creation and only store references to it in member
variables.
Change-Id: I562d2cbddeeff165304fc8844d2af4b765fe4861
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 23629266834a251cb937a885e5223e5ae37cc6fa |
|
21-Nov-2016 |
Christine Franks <christyfranks@google.com> |
Fix janky RepeatDays animation
Bug: 33039716
Test: manual - no apparent jank (or strict mode violations) during
repeatdays expansion/contraction, and systrace reports no dropped
frames during the animation itself.
Change-Id: I923781f44a5db50534640ae605705f7437c805f4
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 2a07ae3286fd5c76f71546890e0f02af99065825 |
|
03-Jun-2016 |
Sean Stout <sstout@google.com> |
Stopwatches and timers continue to work after device reboot.
Bug: 8101723
Upon device shutdown and reboot, the stopwatch will resume state. If
the stopwatch was running, it will continue to run as well as account
for the time that the device was off. Additionally, all timers that
are on the device will resume state. If the timer was running, it will
continue to run on device reboot. If the timer was missed by less than
1 minute, the timer will still go off. If the timer was missed by more
than 1 minute, the timer will go to a new "missed" state and give the
user a notification that a timer has been missed.
Change-Id: Ib7f199ef5be4714b831450933c574f39824d15dc
Stopwatches and timers continue to work after device reboot.
Bug: 8101723
Upon device shutdown and reboot, the stopwatch will resume state. If
the stopwatch was running, it will continue to run as well as account for
the time that the device was off. Additionally, all timers that are on the
device will resume state. If the timer was running, it will continue to run
on device reboot. If the timer was missed by less than 1 minute, the
timer will still go off. If the timer was missed by more than 1 minute, the
timer will go to a new "missed" state and give the user a notification
that a timer has been missed.
Change-Id: I831d7a5172a3cede595db1b62e503ecc8c4c55c2
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 02e72bcfe62fce69715c1dbd8eea7826070c0660 |
|
28-Apr-2016 |
James Lemieux <jplemieux@google.com> |
Route all DAOs to Utils.getDefaultSharedPreferences
Bug: 28051228
This ensures that in all cases the shared preferences are migrated
for FBE use before first access.
Change-Id: I0b1eba1b18dbe03f6ef84625797cf8a6ea879808
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 96422ae1795cb7f838fea49764163a5516846475 |
|
16-Feb-2016 |
Justin Klaassen <justinklaassen@google.com> |
Refactoring SharedPreferences to common location.
Bug: 25860525
Change-Id: I0c55d34b17a2aa5fb94d9d562bebdcc2e44af4d0
(cherry picked from commit 942b3a3956221969c77f9abc447444505eea6929)
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 41ad8d99d3531947b1f7016086cd0e296818b4bd |
|
16-Jan-2016 |
James Lemieux <jplemieux@google.com> |
Handle deleted timers gracefully
Bug: 26591272
Prior to dazzle, timers could inhabit a state of "DELETED" (value = 5).
In dazzle and beyond there is no reason to preserve such a state, but
it is possible for timers to exist in SharedPreferences in such a state,
so it must be handled gracefully.
Change-Id: I1754ef898dfff84c0a3e807c4bd0dd1473f87aad
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|
| 6d603b7c62bb38d763a681a8bf20fadb1442e833 |
|
07-Nov-2015 |
James Lemieux <jplemieux@google.com> |
Refactor Timers to use new unified DataModel
Bug: 24816218
Bug: 25494722
This refactoring introduces a Timer domain object. Instances of these
domain objects are fetched via a DataModel class that is the single point
of reference for all timer data. This allows the data to be shared across
the entire application. In particular, the timer notifications, TimerFragment
and ExpiredTimersActivity all draw upon the same model to determine
what the state of the timers are.
IMPORTANT: The public intent com.android.deskclock.action.STOP_TIMER
has been renamed to com.android.deskclock.action.PAUSE_TIMER to be
more accurate.
Change-Id: Ib904e80a25c6de1861de2b395bec27db16ff0e66
/packages/apps/DeskClock/src/com/android/deskclock/data/TimerDAO.java
|