1eb0637f2a17362476a8876b4437f8a0c0783b86
- When a new display is added, display add event triggers handleDisplayAddedLocked in WindowManagerService asynchronously. - After creating virtual display, application can move on and call addWindow before handleDisplayAddedLock is called. - Application's addWindow leads into creating a new DisplayContent, and a window will be added there. - But when handleDisplayAddedLocked is called later, it will create a new DisplayContent for the display, and the window added by the application will be lost. - This CL tries to fix the issue by checking the presence of DisplayContent before creating a new one. bug: 9975297 Change-Id: I9fac7ffb57c3e1effa8f0e950539cfae73e7e1c6
am
6dd38cc5
: Revert "Revert "resolved conflicts for merge of 45178b13
to jb-mr2-ub-dev" revert to fix conflicts, i\'ll fix it all later."
cherrypick from ics-mr1 docs: source for nw app Change-Id: If50f407a0e56fa802fe9beedaa650e3a131872b2
…
am
9b7b4450
: am 02eab434
: am 4d87d91d
: Merge "If in a mobile captive portal is detected enable fail fast." into jb-mr2-dev
…
Description
No description provided
Languages
Java
77.3%
Kotlin
9.2%
PowerBuilder
6.6%
C++
5.5%
AIDL
1%