DO NOT MERGE: OboeTester: Add game mode for testing dynamic workload activity #2137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note that GameMode and GameState are different.
GameMode is the actual performance mode of the game (STANDARD, PERFORMANCE, BATTERY).
GameState takes in at least 2 parameters, isLoading and Mode (GAMEPLAY_INTERRUPTIBLE, GAMEPLAY_UNINTERRUPTIBLE, CONTENT), and is the app specified state and used for system optimization.
GameManager allows apps to set GameState and users to set the GameMode. To set the GameMode, you must switch the game mode manually with the Game Dashboard outside of the game.
It seems like GameMode is an API that allows apps to handle each of the 3 modes (STANDARD, PERFORMANCE, BATTERY) differently.
If audio apps were to use the game mode API, they can consider changing different buffer sizes depending on the mode.