Bug: 333678561
Test: Manual
 1) Enable dual display feature and confirm smooth presentation
 2) Enable desktop mirroring and confirm feature works
Change-Id: I0bf4f2689a4fd7687f15c097bf50b9cf7556354e

Moving the size override after other compat overrides to make sure the
letterbox overrides can be applied correctly. The fields overridden by
letterbox doesn't need extra override regarding the stable configuration
as all insets are already in consideration.

Besides, check shouldCreateCompatDisplayInsets() before applying the
override to avoid inconsistency when the compat display insets is not
yet created.

This is a partial cherry-pick contains the critical part of the change.

Bug: 332468995
Bug: 340970172
Bug: 336687188
Test: See reproduce steps in b/332468995
Test: CtsWindowManagerDeviceWindow:WindowMetricsActivityTests
Test: CtsWindowManagerSdk25TestCases:AspectRatioSdk25Tests
Test: v2/android-crystalball-eng/health/microbench/startup/hscapps/compile-speed-profile/open-maps
Merged-In: Iee7ae3ea7e483e6f80fa6ef4659627d620653081
Change-Id: If2e2e7f0eb504f2468f262b195f3a1cd28820423

Bug: 331717791
Test: atest UpdatableFontDirTest
Test: Step 1: Build AOSP image and install
Test: Step 2: Install font family.
Test: Step 3: Remove certificate manually by adb shell.
Test: Step 4: Reboot the device
Test: Step 5: Install font family.
Change-Id: I0373a2e66b7a6a51168094772afb36d8905b6979
Merged-In: I0373a2e66b7a6a51168094772afb36d8905b6979
(cherry picked from commit c273a7e8)

Bug: 332711269
Bug: 338927759
Test: atest ExternalDisplayPolicyTest DisplayManagerServiceTest
LogicalDisplayMapperTest
Change-Id: Iad0c5b0ea19a8f1f14642109639fd435b0e43bc4
(cherry picked from commit ab71a6c1)

The case happens when a pip is entering in previous rotation and then
display updates. The transition type can be either TRANSIT_CHANGE or
TRANSIT_PIP:
 PipTask CHANGE
   sb=Rect(0, 0 - 1080, 2340)
   eb=Rect(0, 0 - 2340, 1080) r=0->3
 Display CHANGE
   sb=Rect(0, 0 - 1080, 2340)
   eb=Rect(0, 0 - 2340, 1080) r=0->3

The destination pip bounds should be calculated from (2340, 1080).
Because a display snapshot should have covered the screen, the pip
should go to the end state immediately and only animate the display
rotation animation.

This also merges [1] and [2].
[1]: I110d1c11f3d3fdcfb83698e5cf1ec4efb062bd10
[2]: Ia9c78105f4a9782c156744e6cb38681f265955a0

Bug: 340367710
Test: Enable auto rotation and home rotation.
      Swipe up (do not release touch) an auto pip activity in portrait.
      Rotate the device to landscape.
      Continue the swipe up to enter pip.
      The display should show a rotation animation and
      the pip can show on correct landscape position,

Merged-In: Ia1e5e8c7edb8c2a078a66b587d5d26a495166de2
Change-Id: Ia1e5e8c7edb8c2a078a66b587d5d26a495166de2
(cherry picked from commit 6373912c)

Add a check in TarBackupReader to enable the restore of packages in the V_To_U_Allowlist in the V to U downgrade scenario

Bug: 341732443
Test: atest -v TarBackupReaderTest, manual test (details: https://b.corp.google.com/issues/341732443#comment18)
Change-Id: I12a1f272b17a12abb532a98c0d93f0a9854fcb51

The enhances the concept [1] to sync insets leash position.
Because after [2], the position will be applied with insets
control change.

[1]: I51ebd9f2c90b2b4d12f77d1361acc66ab7777b38
[2]: I5ba0c33ca4542d27bb4dee4ce849f34721f20b14

This also merges I2a886a6a04891a7bf09c1152e52a431326a80d03.

Bug: 337018949
Test: Enable auto rotation. Rotate camera app. The navigation
      bar can won't show on screen center.
Merged-In: Ibb25dc5735674e6618b5c639c4e2e61ffa678f52
Change-Id: Ibb25dc5735674e6618b5c639c4e2e61ffa678f52

We should avoid setting mUserLeaving=true when
bringing task to front that disallow entering PiP
due to the launching task coming to front.

Bug: 336477473
Test: repro the steps in the bug report
Change-Id: I94377538ab922b2ca03f295a847a8b8e4d1904df
(cherry picked from commit 86860b8e)

The hide operation is mainly used to avoid showing navigation bar
with inconsistent rotation after recents activity switches to next
app. So if the state stays at running recents, let the adding
windows show normally.

Bug: 302249163
Bug: 340979786
Test: Disable home rotation. Launch landscape app.
      Enter recents. Long press power key.
      The power menu should be visible.
Test: atest TransitionTests#testAppTransitionWithRotationChange
Merged-In: I692df7227773ff4ca49ff50a02a2eb300dfcd241
Change-Id: I692df7227773ff4ca49ff50a02a2eb300dfcd241
(cherry picked from commit 7970e4f9)

Previously, keyguard will be selected as the backup wallpaper target
if there keyguard is locked and there is an active transition. That
is to avoid wallpaper from being show/hide in a short time when
running recents transition to close app on keyguard.

The condition was a bit broad so the regular transition will also
keep wallpaper target on keyguard. Which could make the transition
change mode of wallpaper become CHANGE rather than TO_BACK when
launching an occlude-keyguard app and then display rotates. Which
could make the condition of seamless rotation rejects the seamless
effect because it found wallpaper is a changing operation.

To avoid such case, only enable the condition if there is a transient
(recents) transition.

Bug: 333557024
Test: Enable auto rotation. Set a secured lock. Turn off screen.
      Double click power key to launch camera when holding the
      device in landscape. There should not have a rotation animation.
Test: On a secured keyguard. Double click power key to launch camera.
      Swipe from bottom to dismiss camera. The wallpaper target
      should only change to notification shade once.
Test: atest WallpaperControllerTests#testShowWhenLockedWallpaperTarge

Merged-In: I43a29e828798f36f39d38af130f98de7c5859ec6
Change-Id: I43a29e828798f36f39d38af130f98de7c5859ec6
(cherry picked from commit 275e2758)

Fixed-orientation activities are rarely tested in other orientations, and it often results in sideways or stretched previews. As the camera compat treatment targets fixed-orientation activities, overriding the orientation disables the treatment.

Fixes: 340818342
Test: atest WmTests:LetterboxUiControllerTest
Change-Id: I23cc542158e8fe53b1b210409dfb96c45ff7462f

- Update string resources
- Make the notification not able to be cleared by "clear all" button

Bug: 331804186
Test: atest FaceInternalEnumerateClientTest
            FingerprintInternalEnumerateClientTest
            BiometricDanglingReceiverTest
Test: Manual trigger dangling force re-enroll
Flag: NONE
Change-Id: I25c1e621f9464c7f0f7a895cf7294c752950b262

Bug: 341027847
Test: atest WmTests:LetterboxUiControllerTest

Change-Id: Ie6436f5e270d85eb6601f379d1b89938731ddca1

Bug: 337864590
Test: build/bootup
Change-Id: I289b0fc5dc13d55d3f90d7c9204acf851997d938
(cherry picked from commit 35022e89)

If this removeTask happens without any consequent actions
(eg. removing a pip task and nothing starts as a result), the
transition system needs to interpret it as ready immediately.

Bug: 339135761
Test: Open netflix video in pip, go to recents and restore netflix
Change-Id: I14bed6164e12bd4d36c24870738188f5e89a4eb1
Merged-In: I14bed6164e12bd4d36c24870738188f5e89a4eb1
(cherry picked from commit 31a9c1f4)

When the letterbox education is disabled we should exclude it
from the initial education flow.

Bug: 335272191
Test: atest WMShellUnitTests:CompatUIControllerTest
Test: atest WmTests:LetterboxUiControllerTest

Change-Id: Iec500496045c9dd324f4a6d8dd1f35712bb0c582

When the last package is removed the uid removed signal can arrive
before which removes the UidState object from the data structure. This
caused the historical appops clearing call to never be made so the
registry is only correct during the first install.

Test: atests AppOpsTest --iterations 5, without then with the change.
Fixes: 333797941
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:7a23d1f7fa42026c5b3b15bc282851bf497d97b7)
Merged-In: If7cc71bec2c609aed501fc06c875f87c167cf521
Change-Id: If7cc71bec2c609aed501fc06c875f87c167cf521

Fix the issue where it was checking for the "set" process state,
which means the process will be killed when next time this app
is being background.

Bug: 308029155
Bug: 339697954
Test: Manual

Merged-In: I6bef56445497d2edcb59a44a6d42dcdb027a6126
Change-Id: Ifb77329dfa2fe4a468a6676cb8b08bb5f1943633

This reverts commit c49cc7d1.

Reason for revert: The following bugs cite the changes to disable() api as the root issue: b/332752827 , b/325856557 , and b/332647161

Change-Id: If556f6fd1c256d1e126b9edc05fdc9bb147a2280

In Android U, all receivers registering for non-system broadcasts
are required to include a flag indicating the receiver's exported
state. Apps registering for non-system broadcasts should use the
ContextCompat#registerReceiver APIs with flags.

Fixes: 339811510
Bug: 331804186
Test: lunch sdk_phone64_x86_64-trunk_staging-userdebug; time m -j90; \
emulator -wipe-data -no-snapshot -logcat *:V -logcat-output logcat.txt
Test: m RUN_ERROR_PRONE=true
Test: atest FaceInternalEnumerateClientTest
            FingerprintInternalEnumerateClientTest
	    BiometricDanglingReceiverTest
Flag: NONE
Change-Id: Ie4d438cc76b3bb2fbd39af999332fcd5e4a52427

Bug: 326485767
Test: atest AccessibilityEndToEndTest#testUpdateServiceWithoutIntent_disablesService
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:74ab528e54558b5a78a9b0f32a2e3f0a61714ae5)
Merged-In: I2d986dc8f09a3cf2f31713237e69e15dcef84514
Change-Id: I2d986dc8f09a3cf2f31713237e69e15dcef84514
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Another verification is needed after Bundle modification.
Bug: 321941232
Test: manual
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:36db8a1d61a881f89fdd3911886adcda6e1f0d7f)
Merged-In: I9e45d758a2320328da5664b6341eafe6f285f297
Change-Id: I9e45d758a2320328da5664b6341eafe6f285f297
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Convertion between dp and pixel just need to be done
when density changes. We implemented an IntSupplier
which returns a cached value updating only when
density changes.

Bug: 334077350
Bug: 339738650
Test: atest WmTests:LetterboxConfigurationTest

Change-Id: I7adb6cd94d9f1908ea15561a1654914cb3665e19

Display rotation on task level and display level is mismatched with
letterboxed bounds if hasFixedRotationTransform is true. This causes
landscape app with fixed aspect ratio letterboxing to start in size
compat mode.

Bug: 334076352
Test: atest SizeCompatTests
      Start non-resizable landscape fixed aspect ratio app folded
Change-Id: I0d4c90d1d6897bdbf61a2680bac0468e5a68ee49

Implement abstract method in :
/hidl/FingerprintInternalEnumerateClient.java
/hidl/FaceInternalEnumerateClient.java

Bug: 339721912
Test: make
Flag: NONE
Change-Id: I79c312ac78d45147874794d0b9798d81d698dcab
Merged-In: Ic2401ae588ae5e2d404dd67d7de67491548fdfa2

Add a re-enroll notification with "set up" and "not now" action buttons.
"set up" : bring users to enroll process.
"not now" : do nothing and cancel notification.

Bug: 331804186
Test: atest FaceInternalEnumerateClientTest
            FingerprintInternalEnumerateClientTest
	    BiometricDanglingReceiverTest
Flag: NONE
Change-Id: Ic2401ae588ae5e2d404dd67d7de67491548fdfa2
Merged-In: Ic2401ae588ae5e2d404dd67d7de67491548fdfa2

We only allow removing dynamic permissions. When removePermission() is
called for a non-dynamic permission, in addition to logging it, we
should also return early to avoid the removePermission() call.

Test: manual
Bug: 321555066
Fixes: 321711213
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:528a87e90ff9354581d54fd37fbe9f95cccbcdb1)
Merged-In: Ie2f43663bc71a06ffadb868d2d0eea5ee78f76e5
Change-Id: Ie2f43663bc71a06ffadb868d2d0eea5ee78f76e5
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

This is similar to [1]. But even if the activity is not embedded, the
organizer process will still need to response for task fragment info
change. So if there is any visible activity on a task which is
associated with tf organizer, the organizer process also need to be
visible state to handle the event.

[1]: I57ef9ebe95e05842e7f325c1a4775e98c7eb57bd

Fix: 337784723
Test: atest TaskFragmentOrganizerControllerTest# \
            testOnActivityReparentedToTask_ \
            activityNotInOrganizerProcess_useTemporaryToken

Merged-In: I42c9cb2b95c5517370ef2d26b948b3f4e0db8ec4
Change-Id: I42c9cb2b95c5517370ef2d26b948b3f4e0db8ec4
(cherry picked from commit 65b9bff7)

There should only close two task fragments together when another task
fragment sets companion to current one. If the bottom tf set it's companion
to top tf, that means the bottom tf will be close while top activity
be finished.
Ref JetpackTaskFragmentOrganizer#setCompanionTaskFragment

Bug: 325504342
Test: atest BackNavigationControllerTests
Change-Id: I1dfb9ed8b27a520db0a240e2645910656d1894df
Merged-In: I1dfb9ed8b27a520db0a240e2645910656d1894df

Update the strings and tapped action for the battery saver auto-turn-on
notification to make it clearer

Bug: 336960905
Flag: com.android.server.power.batterysaver.update_auto_turn_on_notification_string_and_action
Test: Manual Test

Change-Id: I38964a16a689ef0b887759c359d0412e5be9d306
Merged-In: I38964a16a689ef0b887759c359d0412e5be9d306
(cherry picked from commit aa4ccbfd)

One of a11yManagerService's receivers performs xml parsing.
Since this can take a while, the receiver should be registered on the background thread.

Test: atest AccessibilityManagerServiceTest (you'll need to verify via printing or breakpoints that the receiver is on the right thread)
Flag: aconfig manager_avoid_receiver_timeout
Bug: 333890389
Change-Id: I1ee6617fe1a4471d251c7a6d4c52b82a788776b1
(cherry picked from commit cb211281)

Reachability provides no advantages for users in case of thin
letterboxing so it can be disabled along with the related
educations.

Fix: 334077350
Test: atest WmTests:LetterboxUiControllerTest
Test: atest WmTests:SizeCompatTests

Change-Id: Ie00084ab5e6be1f3ff0eed8c3551720940859984

setting/updating service

For test, I registered two tests around on ABTD. CtsAutoFillServiceTestCases module is passing except three known failures:

Test run link:
- https://android-build.corp.google.com/builds/abtd/run/L33300030002610600
- https://android-build.corp.google.com/builds/abtd/run/L58100030002616607


Bug: b/324874908
Test: atest CtsAutoFillServiceTestCases
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:141d9d050346bfc4673c429382deb1b3d210f6ad)
Merged-In: I51c2e3788ac29ff4d6b86aa2a735ff2ea1463a77
Change-Id: I51c2e3788ac29ff4d6b86aa2a735ff2ea1463a77
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Migrate user restrictions to DevicePolicyEngine, otherwise user restrictions will not be able to be queried when upgrading from Android 13 OTA to Android 14.

Bug: 323452689
Bug: 318497672
Test: case 1:Android 13 upgrade to Android 14
1.install TestDPC on Android 13
2.set TestDPC as Device Owner
3.set disallow factory reset
4.update Android 14 via OTA
5.The reset to factory settings in the settings app is still unavailable.

case 2:Android 14(bad version) upgrade to Android 14(new version)
1.install TestDPC on Android 13
2.set TestDPC as Device Owner
3.set disallow factory reset
4.update Android 14(bad version) via OTA
5.The reset to factory settings in the settings app is still available.
6.update Android 14(new version) via OTA
7.The reset to factory settings in the settings app is unavailable.
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:470c1eabca9f341e163a38a2327615e8fa3126ae)
Merged-In: I7c63d52300a1c5aa0678f29c2e4b15195411517c
Change-Id: I7c63d52300a1c5aa0678f29c2e4b15195411517c
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

Bug: 318497672
Test: manual
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:996050c7ce41b6bbf93010bcaa1d490fd470d07a)
Merged-In: Id0ac7d06b57f690d114217f2a34c2a1e8c60a277
Change-Id: Id0ac7d06b57f690d114217f2a34c2a1e8c60a277
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

 Also, after updating packages with NLS components, check
 the approved services and remove from approved list if missing permissions.

Test: atest ManagedServicesTest
Bug: 321707289
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:24b13a64f9f5e5aa7f45a2132806d6c74e2c62dc)
Merged-In: I11901755ec430c6e3145def9d67e4e63cda00806
Change-Id: I11901755ec430c6e3145def9d67e4e63cda00806
24D1-dev is based on 24Q2-release. Therefore, we merged this CL to 24D1-dev.

This reverts commit abf91aba.

Reason for revert: b/329000714

Change-Id: I0c10bb98622f26ca5b114ca4e225de6004b80479
(cherry picked from commit 46533d1f)

Only mute music if an actual change in Bluetooth A2DP state happens
when setBluetoothA2dpOn() is called.

Bug: 334182057
Test: repro steps in bug.
Change-Id: If2494dc9db1252cf1afb6ffcd600553b8140a191
Merged-In: If2494dc9db1252cf1afb6ffcd600553b8140a191

This reverts commit 552f6eab.

Reason for revert: Likely culprit for b/338952107  - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted.

Change-Id: I2eb76c951e3395417c75a55e537f1eeb54e48047

Otherwise because getWindowFrameSurfacePosition returns old position
before the display rotation transform is applied, if the position
doesn't update after the transform is done, it will show old position
in new rotation around a few frames. Such as the handle of navigation
bar may be flickering at screen center.

Bug: 338091119
Test: atest TransitionTests#testAppTransitionWithRotationChange

Merged-In: I21a0f10d4c83b6e7137ea0b389f2bbe1a4c82c2f
Change-Id: I21a0f10d4c83b6e7137ea0b389f2bbe1a4c82c2f
(cherry picked from commit a1d5520a)