Status Update
No update yet.
Comments
yd...@google.com
This functionality was released in benchmark 1.2.0-alpha06:
You'll need to use an Android 13 (API 33) emulator, and androidx.benchmark:benchmark-macro-junit4:1.2.0-alpha06, which removes the requirement for root, and thus works on Play emulator images.
tn...@google.com
Thanks! I should have remembered that :-)
Since we're showing a grid of tasks.... I wonder if we can/should in fact list separate tasks even if they use the same tool! For example, two separate tasks are:
- Reduce UI Jank
- Improve Battery
Both of these would lead to the systrace tool (maybe even initialized to highlight different things?).
Not anything to act on right now for Koala, but figured I'd raise it -- we need to decide whether this is really showing tasks or showing tools :-)
yd...@google.com
No worries, it is a valid point and I am happy to say that we agree--that is actually one of the next steps in our product roadmap! First we wanted to accomplish feature parity, making the transition seamless to existing users (what we are releasing in Koala). Then, divide the existing tasks/tools into more focused and use-case specific tasks; one example being the "improve battery" task that would essentially be the more battery-focused subset of the existing system trace.
yd...@google.com
Burak and Mayank, is there any tooltip text we might want to add, or any other UI to indicate that the system trace contains power/battery data in the meantime?
yd...@google.com
ne...@google.com
It would be quite good to be able to focus on different parts of a tool (such as different focus sets of the systrace, even if it means just scrolling to the right place in the tool for now), IIUC that feature is not yet built. As Yasser mentioned, we were hoping to get to a place where we can actually fully split it out to separate tasks instead.
As for the question in #5, I'm not sure if copy is the best way to solve it since systrace includes the power profiler but also a plethora of other things that would presumably also merit inclusion in the updated title. It might rather make more sense to use the effort to split off power profiler by creating a configuration of systrace that only has the power data and other relevant parts to do power profiling and have it be the separate task. I don't know what the priority on that effort would be compared to other efforts we currently have though, that's more a question for Mayank. @Mayank wdyt?
Description
This could very well be user error -- but I'm filing it as a usability problem :-) I was expecting to find something like "Save Battery (Power profiler)" in the task oriented profiler UI. I thought maybe it was because I wasn't looking at a wear app -- so I switched to that -- I'm running a wear app, I've selected it in the profiler process chooser, the current runconfig is a wear app, etc -- but I still don't see it.
I think maybe the profiler is only available if the hardware has the extra sensor needed for this -- but I think it would be useful if we still showed the task there and instead indicated that it's not supported on this type of device (maybe with a link to a place they can find out which devices are supported/required to do this analysis.)