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
diff --git a/core/java/android/app/ActivityThread.java b/core/java/android/app/ActivityThread.java
index f7c0b4c..6d805ed 100644
--- a/core/java/android/app/ActivityThread.java
+++ b/core/java/android/app/ActivityThread.java
@@ -4617,16 +4617,7 @@
// 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;
}
}