If activity controller was set and application crashed - process was killed,
but records in task history were not erased and AM restarted crashed activity.
This caused crash loop if activity was crashing on every launch.
This CL handles app crash correctly in this case + lets AM handle
instrumentation test crash in ActivityManagerService#handleAppDiedLocked to
remove code duplication.
Bug: 28374171
Change-Id: Idf50d1e2cc784c0ae970aa290b82fe1eedd6d1fd
The /tools/ top-level directory is going away when we move to devsite
(and the Android Studio docs get their own home) so I'm moving the
non-AS docs out of there. Also adding redirects (and fixing redirects
that pointed to the old locations).
For the time being, I'm also adding these libraries in to the
"API Guides" TOC, just so they're discoverable from somewhere; I'm
expecting this to change post-redesign.
See first comment for doc stage location.
bug: 28270787
Change-Id: I07488251384fbd22d2512a797793cf98654f54e7
This is to support CTS's ability to check that the expected verifications
are indeed being performed by the currently active verifier.
Bug 27482754
Change-Id: Iccb9bd273c7893f04e45bfca0708dcfdde595a3e
Started this CL when mnc-mr-docs was the active branch, but now
the production builds come from mnc-docs.
Per feedback from the support library team, updated the support
library overview page to better explain what the libraries are
and what they're for. This is the beginning of a big overhaul of the
support library docs.
The "overview" section has been rewritten and expanded in this CL.
The "revisions" section hasn't been touched, except that the heading
was changed to "Support Library Revision History". (I'd like to
move "Revision History" to a separate page, but I'll do it in a
follow-on CL.)
See first comment for doc stage location.
bug: 27274455
Change-Id: I12ce21c948421e1bd0be5d3151845f900750e7b1
(cherry picked from commit 06ba3db938)
Ensures each action gets at least its minimum width to prevent
an overly long action from squeezing out the others.
Change-Id: Ifb6253051b556bbab4738abef12dad0bb6f3c3d6
Fixes: 27996783
Bug: 28428970
Test for video sources and fix a bug where
we should throw an IAE for surfaces that are invalid
at request time.
Change-Id: I891a2b1568f583300433c7aca6de36d2e2621c63
Moved several USER_STOPPING registered receivers to listen
to USER_STOPPED, since they don't need to be blocking the
shutdown of the user.
Clear all stale broadcasts when stopping a user, so that we
don't unnecessarily start up processes and deliver stale
broadcasts. This was causing code to run when the user was
already stopped and resulted in crashes when other providers
and services couldn't be started anymore. Hopefully this fixes
many of those races.
Bug: 28371487
Change-Id: Ic35a7a23fa8fe009a53f8bf7545d4dad5fa34134
Hour was not updated correctly when a new hour was selected using the
radial picker or when AM/PM was changed, which prevented programmatic
calls from working.
Bug: 28398738
Change-Id: I0c1ffd9f9e569d980e72e74dc62568a56930afc4
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
