| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
into main am: eee659508c
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3554852
Change-Id: Ic93da31c5479074dcf3e83361c6b49635212e3ed
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main
|
|
This reverts commit 2415c43a8bf5e683555fcaa48d1dad522db62229.
Reason for revert: Potential culprit for b/405191766. Will merge after verifying with ABTD.
Change-Id: Ia89aa852c3fcae0e040a911b4e9de8172b4ac177
|
|
Android.bp"" into main am: 3070b84f7d
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3555583
Change-Id: I7f5a2a713f2fb64560321aac4d58c1f0f4f05d82
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
Android.bp"" into main
|
|
This reverts commit 29b36a471b9fec8cade9ee7fa60b031f23884094.
Reason for revert: Droidmonitor created revert due to b/405179425. Will be verifying through ABTD before submission.
Change-Id: I00b9fe274365080d7def6264f13a46070381d6f4
|
|
|
|
into main am: 20ddf54e76
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3540939
Change-Id: Ib55f6df613b8dd9946950ad35f7aa9d8f006fae6
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
main am: b2af58f0c7
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3550700
Change-Id: Idf82a8d7cd5e16f904f9832fb616e0545d5751dc
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
into main
|
|
|
|
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
|
|
Bug: 401370820
Test: presubmits
Change-Id: Ibaaf34b8116a746fd2262d53fd4fc6fbc5b012ec
|
|
Bug: 401370820
Test: presubmits
Change-Id: I8444799641245923ff570361262e0396812c8642
|
|
e4f7d26846 am: 33a3095926
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3546263
Change-Id: I26888b8d45d7f06af3824edf00bfef6d1cd6a013
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
StatementService is not installed when a target has GMS core.
As the installation of this app depends on the build target, move it to
system_ext. system image must not include target specific modules.
Bug: 401090620
Test: atest StatementServiceTests
Change-Id: I138981cd8fe98157098eba9efc3a0684d7ffbe76
|
|
Test: manually
Flag: EXEMPT file not eligible
Bug: 394019582
Change-Id: I0b38fb96eda366ff7f608a303cca07da31e1e8dd
|
|
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
|
|
Bug: 385190204
Merged-In: Ibc80f09d54bec2c83814874d94a8f8eb22b5075f
Change-Id: If7779ae57fd91631d08bd8af5434c2ddd963aad7
|
|
|
|
am: 17b492cd4e am: b79b82f8af
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3507846
Change-Id: I2bdf2af842c039e2b059d0eed803763056c30b3b
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: Ida80c895dfa0228392977a7bc1422afe06358328
|
|
To enable OTP detection, ExtServices requires the ACCESS_TEXT_CLASSIFIER_BY_TYPE permission to access specific TextClassifier. Because ExtServices cannot utilize the role, the permission is being added as privileged to allow its granting.
Bug: 377229653
Bug: 388899782
Test: atest FrameworksCoreTests:TextClassificationManagerTest CtsTextClassifierTestCases:TextClassificationManagerTest CtsPermissionPolicyTestCases:PermissionPolicyTest
Flag: android.permission.flags.text_classifier_choice_api_enabled
Change-Id: I606227245a6c80f5717df92bfd3760f21ee11d11
|
|
This permission is used to gain access to update_engine_log
directory.
This is a subset of android.permission.READ_LOGS and is intended
to limit the log access for components that only want to access
update engine logs.
Flag: com.android.update_engine.minor_changes_2025q4
Bug: 397893018
Test: Flash software, check permissions of directory
Flash software without this patch. Flash software with this
CL on top. Confirm permission. Confirm log files included in
bugreport.
Change-Id: I517c8aab3159cdb970c9499d2aad89cc262b68e2
|
|
From b/291854577, KEYCODE_TV_POWER has some problem as interoperability issues where the TV doesn't act on the HDMI-CEC messages as expected. Also, if the set-top box's and TV's power state are not in sync (one is ON and the other is OFF), the power control could be wrong.
From https://developer.android.com/reference/android/view/KeyEvent#KEYCODE_TV_POWER, it seems this is only for like set-top box to use HDMI-CEC to control TV power or not. But both TV and STB support KEYCODE_POWER.
Bug: 390553665
Change-Id: If664d7a6dd680579c7e6d69e1fcd900edb3530f0
Flag: EXEMPT bugfix
|
|
Flag: EXEMPT add free TV key support
Bug: 394931597
Change-Id: I7cb6f99a153667d5308ce12f592ded71dc50480a
|
|
feb3a51ed2
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3491471
Change-Id: Icfb54d155c50a670e447bd846373ec253ab1d28c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
aosp/3486210 supports pulled atoms from mmd.
Bug: 392783537
Test: manual
Change-Id: I9b90a68012097a8b95bcb2a31047c283c3dd723c
|
|
am: 73e47e18b3
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3490911
Change-Id: Ifc1ee8dcefb3f7db8bf974490e15878602038b81
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
These have been removed in Python 3.12:
https://docs.python.org/3/whatsnew/3.12.html#id3
Bug: 388344853
Test: atest generate_fonts_xml_test -- --abi x86_64
Change-Id: Iaef6fbaa5033443b232dabc90888eb5d6bef64cb
|
|
ca5c29f62b am: b0c7c9916c
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3265331
Change-Id: I006ba03904a925c99e990db7ea3a3bf5f804373c
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
|
|
* changes:
Adding attribute to the new permisison LISTEN_FOR_KEY_ACTIVITY
Adding Permission for a global listener that will notify on user activeness events in InputManager
|
|
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
|
|
events in InputManager
bug: 356412905
Flag: NONE FF will be added in a later CL
Change-Id: I4190965c96b4885c6877c28aa8ba8c9f8b5a3e4d
|
|
Bug: 393122219
Test: atest CtsAppFunctionTestCases
Flag: android.app.appfunctions.flags.enable_app_function_manager
Change-Id: I1038766dc66375c5f9038d88d06b934ed0abc758
|
|
The gesture exclusion region set by the Accessibility Menu Window counts towards the global exclusion limit. With a few menu items, there is no gesture exclusion margin left to be used by apps.
To fix this, the PRIVATE_FLAG_UNRESTRICTED_GESTURE_EXCLUSION flag is set on the Accessibility Menu Window. This ensures that the exclusion region is not counted towards the global limit.
Additionally, this fixes the problem that the Accessibility Menu Window itself runs out of exclusion margin when it has many menu items. In that case, it's easy to trigger the back gesture when the intention is to drag the window.
Bug: 378425927
Test: Manual, i.e. verified that app's exclusion regions are unaffected by the presence of the Accessibility Menu. Also verified that dragging the Accessibility Menu never triggers the back gesture.
Flag: EXEMPT bugfix
Change-Id: I8f4171b92acfdeffd0e1bc383587320e15c9ef71
|
|
PictureProfile/SoundProfile Allowlist
Test: m
Fix: 388912026
Fix: 388912004
Fix: 388911800
Fix: 388912061
Flag: android.media.tv.flags.media_quality_fw
Change-Id: Icb2d993a8857d8ce71bb1d17ae9da14a5f11d519
|
|
8b34ce2db5
Original change: https://android-review.googlesource.com/c/platform/frameworks/base/+/3445377
Change-Id: I6ae412c55390a07cc32a818b81ac1223cf504a4d
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
|
|
info." into main
|
|
Bluetooth apex name has changed from com.android.btservices to
com.android.bt. We now need to update the reference in the code.
Updating apex_available in bp and other reference from within the code
Bug: 383863941
Flag: Exempt build infra
Test: m .
Change-Id: I5d71ac2f7df2a876e87934787c820630df890226
|
|
Bug: 341941666
Flag: android.permission.flags.fine_power_monitor_permission
Test: atest PowerStatsTests; atest android.os.health.cts.PowerMonitorsTest
Change-Id: I8f4abf2116d42e07dbc1aa97c15df29b00acead6
|
|
Due to new feature of freezing apps including system widgets, there is
no updates on system ui when user change profile picture or name.
Because some profile pictures are synced in in background we need to
make sure we update system ui when it happens.
This broadcast is protected by special permission and can be only used
by preinstalled system apps. The broadcast will not slow down the system
as it is fired on rare occasions.
Bug: 383071252
Flag: EXEMPT bugfix
Test: manual
Change-Id: I97c63d27040c6a313164e657d9bbb62f66cb4a3f
|
|
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
|
|
The privileged flag was added to the
SUBSCRIBE_TO_KEYGUARD_LOCKED_STATE permission. This commit updates
the platform's privapp-permissions for the wm.shell package to
include this permission.
Bug: 380120712
Flag: android.security.subscribe_to_keyguard_locked_state_perm_priv_flag
Test: Manually verified device booted with permission flag update
Change-Id: I466da2e6af665d1f1e05e30ac9dd1b6672abe7ec
|
|
"SUBSCRIBE_TO_KEYGUARD_LOCKED_STATE-privileged-flag" into main
* changes:
Update privapp-permissions for shell and systemui
Add privileged flag to SUBSCRIBE_TO_KEYGUARD_LOCKED_STATE
|
|
|