Bug: 177561690
Test: on device
Change-Id: Icafbdf54fe807f8779377b13cb4e4eb265db692e

When the display enters doze mode, it should unregister the light
sensor. It should register light sensor again when the display
state change from doze to on otherwise we will lost lux information
and then the refresh rate could not be locked.

Bug: 177636374
Test: atest DisplayModeDirectorTest
Test: no fps transition in the blocking zone when the display state change
Test: check if the lux will update when the display state change
Change-Id: Ib69314aaf716be38af605f8abcca139c4bdd33f1

Allow DeviceConfig to change the high zone behavior including
refresh rate and brightness thresholds.

Bug: 177636374

Test: atest DisplayModeDirectorTest
Test: adb shell device_config put display_manager refresh_rate_in_high_zone "90"
Test: adb shell device_config put display_manager fixed_refresh_rate_high_display_brightness_thresholds "200"
Test: adb shell device_config put display_manager fixed_refresh_rate_high_ambient_brightness_thresholds "8000"
Change-Id: I1463d6c5daaee46a87a193e98e7f63cad9274b49

Force the display to stay at fixed fps when ambient and
display brightness are high.

Bug: 177636374
Test: atest DisplayModeDirectorTest
Test: no fps transition in the blocking zone when the display state change
Test: check if the lux will update when the display state change
Change-Id: I7d8ed657544bd1423ca8b9afefc87e58530c44dc

Currently we are seeing TEMPORARILY_NOT_METERED occurs on non-5G
devices. This fix adds more checks to prevent incorrect
TEMPORARILY_NOT_METERED being set. Before we root cause the issue,
we only allow this bit when all of the following conditions met.

1. Devices should support 5G.
2. Carriers should support 5G unmetered data.
3. Device should camp on 5G network.

This temporary fix should be removed after we root cause the issue.

Bug: 176119724
Test: Manual
Merged-In: I2b987d24851cdb16d8457b0ec5c546ace5485ed0
Change-Id: I2b987d24851cdb16d8457b0ec5c546ace5485ed0

Bug: 169758206
Test: manual
Change-Id: I98ac9eecd8a497541d9ce0761920db1252eb72e0
Merged-In: I98ac9eecd8a497541d9ce0761920db1252eb72e0

Bug: 177364704
Test: none
Change-Id: I8f19d7d58ee78b64d93de265739a7a880b6a52df
Merged-In: I8f19d7d58ee78b64d93de265739a7a880b6a52df

Use ApplicationInfoAsUser() to get the application information by
user id to make sure we have correct permission, othewise we will
get the SecurityException due to lack of INTERACT_ACROSS_USERS.

Bug: 176313819
Test: atest CtsVoiceRecognitionTestCases
Test: manual.
      1.create profile user
      2.Install sample recognizer app
      3.Function works fine and no security exception occurred after
      apply the change

Change-Id: I6958dbf661373606fb9dba55e386aaea4399a146
Merged-In: Iaf485537b8082d2109d2134ff987dc7244e31218

Auto-generated-cl: translation import
Change-Id: I26837872bece6c11b9f8b302919edbffa3d4441e

* changes:
  DO NOT MERGE Revert "Set fixed fps when ambient or display brightness is high"
  DO NOT MERGE Revert "Allow DeviceConfig to change display settings for high zone"
  DO NOT MERGE Revert "Fix the ambient lux which did not update for blocking zone"

This reverts commit 4a0a896a.

Bug: 176018998
Test: atest DisplayModeDirectorTest
Change-Id: Ic9329c59c358742696adbbca9cc2b33f25787eb1

This reverts commit cf55c210.

Bug: 176018998
Test: atest DisplayModeDirectorTest
Change-Id: Ib576e16257d7903b39efa8015c2af3be8c0d0c40

This reverts commit 400e7d5d.

Bug: 176018998
Test: atest DisplayModeDirectorTest
Change-Id: I58c60a3a124db11e9ae091831a84a704b3c4e6bf

Auto-generated-cl: translation import
Change-Id: I7d579a91209b6663d63f891cd6b6f4e6f24a89b4

When the display enters doze mode, it should unregister the light
sensor. It should register light sensor again when the display
state change from doze to on otherwise we will lost lux information
and then the refresh rate could not be locked.

Bug: 176018998
Test: atest DisplayModeDirectorTest
Test: no fps transition in the blocking zone when the display state change
Test: check if the lux will update when the display state change
Change-Id: Ibf2e7cb2e336c88a583f00f59abcbc9d06ec3d62
Merged-In: Ibf2e7cb2e336c88a583f00f59abcbc9d06ec3d62

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/13122154

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: I1f2497b843db9d953e225da17e16f92f93f2ad99

This ensures that the falsing manager always is testing against the
correct interaction type when it is asked. Prior to this change, we
could end up in states where a user was swiping down (opening the
quick settings) but the falsing manager believed the user was trying
to unlock the phone.

Fixes: 160967364
Test: atest SystemUITests && manual
Change-Id: I176f54a768622dec3e758a7f01ed8aec26223648
Merged-In: I176f54a768622dec3e758a7f01ed8aec26223648

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/13164079

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: I557ca22ba1a854468174e70391601d9379d99b81

Bug: 174243830
Test: manual
Change-Id: I2f81bcd57181791fa95d35ad52e6af2d7d9c8dcf
Merged-In: If305a4b694a9d6fcc27da8279f1f53f9fd9cb685
Merged-In: I345d9ff828021da35556f2d51da512840dda8026

Bug: 174243830
Test: manual
Change-Id: I2f81bcd57181791fa95d35ad52e6af2d7d9c8dcf
Merged-In: If305a4b694a9d6fcc27da8279f1f53f9fd9cb685
Merged-In: I345d9ff828021da35556f2d51da512840dda8026

After the user renames/moves a file/directory, the database of
MediaProvider is not updated. It causes that the file can't be
opened via MediaProvider. Use scanFile to instead of MP.update
for the file/directory.

Handle the .nomedia case for create/copy/move/delete/rename.
Scan the parent directory to update the database.

Test: atest MtpTests
Test: atest --test-mapping packages/providers/MediaProvider
Test: manual. 1. Move/rename the file/directory.
              2. Open the file in DocumentsUI
	      3. create/copy/move/delete/rename for .nomedia case
Bug: 169300366
Bug: 171538933
Bug: 172029805
Bug: 170798581
Change-Id: Ia37be7a027bfe502e3f7c96babe5a5bbed5f942c
Merged-In: Ia37be7a027bfe502e3f7c96babe5a5bbed5f942c
(cherry picked from commit 20079f10)

There is some weirdness with the way the AlertActivity behaves when
it's populated and elements are enabled while it's not actually on
the screen. Work around this by populating the AlertActivity during
onResume() [eg. every time the activity is shown] instead of
onCreate() [eg. only the first time the activity is created].

Fixes: 172699073, 173159446
Test: Manual
Test: Start a staging install
Test: Turn off the phone screen
Test: Wait for the staging to complete
Test: Turn on the phone screen.
Test: See the install dialog has OK/Cancel buttons
Change-Id: Ia9525f20f98f42e6b2b865fa926b9707d416cde4

Auto-generated-cl: translation import
Change-Id: I216f1736a0b63c8cf0c8b4a73e9ba57d5142fd32

[automerger skipped] Protect account chooser activities against overlay. am: fedbadf5 am: e1d00ab8 -s ours am: be9c053c -s ours am: 948bd61f -s ours am: 065fbe9c -s ours am: 91b18936 -s ours

am skip reason: Change-Id I1a16808426934f4a8d12410576d769443e4c2a04 with SHA-1 6ff42dd2 is in history

Original change: https://googleplex-android-review.googlesource.com/c/platform/frameworks/base/+/13194523

MUST ONLY BE SUBMITTED BY AUTOMERGER

Change-Id: I7515c5d471509c53b234d43432ced958e979c84e