One of the optimizations ag/12911059 did was calling
SelectionModifierCursorController.show() before
startActionModeInternal(). The rationale was that if we start the action
mode first, SelectionModifierCursorController.show() would end up
invalidating the action mode twice unnecessarily, once for each handle.
However, with this optimization, we are calling
SelectionModifierCursorController.show() even when onCreateActionMode
returns false.
Reverted this particular optimization to fix the issue.
Added a test which was failing without this fix but passing with it.
Fixes: 199380016
Fixes: 214341747
Test: atest TextViewActivityTest
Merged-In: I793f76a23978cbbbbde2d16e8a522615174bcdd5
Change-Id: I793f76a23978cbbbbde2d16e8a522615174bcdd5
(cherry picked from commit 11bd64482249c9257ee22390de15f69f9c834247)
This change removes the privapp allowlist from Traceur, which had
previously explicitly granted the DUMP, QUERY_ALL_PACKAGES,
START_FOREGROUND_SERVICES_FROM_BACKGROUND, and STATUS_BAR permissions.
These permissions no longer need to be granted because Traceur is now a
platform app.
Bug: 209476712
Test: - Checked that Traceur can still take normal and long traces on
AOSP userdebug and internal user/userdebug.
- Checked that bugreports will stop ongoing traces.
- Checked that the quick settings tile still stops/starts traces.
Change-Id: I33cd317f9fe00e2e08ae205a832237bfe0df044a
Merged-In: I33cd317f9fe00e2e08ae205a832237bfe0df044a
To remove the need of giving system_server the syslog_read permission,
we are introducing dmesgd, a service that will be launched by init and
perform dmesg output parsing and collection of kernel error reports.
In order to trigger the service, BootReceiver just needs to set the
dmesgd.start property to 1.
Bug: 215095687
Test: run on a user device with injected KFENCE bugs
Change-Id: Ifcfe83ad559633558bba623fb514d7b27d97f6af
This allows us to monitor any failed reports using
go/perfetto-monitoring.
Bug: 205892741
Test: New CTS test PerfettoTests#testSkipReportAtoms and
PerfettoTest#testReportAtoms
Change-Id: Idf72bc693c1730fcb522b7a9ecfdf3c9db8b0777
1) Keyname should not be including key_
2) This is bundle type not to be used as int array
Bug: b/216365058
Test: atest
Change-Id: Ia2db386e7394fd09194477e529fc6e8c752623c2
Merged-In: Ia2db386e7394fd09194477e529fc6e8c752623c2
A new VTS test is added to the OMAPI VTS to validate the schema of the
hal_uuid_map_config.xml file.
Bug: b/180640274
Test: atest --rebuild-module-info VtsHalOmapiSeServiceV1_TargetTest
Change-Id: Ib1ae39c0c33c066973ddc3fcb0b0c37535fa515e
Remove usage of hidden symbols for network stats APIs, replacing them
with public API alternatives.
Also fix backup of NetworkPolicy when the set of subscriber IDs is
empty. This as not caught because the test used a hidden API builder
that creates a non-empty set containing null.
Bug: 197717846
Test: atest FrameworksCoreTests
(cherry-picked and fixed merged conflict from ag/16781267)
Change-Id: I45a98795c571ac97bd6025988da156bd06d57e45
Merged-In: I45a98795c571ac97bd6025988da156bd06d57e45
While SystemId/NetworkId in 3gpp2 network are not a one to one match
of MCC/MNC in 3gpp network, they servie the similar purpose and
should have same level of privacy protection.
To have a consistent privacy protection policy, SID/NID are also
redacted when calling app has no location permission.
Bug: 188061647
Test: atest ServiceStateTest ServiceStateProviderTest
Change-Id: Ibf068f950c82270f59aa40e8bb6721f8b9c989bf
The sysprop is needed to avoid JNI when accessing KNOWN_CODENAMES
from native code.
Bug: 211747008
Test: atest android.os.cts.BuildTest#testBuildCodenameConstants
Change-Id: I713a122655f5f8a6a2fed5cee61bbe4094acbeb8
The new xmlnotice utility includes library names in the xml notice.
Supports both the new and the old schema and allows mixing new and old.
Bug: 151177513
Bug: 210912771
Test: m all dist
Test: flash; About Phone -> Legal Information -> Third-party licenses
Change-Id: I69c294a62d1653e9a0ff487e25b1d2eda0b777d3
Full draw will be happened on HWUI under 90/120Hz device,there are
more draw commands under renderFrameImpl than in the 60Hz fps device,
frame.bufferAge() > (int)mSwapHistory.size() resulting in an increase
in power usage.
So need to increase (int)mSwapHistory.size() to 8, set mSwapHistory
add to 7.
Bug: 209371516
Test: Manual
Change-Id: Ic6f21e7b9dc5e7c8f36d03c57b01fa7210cff86f
Merged-In: Ic6f21e7b9dc5e7c8f36d03c57b01fa7210cff86f
