This reverts commit a6e524e127.
Reason for revert: should not use current pipBounds as reentry bounds when the bounds are temporarily expanded due to active menu
Bug: 170748861
Change-Id: I26a2ce4d9fb70db051b941ff09cdb423513b9ffc
Currently, when an out PIP transition happens we combine:
(1) the last user resized bounds, plus
(2) the out pipBounds fraction (mLastReportedBounds)
Using both we create the reentry bounds used to restore
on reentry.
This is actually unnecessary since ag/12307605 and
ag/12309037 both landed. They landed as separate
efforts fixing different issues almost at the same time,
so we didn't realize that getting the last user resized
bounds was no longer necessary with the safe
mLastReportedBounds (i.e. pipBounds) passed into
onPipTransitionStarted.
The pipBounds argument is equal to the last user resized
size with the current fraction applied, so there's no need
to re-calculate it, we can just use it directly.
Bug: 169373982
Test: enter/exit pip and resize multiple times to verify the
reentry size is correct.
Change-Id: I2517d10bfbc8ca9c15b08b32089bdeeb1dd3aab6
If we enter immersive mode (that is, SystemBar is hidden due to
transient mode), inset from that system bar is not applied even when it
becomes visible.
To fix this, we are applying window inset to fit ignoring the visibility
of the system bar. Each overlay view can opt-in to use this functionality
by overriding shouldUseStableInsets's return value to true. It can also
use conditionals to change its return value dynamically (e.g. depending
on whether the IME is visible. See NotificationPanelViewController.)
Bug: 169612767
Test: Manual (see screen shots)
Change-Id: I9d0c460bd3b521f9e334c3f7c9d304e68593b6da
Fixes: 168260114
Test: refactoring, manually enabled security logs, compared with the previous version
Change-Id: I36f4939386b57130767860c13ea2816873f9f46a
Adds the initial API stubs for checking a device's Ultra Wideband
capabilities.
Bug: 170323306
Test: Builds
Change-Id: I6bd58a5fcee1deb151f2120ad3b18f5f7554ae8f
* changes:
Upgrade AndroidFrameworkBinderIdentity to fatal.
Tighten up Binder.clearCallingIdentity() usage.
Tighten up Binder.clearCallingIdentity() usage.
Tighten up Binder.clearCallingIdentity() usage.
Fixes: 169414761
Test: Manual
Test: Add package A
Test: Verify package A exists
Test: Remove A, add package B w/ original-package A
Test: Verify package A exists, but codepath is to package B
Test: Replace package B w/o original-package A
Test: Verify package A removed and package B added
Change-Id: I198ca545f4fea3ae9d2328a845cbd9167eedf8da
Merged-In: I198ca545f4fea3ae9d2328a845cbd9167eedf8da
Revert "Update multi display for new launch mode."
Revert submission 12141146-Same activity in display
Reason for revert: Seems there was a merge error breaking master.
Reverted Changes:
Ic3e5e90ae:Update multi display for new launch mode.
I8344f239e:Use same display for activities in same process.
I697d63ed2:Update car launch params modifier.
Change-Id: I248a4dd160b9af64e9761494892927b42083233e
