From 6bcda6387fb7b93dceeb71156170c8f9a02725ea Mon Sep 17 00:00:00 2001 From: Martin Hibdon Date: Fri, 17 Dec 2010 16:56:07 -0800 Subject: Correctly save Activity's state in saveInstanceState Prior to this change, saveInstanceState would call directly to Activity.onSaveInstanceState(), rather than performSaveInstanceState(). This meant that saveManagdDialogs() was not called, so Activities running under a LocalActivityManager do not get their dialogs restored on configuration changes. Change-Id: Id45110a8716a86958c14f4b1ea5a84c9cdf107f1 --- core/java/android/app/LocalActivityManager.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'core/java/android/app') diff --git a/core/java/android/app/LocalActivityManager.java b/core/java/android/app/LocalActivityManager.java index 5da04f1..c958e1b 100644 --- a/core/java/android/app/LocalActivityManager.java +++ b/core/java/android/app/LocalActivityManager.java @@ -493,7 +493,7 @@ public class LocalActivityManager { // We need to save the state now, if we don't currently // already have it or the activity is currently resumed. final Bundle childState = new Bundle(); - r.activity.onSaveInstanceState(childState); + r.activity.performSaveInstanceState(childState); r.instanceState = childState; } if (r.instanceState != null) { -- cgit v1.1