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
Currently, when we are connected to a wifi network without
Internet connectivity (e.g., a captive portal, or an access
point that's not connected to the Internet), we display the wifi
icon and hide the mobile network type icon. This is incorrect,
because all traffic is in fact going over mobile data. This
could cause nasty surprises if mobile data is metered.
Instead, make the icons reflect the true state of affairs:
- A wifi icon means device traffic goes through wifi.
- A wifi icon with ! means wifi is connected but has no
Internet and traffic is not going through wifi.
- Mobile bars with a network type (e.g., "LTE" means device
traffic goes through mobile data.
- Mobile bars without a network type mean that mobile data is
connected but device traffic is not going through mobile data.
- Mobile bars with ! mean that cell is not connected.
Bug: 17237507
Change-Id: I923edbeab3013f10314633c01922c8684591b15c
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
