This reverts commit c2817ca17f.
Reason for revert: DroidMonitor-triggered revert due to bug b/222503182.
Change-Id: I8ab687811b7b0a76587bcb0903055ebbc35f729a
A PackageState doesn't always have an AndroidPackage, so we need to do a
null check.
Fixes: 222474286
Test: presubmit
Change-Id: I1603f3cb096a72f65360db2ab7d8ff5823c28e0d
The standard dynamic range profile will always be present as part of the
advertised profiles. Additionally the same profile must never advertise
extra latency due to the format selection.
Bug: 215396395
Test: Camera CTS
Change-Id: I0ad7dd23a1b1f742293b4c52a48a8fca98b7925c
Update the WebSettings.setUserAgentString API docs to explicitly specify
the effect it has on user agent client hints and related JS APIs.
This is not a behaviour change for WebView, just making the docs
describe what already happens.
Test: make offline-sdk-docs
Change-Id: I2db282efc4ee42b931824175abe627e871c4a86c
Much usage of isManagedProfile should probably really be isProfile instead, so have the javadoc explicitly point to it.
Bug: 170249807
Change-Id: Ia6c3cc6d052f2b9f6581fd160410b9ef601c3bcf
Test: N/A (just doc)
It seems like when shell transitions is enabled, the recents input
consumer's touchable region was not set up properly. It could have been
relying on the previous behavior of an input window being touch modal by
default. Now that we have removed touch modal from input, ensrue that
the touchable region is correctly set for the recents input consumer
when shell transitions is enabled.
Bug: 216806304
Test: presubmit
Change-Id: I93c07c992b0b4e9b61c694a18fae99da73deadef
Re landing with the following changes:
We initially cloned the SurfaceControl handle to avoid locking when
accessing the SurfaceControl from the position listener callbacks
running from RT workers. But this meant the last reference to the
layer handle would only be released by GC. If SurfaceViews are
created and destroyed rapidly, we would be at the mercy of GC to
release buffers.
Original change:
There are three transaction queues that can submit SurfaceView
changes.
1. Buffer updates via BBQ apply token
2. SCC apply token
3. ViewRootImpl BBQ apply token
It makes sense for most SurfaceView changes to be synchronized with
ViewRootImpl draws since the caller can optionally synchronize the
change with main window content.
This change eliminates the tmp transaction that is applied directly
via the SCC apply token and instead applies them with the ViewRootImpl
draw transaction.
Also take the opportunity to scope down mSurfaceControlLock usage.
Test: atest SurfaceViewSyncTest
Test: go/wm-smoke
Test: run mem tests via forrest
Bug: b/217973491, b/221631942
Change-Id: Idba712d146e62d7346920dc4f060cba92d47fada
Fixes: 212467440
Test: atest OngoingCallControllerTest
Test: verified clicking the chip can still open valid activities.
Change-Id: I7707d01be37582461227edcecf5d559f2019c8a5
In order to test MODULE_LIBRARIES System APIs, the
@TestApi annotation needs to be explicitly added. Also adds
some whitespace changes which were autogenerated when
updating the APIs. Also renames Process.toAppUid().
Test: atest ProcessTest
Bug: 218723058
Change-Id: I49bee200c267550b9616ad0b43022126d2d7cc4b
