As per requested in b/176940932#comment3 and b/156260178#comment32,
extending the valid font size scale range to [0.25, 5].
Existing CTS tests still pass.
BUG: 156260178
Test: atest android.provider.cts.settings.Settings_SystemTest
Test: atest android.app.cts.ApplicationTest
Change-Id: Icff82d727d63da4353342b0f9a5ca3c2ae1671c1
(cherry picked from commit df8852a0b5)
Merged-In: Icff82d727d63da4353342b0f9a5ca3c2ae1671c1
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
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
* 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"
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
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
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 20079f1064)
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
