We set magnification capabilities all by default, but if the user
is using full-screen magnification before migration, we will set it to
full-screen.If the above situation happens, we show a prompt dialog to
inform theuser the new feature when using full-screen magnification
first time.
Note the default value will be applied if the user erases all datas.
Test: 1. Enable/Disalbe full-screen magnification and observe
the values after flashing.
2. Erase all datas and observes the settings values.
atest SettingsBackupTest
Bug: 162525393
Change-Id: I3dc749c2414f3aa9162c0f2a31b512c5e6a3ae80
ANGLE global settings variables have an unnecessary prefix, remove it.
Bug: b/170982184
Test: atest CtsAngleIntegrationHostTestCases
Change-Id: Id98e69820c90ede16cec8e798c0c77200b951966
Those annotations could be inferred by some tools (like Kotlin), but the
https://checkerframework.org/ doesn't check inherited annotations
complaining about all equals() invocations that get nullable argument.
The change was generated by running
find . -name \*.java | xargs sed -i 's/public boolean equals(Object /public boolean equals(@Nullable Object /'
in the frameworks/base directory and by automatically adding and
formatting required imports if needed. No manual edits.
Bug: 170883422
Test: Annotation change only. Should have not impact.
Exempt-From-Owner-Approval: Mechanical change not specific to any component.
Change-Id: I5eedb571c9d78862115dfdc5dae1cf2a35343580
Based on the CONVERSATION_TYPE flag, shows only priority conversations
or all conversations. Defaults to showing all conversations.
Test: locally
Bug: 169783793
Change-Id: I4cb62cc9e4f9e5e488247d97b5624be97a94f8b0
Test: manual - flashed the phone and verified the logging and statsd sampling with default settings
Bug: 131859447, 162927074
Change-Id: I2637100b4945732f7bd792831749ca2614971c5e
The WebView fallback mechanism was removed in Q and replaced with code
to migrate the state of upgraded devices to the new configuration. This
is no longer necessary; remove the logic to simplify the code.
The notion of a WebView provider being designated as the fallback is
kept, as this is still used by the code which checks if there is no
valid provider at all at boot time and tries to fix the situation by
re-enabling the fallback provider for all users - this was added for
b/132815849 and should suffice for any devices which haven't executed
the fallback migration code.
Bug: 129470358
Test: atest WebViewUpdateServiceTest
Change-Id: I4de777b650fb793903f6df74a7ff639190d8b0a9
Add new Settings.Global.SHOW_NEW_LOCKSCREEN property. When enabled, new
lockscreen & aod UI + transitions will show. This is a temporary flag for the
purposes of protoyping which will be removed before release. Therefore, it should
not be backed up.
To toggle the flag (value = 0 is disabled, value = 1 is enabled):
adb shell settings put global show_new_lockscreen <value>
Test: manual
Bug: 170228350
Change-Id: I3b40b1de9bb80d43218fa1e8661fba47b50e9888
Add values to track activation, intensity level, and persistence state
Add an activity action to open the subpage directly
Test: builds
Bug: b/128465252
Change-Id: Icc9989254bc044377c162a8d94eec37723d86c19
The feature is disabled by default and can be in one of 3 modes:
disabled, permissive and block. In permissive we only log but
don't block the touch. This knob is implemented in a global setting
block_untrusted_touches. It can also be disabled per occluding app using
app-compat infrastructure, so if you disable for a certain app, overlays
of that app won't have the chance of blocking touches. More details
on these on go/try-cross-uid-touches.
Each window has 3 modes related to touch occlusion: ALLOW, USE_OPACITY
or BLOCK_UNTRUSTRED. Check code comments for the meaning of each. If the
feature is turned off for the app, then the mode is ALLOW. Else if it's
a SAW, then it's USE_OPACITY. Else it's BLOCK_UNTRUSTED. These states
are passed to InputDispatcher, who then perform the proper checks and
blocks or not the touch.
If input dispatcher deems the touch unsafe, depending on the feature
mode, we filter out such touches and log a message to logcat.
I also introduce a global (secure) setting
MAXIMUM_OBSCURING_OPACITY_FOR_TOUCH which represents the maximum
opacity allowed per UID that's obscuring the touch-consuming window
according to some rules, which are discussed in topic CL for
InputDispatcher code. This maximum is initially set to 0.8, but we'll
be conducting local experiments to determine the final value.
Test: atest WindowUntrustedTouchTest
Test: atest inputflinger_tests inputflinger_benchmarks libinput_tests
Test: go/try-cross-uid-touches for manual testing
Bug: 158002302
Change-Id: I462858ad5f0d11b1261748489385e6409e38e4b1
When the user changes, populate the global config with the current
user's setting state. For new users, don't keep the previous user's
preference
Test: manual, switched between users
Bug: b/110991537
Change-Id: Iae412bccd64784a597ed8d493f1bda4984841cac
This functionality is now handled by the location service, and legacy
settings code can be removed. Full removal to follow later.
Bug: 148963686
Test: presubmits
Change-Id: I7de19f17759b0a13b96dd8960d2dbdb84ffd72d9
People Space is a new feature in SysUI. This global settings entry
will determine whether a user will see the feature and it is not
user configurable, so it should not be backed up.
Test: build
Bug: 169410721
Change-Id: Iaaefaedbd8e17e09633478b44458713f3eae0362
Introduce angle.egl.features to assist ANGLE debugging. The input
contains lists for each opt-in apps. The format is each list of features
is separated by a comma, each feature in each list is separated by a
colon, e.g. feature1:feature2:feature3,feature1:feature3:feature5
Bug: b/169156341
Test: use adb shell command to verify
Test: atest android.gputools.cts.CtsRootlessGpuDebugHostTest
Test: atest CtsAngleIntegrationHostTestCases
Change-Id: I752047df1c2567b4ebf900c3acb4a965e35dd6c2
Add support for submitting buffers in SurfaceView via BLAST using
BlastBufferQueue adapter.
Introduce a new config wm_use_blast_adapter_sv, that is disabled by
default to enable the adapter.
When enabled, the blast SC is created as a child of the main
SurfaceView SC and the main SC is set as a container layer. This layer
will continue to handle position, visibility and transforms while the
blast SC will handle buffer updates via the adapter.
Test: atest SurfaceViewBufferTests
Test: go/wm-smoke w/ & w/o adb shell adb shell settings set global use_blast_adapter_sv 1
Bug: b/168504870, b/168917217
Change-Id: I826eef39e03ea339df54400be0709eaba6c88797
This solves the issue where the device would forget the learned state
when restoring from a backup.
Test: Tested locally
BUG: 159807978
Change-Id: Ia1d5926621c4b45402036aaf06cbab19c12869bd
Twilight mode is not available when the phone starts. So the last state
is rememebered until the phone screen turns off
Fixes: 160842085
Test: manual testing
Change-Id: I78a490c0f083e92022e1995b3e19dc7dd567a7c3
Revert "Allow user to block individual apps from resuming."
Revert submission 12392268-cherrypick-mediaappsettings-5fxuo164a2
Bug: 161813143
Reason for revert: no longer want change in QPR
Reverted Changes:
Id3de52419:Allow user to block individual apps from resuming....
I8c85bc937:Allow user to block individual apps from resuming
Change-Id: I888079abc77f5bc22aefa19c2f7523bb9db05bf8
Implement the following features to support carrier network connection.
This commit is to define the carrier config for each features.
1. Sets default preferred APN
2. Uses dun APN when using Preset APN in roaming network
Also, fixed that to use only APNs with the same set id as preferred
APN.
Test: Manual
Bug: 147969062
Change-Id: If1e6d2bf58de39c22caa901fcd90fb11f104d900
(cherry picked from commit b9beb0d1afda6327b1c7645ac20a016f08e5744e)
This migrates flags inside AlarmManagerService to DeviceConfig.
DeviceConfig is the recommended way and using it means
that we only operate/parse the set of flags that changed instead of
every single flag whenever one of them changes.
Bug: 124466289
Bug: 159068048
Test: atest AlarmManagerServiceTest
Test: atest CtsAlarmManagerTestCases
Test: atest CtsBatterySavingTestCases:BatterySaverAlarmTest
Test: atest SettingsProviderTest:SettingsBackupTest
Test: atest com.android.server.cts.IncidentdTest
Change-Id: I21263f54f57bf2a59daafbc35fe6bdfbaf4f031b
