The primary purpose of validate_framework_keymaps is to perform checks
on all *.kl, *.kcm, and *.idc files using the "validatekeymaps -q"
command. This action can be replaced by using a genrule.

Bug: 318785074
Test: m validate_framework_keymaps
Change-Id: I657466d7ee2cec29900beeb0610cb0d30f34f92e

Settings app needs to retrieve and publish update info from
SystemUpdateManager. This is needed to install 16k developer option
update which enables users to use 16K kernel from local OTAs.

Test: m Settings && adb install -r $ANDROID_PRODUCT_OUT/system_ext/priv-app/Settings/Settings.apk
Bug: 302391134
Bug: 295035851
Change-Id: I89e30a8fc7e753f41c70e3ddbf759fb63ea97bd5

We don't have a way to determine if devices can actually report HID
usage keys. Marking them as fallback only.

Bug: 297094448
Bug: 317838112
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:45f626a154f66f4cceecaf6e32392741a00529a3)
Merged-In: I45710f9e6237c86613717fab779dbd7cc5c66c86
Change-Id: I45710f9e6237c86613717fab779dbd7cc5c66c86

Bug: 309313071
Change-Id: I4fc6132adcb134576df1b846859c273a8bbd5d26

Defines permissions for guarding access to Thread network API.

The permissions are also granted to shell for CTS tests, see the
instructions here: go/ctswrite#write-a-test-to-test-an-api-that-requires-system-permission

Design doc: go/thread-android-api

Bug: 262683651
Merged-In: Ib15d5589bbd304d68840ee52a193676d12110512
Change-Id: Ifc6c1d55cc170a5a200dfb5d531f5e0f86a9507a

... until we figure out a way to determine if a device supports a
specific HID usage code. Right now, having a usage code mapping means we
automatically assume the device can report the key code. Assuming a
device can support a stylus keycode makes the device get classified as a
stylus, leading to widespread misclassifications.

Bug: 291529805
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5fb192aaec7a1d4ebb1384d96b3f79d4b2ca2f2c)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:55930e07d69fbd8ffd27d677a06fd0ba71a30bf8)
Merged-In: I580514bdcbbfbe93df83fa3faa6262077e881243
Change-Id: I580514bdcbbfbe93df83fa3faa6262077e881243

Otherwise the client won't report finishRelaunching to decrease
mPendingRelaunchCount and cause ActivityRecord#isSyncFinished
to return false.

Also skip pre-loading recents(home) if its process is still cached
(e.g. intermediate state when switching user). Otherwise the
transaction may be failed by frozen state.

Bug: 301034389
Test: atest RecentsAnimationTest#testPreloadRecentsActivity
Test: Create multiple users with using different font size, wallpaper,
      dark theme. Launch several apps on each users. Switch between
      the users multiple times. There won't be transition timeout when
      returning from other apps to home.
Merged-In: Ia2761e1e9fadf98ab952440ae884c12cc78697c8
Change-Id: Ia2761e1e9fadf98ab952440ae884c12cc78697c8

Aside from resizing the VirtualDisplay from MediaProjection#createVirtualDisplay,
an app may also set a new output surface on the VirtualDisplay. This output
surface is where the mirrored layers are rendered out to, so we must transform
the mirrored layers in response to any Surface size changes.

Bug: 300481174
Test: atest WmTests:ContentRecorderTests
Change-Id: I062379b9d702fb2c3a13e5442ee14036d1a31637

Bug: 300481174
Test: checked logs
Change-Id: I52c62c5c5e09d2e4aa9c37b23b4ef645cf98bc7b

To avoid malformed transformations due to inaccurate bounds
when the task is in PIP. pause recording entirely when the
task enters PIP and resume when the task leaves PIP.

Bug: 297514518
Test: atest WmTests:ContentRecorderTests
Test: manual MediaProjection smoke tests, change windowing modes
Change-Id: I92ba7a211d0c719e60d8a397f2ba1b250903eb01

it is added to the vendor partition.

Bug: 212639052
Test: press the assist button, check that keyboard
Test: events are delivered to the guest (`adb shell getevent -lt`)
Test: and the asistant window appears.
Change-Id: I1b836b975df2fc46383b3f83a6276936874bfea9
Signed-off-by: Roman Kiryanov <rkir@google.com>

Attempted comparing orientations from different enums; manifested as wildly
incorrect transformations when handling a rotation & the virtual display
is resized.

Bug: 289976187
Test: atest WmTests:ContentRecorderTests
Test: manual check full display & single app capture with rotations
Change-Id: I10b03c5169a03b6540181b4bc4a3f47fa421f675

... until we figure out a way to determine if a device supports a
specific HID usage code. Right now, having a usage code mapping means we
automatically assume the device can report the key code. Assuming a
device can support a stylus keycode makes the device get classified as a
stylus, leading to widespread misclassifications.

Bug: 291529805
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5fb192aaec7a1d4ebb1384d96b3f79d4b2ca2f2c)
Merged-In: I580514bdcbbfbe93df83fa3faa6262077e881243
Change-Id: I580514bdcbbfbe93df83fa3faa6262077e881243

Test: atest 'CtsSecurityTestCases:android.security.cts.ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions'
Bug: 286882367
Bug: 290586831
Bug: 237290578
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0be0367ece4d946de576f7bb1e6e6777633a736d)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:8bddf5091e0bf4e8252abc66169a7bcc9459001a)
Merged-In: Iffe5625ae57c21874805ef98b67faac9f56f87f5
Change-Id: Iffe5625ae57c21874805ef98b67faac9f56f87f5

This is necessary for the settings app to set the bt audio device type
on the AudioManager.

Test: manually set the bt audio device type
Bug: 287011781

Merged-In: I4978b56091b1132f112d4ddec500710964854ec7
Change-Id: I4978b56091b1132f112d4ddec500710964854ec7

Bug: 290540247
Test: N/A
Change-Id: Ic3cc9ecff0d27e973925addb7cf4a87a430c2666

Revert submission 23792411-pss-new-chooser-qpr

Reason for revert: Additional dependency collided with ongoing
development. Most of the a11y bugs motivating this seem to be specific
to partial screenshare, so this ended up adding cost to Chooser
development without clearly solving the underlying issue.. Need to
regroup on a more sustainable solution to this.

Bug: 294040231
Test: Presubmits

Reverted changes: /q/submissionid:23792411-pss-new-chooser-qpr

Change-Id: I3a8be177fdd93fc7414e610019476ceeb40c9e7d

The old one in the framework is deprecated, and not developed anymore.
Partial Screen Sharing is the only thing still using it, and preventing
it from being removed.

There also bug fixes and improvements in the new one, that the Partial
Screen Sharing feature would benefit from.

Bug: 265905535
Test: MediaProjectionAppSelectorScreenshotTest
Test: Manually build and run to trigger the app selector
Change-Id: Icbc5b3bcf641288e12fc99973d8dae3467256a2c

Test: atest 'CtsSecurityTestCases:android.security.cts.ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions'
Bug: 286882367
Bug: 290586831
Bug: 237290578
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0be0367ece4d946de576f7bb1e6e6777633a736d)
Merged-In: Iffe5625ae57c21874805ef98b67faac9f56f87f5
Change-Id: Iffe5625ae57c21874805ef98b67faac9f56f87f5

Test: atest 'CtsSecurityTestCases:android.security.cts.ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions'
Bug: 286882367
Bug: 290586831
Bug: 237290578
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0be0367ece4d946de576f7bb1e6e6777633a736d)
Merged-In: Iffe5625ae57c21874805ef98b67faac9f56f87f5
Change-Id: Iffe5625ae57c21874805ef98b67faac9f56f87f5

Not to break the apps that reads fonts.xml and add new features to
the system font customization at the same time, this CL introduces
new hidden XML file font_fallback.xml which is currently a copy of
the fonts.xml.

The fonts.xml still exists but may not contain the latest system font
settings due to compatibility problems. Application should use the
public API for accessing system installed fonts which is available
from API29.

Bug: 281769620
Test: atest CtsGraphicsTestCases
Test: atest CtsTextTestCases
Change-Id: I556b5fffb0c78f0c6150b472fd240b9a546de93f
Merged-In: I556b5fffb0c78f0c6150b472fd240b9a546de93f

Test: atest 'CtsSecurityTestCases:android.security.cts.ActivityManagerTest#testActivityManager_stripTransitionFromActivityOptions'
Bug: 290586831
Bug: 237290578
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:0be0367ece4d946de576f7bb1e6e6777633a736d)
Merged-In: Iffe5625ae57c21874805ef98b67faac9f56f87f5
Change-Id: Iffe5625ae57c21874805ef98b67faac9f56f87f5

Bug: 290924390
Test: builld successfully
Test: flash aosp_mokey_go32-userdebug and go to settings,
      battery saving mode is fixed at unrestricted for dlc
Change-Id: I7a5be87b89b4f31e10e0b9c0d5fca21ed40f9f92

Map MAGIC button HID key from Google Reference RCU to Android
keycode KEYCODE_MACRO_1 for the MAGIC / customizable button
feature.

bug: 279825318
test: manual
Change-Id: Ic4705f0798ba1630297da83d3bc300afb27d0ad8
(cherry picked from commit 798f9f54)

To add more clarity and improve the user experience, introduce a new
toast string (to replace 'display_rotation_camera_compat_toast_in_split_screen')
which includes the app name so it's clear to the user which app to
relaunch in full screen.

Fix: 282782484
Fix: 267372967
Test: atest WmTests:DisplayRotationCompatPolicyTests

Change-Id: I07a0dc182ba46240449f2b12619c466f7484af06

Bug: 273483670
Test: locally tested.
Change-Id: I49a59ab8688aaf193a79c610738a1db951f2bfdf

This is necessary to allow NetworkStack to identify whether
a connection was setup trough an enterprise-managed configuration,
by querying DevicePolicyManager. Some behavior specific to
enterprise networks require NetworkStack to differentiate this case.

Bug: 189865016
Change-Id: Iaeb91ebf9cccce8bf630fab5d1883473247b4def

Bug: 235303866
Test: Manually done
Change-Id: I8324c16fa8c392163e81fb9f4c21bba3343b6df0

- Currently, a display change while recents transition is playing will
  result in the display change being applied prior to the recents
  animation playing, which means that the transition-end snapshots are
  taken in the wrong display configuration
- Instead, When a display change is requested mid-recents transition,
  cancel the current transition and record the snapshots in place
  (this matchs legacy recents animation behavior)
- Separately, if the snapshot is requested & recorded mid transition,
  then we can ignore the post-transition screenshot (which would be
  wrong in the display change case, or just extraneous even in the normal
  case where launcher has requested a screenshot itself already).
  We do this by comparing the time that the last snapshot was taken
  with the start of the transition.

Fixes: 278189494
Test: Go into Overview and rotate the device and observe the task views
Change-Id: I985cd9c852a326027ae3ab4f7ffe837431d1c654

When a host app re-uses a consent token, protect the user's data
by ensuring no frames are sent out until the user has reviewed
the permission dialog.

Test: atest WmTests:ContentRecordingControllerTests
Test: atest WmTests:ContentRecorderTests
Bug: 271323540
Change-Id: I0451ac709b64414fc75f3dfbca5a3dbe9244682d

The VirtualDisplay may have already been removed by the time WindowManager
attempts to handle an incoming recording session. The returned DisplayContent
is then null.

Bug: 280596594
Test: Manual; no NPE when screenshot from Betterbug
Change-Id: Ie956a6b6fea0efd5bd35afa0f73b415a7f6ca346

We used to refresh the activity only if the display rotation configuration was changing and the treatment was allowed. Now we are also refreshing the activity after stronger letterboxing (split screen aspect ratio is used for the camera activity). This is needed because we want to keep applying the camera compat treatment when the activity is resumed.

Fix: 277818827
Test: atest WmTests:DisplayRotationCompatPolicyTests#testOnActivityConfigurationChanging_splitScreenAspectRatioAllowed_refresh
Change-Id: I61b807f18dc89582c9e1634cd533b1fa9e364d32

IntentRedirection

Earlier the permission was being checked with system server's pid and
uid as we were clearing binder identity for finding the values of
AppCloningBuildingBlocks flag. Because of this the check was moot,
moving the check out, so that it uses callers pd and uid.

Bug: 281738146
Test: atest com.android.cts.appcloning.IntentRedirectionTest
Change-Id: I62642d2c7cd76912ae800b02688cdc91d1a78214

When satellite is enabled by telephony (phone process) it needs to confirm that UWB gets disabled as well (UWB is listening for satellite enablement and disables itself). In order to register to get the UWB state states phone needs UWB_PRIVILEGED permission

Bug: 275415823
Test: atest SatelliteManagerTestOnMockService, Flashed on raven-userdebug: SMS and calls are working fine.
Change-Id: I82c906c429df8b763dea09b1ee249b09e22e26b6

Bug: 277637274
Test: atest GtsCredentialsTestCases

Merged-In: I2b805541a998160313724d24ac1ba9a826fd1d25
Change-Id: Idcfa91f140fa9aa006f93baec805183998459024

This supports wifi scanning.

Fixes: 278310605
Test: compiles
Change-Id: I275adeaabb9fcda27ed66ab05442b48d4ac4613f
Merged-In: I275adeaabb9fcda27ed66ab05442b48d4ac4613f

Bug: 276367261
Test: gts-tf > run gts-dev -m GtsAttestationVerificationDeviceSideTestCases (with local changes to turn off boot state check)
Change-Id: I18d2f77291d0b6ae7f12acecb5b786c9d3657abf
Merged-In: I18d2f77291d0b6ae7f12acecb5b786c9d3657abf

We can't fully support parallel transition collection,
but we can for specific cases (like recents). This CL
adds some hard-coded checks for recents specifically and
allows it to collect in parallel with activity-only
transitions. This is basically way of assigning "priority"
to recents since it is a very user-forward operation
and an integral part of how users percieve device
performance.

Bug: 277838915
Bug: 264536014
Test: In the running task, launch a slow-to-draw activity,
      then swipe to recents or home. It should not wait
      anymore.
Change-Id: Ie09e31bf290847b108578b688f57360536fe7f4e

Validate if the IMediaProjection token (representing
the user's consent) is used to get more than one
MediaProjection instance, or if client app is trying to
invoke MediaProjection#createVirtualDisplay more than
once.

Re-show the permission dialog for target SDK below U.

Follow-on CLs will:
* Black out recording when waiting for consent

Bug: 274790702
Test: atest FrameworksServicesTests:MediaProjectionManagerServiceTest
Change-Id: I30c96d9a9afd69fba29314caeeb867f665bb83ad

This is a best-effort attempt at supporting simultaneous
active sync-groups. It is best-effort because WM is not
transactionalized so we can't really control what goes
into what sync.

For this initial version, parallel syncs must be explicitly
requested. Starting a sync-set that is NOT explicitly asked
to be parallel while an existing sync is active will throw.

Currently, a parallel syncset will ignore "indirect" members.
This means that it will only wait on members that are directly
added to the syncset instead of waiting on the whole subtree
rooted at the added members. This logic only applies to anything
above Activity level. Activities will still wait on their
children regardless since WMCore generally considers anything
inside activities as "content".

In the future, we will probably have to separate "parallel" from
"ignore-indirect".

"ignore-indirect" enables syncs to run in parallel across levels
even if they are part of the same subtree: for example, if an
activity is in one syncset and that activity's task is in another
syncset, the task doesn't need to wait for the activity to finish
and vice-versa.

To handle uncertainty, though, the syncs need to revert to
serializing with eachother if they contain non-ignored overlapping
sub-trees. This is achieved with the addition of a "dependency"
list. If we have SyncA and SyncB active simultaneously, and then
try to add a container to SyncB which is already in SyncA, then
a dependency will be added to SyncB on SyncA instead of the
container. This forces SyncB to wait on SyncA to finish. Cycles
are resolved by "moving" conflicting containers from the dependent
into the dependency so that there is only one direction of
dependencies.

When parallel syncs overlap, the readiness-order is:
first - dependency
second - in order of start-time.

Bug: 277838915
Bug: 264536014
Test: atest SyncEngineTests
Test: this change, alone, should be a no-op so existing tests too.
Change-Id: Iebe293d73e2528c785627abd5e4d9fd2702a3a64