summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Xiang Wang <xwxw@google.com> 2022-10-12 16:48:17 -0700
committer Xiang Wang <xwxw@google.com> 2022-10-25 17:38:10 +0000
commit5abb52c1669a5d582b65f1e6b55d327d21c8fb30 (patch)
treed90cab5830ada078eb6a2738e3497403c34873a5 /libs/androidfw/StringPool.cpp
parent1ddd0c1b959feae702a31c6aeb7645bf682950d5 (diff)
Override config should trigger intervention ignoring opt-in info
In the past we have an inconsistent behavior regarding override config as it will ignore intervention setting such as `mAllowDownscale` but still respect opt-in info as `mPerfModeOptedIn`. This will be confusing and there is no way for OEM or game developers to test new interventions for games without any pre-configured game mode device config. Now they can instead first opt in the game modes temporarily if not pre-configured (to make them available), then apply the override to test. But they should reset the opt-in info and overrides after testing, then communicate the interventions to OEMs. This also fix the bug below where the override config used to contain full information including opt-in info that can be stale. Now it's lightweight as it only contains GameModeConfiguration(s) and will be used together with default config in getConfig call. Bug: b/253102835 Test: atest GameManagerServiceTests Change-Id: Iee14d6eed07b16b6adb86b459edebdeca2b03fbc Merged-In: Iee14d6eed07b16b6adb86b459edebdeca2b03fbc
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions