- Uses a String instead of URI for the main id.
- Uses FLAG_IS_PREFIX instead of isRecursive for UserDataRemovalRequest.
Test: m update-api
Test: atest CtsContentCaptureServiceTestCases CtsContentTestCases:LocusIdTest \
FrameworksCoreTests:android.view.contentcapture.ContentCaptureEventTest
Bug: 126945732
Change-Id: I34ae42678aa4021ea53ed66279cad4049ac2dcb3
It would be nice if there is a common & reliable method for both outer
& internal modules to check the UID presense of the display.
Add more check in Display#hasAccess() to ask system if calling UID can
precense on the specific display, to consolidate only few special UIDs
& display flag checking.
Bug: 117347985
Test: atest ActivityManagerMultiDisplayTests
Change-Id: I2f8989598c99c0962e925c5aa65500972b4fc62b
+ Add a field target to @InspectableProperty
+ Refactor PlatformInspectableProcessor to process annotated fields and
generate InspectionCompanions that read fields.
+ Require that all inspectable getters and fields be public.
+ Make some hidden getters added to View for inspection public.
Test: atest --host view-inspector-annotation-processor-tests
Bug: 126913705
Change-Id: I0c012f42794885f17a397a2e3dd541b3aa4c2634
Prior to fe5dfca the frameCompleteCallback
was posted to the native Looper, which is
effectively a postAtFrontOfQueue. Since it
was switched to the Java-side looper, do
an explicit postAtFrontOfQueue
Fixes: 124801988
Test: speculative
Change-Id: I287c9f3917983503402dcfe3ee7d494eefae8d1f
If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
If the getter calls are made View#saveAttributeDataForStyleable
this might lead to null pointer exception. Add checks to prevent
that.
Test: None
Bug: 126780975
Change-Id: I3e27d6073b65367010bc9d5b002cf9791d434a72
This reverts commit 4d70022b88.
This is so certain tests start passing again. The revert was a low risk
measure for the security update.
We still need to address the crash that this introduces
Test: It builds
Windows now can have rounded corners that match the display shape,
this CL introduces a new xml attribute called hasRoundedCorners that
enables this feature when declared on an animation xml.
Bug: 111514493
Test: winscope
Test: atest WindowAnimationSpecTest
Change-Id: Ie7651bab00c6e9e0ab7ab50cdb14142c8b2b954b
View calls like "attachedToWindow" and "detachedToWindow" can be called
off of the main thread, on "android.anim" this happens in the system
process for application splash screens.
Let's wrap it with a synchronized block.
Fix: 124110476
Test: The crash is a race condition, so the best I can do is make sure
it generally doesn't crash anything by trying out both normal and
virtual hierarchies in Talkback.
Change-Id: I19f972a97b5ac80917f8dd77ac79bf7e3d5e826c
There is no way to add FLAG_SHOULD_SHOW_SYSTEM_DECORATIONS to
hardware or simulated displays, so wallpaper, IME and nav bar were
not showing up even when desktop mode developer option was enabled.
Bug: 123199549
Bug: 125007644
Bug: 124073468
Bug: 124073384
Test: Enable force desktop mode, reboot, create simulated display
Change-Id: Id6f2f3746407467f20c1f26e735b84653e34625d
Turns out when you have IJ set up a lot of things become
more easy to spot.
sLayoutParamsAlwaysChanged was added in ag/818432, but then
not removed in ag/825933 when the feature was pulled.
transformRect was added in ag/173465 but never actually used.
Test: make -j
Change-Id: I69996a3b5e7526941a0e14158e892267075c29f3
expose ISurfaceComposer::getAllowedDisplayConfigs to SurfaceControl.
Test: manual test to call getAllowedDisplayConfigs() from SurfaceControl
observe config change.
Bug: 122905403
Change-Id: I0587ac5ed2eb29788c2ce941d9c54ebfd215ddf9
For packages:
android.speech
android.telephony.mbms.vendor
android.view
android.webkit
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: Iefe25091fa0fcc0adfe4ff85fe5e3ab3ac9c5f10
Allow views to register a list of rects where the device's system UI
should not intercept complex (read: down+move+up) gestures on specific
sub-regions of the view. This should not be used for large-scale,
full-view gesture recognition such as scrolling, but rather for specific
areas such as SeekBar's scroll thumb or DrawerLayout's edge strip for
swiping open a navigation drawer.
Add ability for ViewTreeObserver to observe transformed exclusion rects
Bug: 126360272
Test: atest android.view.cts.SystemGestureExclusionRectsTest
Change-Id: If89b6f66637e40efa12955d6408f6e37b25cb46f
1. Pull out TextClassifierImpl.LabeledIntent to LabeledIntent.
2. LabeledIntent.resolves takes a TitleChooser object, which
allow custom logic like "if the resolved app is a browser, use
title_with_entity. Otherwise, use title_without_entity".
If TitleChooser is not set, the default behavior is to use
title_with_entity if provided, use title_without_entity otherwise.
3. For classifyText, we use a TitleChooser that always return
title_without_entity. So no behavior change in classifyText.
4. If custom titleChooser returns null, fallback to use the default
titleChooser.
BUG: 124428508
BUG: 123946471
Test: atest framework/base/core/tests/coretests/src/android/view/textclassifier/
Change-Id: I7299c40ffc57deb9484d493f8c62b220a5a1e7d8
