Issue metadata
Sign in to add a comment
|
Nexus 5X power.idle_platform shows strange power spike at the beginning of the trace |
||||||||||||||||||||
Issue descriptionFor some reason, the power is always much higher at the beginning of the power.idle_platform stories than at the end. The length of this high-power period seems to vary from story to story. This variation is a source of noise in the Android power benchmarks. It seems that many systrace events during this period are things like "MicrophoneReader", "MicroRecognition", and "AudioIn_52". This seems to happen in every trace. Here are a few examples: https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_0-2017-06-02_05-23-50-58957.html https://console.developers.google.com/m/cloudstorage/b/chrome-telemetry-output/o/trace-file-id_2-2017-06-02_05-24-06-68069.html These events continue for a while after Telemetry's RunStory method begins. I vaguely remember a conversation about "Okay Google" detection being a source of noise in the lab. sullivan@, rnephew@, nednguyen@: do any of you know what might be going on here?
,
Jun 2 2017
I'm interested not just in how to stop the background process, but what we might be doing differently than users that's causing the background process to trigger in the first place. I'd prefer to do the latter, but will settle for the former if it's something that's a really hairy problem.
,
Jun 4 2017
I'm wondering if its the screen turning off... we disable charging so if there is no interaction with the phone, the screen will turn off. Is there a way to look for that in the atrace data?
,
Jun 6 2017
The NextAction date has arrived: 2017-06-06
,
Jun 7 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by nedngu...@google.com
, Jun 2 2017