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
When loading DocumentsUI in management mode (for Downloads), we
normally focus on a single authority and let the other providers
keep loading async. However, when one of the providers kicks a
change notification, we end up blocking the main thread.
Simple fix is to move the blocking into the AsyncTask.
Bug: 17452691
Change-Id: Ie5212ad825b7df719690b29941c9ae9ba2cabe4b
1. Leftover code was setting the state to configuring
before initialization is complete.
2. We were not cancelling the print job if cancelled
when initializing.
3. The remote print document was cancelled even if
doing nothing.
bug:17451600
Change-Id: I79a80b723af8537da260012470748b4e8831fd9e
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
This was especially noticible when double tapping a notification
because of the staggered appearing.
Bug: 17287256
Change-Id: I8f39892fa122bb8b7b6f2a7b1e7be8a9570e661e
