| Age | Commit message (Collapse) | Author |
|
Auto-generated-cl: translation import
Bug: 408276020
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:f0bad97f25f62372c982a620e35931889f787466)
Merged-In: I2a6d9aa4bf5b3fff1bb53b629931a1c2eca1fd3b
Change-Id: I2a6d9aa4bf5b3fff1bb53b629931a1c2eca1fd3b
|
|
|
|
|
|
This change fixes the Memory Tagging Extension developer option Settings
to be greyed out if the MTE state is controlled by AAPM.
The fix consists of:
* A change to the DevicePolicyManagerService to return the MTE policy
regardless of the caller identity - as the getMtePolicy metthod
does not care which admin has set the MTE policy, just the resolved
policy for the device.
* A change to RestrictedLockUtilsInternal to return an EnfocredAdmin
representing that the MTE policy is managed somehow. Other code
in the RestrictedLockUtilsInternal knows how to resolve the right
admin from the EnforcedAdmin.
To test the fix, the MANAGE_DEVICE_POLICY_MTE permission was added
to the shell.
It is safe for the shell to have this permission because:
* A human can query and modify the state of the Memory Tagging Extension
policy via Developer Options.
* If the device is managed and the user tries to disable MTE, there is
an additional check in the DevicePolicyManagerService that only the
device policy client (DPC) can disable MTE.
Bug: 402456665
Test: Manual, turn on AAPM with adb commands and observe the toggle in
Settings.
Test: atest CtsSecurityTestCases:android.security.cts.advancedprotection.MemoryTaggingExtensionTest
Test: atest CtsDevicePolicyTestCases:android.devicepolicy.cts.MtePolicyTest
Test: atest CtsDevicePolicyTestCases:android.devicepolicy.cts.DeviceManagementCoexistenceTest
Flag: EXEMPT bugfix
Change-Id: I55ffdec9b7abc29be503d85a7ae2607ba81938de
|
|
Auto-generated-cl: translation import
Change-Id: I64db9c25d58b573274e7bb1d820555d5133d5f4e
|
|
|
|
This is required for MediaStore_FilesTest in CtsModernMediaProviderTests. We want to verify update of oem_metadata field in MediaStore using update API but it requires privileged permission which cannot be provided to test app. Hence we need Shell to hold this special permission to verify the API behavior.
Test: n/a
Bug: 352528913
Flag: com.android.providers.media.flags.enable_oem_metadata_update
Change-Id: Iece552da4332bc981eac97461c4705d05bbbe322
|
|
|
|
To avoid notifications throttling, rate limit the notifications
instead of delaying the final notification. The final delay doesn't
worj in case the service get's killed, which can happen on a busy
device. Note, this is in control of the system and not the
service/client.
Bug: 395488230
Change-Id: I9fb20868e163292c7e12c5cc12c4e79c7683aab9
Test: N/A couldn't repro
Flag: EXEMPT Minor Change
|
|
|
|
Test: m checkbuild
Flag: TEST_ONLY
Bug: 310268946
Change-Id: Id68adb5ab554a8031f8d03f6158c0e9ffa03604c
|
|
A more generic name is much better as it could still be used for
creating trusted displays and input injection in the future, not only
for sensors.
And make it non-self-managed.
Bug: 368633836
Test: presubmit
Flag: android.companion.virtualdevice.flags.enable_limited_vdm_role
Change-Id: Iaa73b23231aa8a0faba6605edb9a87abb8799475
|
|
Auto-generated-cl: translation import
Change-Id: Ie85aff2fc05a29eb5406ad7c6bbdf24b18b5eb75
|
|
into main am: 20e330d22c am: a23423df54
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3506650
Change-Id: I21641e41a33b93db184385637a51516d5fead29d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main
|
|
main am: 65e1f0d72b am: 2336cc571d
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3509131
Change-Id: I5c485ab7091889b6c4dcbde72c8f2c0264d8d575
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
main am: 0d75e805d3 am: 6e0bef8021
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3507450
Change-Id: Ie36d460353ba8c7ada043cf556b7ea8b5811674e
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the OWNERs
file tidy. We ask that you do not ignore this change and approve it
unless you know a reason the OWNER should remain. It can always be
reverted if needed.
If this change is in error, vote the lowest CR value (i.e. reject the CL)
and the bot will abandon it.
See the owner's recent review activity for context:
https://android-review.googlesource.com/q/cbrubaker@google.com
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: I7512bc77e22872c2b7bac757d93b7323399cfe8c
|
|
Auto-generated-cl: translation import
Change-Id: I1022b69bd50ef68c6e1c8d9bc25e2cc8cc6da657
|
|
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the OWNERs
file tidy. We ask that you do not ignore this change and approve it
unless you know a reason the OWNER should remain. It can always be
reverted if needed.
If this change is in error, vote the lowest CR value (i.e. reject the CL)
and the bot will abandon it.
See the owner's recent review activity for context:
https://android-review.googlesource.com/q/toddke@google.com
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: I5275d6d854ca77ba8d9f30bfaa8287e1e9b61256
|
|
This suggested change is automatically generated based on group
memberships and affiliations.
Please approve this change and vote the highest CR. This will keep the OWNERs
file tidy. We ask that you do not ignore this change and approve it
unless you know a reason the OWNER should remain. It can always be
reverted if needed.
If this change is in error, vote the lowest CR value (i.e. reject the CL)
and the bot will abandon it.
See the owner's recent review activity for context:
https://android-review.googlesource.com/q/svetoslavganov@google.com
To report an issue, file a bug in the Infra>Codereview component.
Change-Id: I4aa01df6dca9d7606fb2af989679b2c63279a5fe
|
|
Auto-generated-cl: translation import
Change-Id: I8aa15fbbbc451948876b863960aaedc41ec23067
|
|
bug:380825247
Manual test:
- M -> to build
- sh vendor/google/tools/flashall -> to install changes
- Set watch to test mode: adb shell am broadcast -a com.google.android.clockwork.action.TEST_MODE
- Select Take bug report and press in details when finished
Flag: EXEMPT refactor
Bugreport: https://drive.google.com/file/d/1vCUk5Q18jWH2IPEbhTBUCZf0K3WE74LD/view?usp=sharing&resourcekey=0-qTNzJx3VoCf3lpsUEBCUIg
(cherry picked from https://partner-android-review.googlesource.com/q/commit:beeaf50d15a1bafb48f006b7cd77393d04180b3f)
Merged-In: Id59ecadbecd84f79474184c0110aa6536ec8abf4
Change-Id: Id59ecadbecd84f79474184c0110aa6536ec8abf4
|
|
Trade-in mode is difficult to test in automation because it is
inherently a user build feature. If it were enabled on ro.debuggable=1
builds, "TIM adb" would conflict with normal adb. So, it is one or the
other, and we have to pick "normal adb" to not break all CI and
developer workflows.
To work around this, we are adding new APIs to ITradeInMode to enable
testing TIM when ro.debuggable=1. This will allow us to test certain
aspects of the SUW machinery and the "getstatus" command.
We do this by setting a new persist property that is read on the next
reboot. On next reboot, normal adb is forbidden from starting, and
trade-in mode adb is allowed to start instead. disableTesting() unsets
the persist property. These APIs are only allowed when ro.debuggable=1.
Finally, we add a test method to schedule the same factory reset
procedure that occurs within "tradeinmode evaluate".
All the testing methods are restricted to ENTER_TRADE_IN_MODE privileges
and require ro.debuggable=1.
Test: adb shell tradeinmode testing start
Bug: 379970773
Flag: com.android.tradeinmode.flags.enable_trade_in_mode
Change-Id: I58234d4d2202e0be347e1a0486b7a0869a7867d2
|
|
Test: n/a
Flag: android.permission.flags.health_connect_backup_restore_permission_enabled
Bug: 392853668
Change-Id: Ic5d10c00643de91a2a42c37f56b319a09c340aa9
|
|
Bug: 393122219
Test: atest CtsAppFunctionTestCases
Flag: android.app.appfunctions.flags.enable_app_function_manager
Change-Id: I1038766dc66375c5f9038d88d06b934ed0abc758
|
|
So tests can rely on them instead of the roles
Fix: 391599603
Test: presubmit
Flag: EXEMPT test improvement
Change-Id: I1deb60e799174ed63bb483b8d3fe91bb97f1731d
|
|
PictureProfile/SoundProfile Allowlist
Test: m
Fix: 388912026
Fix: 388912004
Fix: 388911800
Fix: 388912061
Flag: android.media.tv.flags.media_quality_fw
Change-Id: Icb2d993a8857d8ce71bb1d17ae9da14a5f11d519
|
|
Auto-generated-cl: translation import
Change-Id: I0d5354dd42bfc6f74f7f81be5c78de9195110c67
|
|
Bug: 341941666
Flag: android.permission.flags.fine_power_monitor_permission
Test: atest PowerStatsTests; atest android.os.health.cts.PowerMonitorsTest
Change-Id: I8f4abf2116d42e07dbc1aa97c15df29b00acead6
|
|
|
|
If the screenshot size was less than 1, ScreenshotLocationInfo was not initialized and this led to a NullPointerException.
Bug: b/383927821
Flag: EXEMPT bugfix
Change-Id: Ie950d33ccc7c66d94d8a646de2e3e57aa75b1d3a
|
|
This API will take a caller's UID to fetch content providers available
to it. This will be used to prevent cross user access to content
providers.
Bug: 334024639
Test: atest CtsContentProviderMultiUserTest
Flag: android.content.pm.uid_based_provider_lookup
Change-Id: I430d87629a198a3e9dfe19f6ae1b7e01d4005e6d
|
|
e04c12bd1d am: c18864feb5
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3345004
Change-Id: I8af7c918ef1e7a2879644bc795bf58b9c9366683
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
e04c12bd1d
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3345004
Change-Id: Id98cbea1058ca025b7406e8a3bd56f0890f98444
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
https://googleplex-android-review.googlesource.com/q/commit:7c9f0370c8f0676e141fc42c3ebefa4ce39b014d) Merged-In: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3 Change-Id: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3" into main am: 4b08a4f9c0 am: 434f8b7d30
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3406699
Change-Id: I384ff21af632084df2caec5744eb2ffc8b024f75
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
https://googleplex-android-review.googlesource.com/q/commit:7c9f0370c8f0676e141fc42c3ebefa4ce39b014d) Merged-In: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3 Change-Id: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3" into main am: 4b08a4f9c0
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3406699
Change-Id: Ib704a6449c8e53adddc3492d64ff9b41805e619f
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:7c9f0370c8f0676e141fc42c3ebefa4ce39b014d)
Merged-In: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3
Change-Id: Ia8f72563aa2721e6a75c1b59bf7af1d32e55aea3
|
|
|
|
System discards notifications in case it comes too early.
Bug: 344946064
Test: atest com.android.shell.BugreportReceiverTest#testStressProgress
Change-Id: I9193bbfe487e81bf711112d673961cb285c81bbb
|
|
main
|
|
Bug: b/356843009
Change-Id: I2157e03dfbd9378320fe5d615937c90fd3c8de16
|
|
1) Added SystemApi method getClassifier
2) Added TYPE enums that are requred to use the new method
3) A new TYPE_OTP enum has been added to support OTP detection use cases
Note: It would have been ideal to expose the existing method `getTextClassifier(int type)` as a SystemAPI, however this method is annotated as `UnsupportedAppUsage`. While it is acceptable to expose it as SystemApi, in our case we will need to Flag and Guard with a permission. go/UnsupportedAppUsage#can-i-add-an-annotated-method-to-the-public-sdk-systemapi
Bug: 377229653
Test: atest FrameworksCoreTests:TextClassificationManagerTest CtsTextClassifierTestCases:TextClassificationManagerTest CtsPermissionPolicyTestCases:PermissionPolicyTest
Flag: android.permission.flags.text_classifier_choice_api_enabled
Change-Id: I513e06729e6de244a925c4e169bbdcaedfafc8e0
|
|
|
|
Bug:378047645
Flag: EXEMPT minor change
Test: Verified manually that correct activity
is launched in wear bugreport flow: https://screenshot.googleplex.com/43gvuNFZxByh73V, https://screenshot.googleplex.com/CwYuE65wJyjP2RJ
Change-Id: I709886407f6e81d6011c9e4d5c39dc6492b44596
|
|
BugreportManager API.
This is limited to bugreports of type wear.
Bug: b/378481755
Test: Manually tested Shell can successfully create a BR and forward the result to WearServices
Flag: com.android.shell.flags.handle_bugreports_for_wear
Change-Id: Ic3cf472750389333f8befe9dc13adc187947aa90
|
|
am: 16a91e433a
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3387639
Change-Id: Id00488a9029b12d54eb68938a86318f7086edc28
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3387639
Change-Id: I230126da34eb626bc5b7774e10ddd8d787a36eaf
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|