* changes:
[automerged blank] Don't set background color if TDA doesn't have a valid surface 2p: 62f69423c5
Don't set background color if TDA doesn't have a valid surface
* changes:
[automerged blank] Use TDA for background color instead of new color layer 2p: dc4296e335
Use TDA for background color instead of new color layer
Devices got created twice because I forgot to remove a
debugging statement
Bug: 220168245
Test: MidiKeyboard and MidiScope
Change-Id: I2bd7b28bec3025e62dce39fcd500350a9ca6de8d
Merged-In: I2bd7b28bec3025e62dce39fcd500350a9ca6de8d
We first need to dispatch insets, then we can measure so we don't
need to immediately measure again.
Fixes: 210881360
Bug: 190379081
Test: Presubmit, Boots
Change-Id: Id40a083dd2e122ca71a96213e94b5bbbb45d596d
As it has a marginEnd, it has to be layout_gravity end for FrameLayout
to properly measure and layout
Test: visual
Fixes: 221071029
Change-Id: I07cbcc7bd32992c216825ea8e281b1288d03bfbd
Move the service connector empty check before adding it to the service
connectors map. So when there's no CDM services, there won't be a value in the map.
Bug: 219784113
Test: manually tested no services case using CDM test app. The app
doesn't crash now.
Change-Id: Ib236d42a43c001c0ea5fa4debf5f832daee811c4
Revert "Disable per-process app class to investigate (disabling CTS)"
Revert submission 16804724-disable-per-proc-app
Reason for revert: The revert has reached weekly. Now I'll revert it to see what change it made.
Reverted Changes:
I87f16857b:Disable per-process app class to investigate
I87f16857b:Disable per-process app class to investigate (disa...
Change-Id: Ib84035c7819acc347e0bbba8bfada66300778c63
Test: treehugger
Bug: 185177290
Noticed while trying to switch Cuttlefish to HWComposer3
with ag/16624862. By default, Cuttlefish has a single display
with a single config:
`RanchuHwc: config: id: 0 w:720 h:1280 dpi-x:320 dpi-y:320 ...`
In `LocalDeviceDisplay::updateDisplayModesLocked()`, the display
config ids which come from HWComposer via SurfaceFlinger are mapped
to DisplayRecord's Display.Mode's `mModeId` which are globally
unique ids created from the atomic integer
`DisplayAdapter.NEXT_DISPLAY_MODE_ID` (which defaults to 1).
However, the preferred display config id (`mSystemPreferredModeId`)
was not being mapped. This would lead to boot failures such as:
`
AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: android.anim
AndroidRuntime: java.lang.IllegalStateException: Unable to locate mode 0
`
with ag/16774826 because `mDefaultModeId` was being set to
`mSystemPreferredModeId` which was the unmapped `0` from HWComposer.
(Perhaps the need for this change suggests there should be strongly
typed integers to represent the different id spaces,
`SurfaceFlingerModeId` vs `DisplayAdapaterModeId` or something)
Bug: b/193240715
Test: lunch cf_x86_64_phone-userdebug && cherry-pick ag/16624862 &&
m && cvd start
Change-Id: I8fc0fca6816e037196f51d256430fad480f3b0ff
(cherry picked from commit 53a296d20f)
This is something that sometimes occurs in tests since the detaching of the TDA in not necesseraily synchronized with animations
Test: atest CtsWindowManagerDeviceTestCases:MultiDisplaySystemDecorationTests
Bug: 207667555
Bug: 209936970
Merged-In: I9881453ba14cba4f219861ec4449f2baa8058b57
Change-Id: I9881453ba14cba4f219861ec4449f2baa8058b57
(cherry picked from commit e644ff6102)
