| 770c4030691f11ca36ef0028a336a27eda2049ef |
|
03-May-2018 |
Andrii Kulian <akulian@google.com> |
Preserve custom activity intent on relaunch
An activity can have a custom intent set via Activity#setIntent().
This was lost in ag/3305584
Change-Id: I88f3e164d2cf7f6c62989bba05cd84b9b83befc3
Fixes: 73181785
Test: ActivityThreadTest#testCustomIntentPreservedOnRelaunch
/frameworks/base/core/tests/coretests/src/android/app/activity/ActivityThreadTest.java
|
| d9e2acba96ed59c40de15b37e813e1369d9e5169 |
|
30-Mar-2018 |
Andrii Kulian <akulian@google.com> |
Don't finish activity on duplicate resume request
With ActivityLifecycler infrastructure duplicate resume situations
are limited to double-relaunch scenario and there shouldn't be any
incorrect resume requests. This means that there shouldn't be any
reasons to finish activity when trying to resume it.
Bug: 77240441
Test: android.app.activity.ActivityThreadTest
Change-Id: I70a3fcbff72954ff673b2020be3134be367cd823
/frameworks/base/core/tests/coretests/src/android/app/activity/ActivityThreadTest.java
|
| 829829ca2c1804147dd42b106e5d7f1efe99a1f9 |
|
20-Mar-2018 |
Andrii Kulian <akulian@google.com> |
Don't throw exception for duplicate stop
A double stop request is possible when display is being locked.
An activity may receive a "sleep" message followed by "stop",
both of which try to move it to stopped state.
An example when this happens: a keyguard is set up and the screen
is being locked. The keyguard will occlude the activity, which
causes a transition to paused state and, eventually, to stopped
state. A "sleep" message can be sent sometime before "stop" message
and will ignore that activity is in the process of becoming stopped.
Change-Id: I09e2c26004664b6e73ac5c2b6fe88bdf8271cf34
Fixes: 74967786
Test: FrameworksCoreTests:ActivityThreadTest
/frameworks/base/core/tests/coretests/src/android/app/activity/ActivityThreadTest.java
|
| dfbf9716882f8237e22431b30a89d8dd6b1183fa |
|
09-Mar-2018 |
Andrii Kulian <akulian@google.com> |
Don't throw exception for duplicate resume
A double resume request is possible when an activity receives two
consequent transactions with relaunch requests and the second is one
is omitted. We still get two resume requests for the final state.
Fixes: 74074327
Test: FrameworksCoreTests:ActivityThreadTest
Change-Id: I8bb8594948a17b7fbf595a49026ff33b54b66049
/frameworks/base/core/tests/coretests/src/android/app/activity/ActivityThreadTest.java
|