Setting up the outline of the DP3 release notes, and bumping DP2
stuff to "archive". Updating ID tags as necessary.
See first comment for doc stage location.
bug: 28591801
Change-Id: Ide1bc24ecf8c72fee6b148e30a9b895f2b91d8c9
am: 6954edf67c
* commit '6954edf67c9e4f9717d42ddd3b424dd3164062fd':
Docs: Adds fugu to list of Vulkan-supported devices.
Change-Id: I81493f743cc9452469d93eeee81e2b24bca813de
If the window was add by a client using another client's app token,
we don't want to keep the dead window around for this case since
this funcationality is meant for 'real' apps.
Bug: 28467642
Change-Id: Ie4fdd9f90b122439a2fbcc60085ebfdb562d5c6d
am: 21a55dc82c
* commit '21a55dc82c24ffb8c0d77c1980fe5acc1400001d':
Docs: Adds fugu to list of Vulkan-supported devices.
Change-Id: I372454e0f336d4ae4703ca296e102447db247d61
am: 0de8689243
* commit '0de8689243ae0d48744b7c1584670a10febafe32':
Docs: Adds fugu to list of Vulkan-supported devices.
Change-Id: If89adfe3f280815f26cec7048e50e4d8c9ad7b7d
am: 60e5bc30bb
* commit '60e5bc30bbb41f25836a8bbd2a04bc2eab4b7f8c':
Docs: Adds fugu to list of Vulkan-supported devices.
Change-Id: Iab5e6c2b992c241de667476ce74b2bc6a2d4dac9
am: 0677d4b715
* commit '0677d4b7153327fef6b33c90c5bf61f756c1bea3':
Docs: Adds fugu to list of Vulkan-supported devices.
Change-Id: Ida6a6972ff32917eb9367871d6ea0766cc37d05e
+ By default, OEM unlocking setting is enabled.
+ Add a check to prevent oem unlock being flipped if the setting isn't
enabled.
Bug: 28163088
Change-Id: I087d8d5a1d99a611a8f66ff71a92ec9ea1da4e9f
When the activity locally recreates itself, nothing
on the server side is able to prepare preserving windows,
or replacing windows. The activity was trying to defer
removing the old window, but it was just waiting
until the new one was created, not until it was drawn,
thus resulting in a flicker. It's easy to backpack on the
existing replacement infrastructure.
Bug: 28221875
Change-Id: I55fc4ca78e9e11809473fedd8b30b6a6350cf852
am: 9e5d4e078a
* commit '9e5d4e078a93f187f6ec612734dded61372636fb':
Add HP and Mopria print recommendation service
Change-Id: I6dd1b1dd1787282ad67d7bdd4ffbce070e6de860
This bug was a corner case of stopping lying about
Configuration#keyboard when "Show software keyboard" is turned on, which
was done by my CL [1] in Android N development cycle.
Previous implementation
if (config.keyboard != Configuration.KEYBOARD_NOKEYS) {
had relied on the fact that the system was lying about config.keyboard,
which is no longer valid. We need to change the behavior of
InputMethodService#onShowInputRequested() depending on
Settings.Secure.SHOW_IME_WITH_HARD_KEYBOARD like we did for
InputMethodService#onEvaluateInputViewShown() in [1] to minimize the
impact on stopping lying about Configuration#keyboard.
[1]: Id4d332e3909590c68345e10e1f2e18650efb2eb7
7b739a802c
Bug: 28423439
Change-Id: I8a774cbf61ac706d8446be91b17bceee57a13656
In some cases it is possible for activity manager to request
a resumed activity to stop when it's visibility changes. This
is a valid transition, however we need to make sure to pause
the activity on the client side before stopping it so lifecycle
transition works as expected.
Bug: 28574036
Change-Id: I759b38bbd1c9c3bb0475759bcb638d8223fa504d
am: a5e6553917
* commit 'a5e6553917359bb662c8f2788feb3d617803d406':
Start VPN as early as possible during startup
Split network agent created state from connected state
Change-Id: I5fedffbf3d8f2826b94ccd2f3e1ba1f5563c43af
This reverts commit 895504e557.
Also adds a change to device manager to prevent failure there
as in the bug below.
Bug: 28512889
Change-Id: I4a445ec365133e9e2764e2d625d61fc6ee2008ec
It's possible for a call to updateConfiguration() to happen in the middle
of performTraversals(), after the measure phase has happened, but before
the layout phase. During the configuration call, it's possible for views to
have requestLayout() called on them. This can result in the request flag
not getting cleared, because views that have had layout requested, but which
have not yet been measured, may not be told to layout.
The correct flow should be that any code path causing requestLayout() (which
could be anything that calls out to user/app code) should happen before the
measure phase (or cause a second measure to occur). For now, causing the second
measure to occur is a low-risk simple change that fixes the immediate problem.
Issue #28152259 Calling requestLayout from inside View.onConfigurationChanged can cause problems
Change-Id: I3b532eeacc3784d8d21193d01ddd7fa15ac0684e
am: 2ff157c027
* commit '2ff157c027cb3eb5eddefa39617ec49aeb75a139':
Add a null check for the thumbnail image for transition
Change-Id: I149beb8615e78677e25b07cbf137152165ae38b9
