Obsolete
Status Update
No update yet.
Comments
ap...@google.com
The traces that are generated are correctly being parsed by
Attached is an example trace.
cc...@google.com
That file works for me as well, something is different about the ones I captured (likely device on which it was captured). Filed
@Leland - you should be able to workaround not getting usable macro traces by either trying a different device/OS image, or viewing the traces in
cc...@google.com
Reassigning to the default assignee given it looks like a Studio issue. Will wait for activity on the blocking bug.
Description
This may be because trace is dropping content near the beginning, which is generally more likely to jank. Will see if periodic write to disk fixes this.
Some of this (on more recent platforms) could also be that dumpsys metrics do account for GPU time on recent platform versions, and our metrics don't (for consistency across platform versions, as old platforms don't trace that).