For now, the only supported way to capture TTD traces is via WinDbg Preview. If you have additional scenarios you would like us to support, the team is recommending you submit feature requests via the Feedback Hub.
@AndreyBazhan: As I alluded to in the video, we've had this technology available in internal Microsoft builds of the debugger for some time. We are making it public for the first time in WinDbg Preview.
@bgilly: Please see the followup episode we did recently on System Power Report, in which we discuss what causes energy usage to be categorized as "unknown." Specifically, this question was addressed at around 9:40.
@OzBobWa: I don't know if we want to delve into that argument, it's not really within the scope of our show. But I would mention a few things:
* After doing the battery rundown tests, in addition to just seeing how long it ran until the battery died, it would be more scientific to look at the System Power Report to make sure there weren't other background processes contributing too much to the battery usage.
* To get even more scientifically accurate results from the report, it'd be best to use systems which have integrated power metering chips (we talked about this in more detail in our earlier episode on Energy Estimation Engine). Unfortunately, most devices on the market do not have these.
* As there is video playback involved, the results may vary significantly across different hardware because hardware offload for GPU and audio may be a factor.
* As mentioned in this episode, screen brightness is a big factor. I don't know if these other people who did these tests were forcing a consistent screen brightness across all of their tests. If not, their results could be misleading.