Bug: 305066531
Test: builds
Change-Id: I8766c850cf4bb9e2e217eaff558e800e0508f36c

Bug: 304478767
Test: Compiles
Merged-In: If0b1432b78ec42a02446754ff6cf454fbb875048
Change-Id: If0b1432b78ec42a02446754ff6cf454fbb875048

Bug: http://b/307806447
Test: TreeHugger
Change-Id: Ib07514426643d8682c768b87e32fff2abddcda13

This ensures they're consistently added to all droidstubs modules
for the non-updatable part.

Test: presubmit
Change-Id: Ia17808572b3fa8d75cdc71e7981d562ad0036afc

Bug: 276358140
Test: make update-api
API-Coverage-Bug: 308000143
Change-Id: Icf5df742a30ccdc5b53a2e3cc78f0efd38b2739a

Update VcnGatewayConnection to support disabling safe mode

Bug: 276358140
Test: atest FrameworksVcnTests (new tests)
Test: atest CtsVcnTestCases
Change-Id: If767dbace925c7e13705db2ea6f23c890992405c

Bug: 307352220
Test: atest CtsNfcTestCases
Change-Id: I5b42578dcb4d0bf022fde8623f4f82cb0ac0c74b

Bug: 305065851
Test: treehugger
Change-Id: I768ab21f9a76d4d89cfc03e36a417ed5d7482b49

Bug: 307903002
Change-Id: I0391a2c1d20eac11e1c71bc38d43a1eac1eaec92
Test: N/A

A guest user having a third party launcher cannot open Recents.

When the preinstalled launcher is used, the built-in recents
implementation will be used (QuickstepLauncher.java) and
which means there won't be any task with activityType "recents"
in the display stack, because Home and Recents are the same.

When a third party launcher is used, the fallback recents activity
will be launched (com.android.quickstep.RecentsActivity).

When this RecentsActivity is created, a new task with activity type
"recents" is created and this task remains in the display stack
after the current user is switched to a guest user.
When we try to launch a new RecentsActivity it will not be allowed
since one activity of type "recents" is allowed to exist at the same time.

Solve this by allowing multiple root task for recents activity type.

Test: Install a 3p launcher, use that as default with a guest user and open recents
Bug: 304930756
Co-Author: Isak Lilja <Isak.Lilja@sony.com>
Change-Id: Ibacc05f7dd3ca6e835d7fea1ada87a21faea739a

When forking zygote processes, 'forkSimpleApps' may process multiple
simple apps in the command buffer at once. However, the parsed zygote
arguments are computed based on the first app in the command buffer,
which can lead to all launched processes being assigned the same name.

Move the setting of the child process name into childMain and use the
arguments from it's local ZygoteArguments for the appropriate name.

Bug: 305970538
Test: Verified aosp_cf_riscv64_phone correctly uses unique process names
and PIDs match intended name.
Change-Id: I0febc49649b0ede4c07898b47b0ebe6ac37e7057

Change-Id: I64b2644ffb8ee75043623222b48fba8f2cfc5f08

Bug: 276358140
Test: atest FrameworksVcnTests (new tests)
Test: atest CtsVcnTestCases
Change-Id: I7b460cc3a3b143de212bb5a1b717fc99582f05ec

Fix a bug that the user can still enter pin/pattern
during lockout timeout when doing special user
credential verification.

Bug: 301924294
Test: b/301924294#comment1

Change-Id: I3301a811a5038adc3014fb149274da86b8bd900d

Adding a placeholder so that soong build integration can happen in
parallel with the implementation of this flag.

Bug: 297373084
Bug: 306024510
Test: m aapt2
Change-Id: If9df57daaa871c11e146a8a8f8113fceb2fd96c2