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: 4398aad
* commit '4398aad9542ff58df6ac2aa38f5e31f18021a306':
Show forced resizable based on top activity
Don't move forced resizable info activity to the front
Change-Id: Ib5a88c47ef73b461fb1d09b45e4763b0d6512666
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: 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: 70b58c4
* commit '70b58c4a3ee59bef623cd4bb3d5d10c165bf517d':
Only log when system UID finds missing data paths.
Change-Id: Idc2531e10088ee0859d6af2213e28a4c7f075cf7
am: 2c3f2c4
* commit '2c3f2c4da90613bafc93ed34e53867da10084212':
Only log when system UID finds missing data paths.
Change-Id: I90b8fe98181dc2b7d00f0c9d320acce316d637e9
am: 864bc48
* commit '864bc48e0104451e20281258429677a9ebbab9ac':
Support to pass <uses-library> option through to dex2oat.
Change-Id: Ia276b7594e31177f0295e03982aae96267367887
ViewRootImpl may be null at this point if
we didn't preserve. Sorry about the churn.
Bug: 28413589
Change-Id: Iebfd819490252b52332d94ccefbddfae160087cf
am: ce09139
* commit 'ce091392274585a897e489ed7b49e82ee222f0cc':
Fix a bug where restartLoader would result in a stuck loader
Change-Id: Idb5c97da8760792598a2d78be05b624f120cc6c7
am: 596a4a1
* commit '596a4a1592a8f5e7b708d884145e280df9b638d0':
Fix a bug where restartLoader would result in a stuck loader
Change-Id: I635309e5b37dfca8befdadeb578a71ae1619ac00
To be able to reuse this code when creating a classloader for
the system_server.
Bug: http://b/27245894
Bug: http://b/27702070
Change-Id: I928175a39a1beb0446d863a5b8f5edf94686e768
(cherry picked from commit 5d7d777fa6)
We're really only interested in tracking down when the system UID
tries touching missing data paths, since it's the only one with enough
permissions to mkdirs() directly without going through installd.
Without the guard added in this CL, we'd end up logging for direct
boot aware apps that tried obtaining CE paths while locked, which is
perfectly valid.
Bug: 28272737
Change-Id: Id24f3160f61d8ad8047d5c551bc6a91c868bd301
am: 493576b
* commit '493576bc5db94068b5a767021a4a5c8b6963c836':
Create linker namespace for the system server classloader
Extract pathclassloader initialization to a separate class
Change-Id: Ifbebd0a98c3d80620b53bf7ebef76222e57ca923
This change takes an app's shared libraries specified by <uses-library>
and passes it through to dex2oat to be used during compilation.
Part of a multi-project change.
Bug: 26880306
(cherry-picked from 7b331b6a8a)
Change-Id: I523b1b74775e7ed27072498509e743f1f10b1164
