- Adds a scrim that fades in as the PiP is dragged past the bottom movement
bounds.
- Tweaks the values for minimizing the PiP and dismissing the PiP
- Fixes an issue where the PiP could be minimized in the bottom corners
of the screen
Test: Manual - drag PiP to bottom of screen to dismiss or swipe down on
PiP when it's at the bottom of the screen
Bug: 35358768
Bug: 35358628
Change-Id: Ib4ad5ed7094fef76ea979b46ea7e03d746625d00
When the keyguard is going away or from wallpaper, the clipping will be
applied before the animation starts to avoid showing the docked app over
the area that should be clipped by the divider in splitscreen.
Change-Id: I2ca8f77a2b5d514f65a2032d4279dcb4996814e1
Fixes: 34095975
Test: manual
Add more debug information inside the IAEs thrown during
audio parameter check.
Test: try invalid params for recording, read exception text
Bug: 34119793
Change-Id: Ic4f36fd6ef99c18107e3204ef5e25cc1bc9e704d
We were using a generic context that caused crashes for
the content providers.
Bug: 34657204
Test: manual, calling getCallingPackage() from the provider
doesn't crash anymore.
Change-Id: I2b61e6510d8c6647007987373d03ee5dc97c0889
Fix logging of "Adjusting ABI" to be tolerant to null
packages.
Bug: 36172429
Test: m
Test: manual
Change-Id: Ic6b9a8e09e58dce6be97e464fe3986c709f820de
Previously this test was marked as blocked by b/35034729. This bug
has been fixed, however the test still fails due to other issues
addressed here.
Addressed issues are as follows:
1. Updating rotation by display manager requires a display with the
default display id present. This display is removed during setup. The
first id to be used by a display after this point is the
default id + 1. We already have logic in place to avoid collisions so
it is safe and correct to start out at the default id.
2. Without allowing the animator to complete its steps after a
rotation, future rotations will be deferred. We must simulate the
steps taken by the and resulting from the animtor. These include
marking the orientation change as complete and performing a surface
placement afterwards.
Bug: 35034729
Test: bit FrameworksServicesTests:com.android.server.wm.AppWindowTokenTests
Change-Id: Ib01c047ac49982a4a3c1debaa3cee1b7b9b53632
This should be the highest scoring one, not the first one.
Test: cts-tradefed run cts-dev -m CtsViewTestCases -t
android.view.textclassifier.cts.TextClassificationManagerTest
Change-Id: Ib790d8aa4aeccdd7a7972eaa6c04ed4fc69ad00e
This CL contains following clean up:
- Hide unnecessary constructors.
- Change List<XX> to XX[] since actually all fields are immutable.
- Change font's variant type from String to int.
- Decouple resource related members to FontResourcesParser.
- Add NonNull/Nullable to all fields.
Test: ran android.content.res.FontResourcesParserTest
Change-Id: If456266ffff86d41342572a19662cc8f3cd13181
Also fix a bug that doesn't trigger directory specific update for
removal.
Test: Manual tests.
Bug: 31001477
Change-Id: Ibae8a7aa5c72c82dc5e3cb4951fbc91ea6456964
(cherry picked from commit c574ec40640d83dfbbb0f022103c6dfa774bca40)
- When calling adjustFocusedActivityStackLocked(), prevent the home stack
from being brought forward if the task is not over the home stack. This
was causing issues with the docked stack triggering minimized mode when
a task was removed in the assistant stack.
- When checking the visibility of the docked stack, only base it on the
visibility of the assistant stack when it is above the docked stack.
This was causing issues with the docked stack reporting as visible even
when behind the assistant stack due to the subsequent code being run.
Bug: 35363819
Test: android.server.cts.ActivityManagerAssistantStackTests
Change-Id: I48cc901cb6b6166697a4130cc4639ee8f9581f02
- The orientation needs to be calculated from the screen width/height,
which are set below the current calculation of the orientation (whoops).
This bug was introduced in ag/1905010 and causes extra configuration
changes due to the configuration orientation being set correctly before
it is corrected on the next change (at the end of the transition).
Bug: 36099204
Test: android.server.cts.ActivityManagerPinnedStackTests
Change-Id: Ieca1f73fe61fc1dcea106535c019b52d126b8743
- Added a requestAutofill(view,flags) method, that when passed with
FLAG_MANUAL_AUTOFILL triggers a manual request.
- Added same method for virtual views
- Overloaded existing AutofillService request methods to take a flag.
- Added an AUTOFILL context menu option on TextViews.
- Added a canRequestAutofill() that is used to enable the context menu.
BUG: 35708229
Test: manual verification
Test: existing CtsAutoFillServiceTestCases pass
Test: android.autofillservice.cts.LoginActivityTest#testManualAutofill pass
Change-Id: I1a64d40da3373774451d178b1cabf20f11120e9d
Save the state when the fragment is getting re-created so we come
back up in the same state we left in.
Fixes: 36082443
Test: Change density using "adb shell wm density"
Change-Id: I531de728b1f4bf59d4def7ebc5562b3a1ee6694b
Ostensibly for instant apps, we allow play to mark an app as having
an update available. This will trigger instant app resolution even
if the instant app is already installed on device.
Bug: 35143464
Test: Manual; launch URI of installed instant app, see it runs w/o resolution. set bit. launch URI of installed instant app, see it runs resolution
Change-Id: I511df2b2a3eab39377167c770255ccbe02d5dad2
It always thought the keyguard was going away which was messing with
a bunch of transitions.
Change-Id: Ie50fe71e3f75aa123db7e147ac0402d459b80536
Fixes: 34975365
Test: Open app with light status bar
This washes out the network logging icon in the network monitoring
dialog, making it look strange compared to the dark VPN key.
Fix: 35620542
Test: inspection of dialog
Change-Id: I72bc6337b88b16235dab7b48d11efee4410ede5e
Cross-package use is quite common when only resources are being
considered. A common example is that any application that declares
itself <searchable /> will see cross package resource only use from
the system_server.
Test: manual instrumentation.
Change-Id: Ic7ad166c71a23c6026f4e12bb52309a50210aaaf
Now that ConnectivityMetricsEvent is only used for core networking
metrics and is not @SystemApi anymore, remove unused fields and prepare
for additional new fields.
Test: updated unit tests, $ runtest frameworks-net passes
Bug: 34901696
Change-Id: I15abad19981d491f16f2a3afe401f1e833079907
Now that we have CTS tests to verify the cache clearing v2 logic,
we're ready to enable it!
Switch storage APIs over to "usable space" to match implementation
down in installd. Add a missing clearCallingIdentity(), and offer
better logging for missing appop permission.
Load quotas from disk right away at device boot instead of waiting.
Bug: 35685848, 35684969
Test: cts-tradefed run commandAndExit cts-dev -m CtsAppSecurityHostTestCases -t android.appsecurity.cts.StorageHostTest
Change-Id: I8167e0322b4662ca6c975da5c50715e2d71332a7
This patch adds a few missing counters to APF events:
- an actual lifetime duration to ApfProgramEvent.
- counters for total number of updates to ApfStatistics.
ApfProgramEvents are now recorded at program removal in order to
populate the actual lifetime of the program. ApfProgramEvents whose
actual lifetime was less than 1 second are filtered out.
Finally, instance fields of ApfProgramEvent and ApfStats classes are
made mutable to allow for simple record-like creation. This was not
possible when these classes were tagged @SystemApi.
Test: - manually verified output of $ dumpsys connmetrics list
- unit tests updated.
Bug: 34901696
Change-Id: I02694ebb9421ce1c2aa757fa6aa209d19a654dcd
