Seems more appropriate as this more mirrors the normal release path.
I think everything gets release eventually either way.
Bug: 149591513
Test: Existing tests pass
Change-Id: I6f21d2723e06dbae4e09421efc352c179115bc40
We release the SurfaceControl assosciated with a Surface package
when accepting a new SurfacePackage, or at time of detached-from-window
this way we don't rely on the finalize method.
Bug: 149591513
Test: Existing tests pass
Change-Id: Ic0f7259394836ee094ed49db73b5986b778b450f
* changes:
Remove telephony protection level.
Revert "Allowed telephony to bind network service"
Revert "add telephony role to some permissions needed by telephony module"
NetworkCapabilities#mAdministratorUids is used to track the UIDs that
are administrators of the given Network. This value was previously
stored as List<Integer>. However, general Android API Council guidelines
recommend using Arrays for primitive values. In order to be consistent
with the guidelines, updating the field to use an Array.
Bug: 147903575
Test: atest FrameworksNetTests
Change-Id: I2652a5b0f276b8944454af5cb4b1383a3e054cfa
...If it was killed due to ANR.
Also add support to set a cookie which could be
included into the app kill reason.
Bug: 148413462
Test: atest ApplicationExitInfoTest
Test: atest CtsAppExitTestCases:ActivityManagerAppExitInfoTest
Change-Id: I79d9955d8f5c5f42074f0e1567119b41fc486d50
Clarify that some packages cannot be suspended.
Fixes: 144411650
Test: Javadoc change only; not applicable
Change-Id: Ia89ad60c5445b3bf2a355eb49ea645f4962a1212
Handle the case of a locked profile with unified challenge as a
first-class state: attempts to open work apps in this state will
result in a confirm credential operation, instead of letting the
app launch directly which will result in crashes.
Test: atest ActivityStartInterceptorTest
Test: 1. Turn off a work profile with unified challenge.
2. Manually turn on profile (without unlocking), run
adb shell am broadcast -a com.android.server.pm.DISABLE_QUIET_MODE_AFTER_UNLOCK \
--ei android.intent.extra.USER_ID 10
3. Attempt to launch a work app.
Bug: 72178550
Bug: 138560482
Change-Id: I85f796fe3edeb3c1d6c0dd6d2143d2f44ac22ea7
Adds more comprehensive callbacks and getters for the WindowInsetsAnimationController,
to make it more straight forward to properly use.
Test: atest InsetsControllerTest PendingInsetsControllerTest
Fixes: 151707442
Change-Id: Ida55f609112396c0f6de4c5c4431e0793c2e315e
Add test for constructor and parcel
Test: atest CtsNetTestCasesLatestSdk:android.net.NattKeepalivePacketDataTest
on both Q and R devices
Bug: 151402211
Change-Id: I97015365604be1846e3ecbaf60ac99e334705565
Merged-In: I97015365604be1846e3ecbaf60ac99e334705565
COMPANION_APPROVE_WIFI_CONNECTIONS_PERMISSION
Change-Id: I07b5ea07ccd0d28e589b586dd6fbf4816f035679
Test: None, this is strictly a javadoc update
Bug: 151311975
* changes:
[SP25] Rename functions that add Entry conditionally
[SP24] Rename functions that add Entry unconditionally
[SP23] Address misc API review comment about NetworkStats
[SP21] Address comments for API council review about aosp/1172143
[SP20] Check signature permission when accessing network stats provider
Oversight, the SurfacePackage holds a reference to the SurfaceControl
which is protected by a close-guard. We need a way to close it
explicitly. Going to follow up with a patch to have SurfaceView
manage the lifetime when the SurfacePackage is consumed, but want
to make sure this explicit release gets in ASAP.
Bug: 149591513
Test: Existing tests pass
Change-Id: I7276a2440c38cc6d859b79b4c3ee57bc122ce2a6
