Included changes:
* 4c1b251: Sync AppSearch with google3 update ag/14342999 (8f8b43)
* cdf1913: Add a GenericDocument#toBuilder API.
* 64f80f3: Improve snippeting and matching per API feedback.
* 23dd35c: Move AppSearchEmail out of the prod tree into the test utils.
Bug: 171882200
Bug: 186520196
Bug: 186717514
Test: Presubmit
Change-Id: I9d8e1fb87e6e74c57a38f3a27cdd04a1a3ccf90b
This CL addreses two issues:
1. PipMenuView.dismissPip was previously fading out the PIP
menu, waiting for that to complete, then notifying the task
organizer to remove and fade out the window, and then it would
fade the menu out again even though it was already hidden.
This resulted in a quick flash because the menu and the window
are not faded out in sync.
2. The menu fade out animation had a fixed duration of 150ms,
meaning that even if it starting fading out at the same time
as the PIP window, it would not finish at the same time because
the PIP exit anim duration is longer.
To fix both of them, the X button now hides the menu and starts
dismissing the task at the same time (once), and the dismiss
animation duration is equal to the task fade out animation
duration.
Previous: http://recall/-/e8RgaQ0dFlwFuh0c7GRpyy/g7XMbvBGMyAOKZMuFlYpW0
With CL: http://recall/-/e8RgaQ0dFlwFuh0c7GRpyy/g7XMbvBGMyAOKZMuFlYpW0
Bug: 182727923
Test: Tap X to dismiss PIP, no flashes seen
Change-Id: If9bdda8d0fd8b819c00ec4a592d1b2441d642d00
CarSystemUI has an overlayable.xml for OEMs to overlay. However there
are name collisions for R.id.container for some library we depend on.
Bug: 186786197
Test: manual
Change-Id: Ibb7c2d36e37a039baa7bcddc68b4633ba05bf013
Transfer alerts (HUN/pulse) from the group to priority conversations which are isolated from that group.
Note: In cases where the alert is transferred from a group with 2+ children to the priority, there can be very small flickering because the group is inflated synchronously, so it starts displaying before the message is received to transfer the alert to the priority conversation, which then needs to be inflated asynchronously.
Fixes: 185680162
Test: Using WA, receive messages from 2+ people, where some but not all of those conversations have been set to Priority. Test different numbers of people in each category (single vs. multile) and ensure that whenever an alert displays it shows the message that was just received.
Change-Id: I3c51cc20fe9ade4e24df2cc7d6784471be3ed509
Clear calling identity before calling into AMS in
unhibernatePackageForUser() to make sure we are calling as system user
and avoid security exception
Bug: 186701008
Test: built and flashed to wembley device, then run adb shell cmd
app_hibernation set-state PACKAGE_NAME false. No exceptions found.
Test: atest AppHibernationServiceTest
Change-Id: Icf0c72b85f4c611c84129a6fb9425f4344b4681b
If temp allowlist reasonCode is REASON_PUSH_MESSAGING_OVER_QUOTA, check
DeviceConfig key "push_messaging_over_quota_behavior" to decide if
temp allowlist and FGS start are allowed. Three options:
1. -1, temp allowlist not allowed, FGS start not allowed.
2. 0, temp allowlist allowed, FGS start allowed.
3. 1, temp allowlist allowed, FGS start not allowed. This is default.
The device config command to change the behavior:
adb shell device_config set activity_manager push_messaging_over_quota_behavior <-1|0|1>
If temp allowlist reasonCode is REASON_DENIED, do not allow temp allowlist
at all.
Also, in DeviceIdleController.addPowerSaveTempAllowlistAppInternal(),
there used to be a check if the callingUid is on the mPowerSaveWhitelistSystemAppIds list,
this is unnecessary because upstream callers already checked if callingUid has
permission CHANGE_DEVICE_IDLE_TEMP_WHITELIST, and this permission is a privileged permission,
so removing the check of mPowerSaveWhitelistSystemAppIds should be safe.
Bug: 182796372
Test: atest cts/tests/app/src/android/app/cts/ActivityManagerFgsBgStartTest.java#testPushMessagingOverQuota
Test: atest cts/tests/app/src/android/app/cts/ActivityManagerFgsBgStartTest.java#testTempAllowListReasonCode
Change-Id: Id34b1c26c819dc4fe07838eb2e3a8f0138cbcf8f
this CL fixes issues with "screen on" time reporting as there were
incidences of this time taking much longer than in reality.
Bug: 184765461
Test: Manual - check power on time reporting
Change-Id: If716e6842b8a214b5af0f66ba41f7f2b70fbc51b
* Width is restricted via padding applied to the view when the device
is considered large screen
* Adjusted animation code so bubbles slide in from edges when showing
vertically
* Overflow uses max height available when on a large screen
* Fixed a bug where overflow height wasn't being updated correctly
since it's no longer using an activity
* Fixed a bug where when the view was expanded & you rotated its
position could be off
Test: manual - expand bubble on large screen from left / right edges
in landscape & portrait
=> bubbles should be anchored to edge they are opened from
& positioned vertically along the edge
- expand bubble on phone in portrait
=> bubbles should be anchored to the top edge &
horizontally
- expand bubble on phone in landscape, check overflow
=> bubbles should be anchored to the edge they are opened
from & positioned vertically along the edge, the
overflow should have a restricted width
Bug: 175211639
Change-Id: I7c3f3024260a08ebdf4c6e7c7724e51fbc480f61
MidiManager.BLUETOOTH_MIDI_SERVICE_PACKAGE is a built-in package
which mediates Bluetooth MIDI connections. It functions similar to
CompanionDeviceManager and has no UI to request runtime permissions,
since it's proxying operations on behalf of other apps which have
already requested the permission.
Bug: 184920451
Test: manual
Change-Id: Ifd92ba0c701bb3d2aa927cac7c61cb435437444a
