- Currently, any touch after a quickswitch within an app window will be
  construed as a reset of the frozen task list, however we allow users
  to quickswitch multiple times whenever touching within the mandatory
  system gesture region, so we should also ensure that touches within
  that region are also ignored.
- Also add protologs for when we set/reset the frozen list

Bug: 320408763
Test: Quickswitch, but touch above the nav handle and within the
      system gesture region, verify this does not trigger resetting

Change-Id: Ie8dd880eb2b45812d5b72ec1ae1c23e28ba02250
Merged-In: Ie8dd880eb2b45812d5b72ec1ae1c23e28ba02250
Signed-off-by: Winson Chung <winsonc@google.com>

- Currently, any touch after a quickswitch within an app window will be
  construed as a reset of the frozen task list, however we allow users
  to quickswitch multiple times whenever touching within the mandatory
  system gesture region, so we should also ensure that touches within
  that region are also ignored.
- Also add protologs for when we set/reset the frozen list

Bug: 320408763
Test: Quickswitch, but touch above the nav handle and within the
      system gesture region, verify this does not trigger resetting

Change-Id: Ie8dd880eb2b45812d5b72ec1ae1c23e28ba02250
Signed-off-by: Winson Chung <winsonc@google.com>

This reverts commit 4c4b02c0.

Reason for revert: Already submitted in ag/27435263

Change-Id: Iddf22c98c3fc7edf8502da59de8ed10f8ca4c14b

Remove unnecessary code, no logic change.
Also remove testTransferStartingWindowWhileCreating, it is impossible
to have such code path since there won't create starting window inside
core anymore.

Bug: 341054451
Test: presubmit
Change-Id: I3a27952160bc26bd9618ce96e5c692c78d0983b2

Similar to TaskOrganizer, this supports being able to
register/unregister transition players in a lifo manner.

This will enable integration tests to register a transition
player temporarily and then unregister to restore the
original state.

Bug: 341009477
Test: Existing tests
Change-Id: I011095a35e1c4ea14c3a8fa1abf3576041338705

This allows the refresh state to be reused in other camera compat classes.

Bug: 314960895
Test: atest WmTests:DisplayRotationCompatPolicyTests
Test: atest WmTests:ActivityRefresherTests
Change-Id: If3503d07c45b324fea427f8f820ee467d912c46e

Some popular keyboards have keys that use standard HID usages (as
defined in https://usb.org/sites/default/files/hut1_3.pdf) that
are currently not defined in Android. This change adds the ones
that have been identified so far.

Bug: 287638533
Bug: 287642278
Bug: 287642922
Bug: 287640783
Test: Confirmed that the language switch, settings, emoji picker,
      recent apps, refresh and all apps are now properly
      recognized by testing on a Logitech K650 keyboard in
      ChromeOS mode (Fn+C for 3 seconds).
Flag: EXEMPT resource only update
Change-Id: Icfa5be11b33059c44bc4cb5d838b503d23f90464

Change-Id: If71c545f1a73a86ceb40ef94bf0ae272b672b144

Bug: 337002764
Test: Manually verified on some games
Change-Id: I18d4272bf8ead5f76da5aea4f0af6a48ee6eb8cf

Bug: 312667804
Test: Manual
Change-Id: Ie3b7ba4c32a06bcbce4975acd1fab280fed3b658

So far, we have used `instalable: false` to avoid collision with the
other modules that are installed to the same path. A typical example was
<foo> and <foo>.microdroid. The latter is a modified version of the
former for the inclusion of the microdroid image. They however both have
the same instalation path (ex: system/bin) and stem (ex: foo) so that we
can reference them using the same path regardless of whether we are in
Android or microdroid.

However, the use of `installable: false` for the purpose is actually
incorrect, because `installable: false` also means, obviously, "this
module shouldn't be installed". The only reason this incorrect way has
worked is simply because packaging modules (ex: android_filesystem)
didn't respect the property when gathering the modules.

As packaging modules are now fixed to respect `installable: false`, we
need a correct way of avoiding the collision. `no_full_install: true` is
it.

If a module has this property set to true, it is never installed to the
full instal path like out/target/product/<partition>/... It can be
installed only via packaging modules.

Bug: 335369205
Bug: 337993945
Test: m droid aosp_cf_system_x86_64
Change-Id: If9c053968bde39c3eb3b852f1df1d475161bd846

This CL still keep PRODUCT_COPY_FILE for the original system image
packaging for Make, but create 3 soong's modules which could be used for
soong generated system images.

Bug: 337993945
Test: lunch aosp_cf_x86_64_only_phone-trunk_staging-userdebug ;\
      m aosp_cf_system_x86_64 ; m
Test: lunch yukawa-trunk_staging-userdebug ; m
Change-Id: Ie749de99273f85623861a001e69a9c4187cc8067

This reverts commit fd803f55.

Reason for revert: This change break most of the tv targets. Please test building cf_x86_tv_gtv

Bug: 338497361
Change-Id: I5e9063f3099315de4ec6bde966bf8563f5faac56

go/respectful-words

Change-Id: I8bd5281522e7874b169e60dfcbcc23169e3ab88f

Bug: 337993945
Test: m
Change-Id: I762f41500fb9b360245fbf58a6526dd594ff332e

This allows the camera app state to be reused in other camera compat classes.

Bug: 314960895
Test: atest WmTests:DisplayRotationCompatPolicyTests
Test: atest WmTests:DisplayContentTests

Change-Id: Ie1692a59987267113c4d05bb332bdb28f6a929dd

Bug: b/306336441
Test: manual
Merged-In: I096d28bce5f879f88f185f09014d139f0497cb72
Change-Id: I096d28bce5f879f88f185f09014d139f0497cb72

The permission was recently added to a new API in V in order to limit
the initial launch scope from 3P apps. To keep CTS test coverage, grant
shell the permission.

Bug: 285185747
Test: atest android.security.cts.FileIntegrityManagerTest
Change-Id: I0f22aaef6b5d6418d4ea12557b1e81b3fa5eb7af

Change-Id: Id92e2553837947ce9c97fe60e3a1b02516ea2f7a
Flag: EXEMPT XML
Bug: 335025399

Flag: N/A XML
Bug: 335025399
Change-Id: I4a5e6e8efa94074b4f9a59ae07a3bc1ccec3f7dd

Legacy recents animation was broken for a while after enable shell
transition, it's unnecessary to maintain it.
For shell transition, after introduce RecentsTransitionHandler, it
will set focus window to recents activity in setInputConsumerEnabled
(ref I10e397db956cad90a4510c326163600f0ed63514), so onBackCallback can
handled by focus window directly.

Bug: 333428882
Test: tried back gesture work in recents when either enable/disable
enable_predictive_back_gesture.

Change-Id: I2e2d6dc7adf0dd9b821b65ff328e434c2600bcf5

This transition helps with ensuring the correct wallpapers when
keyguard is showing.
We are experiencing issues with the wallpapers changing visibility
during a transition, thus having an incorrect finish state: a wallpaper
can not become immediately invisible while in a transition (because it
is expected to commit invisibility only at the end), which
implies that if the wallpaper is collected while becoming visible, the
requests to become invisible during the transition period get ignored (because at the end of the transition we are expected to not make it invisible, since it just became visible at the start).
This implies that locking keyguard while there is an ongoing transition
leads to the wrong wallpaper showing on lockscreen, because we can not
hide the home wp simply by requesting to adjustWallpapers. Therefore, we
create a new transition to avoid handling unexpected visibility changes
on ungoing transitions.

Bug: 327970608
Bug: 323226308

Test: manual - delay execution of
KeyguardViewMediator#updateActivityLockscreenState, wait for keyguard to
unlock and observe lockscreen
Test: manual - unlock keyguard, open app, lock keyguard, unlock
keyguard, close app, lock keyguard, observe lockscreen - all in rapid
succession

Change-Id: I80313281219fd6b42fe3dffffde2ef90086b0e59

Test: None
Bug: 294552419
Change-Id: Iff50a45c286578e292f84f5471bfa6105e490df2

After further investigation, it seems that while disabling drumroll
detection by speed change fixed pointer movement issues, the bad pointer
speed values were also breaking tap-to-click. I can't produce drumroll
issues on this touchpad anyway, so let's just disable drumroll
suppression completely.

Bug: <330300506>
Bug: <329585708>
Test: connect DualShock 4 by Bluetooth, check tapping to click works,
      drum your fingers on the pad and check the cursor doesn't jump
      around
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:a4b33afae1a29f5d8f6ec7b579bad151348274bc)
Merged-In: Ie645ac5b4c6fc5c2ea4fc3611d815baa21ecd5c9
Change-Id: Ie645ac5b4c6fc5c2ea4fc3611d815baa21ecd5c9
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Bug: <272518665>
Test: compare responsiveness of pad edges with and without the change
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:d969570a63feda83aadec3fb720587bdd44b9d2d)
Merged-In: I3c44dc74ecb740c0b598623f60b0727cd6ce383a
Change-Id: I3c44dc74ecb740c0b598623f60b0727cd6ce383a
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

SATELLITE_COMMUNICATION is a signature|privileged permission. Used to get satellite status.

Bug: 330585109
Test: presubmit
Change-Id: I827c7dbf5524a56896ad8f9ba2e952c0e09db996
Merged-In: I4e0ffa2ed755b06b5dc05b716a26fa3222b15d14

This happens on two paths:
* Window already visible: When the SensitiveContentProtection system
  service adds a new window/app into the protected list, find all
  visible windows and Toast for any that are protected. This also covers
  the case where projection is started after the window is visible.
* Window becomes visible: Notify WMS and Toast if the window is in the
  protected list.

We can't reuse the approach taken for recording detection callbacks to
listen for visibility changes since that works at an app-level, while
we need window-level visibility events. Also the new approach handles
non-Activity windows.

The logic is kept in WMS since it holds both the protected list and the
visibility of windows. Additionally, this works better for applying the
Toast to FLAG_SECURE windows in the future (for a consistent UX).

Fixes: 323580163
Test: manual - for both login and otp-app hiding: trigger protection
 after window is shown; minimize app and re-open.
Test: manual - send OTP to bubble conversation and expand bubble
Test: atest CtsSensitiveContentProtectionTestCases
Change-Id: If6628b445d6351160c66ff89411f798ce44bf770

SATELLITE_COMMUNICATION is a signature|privileged permission. Used to get satellite status.

Bug: 315928920
Test: presubmit
Change-Id: I4e0ffa2ed755b06b5dc05b716a26fa3222b15d14

Bug: <272518665>
Test: use the DS4 touchpad (over Bluetooth) for a few minutes, check
      pointer movements remain smooth
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:8a83fb37ca2c95646ad9d0f85efeaf613d12eba4)
Merged-In: I07e613c6cf4ea7920b528c03695cf0089ad0bce2
Change-Id: I07e613c6cf4ea7920b528c03695cf0089ad0bce2
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Fixes: 308573259
Test: atest android.content.pm.cts.PackageManagerTest
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:4f882ccfbf955b5fc9e04ef45ff3293885a7d20a)
Merged-In: Ieb9e256b5fbb3b2ccd5d6a695f63011a31e95d9b
Change-Id: Ieb9e256b5fbb3b2ccd5d6a695f63011a31e95d9b
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Bug: 278763704
Test: Manually done
Change-Id: I22bf47a913f3b25b3f095e4ab276af79e51a4a76
Merged-In: I22bf47a913f3b25b3f095e4ab276af79e51a4a76
Merged-In: I54105704d8f453663a2e8781b2cb680d9ab03c73

The issue is thoroughly documented in the bug, but this change ensures
that the biometric logo setting can be done. There is strange behaviour
with 'signature|privilege' where the new 'privilege' scope appears to
break the 'OR' relationship for our framework UI codebase.

Now, we've added the framework UI package within the privapp allowlist
for that single permission.

Bug: 330906693
Test: Build and UI Test On b/329874867

Change-Id: Ic9dcd4a7e31f5b439ccd807b4ea454cf2cee55a0

SCHEDULE_EXACT_ALARM already be used in the Settings's PeriodicJobManager, it's better to explicit declare the usage.

Bug: 329046490
Change-Id: I87412f6b7d2da0451184ee635019402a4cd0760b
Test: presubmit

After further investigation, it seems that while disabling drumroll
detection by speed change fixed pointer movement issues, the bad pointer
speed values were also breaking tap-to-click. I can't produce drumroll
issues on this touchpad anyway, so let's just disable drumroll
suppression completely.

Bug: 330300506
Bug: 329585708
Test: connect DualShock 4 by Bluetooth, check tapping to click works,
      drum your fingers on the pad and check the cursor doesn't jump
      around
Change-Id: Ie645ac5b4c6fc5c2ea4fc3611d815baa21ecd5c9

Bug: 272518665
Test: compare responsiveness of pad edges with and without the change
Change-Id: I3c44dc74ecb740c0b598623f60b0727cd6ce383a

Bug: 272518665
Test: use the DS4 touchpad (over Bluetooth) for a few minutes, check
      pointer movements remain smooth
Change-Id: I07e613c6cf4ea7920b528c03695cf0089ad0bce2

it can be used in cts tests.

Bug: 329872405
Test: manual
Change-Id: I3cce7c94de59cf0043dd19ae6c9f7cfb46d8a932

Flag: ACONFIG android.hardware.biometrics.custom_biometric_prompt DEVELOPMENT
Bug: 302735104
Test: atest BiometricPromptLogoTests
Change-Id: I9d8cd9d361cba171232741af74cd7839db134ae5

Revert submission 25750009-facemanager_20240110

Reason for revert: Project cancelled.

Reverted changes: /q/submissionid:25750009-facemanager_20240110

Bug: 329561487

Test: Local
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5fe554bfd9f28b7b15677dfb74c756f827074ebc)
Merged-In: I7e329f311b3eb599195f415cf39dc28bb11139a1
Change-Id: I7e329f311b3eb599195f415cf39dc28bb11139a1
Revert FaceManager changes.

Move logs to protologs

Bug: 327970608
Test: no

Change-Id: I4fab475d4b8330eca19d68d6040161ea46af58be

Update the docs to explain new behavior.

Bug: 327469700
Test: presubmit
Change-Id: I9004e30410374db7bdc8468a940f88f9e34fa663