No longer an appropriate reviewer for platform code.

Change-Id: I051251f7baee476dd95c4a85b1a6e2e51e9a00fd

Changing the process of how the IME is shown or hidden:
- Showing or hiding the IME is driven through its requested visibility (InsetsControlTarget) via InsetsController/DisplayImeController and thus sent to the server (InsetsStateController).
- When hiding the IME, the requestedVisibleTypes are sent after the end of the animation.
- Introduced new OnImeRequestedChangedListener that is called via WindowManagerService that is called to start the show/hide IME flow in IMMS.
- When the IME becomes (un)available, its leash is (re)set.
- Show/Hide requests from InputMethodManager are redirected through InsetsController.

Test: atest CtsInputMethodTestCases
Flag: android.view.inputmethod.Flags.refactorInsetsController
Bug: 298172246
Change-Id: I8e3a74ee579f085cb582040fdba725e7a63d6b85

This reverts commit b033de9f

Reason for revert: The CL made taskbar flickers

Bug: 343521630
Change-Id: Ie8e7a3f4751cc71f80596099fea73f3e1a848a52

There are several reasons for this requests:
1. Fix "Dim flicker on package installer"
2. Implement overlay transition by animation resources override
3. Activity Embedding Animation Customization

Test: atest TransitionTests ActivityEmbeddingAnimationRunnerTests ActivityEmbeddingControllerTests
Bug: 327332488
Bug: 295805497
Flag: com.android.window.flags.move_animation_options_to_change
Change-Id: I060b87506a1bf732228ec6b44e7e9dd48782ec0c

Auto-generated-cl: translation import
Change-Id: I1c8129f516afbffa109052d388abf1b0ef3ead61

Auto-generated-cl: translation import
Change-Id: I17a76c87833b9078558ba7b21a88e6c5ced29045

Bug: 329451873 (Hudson)
Bug: 329452468 (CW)
Test: Manual
Test: atest NfcNciInstrumentationTests

This is a re-revert of ag/27165777, which caused some post-submit tests to fail: http://shortn/_RTRWeshrUQ

Updates the UI across both Hudson and CW to match Design System 2.0.
Topic includes changes to:
- CarActivityResolver app
- frameworks/…/res car_resolver_list layouts
- frameworks/…/res build time base RRO (Hudson)
- frameworks/…/res build time RRO (CW on top of Hudson)

HSVs:
Hudson unselected (before): https://hsv.googleplex.com/6608441803014144
Hudson selected (before): https://hsv.googleplex.com/6729418717265920
Hudson preselected (before): https://hsv.googleplex.com/5858668019974144
Hudson unselected (after): https://hsv.googleplex.com/5844789772681216
Hudson selected (after): https://hsv.googleplex.com/6714320867033088
Hudson preselected (after): https://hsv.googleplex.com/5281839819259904
CW unselected (before): https://hsv.googleplex.com/6539239947763712
CW selected (before): https://hsv.googleplex.com/4713227354112000
CW preselected (before): https://hsv.googleplex.com/6722643641237504
CW unselected (after): https://hsv.googleplex.com/6387143780859904
CW selected (after): https://hsv.googleplex.com/5084881376772096
CW preselected (after): https://hsv.googleplex.com/5224843321540608

Change-Id: I6e8547314a53f9397df9e2e0f96eb00ff904c21e

Fixes: 321162709

Android no longer accepts applications with targetSdk < 23.
Removed targetSdk API checks that target any version
earlier than 23(M) for View and ViewGroup.

Test: ran CtsViewTestCases

Change-Id: Ibed01c5c97249cc58512964dea475aa84e93f7d6

Bug: 339041893
Flag: backstage_power com.android.server.power.optimization.oneway_battery_stats_service
Test: atest CtsOsTestCases:SystemHealthManagerTest
Change-Id: Id47990cf9c3a87c81525ef02df96c04c62f1422b

Bug: 318683126
Test: atest IntentTest
Flag: EXEMPT bugfix
Change-Id: I5f619ced684ff505ce2b7408cd35dd3e9be89dea

We've been profiling and making improvements to MessageQueue for
some time now and also have OWNERS for MessageQueueTest.java. Would
like to be able to review future changes to the core MessageQueue
class. I also added Message.java for good measure.

Test: presubmit
Change-Id: I961a2468c7b9a451d3b33d78a67f17cccf22cd60

This reverts commit 84ee5e0e.

Reason for revert: Potential culprit for b/344525050  - verifying through ABTD before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted

Change-Id: I62d3cff9a92ab5a0220f4d6cf983038c5493f282

-For Android V, updates without user action are permitted for apps
targeting API 33+
-Updated the conditions for SDK version check in PackageInstallerSession and associated
documentation in PackageInstaller.SesionParams

Bug: 325888262
Test: atest CtsSilentUpdateHostTestCases
Change-Id: Idfe3af5ac5f3a29016634b1486f0a94f7892a445

Bug: 333854840
Test: atest android.os.BinderTest
Change-Id: Iaf1fd1e5daea7103a873bc8f8aa0b78377e57714

We can use this as a "default" ranker in cases where we already know
the desired ranking from the client (subclass/caller) request, as in
`NfcResolverActivity`.

Test: new unit test
Bug: 327665515
Flag: EXEMPT bugfix
Change-Id: Ie3a7c1d061c5834559d5a15d1ceca1c12613ce60

Bug: 340439309
Test: N/A
Change-Id: I718820cb1b6ea9b1f42a4070df9c64fab96c6b2d

It seems that adding @NonNull to a parameter causes "This value cannot
be null" to be appended to its JavaDoc on developer.android.com. Because
the @param tag for the event parameter didn't end with a full stop, this
caused the JavaDoc to read "The InputEvent to check This value cannot
be null".

The @return tag was also missing a full stop.

Bug: 245989146
Change-Id: I015cf07cb94640b585242a485d4d4c44fc739255
Test: none
Flag: DOCS_ONLY

If in future other application use settings intelligence to retrieve Google account profile picture then it is better if app provide Uri, to avoid concurrent file write.

Bug:339351031
Change-Id: Iecd3ae9bf4ff0868667e9cda418fc697eeb5fb75
Test: N/A

Even though preferredRefreshRate is communicated directly to SF, we need to validate that this rate is achievable

Bug: b/330810426
Test: atest AppRequestObserverTest atest VoteSummaryTest

Change-Id: I108f600c7f3876ae11a682b6e6b066343445bacf

Test: presubmit
Fix: 343941691
Flag: EXEMPT bugfix

Change-Id: Id95aa9d1cafc00fa71852d79834793e728df2a10

Help root cause issues where the window does not draw because it
thinks its invisible.

Bug: 342257086
Test: presubmit
Change-Id: I40f12eada2e643e9c351814378a05b66a83a92e3

As requested, we want to avoid boosting when users start scrolling such
as what we did for touch boost.
In this CL, we also make the value of mIsFrameRateBoosting to false
when content velocity is detected.

Also, add a new variable FRAME_RATE_BOOST_TIME for the frame rate boost
use case other than touh boost

Fixes: 343503604
Test: atest ViewFrameRateTest, atest ViewRootImplTest
Change-Id: I8e53cb365740563030a61bf6c1f459c231a2d84f

Link to the docs for their respective AXIS_<NAME> constants instead, which
are up-to-date.

Bug: 263310669
Test: N/A
Change-Id: Ib4213a1574b3ca366686f636b5890b5bde5b421e

This reverts commit faf3e024.

Reason for revert: Seeing failures in b/343340764

Change-Id: Ie522d8f637797f79ac88427bf121bde68c62541b

This allows Perfetto Datasource users to tune the size of the shared memory buffer for the process it is running one.

Change-Id: Ie466ec8b68a1d4800bbc9d606d5f39ecae6b75b7

Explicitly match the actions because the intent filter will match any
intent without an explicit action. If the intent has no action, then
require that there are no actions specified in the filter either.

Bug: 343805037
Test: see CTS
Change-Id: Ic1f4b34a540aaa73090f8d15559d74de5779f174

Follow the same pattern as mLastReportedConfiguration

Bug: 339380439
Test: refactor
Flag: EXEMPT refactor
Change-Id: Ifc8cd7919fa6b6593694546317ddd265bd60e0e5

Fix: 332776308
Fix: 331987297
Test: build
Change-Id: I4560fe8c3c14170eabe0f4d2e3e766683812b05d

Fix: 343778621
Flag: N/A
Test: manual using go/BeeShell:

bsh> com.android.internal.graphics.ColorUtils.colorToLAB(android.graphics.Color.WHITE, lab);
$19 = null
bsh> Arrays.toString(lab)
$20 = "[100.0, 0.00526049995830391, -0.010408184525267927]"

bsh> xyz = new double[3];
$22 = [D@fbe51c5
bsh> com.android.internal.graphics.ColorUtils.RGBToXYZ(255, 255, 255, xyz);
$23 = null
bsh> Arrays.toString(xyz)
$24 = "[95.05, 100.0, 108.89999999999999]"
bsh> com.android.internal.graphics.ColorUtils.XYZToLAB(xyz[0], xyz[1], xyz[2], lab);
$25 = null
bsh> Arrays.toString(lab)
$26 = "[100.0, 0.00526049995830391, -0.010408184525267927]"

Change-Id: I83ccf289578ac66d901d884433909e1b99b4ab40

We take into account the CharacterStyle spans that change the color of
the text to be different than the original global Paint color. This
matches the high contrast background to each span of text that is a
different color.

Also, fix the isHighContrastTextDark() function which was converting
LAB wrong because of incorrect documentation (see b/343778621)

Fix: 340552436
Flag: ACONFIG com.android.graphics.hwui.flags.high_contrast_text_small_text_rect TRUNKFOOD
Test: atest frameworks/base/core/tests/coretests/src/android/text/LayoutTest.java
 && atest frameworks/base/core/tests/coretests/src/android/text/SpanColorsTest.java

Change-Id: I8e9723409b8219ad9c869dc5a7c767d2ec669939

The change is to facilitate the OobConfig application to pass the lock information to the modem.

Bug: 342411308
Test: Built successfully
Change-Id: I14a7a19286a7b2a9d073bcbaac7b35d6310d67f6

Bug: 336976070
Test: manual
Flag: aconfig support_resume_restore_after_reboot DISABLED
Change-Id: I9de421ff7285ee6aa3b3729cb33b764e6f685111

Fixes: 343772301

In our UXR study, we found that for velocities greater than
1500dp/s, we need to use 120fps to get a premium experience.
Below that, 80fps is required for a premium experience.

Test: modified existing tests
Change-Id: I010d5a7113fe1651a04b9f3dad14ce77d87daf19

Fixes: 343755505

The Windowless Snapshot surface doesn't need to use the View
system's voting mechanism. Instead, it should fall back on
SurfaceFlinger's frame rate calculator so that visible Activities
aren't pushed to 120Hz unnecessarily.

Test: manual
Change-Id: I4195549d93818ffb9187401b6f96cff04261ade1

[API Abuse - Text Consistency] Eliminate zero width, invisible formatting chars  and consecutive spaces

Some apps use different invisible characters like  in their contents to prevent the content getting truncated or trimmed.
Such character combinations can also look like multiple new lines when there are many and they can also prevent us removing consecutive new lines.

Bug: 313439845
Test: NotificationBigTextNormalizer
Flag: android.app.Flags.clean_up_spans_and_new_lines
Change-Id: I36474427f3934450a7779f8e0afa619c6ad9a2b2

Sending the normal computed index to the AudioPolicyManager together
with the devices which are operating in absolute volume mode. The APM is
responsible for avoiding the double attenuation based on this
information.

Flag: com.android.media.audio.abs_volume_index_fix
Test: logs manual - DEBUG_VOL = true
Bug: 340693050
Change-Id: I9435723b0bc100f74553ff87c1407355117194b6

Bug: 341013064
Test: atest FrameworksCoreTests:WindowOnBackInvokedDispatcherTest
Test: Manual, i.e. testing IME behaviour in test app when using onKeyPreIme.
Change-Id: I63992e62d4ab2865dd414db77fead6ead52f0931

This refactoring aims to slightly simplify the IME back callback registration. The alternate constructor for OnBackInvokedCallbackWrapper is removed and with it a number of back and forth communication between ImeOnBackInvokedDispatcher and WindowOnBackInvokedDispatcher. ImeOnBackInvokedDispatcher also no longer needs to hold its own touch tracker, handler and BackProgressAnimator.

It comes at the cost of one more layer of callback wrapping. This means that the OnBackInvokedCallback coming from the IME is wrapped once before sending it from the IME process to the app process. It is wrapped a second time when it is sent from the app process to WM (if it is the top callback).

Bug: 341013064
Test: atest FrameworksCoreTests:WindowOnBackInvokedDispatcherTest
Test: Manual, i.e. testing that registered ImeOnBackInvokedCallbacks work correctly.
Change-Id: I45744fb5c62786a437880c013427083f42562e55

Bug: 343631648
Test: atest NotificationLockscreenUserManagerTest
Flag: android.app.redact_sensitive_content_notifications_on_lockscreen DISABLED

Change-Id: Ibc613b0859531e16651645288bedbdcbef7e9824

Add Wear haptic settings for Active Unlock in main. These changes exist
only in tm-wear-kr3 right now, which means they need to be migrated to
main, and then later cherrypicked down. These global settings will be
accessible by other areas and are part of adding toggles to the Settings
pages on the watch.

Flag: EXEMPT bugfix
Test: with other CL
Bug: 379477908
Bug: 339488475
Change-Id: I2d5f06356e771124e62d7824112dd27c5edbc8af