summaryrefslogtreecommitdiff
path: root/core/java/android/app/WaitResult.java
Commit message (Collapse)AuthorAgeFilesLines
* Add a new launch type for hot start with relaunched activityRiddle Hsu2020-11-181-1/+17
| | | | | | | | | | | | | | | | | | | | | | | An existing activity may be relaunched when moving from background to front if the current configuration is changed and the activity cannot handle the change. The relaunch type was reported as a hot start because its process is alive and the original activity exists. But the relaunch needs to destroy the original activity and create a new instance, which may even take longer time than a warm start. So the case should be separated from hot start. Also: - Make WaitResult#launchState is always populated by ActivityMetricsLogger, so "am start -W" can get consistent launch type. - Remove dead code in ActivityRecord#ensureActivityConfiguration that it already early returns if !attachedToProcess. Bug: 172528316 Test: atest ActivityMetricsLaunchObserverTests#testLaunchState Change-Id: I3ef64ce1e23b2f13d42fa2b12bc31c0cdb4652fc
* All Parcelable CREATOR fields are @NonNull.Jeff Sharkey2019-02-281-1/+1
| | | | | | | | | If they were null, then the Parcelable would fail to work. Bug: 126726802 Test: manual Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014 Exempt-From-Owner-Approval: Trivial API annotations
* AM: Report launch state with activity launch infoVishnu Nair2018-12-131-0/+51
| | | | | | | | Bug: 119988524 Test: atest ActivityMetricsLoggerTests Test: adb shell am start -W ... Change-Id: I1d323e84d725722a198a60c51884dba897ec253f
* AM: Use ActivityMetricsLogger to get app launch timesVishnu Nair2018-09-281-4/+1
| | | | | | | | | | | | | | | | | | | | - Make ActivityMetricsLogger the single source of truth for activity metrics and use it to provide data for Tron, logcat, event logs and {@link android.app.WaitResult} - Remove LaunchTimeTracker - Remove workaround added for b/80084651 - Remove thisTime from WaitResult and logs - Remove am_activity_fully_drawn_time EventLog Tag Compatibility Changes: - thisTime removed from logcat and eventlog. Only totalTime will be displayed. - Change in activity visiblity during launch will invalidate totalTime. am start -w will only report WaitTime in this case. - am_activity_fully_drawn_time is removed from event log. Bug: 67683350 Test: atest CtsActivityManagerDeviceTestCases:ActivityMetricsLoggerTests Change-Id: Ib033594b961be9227256eba2a519dd6c2e3db573
* Check component before notifying activity is visible.Bryce Lee2017-04-061-0/+11
| | | | | | | | | | | | | | | | | ActivityStackSupervisor tracks WaitResults which are waiting for an Activity to become visible. This is used exclusively by ActivityStarter to wait for an Activity to be brought to the foreground before returning. However, there are some cases where other Activities will report a visible state in between. Without a qualifier, these would cause the ActivityStarter's WaitResult to be fulfilled and the wrong information would be returned. This changelist specifies a component the WaitResult should be triggered on. Change-Id: I7c356a8d153ddc24603acc55749e9992f9000c3f Fixes: 36860122 Test: cts-tradefed run cts -m CtsServicesHostTestCases -t android.server.cts.ActivityManagerAmStartOptionsTests#testDashW_Direct
* Move IActivityManager to aidl.Sudheer Shanka2016-11-041-0/+72
Bug: 30977067 Test: Existing tests are passing, dump commands still working. Change-Id: I9cf81c4d381ebce14a6c701e409cbb269f2ff1fb