diff options
| author | Wale Ogunwale <ogunwale@google.com> | 2015-12-14 15:04:22 -0800 |
|---|---|---|
| committer | Wale Ogunwale <ogunwale@google.com> | 2015-12-14 15:04:22 -0800 |
| commit | 14e811f5d99dc5368d9f668382009306f9f5f869 (patch) | |
| tree | be6ff956326ca832e05c87e47e61c2890073ff82 /tools/aapt2/java/JavaClassGenerator_test.cpp | |
| parent | 88b3b57341e03fb4da2a798c547da40f2e1427c8 (diff) | |
Still save config on client side when not reporting to activity.
On the client side we have additional protection not to save new
configuration reported by activity manager if the app isn't handling
any of the configuration change that occurred. This is done because
the activity is expected to relaunch for any configuration it doesn't
handle. However, with multi-window support the activity manager doesn't
relaunch an activity if the configuration change doesn't cross a resource
threshold.
We now save the configuration on the client side when activity manager
tells us not to report the changes to the app (i.e. configuration
changed, but wasn't big enough for relaunch)
Bug: 23904868
Change-Id: I54f65cad65c1b8ed5da1165a8b2816adbea41d4b
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions