NSD_ON setting has never been set since it created. The
NsdService is the only user which read/write the setting.
However, NsdManager cts test must running with nsd service
enabled that means this setting should be enabled
always. And this setting is the hidden symbols that
NsdService can't use it after move to mainline module. Thus,
remove this useless setting.
Bug: 206702844
Test: m
Change-Id: Idb5dfc71ebfe2eacd476dd8646aad9adc4975149
Add fields for lingering bearer bitmask and is always on
Update values for MTU V4 and MTU V6
Test: atest DataProfileTest
Bug: 198822816
Change-Id: Ia007f22a5c976fa139e61d981779a65b5e3ffd3e
Merged-In: Ia007f22a5c976fa139e61d981779a65b5e3ffd3e
Add a setting to support for NITZ retention, see the comments for
details. The comments for related settings have also been updated to
better reflect their meaning / improve consistency with the new setting.
Bug: 204415203
Test: See frameworks/opt/telephony/ change
Change-Id: Idb21dc9ea7a1ad5cbb7a8bd238ab9a71174ee1ff
- Added a telephony provider entry for storing the user's settings.
- Added new vonr_enabled_bool config to determine whether VoNR
should be enalbed for carrier
Bug: 202150953
Bug: 205625979
Test: manual
Change-Id: Ie56a7de3fdb978353af77bafb55b0e37c22b58a4
Merged-In: Ie56a7de3fdb978353af77bafb55b0e37c22b58a4
This remove the leak of hidden private field and add an api to get
entreprise raw contact
Bug: 194119078
Test: Build
Tag: #refactor
Change-Id: I9285cd54545e1359a4a7f57826ddb1a0e1dcdfbe
Clarifying that you CANNOT use LIMIT in the where clause and provide
instructions on the right way to limit results.
Test: Docs only change
Bug: 175599057
Change-Id: Ib4e828fc33ae9b75e7a240e9f456907049fcc35e
For experiment flag testing, adding lmkd flag in DeviceConfig.
Bug: 194316048
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
Merged-In: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
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
Test: Cherrypick ag/15542611
Test: Ensure Assistant invocation is set as the LPP action
Test: Adjust LPP sensitivity
Test: Hold LPP for the set time
Test: Observe activation duration matches set time
BUG: 192995149
Merged-In: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
Change-Id: I820a9d83fd56bfa9ca978e82eb779cf3d519a5ab
For experiment flag testing, adding lmkd flag in DeviceConfig.
Bug: 194316048
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
Merged-In: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
For experiment flag testing, adding lmkd flag in DeviceConfig.
Bug: 194316048
Signed-off-by: Suren Baghdasaryan <surenb@google.com>
Change-Id: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
Merged-In: I1f13d6bbb4a9a7fd8825d7e5acde416750271df4
Remove setting option and show lockdown button by default in the power menu
Fixes: 185618694
Test: atest GlobalActionsDialogLiteTest
Test: flash device, set PIN, observe button present
Change-Id: I7c8f976fd73f6edf3edb26c8de31fd83eb9ac296
App processes might need to read the Settings value using system code.
Therefore this key is @hide but should be @Readable.
BUG: 191519696
Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest
Change-Id: Idf1512ebf3487d74a18ad2dc13ee7cbb2c7643d0
Some users had a bad default value from a previous build. This renames
the flag so that they will still get the correct default when upgrading.
Fixes: 191786947
Test: manual, atest
Change-Id: I8fa3077bf7c8a4414ebc259174214538684f6560
This reverts commit 516cb2d025.
Reason for revert: Add back after merging f2fs/f2fs-tools changes removing immutable bit stuffs
Bug: 188928405
Change-Id: I6a6fcde1190bff14abe1a67a75b8e7be95d89072
This reverts commit e41b029d85.
Reason for revert: b/189985437
com.android.tradefed.targetprep.TargetSetupError[APK_INSTALLATION_FAILED|520001|DEPENDENCY_ISSUE]: Failed to install com.android.devicehealthchecks with ...
Change-Id: I06fe7d94f6dab474c74b093de8692f08d4031b62
Modern f2fs implementations starting in S support compression
natively within the file system. The data blocks of specific
installation artifacts [eg. .apk, .so, ...] can be compressed
at the file system level, making them look and act like any
other uncompressed file, but consuming a fraction of the space.
However, the unused space is not free'd automatically. Instead,
we must manually tell the file system to release the extra
blocks [the delta between the compressed and uncompressed block
counts] back to the free pool.
Because of how compression works within the file system, once
the blocks have been released, the file becomes read-only and
cannot be modified until the free'd blocks have again been
reserved from the free pool. For these installation artifacts,
that is not a concern.
Test: atest CtsAppSecurityHostTestCases:SplitTests
Test: atest CtsAppSecurityHostTestCases:IsolatedSplitsTests
Test: atest CtsAppSecurityHostTestCases:PkgInstallSignatureVerificationTest
Test: atest CtsLibnativehelperTestCases
Test: atest PackageManagerTests
Test: Manual. Boot the device and see cblocks for stub APKs are released
Test: Manual. Disable and re-enable stub APK and see cblocks are released
Bug: 188928405
Change-Id: I4b29dab263d02a79d7b1593d35ae28101d33679a
