So in the right hand side, we have also an option to upload or open the trace files.
So in the real world scenario, when a test to test a particular bug, he or she can enable the traces
you either using the ADB shell or by using the tiles option.
And then from there you can extract these traces and give it to the developer.
So in that case, the developer already has these traces and he can simply go and add it, select the
file and upload it, and you'll get a similar visualization.
I will quickly show you how to do that.
You can find all this information in source dot android dotcom under tracing window transitions.
So here the first step is basically to enable the tiles option.
So here within the emulator at the top, these tiles, right.
So you can bring the trace here.
So to do that, we should go to settings and system developer option settings, developer tiles.
So here, just go there and then you can simply enable the mean scope trace.
So once we enable it, then we can start the trace right from here.
So in scope trace.
So this will start the tracing.
So this is an easy way for the developers to start the trace so they can simply keep this on all the
time and simulate the bugs and they get the trace.
And you can just use the ADB shell to export the trace and give it to the developer or the concerned
person.
Okay.
And here we can see the commands to manually start the tracing.
Stop the tracing.
So for example, to start the trace, it's copy this.
So in the emulator I could simply start this like ADB shell cmd window start tracing window trace tracing
start.
And this has started the tracing now.
So that race will be stored with this name under this path.
And now I could stop it.
Stop.
So now it stopped and the trace is written here.
So from here you can pull it by using ADB pull command.
So now you can see the file is already pulled and this should be there in the home part.
So we have the file over here.
So now let's go to the wind scope.
So in the wind scope, I could simply come here and click on the ad and then select the trace file,
which I have now exported.
Just click on and submit it.
So now I have the same visualization.
So this is kind of dump dumping the current state.
So if I have done multiple operations in the emulator after starting the trace, then I would have the
timeline at the bottom.
But in this case, I haven't done anything on the emulator.
So that's why we only have the current dump state and it's showing the launcher because I haven't opened
any apps, so that's where it's showing the launcher.
So, so we have basically two ways.
So through ADB, so this is the quickest way and this is mostly helpful when the developer is able to
simulate the issue, then we could simply connect the emulator or the device through this proxy to in
scope and we could sort out the issue.
And in the other case, the open file.
Once we get the trace files from the testing team or a client, then we could use that file and open
it up in window scope and check the state of windows and we could figure out when and how the issue
has happened.