Set floating menu mode by default, but if the user uses accessibility button in the navigation bar to trigger their accessibility features before migration, then set it to keep the navigation button mode.
Bug: 173940304
Test: 1. Push old version of db and apk
2. Enable/Disable accessibility features in navigation bar
3. Push new version of db and apk
Change-Id: I465eb2190f0e1ca9a6a6be928752a07d5e9576da
This adds a setting to turn on/off the toast notifications shown when
an app accesses clipboard.
Bug: 182349993
Test: atest SettingsProviderTest
Change-Id: I6922ed5a74fae17602a2ac20a199a7d6c03014b9
We already have this check on the client side. Copying it over to the
server side for cases when the server side is called directly.
BUG: 175024829
Test: atest com.android.devicehealthchecks.SystemAppCheck#system_app_crash
Change-Id: Ib540b9bdb29343eec79a2f31e0b26fe333117395
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
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 cae34b8e22 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 cae34b8e22.
Test: Included
Bug: 170858298
Change-Id: I18428a6df9abf0e8e37c1c179be6843e4eee793c
Cnfig flag, config_magnification_area, determines if the device
supports magnification area or not.
If OEM doesn't support magnification area, we should adjust the
magnification capability setting and window magnification prompt
setting.
Bug: 177371954
Test: atest SettingsBackupTest
Change-Id: I67947285eb6a73b8e0e21d1db866c426a0ea49d7
(cherry picked from commit f9d7150a5c)
Merged-In: I67947285eb6a73b8e0e21d1db866c426a0ea49d7
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 :)
Also adds a config flag for the smart autorotate to indicate whether the
feature is enabled.
Test: make RunSettingsRoboTests
Bug: 172370409
Change-Id: I23ff3247827dca188e10d0bd8f00c37e2cd0b920
There are two categories of color modes: the standard color modes, which
are defined and implemented in AOSP, and a reserved range of vendor color
modes, which are defined and implemented by the vendor. Currently, there
is no way to distinguish between two vendor's color modes that use the
same value within the reserved range. This will allow OEMs to specify a
hint as to which vendor's color mode definitions were used on the
original device. If the hint from the restored device matches the hint
on the new device, the color mode from the restored device can still be
considered valid for the new device if it is within the vendor reserved
range. If it does not match, the restored device's color mode value is
invalid on the new device, and must be replaced by the default on the
new device.
Bug: 167449433
Test: builds
Change-Id: Ie5ac0a2d783e1ea703e0342f5cdb41dca07d04d4
This key handles the fade effect of the accessibility floating menu.
Bug: 173940865
Test: atest SettingsProviderTest
Change-Id: I9e6e02920e331cd326e1667d968a0397dde8d377
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
Adding a new annotation that can be fetched at runtime.
The settings keys annotated with the new annotation can be accessed via
the get* methods, even if they are marked as @hide. Access to a value
that is not annotated with @Readable will end up with an
IllegalArgumentException.
Notice that if a caller tries to call get* method with a value that is
not defined in the Settings.Secure, Settings.System or Settings.Global
classes, this access is still regarded as valid. We only reject accesses
where the value is defined in one of the three classes, but is marked as
@hide and does not have @Readable annotation.
This CL adds @Readable to all existing hidden keys and public keys.
A follow up CL will remove the @Readable annotation for the hidden keys
added in S. The end result would be that all the keys (hidden or public)
can be accessed if they were added before S. From S and beyond, only
public keys can be accessed.
+ also fixed some formatting issues
BUG: 175024829
Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest
Change-Id: I8a2733580ff9c9d01cbdb0f14ad56c2062a2f956
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
Until now, def_user_rotation was effectively a dead default:
- added missing def_user_rotation -> USER_ROTATION first-run initialization
- corrected the setting type when upgrading database
Bug: 178000973
Test: set def_user_rotation to 1 in default.xml and flash Pixel 3a
Change-Id: If2aa9665a0167f696f6b16a16be48ac473271631
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
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
Exempt-From-Owner-Approval: Change already merged on internal gerrit.
Change-Id: I0731fa842c69683953baaf9ec3a9a03454f4c607
Merged-In: I0731fa842c69683953baaf9ec3a9a03454f4c607
* ACCESSIBILITY_FLOATING_MENU_SIZE: control different size
* ACCESSIBILITY_FLOATING_MENU_ICON_TYPE: control icon type
* ACCESSIBILITY_FLOATING_MENU_OPACITY: control the opacity value for fade out effect
Bug: 173940865
Test: atest SettingsProviderTest
Change-Id: I0399366b6ea05268e3d3ad1f24962fffde8d686a
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
