When dispatching to self, ViewGroup is not applying padding
to localVisibleRect, only when dispatching to child views.
Also when deducting padding from the visible bounds,
it must be intersected with bounds, not subtracted.
Test: atest ViewGroupScrollCaptureTest
Bug: 185153400
Change-Id: Ib92e4c552fbe02fd863123f166878e19b8b1c952
Revert "[ANAPIC Review] Modify radio 1.6 based on ANAPIC comment..."
Revert "[ANAPIC Review] Modify radio 1.6 in telephony side"
Revert submission 14098561-ANAPIC_1_6
Reason for revert: broke the builds
Reverted Changes:
Ibcbdc0cac:[ANAPIC Review] Change the type of List by ANAPIC ...
Ie8d40439e:[ANAPIC Review] Modify radio 1.6 in telephony side...
I24106cba4:[ANAPIC Review] Modify radio 1.6 based on ANAPIC c...
I71b0d0014:[ANAPIC Review] Modify radio 1.6 based on ANAPIC c...
Change-Id: I33ee563f99b56ed478656474dc24c030f35ebf44
Temp. solution to get the build going. This is okay as we need to remove
this option anyways since we are now using
WindowContainerTransaction#setLaunchRoot
Bug: 185192439
Test: manual
Change-Id: I5b7fa6c9ddb57b74af4b8e0862723e1f7c4e72bd
CryptoObject still called the legacy AndroidKeystoreProvider which did
not return the correct operation handle for per operation auth bound
keys.
Bug: 184804041
Bug: 185181377
Test: CtsVerifier->Security->Biometric Tests->2a Strong Biometrics +
Crypto
Merged-In: I0bceff0425e7ef32c394f33deda3c78f729c0c6c
Change-Id: I0bceff0425e7ef32c394f33deda3c78f729c0c6c
This change adds a "BluetoothPermissionChecker" that ensures that
all Bluetooth permission annotations are consistent. In addition, it
verifies that all Bluetooth public APIs have been audited to be
permission protected where relevant.
We've currently standardized on saying that APIs that return device
or Bluetooth state information (without sharing details about any
particular remote Bluetooth device) do not need to be permission
protected.
This change is only annotations and has no behavior changes.
Bug: 183626724
Test: ./build/soong/soong_ui.bash --make-mode Bluetooth RUN_ERROR_PRONE=true
Change-Id: Ie80b15b058359bf1e9a6ee881b89cb3e5b584ca1
Since the phone can switch to/from CDMA, returning when not CDMA could
cause issues later on. This essentially reverts ag/13862397 and updates
the documentation to call out more clearly when ISE is thrown.
Test: make
Fix: 175665470
Change-Id: Ie6ab0fd4b317d66a74a7c667a0ed6a54ee56c150
Avoid most floating content by centering the requested content within
the view instead of just scrolling so that it's visible.
Bug: 174571735
Test: atest RecyclerViewCaptureHelperTest, plus manual testing across
major apps.
Change-Id: Ie275f5c37998a9d88e5ccde7af043443cbc4d94c
Without this fix, an apk-in-apex located in path
/apex/com.android.mediaprovider will be added as apk-in-apex
for com.android.media too, just because they have the same
prefix.
Added a info log too to make it easier to understand which apk-in-apex
is being registered under which apex.
Bug: 170640411
Test: Manual testing
Change-Id: Idc989ac84777589b4bdd72012833cdbdab7e872c
Merged-In: Idc989ac84777589b4bdd72012833cdbdab7e872c
(cherry picked from commit c45a426e8e)
trigger One-Handed mode many times quickly in a short time
To prevent entering or exiting OHM quilcky in a shot time.
Bug: 185304468
Test: manual
Test: atest WMShellUnitTests
Change-Id: Ibc5ade564da241d5871b3b037c97bd68a6b03a5d
The current metrics collection in RRMS is incorrect. Here is the desired
behavior:
- Successfully got resolution: log the rotation result.
- Feature is disabled: log RESOLUTION_DISABLED.
- Remote service is not available: log RESOLUTION_UNAVAILABLE.
- Request timed out or no face detected: log ORIENTATION_UNKNOWN.
- All other failures: log RESOLTUION FAILURE.
Test: none.
Bug: 185512682
Change-Id: Iae94122840a3078a93b34e38fe15f9da902144cb
Demo video: https://b.corp.google.com/issues/183229367#comment8
Thanks to jdemeulenaere@'s hard work on animations, this is an easy
change on my end.
Test: atest and manual
Bug: 183229367
Change-Id: I9411bf6fc11b380717ac139ef57f1c67011cac61
This ensures that the major action buttons have a minimum visual emphasis in the layout.
Bug: 179178086
Test: manual
Change-Id: I58744ada45d789a9acb53b0f4965354835595b19
This change causes HINT_EXCLUDE to take precedence
over HINT_INLUDE when both are present.
Test: atest ViewGroupScrollCaptureTest
Bug: 184370898
Change-Id: Ie4779067c3db82c65816dc4a5129badf74b3c9b4
Add the ability to override time detector "origin priorities" config
with device_config. This is primarily intended for use by tests to set
the device into known states, regardless of the static xml OEM partner
config.
For example, to test the new "external" suggestion code in CTS, even a
device that does not support it "out of the box" can be set to just use
external suggestions and verify the associated code paths are working.
Previously, external time suggestions were untestable on devices that
didn't use it "out of the box".
Similarly, carrier acceptance tests could use this to just set "nitz"
from the priority list and ensure that NITZ behavior is working as
expected.
An initial TimeDetectorShellCommand implementation has also been written
to provide help that lists the device_config key, and expose settings
state. The set_auto_detection_enabled command can be added after bug
172891783 is complete.
This change also makes the origin priorities more dynamic. i.e. config
overlays like locale or MCC-based resource configs could now also affect
the origin priorities, previously the string was read once and cached
forever.
Bug: 183239968
Bug: 172891783
Bug: 172230856
Test: build / treehugger only
Change-Id: Ic67f35aa6d417bbbb4172643c10a796d484ccd1f
