We would add a StageChangeRecord for a closing task even when the task
transition change was TRANSIT_TO_BACK. When both of the split stages had
one child task each nothing would happen, but if one of the stages had
two child tasks we would enter logic that assumed that one of stages was
closed. This change adds a StageChangeRecord for a closing task only
when the transition mode is TRANSIT_CLOSE.

Bug: 314688953
Test: atest WMShellUnitTests
Test: Open Gmail and Chrome in split, go to the compose-email screen in
      Gmail, receive call, answer and hang up the call, observe that
      Gmail and Chrome are still paired.
Change-Id: I8ee6c078bd8a1816a96a9515b1a50e652de70d1c

This is a clean up commit to remove legacy ConnectivityAnnotations
as the annotations are defined in the ConnectivityManager, and is
unused.

Test: m
Change-Id: Id3aec16559618ab563815fbdd4c8da54c54cafef

Move the files VpnManagerServiceTest and VpnTest from their
current location. Unit tests should ideally reside alongside
the code they test. The original placement likely hindered
their inclusion in module testing. Additionally, SDK checks
have been removed from the tests since they are now considered
platform tests.

Test: atest FrameworksVpnTests
Change-Id: I27b399d37c3536f4dbf39d2f8ef5242eb4ab6ba7

Initialize the test for VPN related unit tests.

Test: make FrameworksVpnTests
Change-Id: I210c3a23fc5bea4b58163065fae28d816e57b946

Many files that reference android.security.KeyStore don't actually do
anything with it.  This is apparently because the functionality of this
class got moved to other places, but it was forgotten to remove the
actual references to the class.  This CL removes all such references
from frameworks/base.  Where made possible by removing an import of
android.security.KeyStore, it also updates references to
java.security.KeyStore to be simply KeyStore.  java.security.KeyStore is
the real KeyStore that is part of the public API.

Bug: 326508120
Test: presubmit
Change-Id: Ie63b8dfc8bb562b33e6e529d537bde64ae2c6d53

This only affects informational logs.

Test: presubmit

Bug: 325789335
Change-Id: I6c04fd8abbe8a66b8485a6151da7504b47c22f16

With the effort to support non-"everything" stubs generation from api
signature files, https://r.android.com/2977092 enforces all
java_api_library modules to specify the `stubs_type` property. In order
to accustom to this enforcement, this change specifies the `stubs_type`
property as "everything" to all bp-defined "everything" stubs generating
java_api_library modules.

Test: m nothing --no-skip-soong-tests
Bug: 319162970
Change-Id: I0a21420b4aa9eccd1eeb2022f3c9c952f607a480

a2e8b91a

Bug: 304347838
Change-Id: I058cf66bb574150d94b87914b11ba3c216849cb1

Change-Id: Idafbb29affc1eb5b5ccbd4ce1eb33dc2b10c62fe
Test: N/a

When a user backs out of the "Add ringtone" menu no ringtone is
shown as selected.
   This change fixes this issue by handling RESULT_CANCELED code
from the activity for "+ Add ringtone" to show the list properly.

Bug: 176465037
Change-Id: I4cc4b4c01477e173c766b67167c0e249a6d55bbf

Merge "Suppress HiddenAbstractMethod on Notification.Style.areNotificationsVisiblyDifferent" into main

A bug was introduced by recent changes to filter out redundant process
state changes.
NPMS was caching UidStateCallbackInfo objects per uid and not clearing
it or resetting the procStateSeq when the uid went away. This resulted
in state-changes not being processed after app restarts.

For example, if an app exited from TOP, it would lose network access due
to some rules, but the last UidStateCallbackInfo would stay at TOP. If
the same app restarted, the change would be filtered out as
uninteresting even though the network rules require an update.

Test: atest FrameworksServicesTests:NetworkPolicyManagerServiceTest

Bug: 326370901
Bug: 326675380
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:cafca44d84955504857e337fced3bef2912802bd)
Merged-In: I016435abcfd5300f33374e5d5c144b25f81728b4
Change-Id: I016435abcfd5300f33374e5d5c144b25f81728b4

Test: unit test
Bug: 291137901
Change-Id: I8cd6b756b446fbeab782dcd78baac42326d8d7dd

Remove methods from android.security.KeyStore that have no real callers.

The methods with @UnsupportedAppUsage could be called via reflection by
apps targeting an old SDK level.  But since there is no valid use case
for these and they were already replaced with stubs in Android 12,
removing them is allowed by the non-SDK interface policy.

Bug: 326508120
Test: presubmit
Change-Id: Id742604786e71a212244f7800b9c245cea193057