There where 2 different issues which could lead to the dozemode
not working correctly:
1. The new workarabout where we show the expanded notification
if it has the same size as the collapsed, requires that dozemode
is also called on the right notification
2. When the children were not layed out yet, this calculation could be
wrong and the wrong child was selected, leading to the same issue.
Bug: 26459664
Change-Id: Ib67dcaf2ba9b8b9a1bfa5ece5b7d6c4dff677939
Group children are now isolated into their own group for a few seconds
until it's merged into the group again when they are
heads upped. This makes notifications groups finally usable with
HUNs again.
Change-Id: I0cb5e4f7a70e09989030dfe70ddcbb50575c1c02
When pulling down on a heads up notification the scrim would
fade in from 0 instead of fading to the new position.
The old behavior didn't work if the heads up notifications were
big, so we had to change it in order to always have a scrim.
Change-Id: I9ae387b75136c9240d863e06a8649c85b3c6c9dc
Heads up notifications can now be expanded with the expand
button. The notification stays there until the user dismisses it
or collapses it again.
Change-Id: I0f1b729915317bbbd6f13c3d968c933ffbe6feeb
- Should be updating the app text color to match the activity text color
- Fixing issue with indicator showing when fast toggle is disabled but
the indicator flag is enabled
- Tweaking layout so that the buttons are flush with the borders so that
we capture the full area for press/long press
Change-Id: Ia9b081883562ef4fd1c01fd42bc786a1feeb0854
When going from fullscreen to non-fullscreen configuration, task config
changes was always non-zero because in fullscreen, task override config
was empty. Instead, use the actual previous configuration to calculate
diff.
Also make recents handle screenLayout changes.
Bug: 26593320
Change-Id: I57633d60b1e0fc4ae506e276410191a44e1fe221
* changes:
Adding reveal transition to show app-overlay.
Fixing issue with multiple focus timer animations running.
Fixing several regressions with affiliated tasks.
Starting the dismiss animation in parallel with the gesture.
- Instead of long-pressing the icon to launch into app info directly,
this will mirror notifications and reveal a space that can show the
app name and a link to app info.
Change-Id: I91c5839719b030a65744f5e677a436e9c719c578
- Now that we are sorting tasks for freeform and history, ensure that
the affiliated tasks have a useful active time (based on the task
they are affiliated with) for sorting
- Fix issue with the initial stack and focus state not taking the
launch task into account due to the launchTask flag not being set
until the activity was started (now set in RecentsTaskLoadPlan)
- Fixing issue with affiliated tasks not being launched from the stack
due to the animation trigger not firing when the action button is
already hidden/visible
- Fixing issue with title text being occasionally hidden (something we
only need for freeform tasks)
- Tweaking the launch/enter animations for tasks occluded affiliated
tasks
Bug: 26685208
Change-Id: I0f6e9dbf8deec2e4fc15364e686367cc0f57b41f
- Introduces notion of ignored tasks for the purposes of layout in
TaskStackView. This can be used during drag and drop, and while
dismissing to calculate the state of the stack without the task that
the user is currently interacting with.
- Fixing minor layout issue when the front/back task transforms are
improperly calculated when there is a single task
- Fixing minor issue when the anchor task is calculated incorrectly when
dismissing task views
Change-Id: I1eb0864a52e53562e4d573a6ed4f8a5a1615aff9
CarNavigationBarView extends NavigationBarView and provides a different
layout for the navigation bar which does not include all these buttons.
As a result, SystemUI will crash.
Change-Id: I1be079814faa26925721ec86a6f108506f54b99e
The full screen user switcher wasn't needed by the original
author so adapt it for the auto use case because it fits
really well. This change adds in some legal text (TBR - legal)
and tweaks the layout a bit.
Bug: 26559008
Change-Id: Ib78d0ec8a8d4ec8411dbbffe5852c5307c2cf42f
When there was a state change or layout when there was an animation
set as the mobile icon in the status bar, we never stopped the old
animation, which was infinite. This was using more and more CPU because
the animations never got stopped.
To fix this, we don't update the drawable when a layout happens and we
stop the previous animation when replacing the icon.
Bug: 26616870
Change-Id: If501155d1a99d587e50a1b77ebb03a21c940662b
Improve general status bar goodness, more exactness, less breakage.
Extra extra icons, disabled by default.
Control all the status bar things!
Probably other stuff (10000).
Change-Id: I5d6282a4dcbcefea9f0880042cdf6293cb693712
- Removing calls to ensureCapacity, which was causing reallocations when
using a temporary set with multiple uses.
- Fixing issue with update callback not being called when immediately
updating a TaskView’s transform
- Adding utility methods in preparation for refactoring code
Change-Id: If62c3751ed6af15092a34435df08bb4d627536ea
- This happened because the RecentsView had the same priority as the
touch handler, which updates the visible dock states, which RV uses
to determine what to draw, resulting in the first time after rotation
to not show the right targets. The touch handler should now have a
higher priority than the view that depends on it.
Change-Id: I9441e34f677fe105757c237db0f6970e7cf8203b
