The method MediaBrowserService.getBrowserRootHints can be called
inside of onSearch(), but the JavaDoc does not mention it.
This CL adds this information in the JavaDoc.
Test: Called getBrowserRootHints inside of onSearch method.
Change-Id: If82a371c8d06aab396e29141827c8991cff2cd3e
Atomic file requires sync between writers otherwise we may end
up with partially written settings file and no backup to recover.
Test: not testable by how we hold a mutex
bug:35915719
Change-Id: I97eebf869fa7e4989dcd2a29e4418c22706edcb8
1. Added a new API for a connected auto-fill service to
disable itself
2. Added a new shell command to destroy all pending sessions
which is used in CTS tests
3. Fixed a bug where the unbind timeout was in minutes
instead of seconds
Test: wrote CTS tests, all auto-fill tests pass
bug:35848030
Change-Id: I681605aa0b8c004a0f14e30b57117c291d89a894
This reverts commit 8e90cc3e3adf1d84b92b0b165193762cc8bb295d.
Both ANativeWindow and AHardwareBuffer need to be
available in libandroid (as well as libnativewindow)
otherwise it would make our developer’s life
very difficult when they want to support multiple
versions of android.
Moreover, this would have an impact on AndroidStudio
when doing an NDK project.
Test: compiled
Bug: treble
Change-Id: I2cc63b06b3f80fa80f7170ba2ba2996228fa9b2c
Stop relying on the file marker recorded by the runtime. We have the
same data available from the DexManager.
The clean up CL to remove the handling of the file markers will follow.
Test: verify that "shared packages" (e.g. gmscore) are not compiled with speed-profile.
Bug: 32871170
(cherry picked from commit 07b6eabe79261267ecd7114790e96e1f6828672a)
Change-Id: I2969b75fa77d38dde0073ef67aa89b1dc91237b5
Merged-In: I6cc5834ac88489e69896cd5fba9ed9968aa7f5a2
Pass '&' marker to dex2oat classpath when compiling secondary dex files.
This will skip class path checking when loading the oat files.
Test: adb shell cmd package compile -m speed -f --secondary-dex com.google.android.gms
oatdump --header-only --oat-
file=/data/user/0/com.google.android.gms/app_chimera/m/00000006/oat/arm64/DynamiteModulesC_GmsCore_prodmnc_alldpi_release
check that the class path contains the special '&' marker
Bug: 32871170
(cherry picked from commit aae35767b6bca6f872c906a0fd38d7adb61217bd)
Change-Id: I7f3c6743e749316ee02e8586a525ad28ae1ef765
Merged-In: If0628aeb4e3f5717604bfc4a87a4b1d438e5fa65
When we compute configuration changes to decide whether to relaunch
an activity or just report a coniguration change, we were calculating
task override changes and global changes separately. This results in
incorrect set of detected changes if we're moving between the
displays. E.g. when moving from secondary display to the primary
a lot of override config values change from empty to non-empty.
This CL switches to calculating configuration changes for merged
task configuration (global + overrides).
In this second version switched to not marking change to undefined
value as an actual change when comparing configuration, so it will
behave similarly to Configuration#updateFrom. If new configuration
with undefined value is applied to an old one with corresponding
value already set, it won't be overwritten to undefined.
Bug: 34164473
Bug: 35911519
Test: android.server.cts.ActivityManagerDisplayTests
Test: #testOnMovedToDisplayCallback
Change-Id: Ie1b90ccd2181aa5fdab4f57b9856e7de6959a6cb
