Also adds a config flag for the smart autorotate to indicate whether the
feature is enabled.
Test: make RunSettingsRoboTests
Bug: 172370409
Change-Id: I23ff3247827dca188e10d0bd8f00c37e2cd0b920
* Minor bugfix in call log to handle USER_CURRENT
* add TelephonyLocalConnection that allows frameworks/opt/telephony to
call code (indirectly) in packages/services/Telephony
Bug: 177613111
Test: atest CallComposerTest
Merged-In: I602b51da6009c884364a026781ca3c160978fbd1
Change-Id: I61af7553b4b3d71fe87c86fca62941747d43ef55
Add a constant for "system_time" to DeviceConfig for server-push feature
flags. "system_time" has been added server-side under cl/353067789.
This change references the new namespace for device-side config code.
This change is following the go/android-flags-setup process. Flags will
be added in follow up changes.
Bug: 159121373
Bug: 178107773
Test: build only
Change-Id: If49365cddc5827382ea4c466322c9fc65777d564
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
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
Rotation Resolver Service provides the suggested screen rotation
to the system server.
Bug: 162359770
Bug: 172370409
Test: atest RotationResolverManagerPerUserServiceTest
Change-Id: Ia43dfdba8502e04768933ef46a4ac8a687d4936c
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
'fonts' thread will block UI thread, so it should have a higher priority
than DEFAULT.
Bug: 178195682
Test: adb shell "ps -A -l -T" | grep fonts
Change-Id: I4fd67389abcfd7d1b78a3db3dc86422a7a837024
.. to consider if the caller is holding the permission
SYSTEM_APPLICATION_OVERLAY.
Bug: 171177581
Test: Manually verified using wellbeing app
Change-Id: I58907de33015d7441818110e94612ec3d29d07ad
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
Add new column definitions in the call log db to support storing the new
call composer elements in the call log. Also refactor addCall to use a
builder pattern, and add READ_VOICEMAIL for shell in order to support
new CTS tests
Test: atest CallLogTest
Bug: 174798736
Change-Id: I00e127510c382d9ff0ffc70f4c5ad7179ac7319a
Add code to support copying call composer pictures between users and the
shadow call log when booting into the DE state.
Bug: 174798736
Test: atest ShadowCallLogTest
Change-Id: Ic70f7b74362e797617d66796407a082c19e0c4f4
* changes:
Improve RemoteViews to simplify notification view hierarchy.
Fully custom view notifications now receive minimal decoration when targeting S.
Add feature flag for app hibernation so that we can begin implementing
behind a feature flag.
We use DeviceConfig as per instructions at go/android-flags-setup so
that we may eventually roll this out to dogfood devices using P/H and
Mendel.
This is the downstream merge of http://aosp/1542244
Bug: 175829330
Test: Builds
Change-Id: I27b4bdd9b6ed25b06fc685183f0dc872094f1b5c
* 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
* 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
Disable the VM policy violation for intents that contain a content URI
but don't have FLAG_GRANT_URI_PERMISSION when scheduling alarms.
Fixes: 160426113
Test: atest CalendarProvider2Test
Change-Id: If6e4a03609fc3d03dde66bcaa3136b23662ccaeb
(cherry picked from commit 224822ecaf)
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
Disable the VM policy violation for intents that contain a content URI
but don't have FLAG_GRANT_URI_PERMISSION when scheduling alarms.
Fixes: 160426113
Test: atest CalendarProvider2Test
Change-Id: If6e4a03609fc3d03dde66bcaa3136b23662ccaeb
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
