There will be no special protection mechanisms around MODULE_APPS,
so we're going to remove it for now.
All the MODULE_APPS should be protected with a permission, etc, so
the change should be safe.
Bug: 148177503
Test: Build / treehugger
Change-Id: I76328c2d5aaa3f171bf8afde5b3d1accad8c2e2b
The usage was removed from opt/net/wifi earlier.
Also, cleaned up a bunch of other settings in SettingsProvider
that were previously removed in ag/10080845.
Bug: 141623345
Test: Compiles
Change-Id: I18690ee12d6b701b6f487285e36ca0143244bcfd
AT&T requires showing data coding scheme, location check
time, whether shown to the user or not in the test menu.
Expanded database to support this.
Bug: 144152683
Test: Manully sending fake messages and verified database
Change-Id: Ib5b78802e7548da9f92492aae4c94ed3488b5e3d
RawContacts.BACKUP_ID is public and might be used by 3P. So we will not
deprecate it.
Test: build
Bug: 147668000
Change-Id: I63d4541340cde03e7269b0680a61b7fd198e7df9
and cache things on the first round trip.
Test: atest frameworks/base/core/tests/coretests/src/android/provider/NameValueCacheTest.java
Bug: 147739090
Change-Id: I9ed48f34be096f2b2d673ee1f5330388c14b695c
1. Background started foreground service shall not have
while-in-use permissions including location, camera and
microphone. Many exemptions have been applied including:
--FGS started by widget.
--FGS started by notification.
--FGS started by IME or other visible app.
--FGS started by ROOT_UID, SYSTEM_UID, NFC_UID.
2. Add a phenotype key KEY_DEFAULT_BACKGROUND_FGS_STARTS_RESTRICTION_ENABLED
to turn on/off this feature (default is on).
3. In dogfood, if a background started FGS with while-in-use permission
(any of location/camera/microphone) run into this restriction, the FGS
will not been granted these permission. we show a toast message to
alert user and ask them to write a bugreport using instruction at
go/r-bg-fgs-restriction. So we can have a statistic how many apps will
be impacted by this feature.
These is a flag Settings.Global.FOREGROUND_SERVICE_STARTS_LOGGING_ENABLED
to turn on/off the toast message (default is on, in dogfood)
Bug: 136219221
Test: atest android.app.cts.ActivityManagerProcessStateTest
atest android.app.cts.ActivityManagerApi29Test.java
atest android.app.cts.ActivityManagerFgsBgStartTest
Change-Id: Ibc8aaa6839a69136f9311bfacdbab9705b31b6a7
Bug: 144838882
Test: atest SettingsProviderTest:SettingsBackupAgentTest
Manual: 1) Run backup for settings
2) Change several settings
3) Run restore for settings
4) Through adb logcat verify settings changed in 2) are
not restored
Change-Id: Id309a9417b992eddddb9fe2830f2a691224af9af
1. Move isSatisifed into RuleEvaluator to minimise the API surface.
2. Add a new global settings for skipping integrity component for rule
providers.
3. Incorporate changes suggested by API review in http://b/147835536.
Note that this change is forked from ag/9974531.
Test: atest frameworks/base/core/tests/coretests/src/android/content/integrity/
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/integrity
Bug: 145290357, 147835536
Change-Id: Ic358a83b6bdcd4cb783e6904869f7dc2d136a55e
Shadows are generated on PiP and Freeform windows by setting an
elevation on the window's DecorView. The elevation is passed back
to wm as surface insets to generate a large enough surface for the
client to draw its content and render shadows around it.
This cl introduces a new settings which overrides the setElevation
call in DecorView and sets a shadow on the task surface. The
elevation of the DecorView and the surface insets will remain unset.
Add a surface crop to the task surface so we have proper bounds
to draw shadows.
Test: go/wm-smoke
Bug: 136561771
Change-Id: Icc45e4fac3d495df5272d2e5f37163b9e7caeb4c
Add the ability for the user to turn on/off UCE in settings.
Bug: 148167203
Test: atest CtsTelephonyTestCases:RcsUceAdapterTest
Change-Id: Ic53a9ef32343bfa4d96c2cf7fc0f0791265d2bd1
Exposing APN specific constants for use within APN classes in other modules.
Bug: 148170690
Test: make, flash
Change-Id: I86d513a0e1a4a04d8ec199463942dea416cee5e1
Adds a new API that allows applications to provide payment cards and
other relevant passes to SysUI which are then shown in the Quick Access
Wallet (long press on Pixel). See go/aospqaw-dd for details.
Bug: 144342153
Test: manual - started device, didn't blow up
Test: atest - run from frameworks/base dir
Change-Id: I8fef3116e6e4bd1f8a4f5a907892ea8993b49b0e
allows the use to set the start and end automatic dark theme
activation within a day.
Fixes: 147649309
Test: atest UiModeManagerServiceTest UiModeManagerTest
Change-Id: Iaa3593d4e8863412e3703ce9f089b88dd4df1225
For ViewRootImpl on BLAST experiment, setting up namespace and flag to
turn on Blast adapter through P/H experiment
Bug: 147096935
Test: build, boot, adb shell device_config put
window_manager_native_boot wm_use_blast_adapter true/false
check that BLAST adapter is turned on/off as expected
Change-Id: Ie1b158721ac9b751fcf3954310259f14486d3bb8
When there is a new DeviceConfig access related calling package
will be monitored for 48 hours for crashes. If crashes occur,
only relevant accessed namespaces are reset.
Test: atest RescuePartyTest.
Bug: 136134408
Change-Id: I8d585496783812842c34f440e250469c2d510f3a
This is required for the direct tabbed DocsUI experience that doesn't
involve the up-front disambig (that always only has one app in it).
Bug: 145895146
Bug: 147900456
Test: atest CtsProviderTestCases:android.provider.cts.DocumentsContractTest
Change-Id: Ic44b592382d880cdd76df2885ca8c52b1b697697
This secure setting doesn't need to be backed up because it represents a device state (e.g. airplane mode) and not a user-specified configuration.
Test: SettingsTest, Settings_SecureTest, SettingsProviderTest
Bug: 147584235
Change-Id: Ic89182297b095d128c63a4b422b4af2e3a63f3d3
Minimal post processing might not be very well supported on all TV
displays (e.g.the switch to/out of the low latency mode might be too
slow or there might be flickering on the screen or some color
interference, etc). This depends on the vendor implementation of minimal
post processing. In such cases, we want to give the user an option to
disable this feature in the settings menu. This means that any calls to
the API (Window.setMinimalPostProcessing) will be ignored and no signals
will be sent to the display.
This CL adds the necessary flag to Settings.Secure. The value is read
from DisplayManagerService, which combines it with the information from
the WindowManager and the display capabilities to request the right low
latency mode on the display.
Bug: 144356279
Test: m && ./vendor/google/tools/flashall
1. adb shell settings put secure minimal_post_processing_allowed 1
2. Open Activity that prefers minimal post processing
3. adb shell settings put secure minimal_post_processing_allowed 0
-> this should turn ALLM off
4. adb shell settings put secure minimal_post_processing_allowed 1
-> this should turn ALLM back on
5. Exit Activity
-> this should turn ALLM off
Change-Id: I2d24a9a004d4939b0439d466ef2ca279803fd67f
Some APPs(like OMA DM) might enable or disable 5G settings, so redesign
the setPreferredNetworkType behavior.
1. Create allowed_network_type in telephonyprovider
2. Create get/set allowed network type API
3. When APPs call setPreferredNetworkType() that will AND with allowed
network type.
Bug: 136730709
Test: By Manual
1. setAllowedNetwork to disable 5G
2. setPreferredNetworkTypeBitmask to set NR_LTE_GSM_WCDMA
3. framework set LTE_GSM_WCDMA to modem
Change-Id: Ia257e6ddaa33c32bc09340a59c9daf71ce1fa8cf
Common Criteria mode puts device into a state where certain
funtionalities are tuned or turned on to meet the higher security
requirement from Common Criteria certification. Device Owner
can use the new device policy API to toggle Common Criteria mode.
Bug: 137937540
Test: atest FrameworksServicesTests:DevicePolicyManagerTest
Test: atest SettingsProviderTest
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testCommonCriteriaMode
Test: atest com.android.cts.devicepolicy.OrgOwnedProfileOwnerTest#testCommonCriteriaMode
Change-Id: If07c053437e980ed3317d3838cc74e5bfd44efce
WifiConfiguration used in the feature of add apps Wi-Fi networks was deprecated, need to be changed to use WifiNetworkSuggestion instead.
Bug: 136472483
Test: just add action, test case will be in Settings App side.
Change-Id: Ia1e4ab88dd70f951ff4e9115b1e373a9886ab565
