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
New annotation field that allows Settings key owners to specify the
maximum target sdk level of the caller app allowed to read the
hidden settings key.
Test: atest android.appsecurity.cts.ReadableSettingsFieldsTest
BUG: 187314081
Change-Id: Ibb603df4c8bca75e3788258e69862595c22e5154
Add a system setting to signal that the Clockwork
Home application has finished initializing.
The setting is marked as transient so it's value
is not persistent during device reboot.
Bug: 149253712
Change-Id: I74e75509dd22b3a1a5cc4c88866d059fed44a347
(cherry picked from commit 3084060da2b4c4fc66a47b75ef85adc11c4de36f)
- Add a new setting to control whether smartspace recommendations are
enabled
- Remove setting to block individual apps from resumption
Bug: 187925818
Test: atest MediaDataManagerTest
Change-Id: If1d5f4c5a204e655a90dd2cca6687acdfcd12fec
Bug: b/188122403
Test: Manual. Triggered an ANR and verified the error id is present in
the ANR dropbox entry.
Change-Id: Id6ac956ca5fe635189d12a9e2c0ba14e26e8719d
Create a new DeviceConfig entry to replace the prior Settings entry on
which the location ignore settings allowlist is based. This allows us to
allowlist based on attribution tag, and eliminate holes for large
applications.
Test: manual + CTS + GTS
Bug: 187421886
Change-Id: I31e61db79b93e202bd8c66efae1bb5aaf0c88ff5
Wallet/controls privacy setting has been moved and split into
two. Migrate the old setting if the user had previously used
controls. From the QS tile, launch the activity differently when on
the lock screen.
Fixes: 188175341
Test: atest DeviceControlsTileTest
Change-Id: If38ae1c3f0bcc8e0e75146dda09276c13a0604e9
Add a secure settings to control the game dashboard shortcut always on
option for all games.
Bug: b/185822999
Test: manual
Change-Id: I96b6ebd6c25230e8f12f3871ef1e78fcce9225e8
The unique id is added so that the trace and ANR can be easily linked
server side. Also moves the logging of the ANR atom before the ANR dump
takes place so that the Perfetto trace captures data closer to the point
in time when the ANR happens.
Bug: b/188122403
Test: Manual.
1. Enabled the flag:
adb shell device_config put perfetto_error_logger append_perfetto_uuid
true
2. Triggered an ANR using a test app. Logs from PerfettoTraceErrorLogger:
adb logcat -s PerfettoTraceErrorLogger
--------- beginning of main
04-30 14:07:02.527 1782 12583 I PerfettoTraceErrorLogger: Pushing trace
counter: 6c555dc6-3f46-4997-8844-706d91156600#PerfettoMonitoredCrash
3. The UUID is present in the ANR dropbox headers:
adb shell dumpsys dropbox data_app_anr --print | grep
6c555dc6-3f46-4997-8844-706d91156600
PerfettoUUID: 6c555dc6-3f46-4997-8844-706d91156600
Change-Id: If7110692cb0856e693f595e24b067ce1bc7d0a38
This adds a "sync disabled" mode which disables bulk updates to
device_config (AKA server flags). This is intended for use during
automated and manual tests that use device_config settings to set the
device into specific states for tests. Without this, devices can sync at
an arbitrary point during a test which can undo device_config changes
the tests have made and cause them to fail / flake.
This mechanism is independent of the mechanism used to sync, thereby
making it suitable for use in CTS or other AOSP tests, i.e. to disable
sync regardless of whether GMS core or an alternative is handling the
sync.
Test: atest core/tests/coretests/src/android/provider/DeviceConfigTest.java
Bug: 185786624
Change-Id: Icd0ce798642eb136dc8b9b1a58a4ecbc6212fdba
* changes:
Add the new migration tooltip for accessibility floating menu.(2/n)
Add the new migration tooltip for accessibility floating menu.(1/n)
Add key ACCESSIBILITY_FLOATING_MENU_MIGRATION_TOOLTIP_PROMPT.
Remove @GuardedBy on a final, immutable field as it is causing
errorprone warnings on a work-in-progress commit.
ContentProviderHolder.mUri is accessed in multiple places without
holding mLock, and it is final and documented as immutable so should be
safe to access without mLock. This commit should reduce ErrorProne
warnings now and in future.
Bug: 185786624
Test: build / treehugger only
Change-Id: Ic7fbe550ff6f538f336cfb859f66daa94844ca28
The key used to show the migration information related to
the accessibility floating menu.
Bug: 175365399
Test: atest SettingsProviderTest
Change-Id: Ifabc412b990c72ad345bab2d5d8539a57bd6ca5d
