This CL needs to be reverted after the issue is fixed, as it clutters
the code a lot.
Bug: 17439581
Change-Id: I548fdd73bbcd6d6ce727901f9dcd9f3f7268db9d
Instead of pulsing every 30 seconds to mimic the LED, use
a function that pulses more frequently for new notifications,
decaying to a slower pulse, and eventually stopping.
Specifically, the step function for the interval is:
- 10 seconds for the first minute
- then 30 seconds until the five minute mark
- then 60 seconds until the 30 minute mark
- then no pulsing at all
- Since we pulse more frequently on new notifications, remove
the "multi-pulse" concept.
- Move all doze-related duration parameters to a new helper,
backed by config, overridable by sysprops, include in dump.
- Wake up from dozing when hitting volume keys during a pulse.
-
Bug:17393939
Change-Id: Ica86f08b25c738338fced165c77faf3dfccd0343
Saves us some memory and more importantly, prevents layer trashing
and some skipped frames when building the layers.
Bug: 17287256
Bug: 16513124
Change-Id: Ief7c9a892da57bc77264de016f5118277e648f45
Since we actually only need to animate the yCoordinate in
the drag down motion, some clipping artefacts were left
in certain cases.
Bug: 17345758
Change-Id: I659a64b7ae5c7abcfa04c20347ec56a2d5f4f75c
Only intercept when touching on the panel and not on the left or
right of the panel. Fixes a bug where the user couldn't dismiss the
panel by tapping outside.
Bug: 17437547
Change-Id: Ice484a301683fa2df1f2a21f13977023b48189f4
When the QS panel was expanded, the Notifications and the
clock were not positioned, leading to a jump on the next
layout when any notification came in or was swiped out.
Bug: 17315258
Change-Id: I19276054e8c0a364a452d2041c1c4af858ba32b7
- When dozing, the first motion event triggers a wake up.
- Fade the backgrounds to ease the transition out of doze.
Bug:17167296
Change-Id: I5615ca0839dfa3ed2cf3001baf407c707f0676d5
When handleShowDetailImpl is called twice in quick succession (show
then not show), there is a race condition. If the second call comes
in before the animation finishes, the second call will call
setGridContentVisibility(true) before the onAnimationEnd callback
calls setGridContentVisibility(false). At that point the grid
is assumed to be visible when it isn't.
To fix this the HideGridContentWhenDone listener removes itself
as a listener when the animation is cancelled, this will avoid
onAnimationEnd being called in this circumstance, leaving the grid
visible (as it is assumed to be).
Bug: 17424221
Change-Id: I67b84b669ebe0e061e4a2c7f98e8151c221ee4fb
