If a system VPN app specifies in its meta-data that it should use the system's
branded VPN icon instead of the standard one, the Quick Settings footer and
status bar show it instead.
Bug 27146125
Change-Id: I3cfe4dda156d9147bdb339ba6bce82c72ca7393d
Making mZenModeController in PSB protected.
Bug: 27101250
Change-Id: Ibb3e66fb59b245aa293bbc32d1c1009ac1a0499a
(cherry picked from commit ac72fc49227fc02a919827a877637df4b0a65cf0)
Make mQsExpansionEnabled protected in NotficationPanelView.
Bug: 27836776
Change-Id: I35479e990607d6801effd3fa64fd3ffb1f9503dd
(cherry picked from commit 8af5736425d60641268943fe4d7e23a2b7d99c8a)
am: 2f1b6bc
* commit '2f1b6bce0a47b20cc51911c6e95116578443fb1c':
Fix config change layout. (Part 2)
Fixing issue with tasks being laid out with the wrong bounds.
Launch state/config change audit. (Part 1)
am: 67533ee
* commit '67533eea19f58809c608fa28a3fedd092d06e5ef':
Fix config change layout. (Part 2)
Fixing issue with tasks being laid out with the wrong bounds.
Launch state/config change audit. (Part 1)
- Fixing issue where the initial state was not correct after rotating
the screen. We needed to update the layout, but that could only be
done after the task stack view is laid out. Now we set a flag to
update the initial state of the layout on configuration change, and
only scrolling to the front when it makes sense.
Change-Id: I2586b90d1e869708b97bcd1a4446f4d87fa521cc
- When hovering over a drop target, we update the stack bounds, which
changes the task rect. If we happen to pick up new tasks and measure
them during this point, they will be measured with the wrong rect, and
once you stop dragging over a drop target, they will not have the
right bounds.
Change-Id: I6711152878a4afd48518e01477fd793a4c132648
- Fixing issue with onResume logic being run even when the window focus
is changing. This only needs to be run when we are launching into
Recents again.
- Removed a bunch of launch state flags that are no longer necessary
because of changes to configuration handling. This reduces the work
that we have to do on resize, etc.
- Decoupled the resume with the stack-update, which fixes a couple
issues where we were updating the layout unexpectedly.
- Fixed an issue where we were not updating the nav bar scrims on
configuration change
- Fixing margin start/end regression in header bar
- Fixing small issue with paddings being scaled beyond their base size
- Fixing issue where the clip state was not properly getting reset
causing lots of overdraw.
Change-Id: I9aeb191a99ff23807b3f5d905f6480b10157a060
- Fix calculation on which side to apply dimming.
- Fix dismissing parallax logic for new resize handling.
- Remove wrong/unnecessary resizeStack call
Bug: 27738239
Change-Id: Iaac671ca03e19aa70fa779d319b5fe84ff3b40ba
am: ea42b59
* commit 'ea42b59a06f27b9ba282b448aec1d93436221711':
Implement transition for docking task in recents #6
Implement transition for docking task in recents #5
Implement transition for docking task in recents #4
Implement transition for docking task in recents #3
Implement transition for docking task in recents #2
Implement transition for docking task in recents #1
Show a scrim activity if task is not resizable
am: a04c532
* commit 'a04c532a09b8d946ebc9a086f673220059218869':
Implement transition for docking task in recents #6
Implement transition for docking task in recents #5
Implement transition for docking task in recents #4
Implement transition for docking task in recents #3
Implement transition for docking task in recents #2
Implement transition for docking task in recents #1
Show a scrim activity if task is not resizable
* changes:
Implement transition for docking task in recents #6
Implement transition for docking task in recents #5
Implement transition for docking task in recents #4
Implement transition for docking task in recents #3
Implement transition for docking task in recents #2
Implement transition for docking task in recents #1
Show a scrim activity if task is not resizable
- Use a future to provide the app thumbnail so the app can restart
in parallel when recents draws the bitmap (extremely expensive).
- Don't call startRecents from AM when recents is already running - this
messes up the transition information.
- Make sure to put the task into resizing mode if it needs to be restored
from the disk.
- Some minor fixes for the transition animation spec.
- Add NO_MOVE_ANIMATION to recents flags to prevent wallpaper
flickering.
Bug: 27607141
Change-Id: I7d0c75b88775ab467927b8cf94303ddb60222e7f
- Put window into resizing mode when docking it from recents,
so it fills the "void".
- Send whole task bitmap window as the thumbnail, to make
the transition smoother.
Bug: 27607141
Change-Id: Ib647d44d9777f1155deab818d1fd5425c1bdd3d1
- When the docking transition is happening, defer updating
the bounds of the home stack until the transition is done.
This is to preserve the scrim which is drawn in the recents
activity.
- Use the PROLONG_AT_START infrastructure to hide the task
in recents when starting the app transition.
- When recents finally get resized at the end of the transition,
reset it's draw state so we don't move the old surface around,
and the new surface gets drawn at the new position, to avoid
flickering.
- Remove hack around not layouting docked divider if it's not
visible, it's not needed anymore and resulted in a wrong
initial position.
- Fix animation selection for docked stack divider.
- Make sure win.moved() always gets called.
Bug: 27607141
Change-Id: I76c35f09461f044a90e2c88335008284b5839cc0
