| fe4f416602026b464c94268a90b62677d5de2582 |
|
12-Sep-2016 |
Sean Stout <sstout@google.com> |
Tapping Timer/Stopwatch notifications doesn't crash on KK.
Bug: 31381487
Test: manual - Tap notifications on KitKat
Change-Id: I1ae5ecf91c0079fea95620de764fd520ee560ec7
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.java
|
| ba27a4ded731598feb18a49818110815c1998114 |
|
01-Sep-2016 |
Justin Klaassen <justinklaassen@google.com> |
Fixes from merge of ab6a8e1 - DO NOT MERGE
Bug: 30076796
Change-Id: I88f075b4c6fc95e54a92d11328e4258521c7054e
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.java
|
| ab6a8e1f3e21977b0fddfa03ee0ba942830dc00a |
|
29-Aug-2016 |
Justin Klaassen <justinklaassen@google.com> |
Cleanup exported APIs
Bug: 30076796
- Removed preliminary support for deeplinks since Clock doesn't have a
public content provider.
- Removed unnecessarily exported intent actions since Intents
specifying explicit components don't need to register specific
actions.
- Removed unused strings and resources.
Change-Id: Ifbee006dbd752ecdcfe0125cabe19ffda40ea659
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.java
|
| 0a3313e231702cc9944e9a17e52aea62eb25afab |
|
12-Jul-2016 |
Sean Stout <sstout@google.com> |
Negative time timers expire if you resume them
Bug: 30066072
Though it is still possible for a timer to go negative and not fire,
if the user pauses a negative time timer and then resumes it,
it will immediately fire.
Change-Id: I27945febbbf8ee10ada6e523261738024b7c2e80
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.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/timer/TimerService.java
|
| 0dd0cac610cd59762c8b604da6c437b18a29246b |
|
09-Jan-2016 |
James Lemieux <jplemieux@google.com> |
Promote TimerService to the foreground while expired timers exist
Bug: 26471891
This makes the clock app unlikely to be killed in memory pressure
situations while expired timers are ringing.
Change-Id: I89f141a835e3de67a58671d6c5b381de52be5c18
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.java
|
| 437da3b08ce9ce1b32f4e544816cb3431ceb8d4e |
|
13-Nov-2015 |
James Lemieux <jplemieux@google.com> |
Simplify HandleDeskClockApiCalls, TimerService and StopwatchService
HandleDeskClockApiCalls used to pass through all timer and stopwatch
mutations to the corresponding Service to complete. This complicated
the logging of the corresponding event unnecessarily.
After this change:
- StopwatchService is only invoked from stopwatch notifications and may
now assume the event label
- TimerService is only invoked from timer notifications and AlarmManager
and may now assume the event label
- HandleDeskClockApiCalls.EXTRA_FROM_NOTIFICATION has been replaced
with HandleDeskClockApiCalls.EXTRA_EVENT_LABEL which explicitly
identifies the label of the event
Change-Id: Ic9796c43e826f82138ee431d3abb02524c0146ba
/packages/apps/DeskClock/src/com/android/deskclock/timer/TimerService.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/timer/TimerService.java
|