am: a1bca975ef
* commit 'a1bca975efce3830d3c97a98db785151daeda465':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: Ib8af31efc5117528d2599fa03bd5ed74f6606fe7
am: 07f8d94c6e
* commit '07f8d94c6e53cfd7dd389027fc2471ce5ea07846':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: Id5755e333af7552537ddf02c07f0ef12d998b427
am: d1c30db548
* commit 'd1c30db548da90d5bc092821c6fee4b4ef060bbb':
ShortcutManager: When app's data is cleared, remove all shortcuts,
Change-Id: I798a064e17a628999568a3a68634318ff1126bf4
Consistency for:
* Early return on calling setter with the current state
* Calling setWillNotDraw when divider is configured with drawable
and visible
* Calling requestLayout to trigger a relayout pass
Also fix a bug that wouldn't show end divider when all non-GONE
children have 0 width/height.
Bug: 28398719
Bug: 28404367
Change-Id: I16796c74a52ac4c3041390c75add2ec3c33bea8b
There is a narrow window of time during user unlock where we're
reconciling user storage and dispatching the "unlock" status to
various internal system services. While in this "unlocking" state,
apps need to be told that the user still isn't actually "unlocked"
so they don't try making calls to AccountManager, etc.
The majority of internal services are interested in merging together
both the "unlocking" and "unlocked" state, so update them.
Clarify naming in AccountManagerService to make it clear that a local
list is being used, which mirrors the naming in MountService.
To match UX/PM requested behavior, move PRE_BOOT_COMPLETED dispatch
after the user is unlocked, but block BOOT_COMPLETED dispatch until
after all PRE_BOOT receivers are finished to avoid ANRs.
Bug: 28040947, 28164677
Change-Id: I57af2351633d9159f4483f19657ce0b62118d1ce
am: c2be3ea
* commit 'c2be3ea7cdf0e4ae3f64bec94e937a53bd975094':
Prevent pinned stack from having extra elevation
Change-Id: I33675b67b7d84eb23ffdec6c9a8e21cd19f3064c
am: 0f01857
* commit '0f018570fff044bb68b8009815ae7e5c397d09fd':
Prevent pinned stack from having extra elevation
Change-Id: If115698ec6168bfced727b7488cc38b833d4618a
Pinned stack doesn't have focus, so there's no need for setting extra
elevation to show shadow for focused case.
This removes extra eleavtion for pinned stack, and improves the PIP
animation quality by preventing extra surface size change
at the end of animation.
Bug: 27364161
Change-Id: Id099a78de48b2e038a69600c94454b5cbfe0628f
am: c097c93
* commit 'c097c9377e6a7e2f6577dd374dc218ef4f57c2eb':
Make isCaptivePortal perform both HTTP and HTTPS probes.
Change-Id: Iced513171ceb6e3e1c4fea545786e59b8c64b40a
am: 4398aad
* commit '4398aad9542ff58df6ac2aa38f5e31f18021a306':
Show forced resizable based on top activity
Don't move forced resizable info activity to the front
Change-Id: Ib5a88c47ef73b461fb1d09b45e4763b0d6512666
am: 7146d02
* commit '7146d02910808367f30c82b7b05d757b47a2bc66':
Make isCaptivePortal perform both HTTP and HTTPS probes.
Change-Id: I2c0625395528fe4984cd18f5b34981b9ef0e9969
am: 1601067
* commit '16010672874c7fbacd248c87a31396f7d8222334':
Show forced resizable based on top activity
Don't move forced resizable info activity to the front
Change-Id: Ifa8fb6f3c0c98a74b959be82a523dd4987a0d9d5
am: 1d3c594
* commit '1d3c59457c9bcf30e6ecb898e64d9d9725e7803e':
Make isCaptivePortal perform both HTTP and HTTPS probes.
Change-Id: Ic58f5be8dce42c17213ef261f348eda31c6c11e7
am: 831ecc8
* commit '831ecc81f982282bdcc2121c2fa3ece22ac997e0':
Show forced resizable based on top activity
Don't move forced resizable info activity to the front
Change-Id: Ib61028c751a31b437fb459bd094c2fedadd40abe
Since activity manager only issues a configuration change when
we are not relaunching the activity, the optimization to suppress
that on the client side is not needed anymore and only leads to
issues where there is a change in smallest_width but we are not
relaunching the activity because the change doesn't cross a size
threshold.
Bug: 28050773
Change-Id: I303c190bd7390363d1030edcdb2913b7c64c666d
If we start the forced resizable activity with an existing task,
avoid moving that task to the front. This can cause that a previous
task that was moved to the back gets moved to the front again just
because we started that activity. That's not good.
Bug: 28223489
Change-Id: If8acf31b8be98b82665de1015d5621331c37fb64
am: 8aad038
* commit '8aad0386145df5a11cc9140a4b7e8d4588e64aa5':
Fix issue #28431297: Crash in system process
Change-Id: Ibfe02253fe0a4d4981680e58de4d90422e05c9e0
am: 77ea251
* commit '77ea25191f96c71c634fb1cc8589f83140a79233':
Make sure FIRST_LAUNCH is after PACKAGE_ADDED
Change-Id: Ic386fa6ce64fbbe52b377105891c3904c3f48011
am: 2501220
* commit '2501220e1f473752b5eadc663f7486668e9b9fc6':
Fix issue #28431297: Crash in system process
Change-Id: Icae0787b41e5c47339496e0c08457e331e37162f
am: 1a2f993
* commit '1a2f993ba5a81899500b989683364708025e13a5':
Fix issue #28431297: Crash in system process
Change-Id: I46aec10a524e6864b414d12bb2a79bc24d8b47ae
