Age | Commit message (Collapse) | Author |
|
Bug: 220074017
Change-Id: Idfdd94e902f656ac65a2a75dfdd199f6f85ba472
|
|
Test: Manual
Bug: 191608501
Change-Id: I7656f78f47183e9e61d98a3ccbac94690570df20
Merged-In: I7656f78f47183e9e61d98a3ccbac94690570df20
(cherry picked from commit 760255d89420efb2b948e26cd61535a7b9561c4a)
|
|
Remove support for ANGLE's libfeature_support_angle.so.
This also removes all of the logic related to checking the rules file,
since libfeature_support_angle.so is what parsed the JSON rules file.
Bug: b/187342779
Bug: b/184757175
Test: make and manual verification ANGLE is loaded
Change-Id: I02ac083fb8144465b60ac0ed2738c73b31addda1
Merged-In: I02ac083fb8144465b60ac0ed2738c73b31addda1
|
|
Starting with Android 12, start backing up this setting to restore the
user's pref across devices. For users upgrading to a 2021+ device,
they will get the new default (assistant on long-press). If this user
then restores to an older device, they will then get this new behavior
on that device as well, even though it isn't the device default.
Fixes: 189874533
Test: atest SettingsBackupTest
Change-Id: I4b9864045bf12f30da03e3715f5e368bdf48a198
|
|
Create a new DeviceConfig entry to replace the prior Settings entry on
which the location ignore settings allowlist is based. This allows us to
allowlist based on attribution tag, and eliminate holes for large
applications.
Test: manual + CTS + GTS
Bug: 187421886
Change-Id: I31e61db79b93e202bd8c66efae1bb5aaf0c88ff5
|
|
The key used to show the migration information related to
the accessibility floating menu.
Bug: 175365399
Test: atest SettingsProviderTest
Change-Id: Ifabc412b990c72ad345bab2d5d8539a57bd6ca5d
|
|
This CL removes the existing TestApi
WindowManager#setForceCrossWindowBlurDisabled and replaces it
with Settings.Global#ENABLE_WINDOW_BLURS.
Bug: 14186649
Test: m && atest BlurTests
Change-Id: Ia15b7932ea973a9ed195c507558cdc71f194b366
|
|
|
|
Bug: 177299699
Test: manual
Change-Id: I711d078281ae9cc17ebb21e6c3f857caad31016a
|
|
Device default value set in config_keyChordPowerVolumeUp in
config.xml; can be overridden for all users with
Settings.Global.KEY_CHORD_POWER_VOLUME_UP.
Value may be one of:
0 - no-op
1 - vibrate mode (current AOSP default behavior)
2 - launch assistant
Bug: 179673796
Test: adb shell settings put global key_chord_volume_up <0, 1, or 2>
adb shell dumpsys window | grep mPowerVolUpBehavior
adb shell input keycombination POWER VOLUME_UP
Change-Id: I0e03155bdbe61d9fdd6838fe2c860749cf360907
|
|
Bug: 177299699
Test: manual
Change-Id: I4947117b6bb11678e3ad761204d720354b9e73ae
Merged-In: I4947117b6bb11678e3ad761204d720354b9e73ae
|
|
Fixes: 183120687
Test: manual
Change-Id: I5632e131b47058ebe25ab21db004eb90498bc299
|
|
Only registered when:
- udfps enrolled
- AOD is not enabled
- quickpick enabled:
adb shell settings put secure doze_quick_pickup_gesture 1
Currently by default, quickpickup is not enabled
On gesture trigger, AOD screen will show for 5 seconds
Test: manual
Bug: 176550666
Change-Id: I804a2590c1d95acad62fbfbc85228ecfc8bfa3ed
|
|
Replace usages of DEVELOPMENT_ENABLE_SIZECOMPAT_FREEFORM with
DEVELOPMENT_ENABLE_NON_RESIZABLE_MULTI_WINDOW so that we can use one
setting to control all multi window mode
Bug: 176061101
Test: pass existing
Change-Id: I873b4902f3995815721401b30236919ffdbc6a82
|
|
This is the changes in Settings (to store the current screen side) for
the one-handed keyguard. This also checks in symbols.xml to expose the
platform config to SysUI (the lines in symbols.xml are currently in
config.xml; I'm assuming that a previous revert didn't remove them).
Bug: 170858298
Test: included.
Change-Id: I9d91a9360c821562634e83295f5e2e340f6de1d5
|
|
This reverts commit 868e770b824b5d776d64fd9364f24a6aa1ed5ab5.
Reason for revert: Breaks password entry - b/180993584
Change-Id: I9a1771b795c90b1cfe6c2457d390ac53235c6c94
|
|
* changes:
[CEC Configuration] Move 'hdmi_cec_version' to SharedPreferences
[CEC Configuration] Run HdmiControlService change notifications in the service thread
|
|
I'd like to test other things (like tap makes the IME move), but to do
that means replacing the mock with a proper fake. That can come later,
but this at least tests that the flagging works correctly.
The changes between this and
commit cae34b8e22f8a7baa845bfd31f472ed728c67a89 is the bouncer height is
now measured using wrap_content, so the placement can be controlled
properly by the outer View (as the position of the bouncer changes
depending on the size of the screen).
This reverts commit cae34b8e22f8a7baa845bfd31f472ed728c67a89.
Test: Included
Bug: 170858298
Change-Id: I18428a6df9abf0e8e37c1c179be6843e4eee793c
|
|
Test: cts-tradefed
Bug: 171958586
Change-Id: I01d374c9a69d23f0d242c0c8ec2364454692ddd4
|
|
Throttle location providers completely when the device is completely
still, and provide "faked" locations instead.
Bug: 172688700
Test: manual + atest StationaryThrottlingLocationProviderTest
Change-Id: Iba4e50ebf78cd8c6a9f2433ecb6e967d3a533c63
|
|
This reverts commit 6c5bfcb40fdcf2499098daad37577e7ead67699a.
Reason for revert: Bug: 179493042
Test: Manually verified
Change-Id: Iebcaa9e92a2f83419c07936aa5aa3c81970da34a
|
|
This is currently enabled by settings
persist.sysui.keyguard.one_handed_keyguard_enabled to true. If enabled,
this will cause "one-handed able" security modes to be measured with
half of the width of the SecurityViewContainer. Tapping either side of
the screen will then move the keyguard by changing the margins.
There's some flaws here, but it's a start. There's a frame of the
bouncer being on the wrong side of the screen if the keyguard is on the
right, and it doesn't respond to opening/closing the device properly yet.
Bug: b/170858298
Change-Id: Ib997b9b3cb4ca7a069c805c7a8f3a79434eebd4c
Test: Incoming :)
|
|
Bug: 171846124
Test: Tested manually
Change-Id: Ib13aa832e186ae964069d888c1c4b8321a0f7fc1
|
|
Add support for new sysui overlay in order to disable aod/ls layouts
from the preview builds.
Bug: 178471752
Test: atest KeyguardUpdateMonitorTest
Change-Id: Iaf1dd2ba73368a3c43efe81c10aa9df42df6fdbe
|
|
1. Add a setting to enable this.
2. Allow non-resizable apps to be moved to split-screen when the setting
is on.
TODO:
1. Add a developer option for this
2. Fix SizeCompatMode when the non-resizable app is in split screen
Bug: 176061101
Test: adb shell settings put global enable_non_resizable_multi_window 1
Test: atest WmTests:ActivityRecordTests
Test: atest WmTests:WindowOrganizerTests
Test: atest WmTests:WindowManagerSettingsTests
Test: atest CtsWindowManagerDeviceTestCases:MultiWindowTests
Change-Id: Ife9e5e5848614f072efb3b23f71472561e00488c
|
|
|
|
This reverts commit 8e089728c7050819e82b9e278db4c3487bd78308.
Reason for revert: It turns out we don't need this feature
Change-Id: Ibc042e451d66a1b87ed416bed41461df52f70a66
|
|
* The level of decoration for fully custom notifications can be customized with FULLY_CUSTOM_VIEW_NOTIF_DECORATION
* The level of decoration for decorated notifications can be customized with DECORATED_CUSTOM_VIEW_NOTIF_DECORATION
* Adds some helpful logic when "backporting" S logic so that we can see what UNDO notifications will really look like.
Note: this patch now includes code that used to be in separate reviews: I700472b9c8fba2563b447f570cab7dd60a0a3984 and I55e12843a3edc6e9a78e5b8c848400a8f9228d1c
Test: Manual
Bug: 173522761
Change-Id: I7aba1aec2ba3023857735754c000977c4491b774
|
|
d1ebbf5086 am: dd1d1cbacc
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/1520701
MUST ONLY BE SUBMITTED BY AUTOMERGER
Change-Id: Ifbdca1201aa118e59b45f7dd89441a210fc2fa9c
|
|
This flag forces the compat framework to assume we're on a
non-debuggable build, and use stricter rules for enforcing
the change id override policy.
On a non-debuggable build, this flag has no effect.
Test: atest OverrideValidatorImplTest
Bug: 158696818
Change-Id: I3b13f1898e7ff00580140debe2ced9f8074502ea
|
|
|
|
Adds Restricted Mode functionality to NetworkPolicyManager. When this
mode is turned on (via setting), only apps with
android.permission.CONNECTIVITY_USE_RESTRICTED_NETWORKS will be able to
use the network. For all other apps, the network will be blocked by the
firewall. This is controlled by a new allowlist firewall chain
fw_restricted_mode.
As a first step, this implementation still requires a reboot after the
enabling / disabling the mode to take effect. I will provide the dynamic
configuration in the next CL.
Test: atest CtsHostsideNetworkTests && atest
NetworkPolicyManagerServiceTest
Bug: 170322816
Bug: 157505406
Bug: 170322455
Bug: 175281879
Change-Id: I0731fa842c69683953baaf9ec3a9a03454f4c607
|
|
Test: manual
Change-Id: I560ac597bf8e8320d1d9e404ffcf1e6464cfe82d
|
|
|
|
Move battery saver to retrieve remote configuration values via
DeviceConfig. Some products allow users to customize which battery saver
toggles are active, so leave the Global settings flag around to track
the user's choices. The user's choices will override anything sent from
the server.
Also renaming some of the flag names since we don't need to support
backwards compatibility for server-side pushes.
Bug: 79580230
Bug: 124466289
Test: atest com.android.server.power.batterysaver.BatterySaverPolicyTest
Test: atest com.android.server.power.batterysaver.BatterySaverStateMachineTest
Test: atest com.android.server.power.batterysaver.BatterySavingStatsTest
Test: atest com.android.server.power.PowerManagerServiceTest
Test: atest CtsBatterySavingTestCases
Test: atest CtsLocationFineTestCases
Change-Id: I47684efa5c4426e1c524fb9c1d4d407ee66fa3b7
|
|
DisplayWindowSettingsProvider currently only supports reading display
window settings from a single file location. However, this doesn't
support the use case where a device may want to ship with multiple
vendor display setting experiences and allow switching between them at
runtime.
This updates DisplayWindowSettingsProvider to allow overriding the file
path that's used to read display settings. The default is still to read
from the main settings file stored at /vendor/etc/display_settings.xml
but can be changed by setting the global setting:
DEVELOPMENT_WM_DISPLAY_SETTINGS_PATH.
This also removes the flag DEVELOPMENT_IGNORE_VENDOR_DISPLAY_SETTINGS to
since ignoring vendor display settings entirely is no longer needed.
Test: atest WindowManagerSettingsTests
Test: atest DisplayWindowSettingsProviderTests
Bug: 172342357
Bug: 173540615
Change-Id: I11fd2945a4dacef80e1ab921d585c712f20ae55b
|
|
|
|
Isolated storage was added in Q (and enabled by default) and has been
replaced by FUSE in R
Additionally, we can remove the ExternalStorageMountPolicy concept
which is only required if isolated storage is false
Cleanup in preparation to introduce DeviceConfig changes for
transcoding
Bug: 169327180
Test: Builds
Change-Id: Ie2686d8efa6654ea6c4b4ca8c121c0c1841a6356
|
|
This functionality is no longer needed as all battery saver related
logic is handled within location code.
Bug: 69373668
Test: presubmits
Change-Id: Ie79d6334e0aff5a6562ae0014b9274c81434b977
|
|
|
|
This setting will store an emergency number locally if government
provided emergency number (such as 911, 110) are not desired by user,
used by emergency apps such as EmergencyInfo and Personal Safety on
Pixel.
Bug: 172609395
Test: manual/rebuild
Change-Id: I8732c20f0438e521eaec73758242015794c80c3b
|
|
Test: manual
Bug: 162927074
Change-Id: I4eaae9db74ac1b23bdd0e90a6981a852375f788b
|
|
|
|
(2/n)
This change introduces the DEVELOPMENT_IGNORE_VENDOR_DISPLAY_SETTINGS
setting which controls whether or not WindowManagerService should return
display vendor settings provided in the vendor/ partition. This will be
added as an entry in Developer Options to allow ignoring vendor settings
and using the default settings.
Test: atest WmTests:WindowManagerSettingsTests
Bug: 168808369
Change-Id: Iece0b76e4861be56186333134d7d5b25cab5c7e0
|
|
Test: on device
Bug: 168111993
Change-Id: I2ee4414fbc1fcb7abe8a3d5b1099a3e6e58a6777
|
|
This flag will enable the BLASTBufferQueue adapter for use by ViewRootImpl.
BLASTSync and the BLASTBufferQueue in SurfaceView are still behind seperate flags.
Bug: 168506246
Test: Days of manual testing on multiple devices (stressed: app switching, rotation, SurfaceView, PIP, Split-screen). Multiple presubmits. 5 passing runs of flicker. Systrace inspection. App startup perf tests. Inspection of jankstats from experiment based flip in R dogfood.
Change-Id: I2b6e37884d938d327479977becbbce8e38e521f0
|
|
|
|
|
|
|
|
New flag: Settings.Global.SHOW_NEW_NOTIF_DISMISS
- Do not backup to other devices
- To be removed before release
Usage:
adb shell settings put global show_new_notif_dismiss [0|1]
- 0 to disable
- 1 to enable
Test: treehugger
Bug: 171817112
Change-Id: I8712a7f8a2bac6483afd52ede9e478f8b08d661d
|