From 1793d4769b9d357d4ec6e27099252bc1a938d100 Mon Sep 17 00:00:00 2001 From: Jorim Jaggi Date: Wed, 27 Apr 2016 20:59:40 -0700 Subject: [PATCH] Remove optimization to report config change 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 --- core/java/android/app/ActivityThread.java | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/core/java/android/app/ActivityThread.java b/core/java/android/app/ActivityThread.java index f7c0b4c32bc90..6d805eda2b384 100644 --- a/core/java/android/app/ActivityThread.java +++ b/core/java/android/app/ActivityThread.java @@ -4617,16 +4617,7 @@ public final class ActivityThread { // onConfigurationChanged int diff = activity.mCurrentConfig.diff(newConfig); if (diff != 0) { - // If this activity doesn't handle any of the config changes then don't bother - // calling onConfigurationChanged as we're going to destroy it. - // Except in the case where the configuration changed on the activity manager side, - // but wasn't big enough to cause a resource change so the activity wasn't destroyed. - // In this case we still want to change the configuration of the activity but not - // report it to the app. - if ((~activity.mActivityInfo.getRealConfigChanged() & diff) == 0 - || !reportToActivity) { - shouldChangeConfig = true; - } + shouldChangeConfig = true; } }