| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Q: is the playback loop by default? |
Sorry, something went wrong.
|
@flamme yes, we can maybe also add a loop button to the player controls to control this better. |
Sorry, something went wrong.
| val durationMs = IntentBasedTestSupport.getDurationMs(extras) | ||
| val useMMap = IntentBasedTestSupport.getMMapEnabled(extras, player.isMMapEnabled()) | ||
| val bufferFrames = IntentBasedTestSupport.getBufferFrames(extras) | ||
| val toggleOffload = IntentBasedTestSupport.isToggleOffloadRequested(extras) |
There was a problem hiding this comment.
Q: shouldn't offload or not be decided by the performance mode? Why it is needed to have another toggle for offload?
Sorry, something went wrong.
There was a problem hiding this comment.
Removed the toggle based intents
Sorry, something went wrong.
# Conflicts: # samples/powerplay/src/main/kotlin/com/google/oboe/samples/powerplay/MainActivity.kt
| Back | FazBrowse Home | New Git URL |
Description: Intent-based Automation and Stress-Testing for PowerPlay
Summary
This PR implements a robust command-line interface for the PowerPlay sample app via Android Intents. This enables full control of the audio engine via adb, facilitating automated power profiling, stress testing, and validation of PCM Offload behavior without manual UI interaction.
Changes
Supported ADB Parameters
How to Test
You can verify the automation by running the following command to start a timed, background offload session:
adb shell am start -n com.google.oboe.samples.powerplay/.MainActivity \ --es command play \ --es perf_mode offload \ --ez background true \ --ei duration_ms 10000