PendingIntent.FLAG_ONE_SHOT is needed to prevent the PendingIntent being
reused.
Also, flag and activity option of credential intent in BaseStatusBar
is not same as the one in ActivityStarter. Added a new
function startConfirmDeviceCredentialIntent in AM to centralize it.
Change-Id: I2d9e5923ad5d4d012f10057c409c666c8ca299a3
Fix: 28309964
am: cdfe208a99
* commit 'cdfe208a99906b4157305ea0c4af06d2e303d830':
Don't back up wallpapers that we've been told not to
Change-Id: I45e4c3c47e371c3808e5669e2c7af6d8405edb7a
Print interval clamp message
only for periodic jobs having
period/flex less than the minimum value.
Bug: 28296128
Change-Id: Id0d7c3b56048582a490bb8214eca491ec2bbdc93
am: 665189f
* commit '665189f92646d34bf02082120cba3c62aa718770':
Don't back up wallpapers that we've been told not to
Change-Id: I45d037436e349445f091a7dad5abad4b7421ad8e
In addition, now that the full uncropped wallpaper image is being
backed up, we now handle that via the full-data backup path instead
of key/value. Restore still knows about legacy data that gets
delivered via the older key/value mechanism.
This change also has the effect of removing the size limitations
around wallpaper restore acceptance. Any size source imagery is
valid, as crop & scale are rerun in a device-appropriate way
after the restore.
Bug 25453848
Bug 25727875
Change-Id: Idc64a2eaab97a8ecc9d2b8ca5dc011f29cab324d
am: e1b5670
* commit 'e1b56701fd219227adae615fe81f03d5db4ae433':
Remove links to createAndInitializeUser() and createUser()
Resolve merge conflicts of a5060ee to nyc-dev
Change-Id: I8cf43f9ad491c6f23eb5fe0051293267ab2d03bf
am: 254f1b8
* commit '254f1b8a43480749b7061129289d34bc15d345a5':
Remove links to createAndInitializeUser() and createUser()
Resolve merge conflicts of a5060ee to nyc-dev
Change-Id: I32a3081af9ca5533785c90b7239ffd5b5e69d5bf
am: 59c9a93
* commit '59c9a93fc268e226495d4ee8cf7c507c2ea2c433':
Remove links to createAndInitializeUser() and createUser()
Resolve merge conflicts of a5060ee to nyc-dev
Change-Id: Iddc9419069d8f5d555baf0c1ef4b2f2ebf75c370
Previously if we failed to load an asset path, we would return a
null AssetManager which would lead to an immediate NPE.
Throw a proper exception instead, detailing which path failed to load.
Bug:28216288
Change-Id: I491b9316b837bf333b5ae78d4eb1ee31741617ec
am: 512ab59
* commit '512ab599fc903da21b67c0c4d01ce9ffb8e6d68f':
Kill foreground apps when turning off work
Change-Id: I83e0e9792225416c6a0c9de4a8201dcb2e37666f
am: 49425d6
* commit '49425d612cee3864a316e9ecb6ec3faeae519b1e':
Kill foreground apps when turning off work
Change-Id: Ie8ea1ec98232437623c83f7d32c1f05c47580b35
Add test method to remove admins that declare
FLAG_TEST_APP without informing them.
The method will also remove the device and profile
owner status of the admin.
Bug: 28027468
Change-Id: Idb4d3299a9c6595c94bfb424546cd8a384131835
Introduced new error codes so that Instrumentation can
include the correct message in the exception.
Bug: 28216630
Change-Id: I93ee77153cdad11fa208c74c28c6790db27c9753
am: dbc4e4f
* commit 'dbc4e4fa83d6fb460165be22798bbf04422be9c2':
Work on issue #28221912: Starting service as foreground might...
Change-Id: I243f791317962d2ab9eea156b0f146f6fcc96fcb
am: 9c211a3
* commit '9c211a339689a2e54da3315ccdbf22add472c76a':
Work on issue #28221912: Starting service as foreground might...
Change-Id: I9f94c6adca6891ac0e43b83f45001092536c7ee9
While work apps will all be killed as we stop the profile user when
turning off work, this can sometimes take a while. So let's kill the
foreground apps as soon as work profile is being turned off to make
the user experience nicer.
Bug: 27631526
Change-Id: Icdd3799385a98ee531b0b4247e8ede78f6f10da8
This undoes the automerger skip which occured in
commit e740c84dc3 and
replays it as a standard (NOT -s ours) merge.
Change-Id: If5a47be26f73d6a0735c425cd66310a3e2a89086
Dialer recreates activity inside onConfigurationChange
when configuration changes significantly. Recreated
activity in this case was initialised with old base version
which resulted in incorrect configuration in split-screen.
This CL updates configuration when activity is created from
override config.
Bug: 27976063
Change-Id: I0ac002a5661154ec25f2d5aba3d44070b683ba2f
am: f6267a0
* commit 'f6267a0ac1fcfdd2f83a9b20934bdf4bea9ee65f':
Be bug-compatible with Fragment#setUserVisibleHint < N
Change-Id: I38d063ed28041d07f188250408e98c5272be2d11
am: de7b2ed
* commit 'de7b2ed881d75cb7f21ae2199b9af68ae019becf':
Be bug-compatible with Fragment#setUserVisibleHint < N
Change-Id: I4bf16f207710cc9b9214d4c97e260a1348c3fe19
Prior to Android N we were simply checking if a fragment had a
FragmentManager set before we would trigger a deferred
start. Unfortunately this also gets set before a fragment transaction
is committed, so if setUserVisibleHint was called before a transaction
commit, we would start the fragment way too
early. FragmentPagerAdapter triggers this situation.
Unfortunately some apps relied on this timing in overrides of
setUserVisibleHint on their own fragments, and expected, however
erroneously, that after a call to super.setUserVisibleHint their
onStart methods had been run.
Bug 28184671
Change-Id: Ie40d5f6963d312c2fad4a48fb4f992d33e65c83b
