So far, we have used `instalable: false` to avoid collision with the
other modules that are installed to the same path. A typical example was
<foo> and <foo>.microdroid. The latter is a modified version of the
former for the inclusion of the microdroid image. They however both have
the same instalation path (ex: system/bin) and stem (ex: foo) so that we
can reference them using the same path regardless of whether we are in
Android or microdroid.

However, the use of `installable: false` for the purpose is actually
incorrect, because `installable: false` also means, obviously, "this
module shouldn't be installed". The only reason this incorrect way has
worked is simply because packaging modules (ex: android_filesystem)
didn't respect the property when gathering the modules.

As packaging modules are now fixed to respect `installable: false`, we
need a correct way of avoiding the collision. `no_full_install: true` is
it.

If a module has this property set to true, it is never installed to the
full instal path like out/target/product/<partition>/... It can be
installed only via packaging modules.

Bug: 335369205
Bug: 337993945
Test: m droid aosp_cf_system_x86_64
Change-Id: If9c053968bde39c3eb3b852f1df1d475161bd846

This CL still keep PRODUCT_COPY_FILE for the original system image
packaging for Make, but create 3 soong's modules which could be used for
soong generated system images.

Bug: 337993945
Test: lunch aosp_cf_x86_64_only_phone-trunk_staging-userdebug ;\
      m aosp_cf_system_x86_64 ; m
Test: lunch yukawa-trunk_staging-userdebug ; m
Change-Id: Ie749de99273f85623861a001e69a9c4187cc8067

This reverts commit fd803f55.

Reason for revert: This change break most of the tv targets. Please test building cf_x86_tv_gtv

Bug: 338497361
Change-Id: I5e9063f3099315de4ec6bde966bf8563f5faac56

go/respectful-words

Change-Id: I8bd5281522e7874b169e60dfcbcc23169e3ab88f

Bug: 337993945
Test: m
Change-Id: I762f41500fb9b360245fbf58a6526dd594ff332e

Bug: b/306336441
Test: manual
Merged-In: I096d28bce5f879f88f185f09014d139f0497cb72
Change-Id: I096d28bce5f879f88f185f09014d139f0497cb72

Bug: 278763704
Test: Manually done
Change-Id: I22bf47a913f3b25b3f095e4ab276af79e51a4a76
Merged-In: I22bf47a913f3b25b3f095e4ab276af79e51a4a76
Merged-In: I54105704d8f453663a2e8781b2cb680d9ab03c73

(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:2b08c16e9e3ed00c2fd9a94ab34b094af2866c87)
Merged-In: I351e394a173291318db37bbe61cdf93adff9a3b9
Change-Id: I351e394a173291318db37bbe61cdf93adff9a3b9

Add virtualmachine gid for apps with MANAGE_VIRTUAL_MACHINE
permissions.

Bug: 322197421
Test: Booted device and processes and checked that the correct
capabilities are given.

Change-Id: I14e7df4dd284e00a44eb92d753c7e7e58b1e2526
Signed-off-by: David Dai <davidai@google.com>

Change-Id: I87e21b50a247f82d65a3cd46cd1612676d9dcbe0

Because `system.img` is a dependency of `fontchain_lint`, and
`system.img` is currently not generated inside `Soong`, it is not
possible to directly convert `fontchain_lint` to `Android.bp`.
Move it to build/core/task first.

Bug: 319050958
Test: m fontchain_lint
Change-Id: Iad483117a609786ecfb885b13015f18dda113155

The primary purpose of validate_framework_keymaps is to perform checks
on all *.kl, *.kcm, and *.idc files using the "validatekeymaps -q"
command. This action can be replaced by using a genrule.

Bug: 318785074
Test: m validate_framework_keymaps
Change-Id: I657466d7ee2cec29900beeb0610cb0d30f34f92e

Settings app needs to retrieve and publish update info from
SystemUpdateManager. This is needed to install 16k developer option
update which enables users to use 16K kernel from local OTAs.

Test: m Settings && adb install -r $ANDROID_PRODUCT_OUT/system_ext/priv-app/Settings/Settings.apk
Bug: 302391134
Bug: 295035851
Change-Id: I89e30a8fc7e753f41c70e3ddbf759fb63ea97bd5

We don't have a way to determine if devices can actually report HID
usage keys. Marking them as fallback only.

Bug: 297094448
Bug: 317838112
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:45f626a154f66f4cceecaf6e32392741a00529a3)
Merged-In: I45710f9e6237c86613717fab779dbd7cc5c66c86
Change-Id: I45710f9e6237c86613717fab779dbd7cc5c66c86

Bug: 309313071
Change-Id: I4fc6132adcb134576df1b846859c273a8bbd5d26

Move TPL logic from surfaceflinger to system server. When a TPL is
registered, start listening to window info updates and start checking
for whether thresholds will be crossed. This allows us to move the logic
away from the composition hot path and optimize to handle multiple
listeners. This change also consolidates all the TPL logic into its own
thread.

Bug: 290795410
Change-Id: Ib4ab68d7f116ace168bf994c0fd5c0c08c4496a6
Test: atest TrustedPresentationCallbackTest

(Night mode comes later, once UiModeManager changes are ready).

Test: atest ZenModeHelperTest
Bug: 308673540

Change-Id: I7deba78255ebe18c088cd3456c56f7801210f876

This reverts commit ae3a5365.

Reason for revert: possible mem regression b/314407848

Change-Id: If2fd10d1ec46d00d3349636cd4e117ebbd038cfc

(This is needed to be able to exercise the new API in a CTS test.)

Test: (see other CLs in this topic)
Bug: 268089816
Change-Id: I63de51fbb837071fbf99b8bdc9135bcfb3b12b52

Move TPL logic from surfaceflinger to system server. When a TPL is
registered, start listening to window info updates and start checking
for whether thresholds will be crossed. This allows us to move the logic
away from the composition hot path and optimize to handle multiple
listeners. This change also consolidates all the TPL logic into its own
thread.

Bug: 290795410
Test: atest TrustedPresentationCallbackTest

Change-Id: Ib649f157ddbb6b5a952cedeb235f6ace6f5e43ae

WindowManager receives updates from DisplayManager through
onDisplayChanged() callback by reading the DisplayInfo
objects after receiving this callback.  This CL makes
WindowManager to defer the updates if there is a collecting
Shell transition. This is needed to allow starting physical
display change transition if there is another transition
running.

Previously this was silently failing without starting
a display switch transition.  It also changes the behavior
of PhysicalDisplayTransitionLauncher: now it starts the
display change transition even if it's not an 'unfold' transition.
UnfoldTransitionHandler will decide if it wants to handle
'unfold' display change and default transition handler will be used otherwise.

Bug: 259220649
Bug: 277866717
Test: atest PhysicalDisplaySwitchTransitionLauncherTest
Test: atest DisplayContentTests
Test: manual fold/unfold with apps/split screen/
  split screen + PIP
Change-Id: Ib0d0624bf141ff16578d7902bec98272d17ee36f

At the moment Action+Grave will go back, but not Action+Escape;
Escape is the top-left key, not grave.

Bug: 313612728
Test: Flashed build, confirmed Action+Escape goes back
Change-Id: Ieb83fb0373f62e39e2debed72cdbc1b6761760ff
Flag: NONE

Preventively ensure the dimLayer has not been released before trying to access it.

Fix: 308448047
Test: atest CtsWindowManagerDeviceOther:android.server.wm.other.MinimalPostProcessingTests#testTwoVisibleWindowsSecondOnePrefersMinimalPostProcessing --iteration 100
Test: atest DimmerTests
Change-Id: Id08838e0a98ba949382442b8fac8e81156d1aa40

The LayoutParam secure flag set by the client is set on the WSA level.

This causes a few issues:
1. Child windows don't inherit this flag since child windows are added
   beneath WS
2. Prevents moving the WSA's SC to the client since the secure flag
   needs to be set in WMS.

Test: FlagSecureTest
Bug: 308662081
Change-Id: I724ab0d834b0d74b33ccbb6bbd2c6f9c622c2a15

This is required for CtsVoiceInteractionTestCases.

Test: presubmit
Bug: 291656263
Change-Id: I0fa57a0ec0d337f5bf2970a536e20bdc94d4f312

Instead of adding yet another virtual display flag, the API is in
VirtualDisplayConfig and uses WM's DisplayWindowSettings to store the
bit whether home is supported.

The difference with the existing FLAG_SHOULD_SHOW_SYSTEM_DECORATIONS
is that it also adds navigation bar and the new API doesn't. The flag
is hidden but there are existing clients of it.

Several caveats:
 - Need to use displayUniqueId instead of displayId because we should
   tell WM about the home support before the display is actually
   created and the display listeners notified.
 - Interacting with the DisplayWindowSettings requires the WM lock,
   which must not be acquired while DisplayManagerService is holding
   its own lock because this may and will sometimes cause deadlock.
 - So extracting the displayUniqueId generation logic before the DMS
   locked region of actually creating the virtual display and passing
   it to WM to store the settings.
 - Change in the virtual display uniqueId generation: reusing ids per
   package/uid causes problems in when displays with the same name
   are created and released quickly (CTS). When there are no display
   devices, the same unique id is used, but the DisplayWindowSettings
   may not have yet received the previous onDisplayRemoved callback,
   so the setting for that uniqueId is removed. Making the uniqueIds
   truly unique fixes this and there's no realistic danger of an
   overflow.

Fix: 291749213
Fix: 297167917
Test: see CTS in topic
Test: atest VirtualDisplayAdapterTest
Test: atest DisplayWindowSettingsTests
Test: atest DisplayAreaPolicyTests
Change-Id: If72696a793a9c4d63d4f8b72de7433b0dd440909

Fix: 300385158
Test: presubmit
Test: manual, verified that KEYCODE_LANGUAGE_SWITCH reaches the framework

Change-Id: If98addb0f9f3cff93bb0159b8fde171acf6a3998

- Remove embedded window check, EmbeddedWindowController#getByFocusToken
  should search with input token instead of window token, so it always
  return null nowaday.
- Skip search if the closing target isn't visibleRequested, usually that
  means the closing transition is collecting or playing, either case the
  window shouldn't receive another back invoked event. Inject the back
  key then next focus app will handle it.
- Use TYPE_CALLBACK if we cannot find any task below current task, this
  could also happen on some specific device.(e.g. No home)

Bug: 303266152
Bug: 309683765
Test: atest BackNavigationControllerTests
Change-Id: Ia1f5ec664ea7154d9c8ac59cbc247a51226dfdf1

Defines permissions for guarding access to Thread network API.

The permissions are also granted to shell for CTS tests, see the
instructions here: go/ctswrite#write-a-test-to-test-an-api-that-requires-system-permission

Design doc: go/thread-android-api

Bug: 262683651
Merged-In: Ib15d5589bbd304d68840ee52a193676d12110512
Change-Id: Ifc6c1d55cc170a5a200dfb5d531f5e0f86a9507a

Defines permissions for guarding access to Thread network API.

The permissions are also granted to shell for CTS tests, see the
instructions here: go/ctswrite#write-a-test-to-test-an-api-that-requires-system-permission

Design doc: go/thread-android-api

(cherry picked from commit 03aa71cd4b5eabe9310d3c4d4db10038b80853d1)

Bug: 262683651
Change-Id: Ib15d5589bbd304d68840ee52a193676d12110512

Bug: 292533010
Test: atest CtsGetBindingUidImportanceTest
    ... with and without android.app.get_binding_uid_importance set.

Change-Id: Iee6f0e08ba499f2f51d8173e45168c69933cd451

Update ContentRecorder & MediaProjectionManagerService to log a MediaProjectionTargetChanged atom upon recording starting and further updates to windowing mode.

Bug: 304728422
Test: atest WmTests:ContentRecorderTests
Test: atest FrameworksServicesTests:MediaProjectionManagerServiceTest
Test: atest FrameworksServicesTests:MediaProjectionMetricsLoggerTest
Change-Id: I5120ba2571fb2e6e084e72c4fd079767530ccdeb

Test: None
Bug: 308352352
Doc: https://docs.google.com/document/d/15MiUQNkH2cXjrHbsLRxW5v4pyddwgyTBK-9cKB1oD58
Change-Id: Ibe3a336ebb3525a719147fe6f991c910b214e370

Adds logic to UnfoldTransitionHandler that
takes over animating a transition if it contains
changes related to unfold.

Bug: 259220649
Test: atest PhysicalDisplaySwitchTransitionLauncherMixedTest
Test: manual unfold 20 times =>
  verify that there is no black screen delay
Test: artificially increase collecting of rotation transition
  => rotate and unfold device, check that animation works
Flag: handle_mixed_unfold_transitions
Change-Id: I3285c1b6a45da63ac7846e9d5929db9426b069ae

... until we figure out a way to determine if a device supports a
specific HID usage code. Right now, having a usage code mapping means we
automatically assume the device can report the key code. Assuming a
device can support a stylus keycode makes the device get classified as a
stylus, leading to widespread misclassifications.

Bug: 291529805
Test: atest inputflinger_tests
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:5fb192aaec7a1d4ebb1384d96b3f79d4b2ca2f2c)
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:55930e07d69fbd8ffd27d677a06fd0ba71a30bf8)
Merged-In: I580514bdcbbfbe93df83fa3faa6262077e881243
Change-Id: I580514bdcbbfbe93df83fa3faa6262077e881243

This introduces a new ReadyTracker class based around tracking
explicit conditions instead of an arbitrary set of heuristics
mixed with legacy.

Usage involves constructing a ReadyCondition and adding it to
a transition's tracker. Once the condition is met, call `meet()`
on the condition.

The new ReadyTracker considers the transition ready if there
was at-least one condition added and all the added conditions
have been met.

This is just the base implementation so it isn't really
functional yet. This does add ready-conditions in most of
the places where the old method's defer/continue were used.

Bug: 294925498
Test: atest TransitionTests
Change-Id: I6cbd9152d03e707e0e7134fa8ada2902e5af847e

The new scaling takes into account the asymmetry in pixel size on the
external display for better rendering.

Bug: 304248677
Test: atest WmTests:ContentRecorderTests
Change-Id: I7502538c5423343da93c20bfb7c6c8bea33dd7d2

Collect the changes on a dim layer and assign only the last requested to
a transaction
- Avoids issues with transaction ending up in the wrong order
- Allows smooth transactions between different alpha values
- Does not treat the entering animation as a special animation case

Test: DimmerTests
Bug: 281632483
Bug: 295291019

Change-Id: Ic3e6ce1f107bfc3ac925eb167b8bc89a5df478c8

Bug: 281769620
Test: Manually done
Test: atest FontListParserTest TypefaceSystemFallbackTest
Test: atest CtsGraphicsTestCases CtsTextTestCases
Change-Id: Ice5a51024c7fbba2af7c5886c751e2508c3670d7

Bug: 290068850
Test: manual
Change-Id: I394f38d6960deae36237b3a7122fd343dc7a1934