If present, the system property "ro.config.lock_wallpaper" provides a
filesystem path to a decodeable image file to use as the system's
out-of-the-box lock wallpaper imagery. In the absence of this
system property, or if the indicated file is absent or unreadable,
then the new framework resource
com.android.internal.R.drawable.default_lock_wallpaper is consulted to
locate a usable asset. This mechanism parallels the existing one for
the default system wallpaper.
By default there is no specific lock wallpaper asset; the resource is
defined to be @null in the standard config.xml file. A product that
wants to define such a factory-default lock-only wallpaper image
will provide the asset as part of its framework resource overlay.
Bug 27828056
Change-Id: Iebf3706222370d0a0a4baf88d71a59ead07a25c7
am: 77ab7fc8d4
* commit '77ab7fc8d4f4596b1275a7065f05380e22da3a1a':
Lock down networking when waiting for always-on
Change-Id: I4160a61ca437d20df4342a44ed24fc6ad47962c6
am: d171df660e
* commit 'd171df660e19bdba4d188beeb8b6023874712413':
Lock down networking when waiting for always-on
Change-Id: I7be0a85597936421750d1da0fde3d55d7d4fabc5
am: d2d8e9b228
* commit 'd2d8e9b22830a07d12f1542a5dc9476a3ab3d7bb':
Store the appropriate layout id for the infrated view, so that it can be used for verification during reapply.
Change-Id: I04ca85225233f4165c3c9cd1ab56d9c772b7d7c1
am: 2a1076339e
* commit '2a1076339ecb7ba9b7c8829bb3c3285df29a67e3':
Two phases to set the password for disk encryption
Change-Id: I884dae66b133d8b9312a7793d415964e13ed8105
am: 56a9395aeb
* commit '56a9395aeb198e0a7db5e9666cc81ba7ce5f8e0d':
Two phases to set the password for disk encryption
Change-Id: Ieac13a4c2775e3d2bc5463f4161c6e8b151bf6c9
am: 56a9395aeb
* commit '56a9395aeb198e0a7db5e9666cc81ba7ce5f8e0d':
Two phases to set the password for disk encryption
Change-Id: I76b3b1351ea85d8a5e42da523f57a291b3a1b0d9
Preallocate storage lists and avoid TextUtils and its string
builder for a common code path.
Optimize list join helper to not have a check in the loop.
Bug: 28801010
Change-Id: Iafc582031f973d718252b34bcda6405a77425628
am: 6e2ee9e382
* commit '6e2ee9e382dd86340d5242fe04a623b9cda10f6e':
Mark occluded home stack as invisible.
Change-Id: I1762cf46b675fe2c5151332a53139e95d676cb01
am: 32b54f2e42
* commit '32b54f2e42c4ff793c418c29c0ce9ef0be2a4a16':
Mark occluded home stack as invisible.
Change-Id: Iae4279835f345b2b294acca20760634ba031f0bd
am: 32b54f2e42
* commit '32b54f2e42c4ff793c418c29c0ce9ef0be2a4a16':
Mark occluded home stack as invisible.
Change-Id: Iaa68bb7c93ffd8bcfc9af3e66fd7fced7787a671
am: dbf0dbd8c2
* commit 'dbf0dbd8c216e801b3d95f83d13ae05c1ba0ea39':
Retail mode flag and some clients for it
Change-Id: I5f9e7c49759154925c6f20ab3fd647d84259b1bb
During the PiP animation, we have two basic requirements:
1. We need to scale windows to the pinned stack bounds.
2. We need to halt resize and movement notifications to the client.
As we end the animation, we need to disable these states at differing
times. First we need to deliver a final resize and movement notification
to the client for it's new position. However, Surfaces may not
immediately resize (in particular in the case of child windows,
it may be some time!), furthermore Surfaces may resize at different
times so we need to persist scaling on a Surface by Surface
basis after reenabling resize notifications.
Bug: 28559097
Change-Id: I6d52a3e213e08a34f4c0eea892b2a84cd4c20e18
