GitLab

Bug: 25780110
Change-Id: I454ee709d296c7a2860281b2e981476608df1e57

- add precision to some wording for translators
- update widget provider XML layout

Change-Id: I78d7d29b2ed2ea4768c0e36d125b38df971c1484

Change-Id: Ife7cf799c6d9ca5cf15deff3337526295fdf19b5
Auto-generated-cl: translation import

Bug: 24977472

By default, the menu is inflated after the first draw. A proactive
call to Toolbar.inflate(...) during creation defeats this default
behavior.

A second problem is that the menu that is inflated by default for
DeskClock contains the search menu item which is briefly shown.
By defaulting that menu item to be invisible and only making it
visible when its corresponding controller exists, the
dancing/flashing effect is avoided.

Change-Id: I933ab9a59b471abe26e1cf07385e4a4c128d1808

Bug: 25706729
Change-Id: Idf41102e733c5056f98ac4873a5b1dde442ffefe

Change-Id: I9474d45596185cb75b9f7cf061948d862a7ea7e7
Auto-generated-cl: translation import

Change-Id: I59086de027fc696976811b25303c5374523cbf86
Auto-generated-cl: translation import

Merge "Simplify HandleDeskClockApiCalls, TimerService and StopwatchService" into ub-deskclock-dazzle

Bug: 25121359

Calling Activity.recreate() while the activity is paused will create
a new copy of the activity that remains paused, even if it is the
foreground activity.

To work around this, we delay recreating the activity until after
it identifies as being resumed. This produces a noticeable flash
but is far better than the alternative...

Change-Id: Iae770a25fb5b6f80d50a321a0f2f4cd792eceb10

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

Bug: 25177293

If the default system alarm ringtone is invalid or malformed then
RingtoneManager will return a null Ringtone. In which case we now
fallback to playing our own internal alarm ringtone.

Change-Id: I1beeec0fc8998ad684e67062ffc0fd0d03f66f68

Change-Id: Ibe429ba988a8842715c8732b4524eefb2655f7e4

Bug: 25630846

Change-Id: I3a7566f6ef2c20ceb487e864fde0f0d12582f8cc

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

Bug: 25631044

The clock tab animation was noticeably longer than the other
tab animations. Some rotations were removed to shorten its
duration. Also, animated vectors are v22+, so the resource files
were moved into /animator-v22 to fix some lint warnings.

Change-Id: I90b116df2a3cc7a30bdd69b8e478207dd3f016fb

Bug: 17903090

When an alarm is missed the alarm_instances table actually contains two
entries for the same alarm.

- one represents the missed alarm
- one represents the next upcoming alarm

The query that joins alarm_templates to alarm_instances would return
two rows for the same alarm in this case. Since the alarm_instance data
is used offer a predismiss button in the UI, it is fine to ignore the
missed alarm in this join.

Change-Id: I720e48c9274b42d3cda9d57d3eef099c5dcd3902

Bug: 23819400
Change-Id: I308f65160d76655a1829de1dec1d3dc4c91e819f

Change-Id: I15eeae825ce267aaf7742650b84fa73a6ac103ca
Auto-generated-cl: translation import

am: 16d75d8d  -s ours

* commit '16d75d8d':
  Import translations. DO NOT MERGE

Change-Id: I1afa8b26bc5f6422ed64208150efb74e2194cd99
Auto-generated-cl: translation import

Change-Id: I2a0cc2fc4c176b4c5ef92303b034bed53bc803ac
Auto-generated-cl: translation import

am: 460a4e02

* commit '460a4e02':
  Re-post notifs removed when AlarmService is destroyed

Bug: 25319162
Change-Id: Ie9183986e5aab3067ac44f7582323c239aa42063

Bug: 2379179

Also make the label input singleLine, since that is how we display it
in the rest of the UI.

Change-Id: I06a4507213bbcb75edcb4e632c24dcc283f5c3df

Change-Id: I280443527becfb14445adefb4d737357cb3e2e39
Auto-generated-cl: translation import

am: 6713ec0c

* commit '6713ec0c':
  Write STATE_DELETED prior to deleting timer instances

Bug: 25220599

By writing STATE_DELETED to shared prefs prior to deleting the timer
instance, listeners have a chance to react to the state change and can
still successfully instantiate the TimerObj.

Change-Id: Ic33da9de715e22f4aac9b861afc0708ba08a01ec

Bug: 24636103
Bug: 25026017

In combination with ag/795890, may help solve the stale notification
issue.

Change-Id: I7f5f9da8cedd102544f7f34efd24b0dc7b8f38e0

Bug: 24963430

Change-Id: I54576422d1a7216d23536a76896ff9e47eac85c8

Bug: 24307555
Change-Id: If217226fd4f71c0c2ceb74732d8885cf4dc26ea6

Bug: 24679862
Change-Id: I62a1f790aba324d790c648fe184ef9926ceb3b5e

Change-Id: I5010bc0e12478bdc0c970dca7e96556dbb29fb86
Auto-generated-cl: translation import