- activating manage focuses on first item in manage menu
- scrimview no longer highlighted expanded bubble focus list
- bubble now says double tap to activate
Bug: 158811290
Bug: 158811563
Bug: 158811388
Test: manual
Change-Id: I72f348d1407df6fe73103001145891d55b7537da
Bug: 158675544
Bug: 158675318
Test: manual - rotate phone to landscape, with stack expanded /
collapsed-then-expanded, select bubbles and overflow, see that
Overflow height matches normal bubble activity
Expanded view at correct location and size
Pointer still points to correct bubble
Bubble spacing is wider as intended
Change-Id: I32bf1cdeaa4bade4d806e04b423f56991b41c3be
Allows vendors to modify the window container transaction
when finishing a bounds resize.
Bug: 159147615
Test: atest SystemUITests
Change-Id: Ibacaafb7ca2f79864997d3a43c372cf1814c8e3c
DeviceIdleController sits higher in the lock hierarchy than
AppStandbyController, so ASC shouldn't call out to DIC with its lock
held. In order to know if an app is power whitelisted, ASC needs to call
out to DIC and cache the result outside of holding the lock.
Bug: 158779091
Test: atest CtsBatterySavingTestCases
Test: atest CtsJobSchedulerTestCases
Test: atest CtsUsageStatsTestCases:UsageStatsTest
Test: atest FrameworksServicesTests:AppIdleHistoryTests
Test: atest FrameworksServicesTests:AppStandbyControllerTests
Change-Id: Iff500f3ab00f6881348926604be7ab07693bdf40
In order to save memory, FuseAppLoop maintains a buffer pool to use
when dispatching the read/write requests. Currently, it uses
the threadId of the ProxyFileDescriptorCallback as the key for this
buffer pool and this can result in an issue when a caller creates
multiple ProxyFileDescriptors with ProxyFileDescriptorCallbacks
running on the same thread. When this happens, it is possible that
a buffer is reused before a read/write request which was using it
earlier has been handled and would result in data from read/write
requests on different fds getting mixed up.
Bug: 158568683
Test: atest --test-mapping apex/blobstore
Change-Id: Iaffd54f4430ecb3778f01c80f5a1684ac448f8dc
Instead of setting mHideMenuAfterShown to true for all cases, only do it
when accessibility isn't enabled.
Bug: 158662766
Test: Double tap when PIP focused
Change-Id: I18713ab1fdf511b74108df355204b2c54913a078
Previously we were only updating appOps for notifications with standard
layouts that were associated with a foreground services. However,
non-foreground service notifications can be tagged with appOps, so we
make sure to update these notifications' appOps whenever appOps are
changed. (We do this by tracking all notifications with standard
layouts instead of just the foreground service notifications)
Test: atest AppOpsCoordinatorTest ForegroundServiceControllerTest
Test: manual (use camera on whatsApp, receive message with app op, quit
app, see that app op is gone on the notification)
Fixes: 158585352
Change-Id: I674fc42441c2847a030df03516484ee6cd9217ac
Change-Id: I0527b8596277e53bea5a68aa57e0726aea9d14ac
* this reverts ag/11592765 since it causes a regression for b/145949573
in the following case:
1. user taps on a field for which autofill returns null and augmented
autofill is triggered
2. user goes home, which sets the mExpiredResponse to true
3. user comes back to the app, now tapping on the input field over
and over, each tap will trigger a new augmented autofill request
* the fix is to revert the above patch, and then handle the input
method switch for augmented autofill case by setting the current
view to null, and also setting the augmented autofill id to null,
such that the entire autofill flow will be executed again.
* note that this patch changes one behavior - in case regular autofill
returns null and augmented autofill is triggered, switching input
method and tap on the field again, it will trigger regular autofill
again (before this patch, it will only trigger augmented autofill)
Test: relevant cts tests
Test: manual testing that on the chat app, switching input method
and then tap on the field again triggers a new request
Bug: 150483555
Bug: 157412832
Change-Id: I0868ff62047f66402885f9821f7981ca4596f76b
This call to updateRelativeZ may be triggered from the
RT frame callback which may be triggered after we are detached
from the Window and in that case will be null. If we are detached
we are also going invisible so there is no need
to set a relativeZ.
Bug: 158706756
Test: Existing tests pass
Change-Id: I46aa824807b7b275e6a015c428fe7467a72ca949
This change adds a cache layer for the return of
shouldFilterApplicationInternal in AppsFilter. This cuts most operations
that rely on app filtering nearly in half by removing a good deal of
branching that used to exist on the critical path for a crosshatch.
Before this CL:
android.os.PackageManagerPerfTest#testGetApplicationInfoWithFiltering:
getApplicationInfoWithFiltering_mean: 983719
getApplicationInfoWithFiltering_standardDeviation: 120061
getApplicationInfoWithFiltering_median: 1061674
getApplicationInfoWithFiltering_min: 827489
android.multiuser.UserLifecycleTests#createAndStartUser:
Mean (ms): 4243.10
After this CL:
android.os.PackageManagerPerfTest#testGetApplicationInfoWithFiltering:
getApplicationInfoWithFiltering_mean: 426340
getApplicationInfoWithFiltering_standardDeviation: 18861
getApplicationInfoWithFiltering_median: 427002
getApplicationInfoWithFiltering_min: 407887
android.multiuser.UserLifecycleTests#createAndStartUser:
Mean (ms): 3387.25
Note: this is a 2nd attempt at this change that fixes a few from the
previous at ag/11622391. This works with multi-user and updates tests to
ensure this stays true. It also improves peformance when building the
cache by pre-allocating the SparseBooleanArrays to their max sizes.
Test: atest AppEnumerationTests AppsFilterTest PackageManagerPerfTests
Fixes: 150405193
Change-Id: I6e0446068f46af0f22e0259ab7b6cdbbc7e08a22
Merged-In: I6e0446068f46af0f22e0259ab7b6cdbbc7e08a22
Merged-In: I67969ee2dec7a70442d2bea43c99fba977ee33f4
The matrix returned from getTransformationMatrix is used by a11y
controller for computing the touchable region. Since the touchable
region doesn't include the surface insets area, the translation in the
method should not be affected by surface insets.
Fix: 151868913
Test: atest WindowStateTests
Change-Id: I1ae58716d7270a58d527b807b74cdadc6e4624ab
Found a potential issue where the adapter list was being updated on
the bg thread, and could cause conflicts while the recyclerview is
loading.
Fixes: 159028662
Test: atest ChooserActivityTest
Change-Id: I60abd9a8325964ed2ca1218e8846f816b02da431
