This reverts commit 7b40358fa3.
Reason for revert: False positive - this works and patch not needed.
bug:109583877
Change-Id: If708350b03292cfa3bf9841199739e06c82f6c4f
When resolving the broadcast targets we did not consider instant apps
even if the source is an instant app. This prevents the case of the
instant app sending the broadcast to itself. The broadcast queue already
enforces that if the broadcast is not from a full app that wants to
advertise to instant apps or not from an instant app sending it to itself
then it is not dispatched. Hence, the broadcast queue already determines
the right targeting. This change makes sure that if the source is an
instant app we also resolve instant apps and then the targeting logic
in the boradcast queue would ensure that an instant app can only send
a boradcast to its own UID.
Test: cts-instant-tradefed run cts-instant-dev -m CtsBackgroundRestrictionsTestCases
-t android.app.cts.backgroundrestrictions.BroadcastsTest
#testNonSupportedBroadcastsNotDelivered_manifestReceiver
bug:109583877
Change-Id: Ifb7230df87c4721e4c05d77b5957d825f3846ca7
The animations could go wild at times, leading to overlapping
messages and ugly renderings. This improves the animations
overall and fixes those cases.
Test: add messages, observe animations
Fixes: 78114531
Fixes: 80409521
Change-Id: I6f21b87706ccc2e85f1edbd9489e4bf7e686d7d8
Don't enforce the startForegroundService() requirement to transition to
foreground when the app hosting the service doesn't yet target the API
level at which this semantic was introduced.
Bug: 79377529
Test: manual (ApiDemos is pre-O)
Test: atest CtsAndroidAppTestCases
Change-Id: Ib0b970211d4ee6a86e22c89aff47b05403907ed5
These files are used by devsite only, so are maintained in piper.
bug: 79155333
test: make ds-docs (human review)
Change-Id: I5d5662a2a401872a669dba0916b20a79bcfca7ae
(cherry picked from commit 9e64abe7d7)
Fixes an issue where the max aspect ratio was not correctly calculated
if there was a display cutout.
The issue was that the max aspect ratio logic assumed that nothing ever
applies a top inset (n.b. the status bar is ignored for this inset).
This is no longer true with display cutouts, which
cut into the app bounds from the top.
To make things work, we now need to grow the bounds for the app window
by that inset. Later on, the top part will be trimmed again for the
bounds reported to the app. Note that we cannot outright discard the
top part, or colored bars would cease to work.
Change-Id: I53925196a6a41736fc4748b12bbc3b8a9b0d174b
Fixes: 80248462
Test: atest AspectRatioTests
The animation---which was responsible for causing relayouts
that would in turn bind views, which involved package
manager roundtrips---would lock out interaction with the rest of
the share sheet for at least 400ms while the animation ran
(often much longer if services were slow to start or respond).
Now the main UI is never blocked, and direct share targets
can take as long as they like (up to 2sec) before appearing.
It's really fast now, basically.
Bug: 67622422
Bug: 63521992
Test: atest com.android.internal.app.ChooserActivityTest
Change-Id: I21826e282226f2b2ce6d3d1b5862dbfc449f5918
OpEntry.duration was being used to indicate that the
operation was still running if -1 is returned. A recent
change caused a regression.
Adding a new mRunning field in OpEntry to explicitly
hold the running state, even when partial duration is
updated.
Change-Id: Ib29f4c903f990aaa202e84f964959aedfc24abdb
Fixes: 80242152
Test: atest FrameworksServicesTests:AppOpsActiveWatcherTest
Test: Launch maps and verify the location icon is visible
in the status bar
LocationManager#requestLocationUpdate
- Cannot depend on LocationManager#isProviderEnabled, since it always returns
false for FLP.
Bug: 80199046
Change-Id: I9c85b8a9468bceca0620c5aff16655ed633ee36b
Fixes: 80199046
Test: Manually added a CTS test to trigger the flow in AOSP build on
device, and successfully caught the exception when requesting location
updates from NLP.
- Only send the hit target for visible buttons, otherwise we will defer
starting the recents animation when swiping over them even if they are
invisible.
Bug: 80320221
Test: Swipe up over hidden rotation button, ensure we don't defer the
animation start
Change-Id: Ie6126eb25ca6cdda1dce2dccec92d83b8aca0563
The animation needs to be added to the animation list before starting
to ensure it's in the list before onAnimationEnd is called. Specifically,
this can happen if the duration is 0 since the animation will complete
very quickly. If that occurs, the animation will be added to the list
after it's been "removed" which means there will continue to be a reference
to that animation even after it's completed.
Also fix a few other issues:
1. Don't create a dim layer if stopDim is called. This causes excess
layers to be created, just so they can be destroyed.
2. Add try/catch to dim layer create so the system doesn't crash if the
layer fails to create.
Test: Enter split screen and move divider so dim layers are show and
hidden. There are no longer excess dim layers being created and leashes
are being properly dereferenced.
Fixes: 80206408
Change-Id: I7198bd5e972fce32633869697a4d26f51e675d48
Some devices have hand-crafted, artisanal haptics to go along with the
dulcet tones of the ringer. When making such a device, we really want
our users to have the opportunity to appreciate the fine buzzes and
clicks we spent so long orchestrating, and so this makes it possible to
default VIBRATE_WHEN_RINGING on.
Bug: 79212179
Test: manual
Change-Id: I52bf133345bd3e8b09b591b9bac4711d0d485094
Test: Make sure not logs are written on: logcat -b events | grep -w 1302
Test: Re-anble tron log with settings put global battery_saver_constants send_tron_log=true
and make sure logs are written on: logcat -b events | grep -w 1302
Bug: 74742911
Change-Id: I1f4159b7194fbc29be7f76669aa4e53084ed27e7
- Add icons to the right and shortcut modes
- Add color
- Make sure dialogs are secure
Test: manual
Bug: 79960669
Change-Id: I6d251b0ea5bd3c1b3eed32b184e4aae22c52ffb5