Our wiki serves to provide guidance on advanced configurations and usages of Trinity, as well as reproducing the evaluation experiments dicussed in Trinity's paper. In detail, we focus on the following topics.

The installation process of Trinity's Guest OS is the same as that of installing Android-x86 on QEMU. Our guide here aims to simplify the official document of Android-x86 to avoid some unnecessary setups.

This part of wiki gives instructions on advanced usages (e.g., adb connections) that you may find useful for debugging and resolving issues.

While being a functional product, Trinity is also an academic project. Therefore, it's essential for readers of our paper to be able to reproduce our claimed results. To this end, this part of the wiki focuses on guiding interested readers to 1) generate our papers' figures with our measurement data, and 2) conduct the major experiments performed in our study. You can find them below.

This page demonstrates how to generate our major figures in our paper and provides our raw evaluation data and their format explanations.

To conduct our experiments independently, you need to understand the setup of all the other evaluated emulators if you wish to compare Trinity's results with theirs as shown in our study (feel free to skip this step if you want to save the trouble and only evaluate Trinity). We then detail how to conduct the major experiments discussed in Trinity's paper. In particular, we provide short videos to facilitate your understanding of the experiment process if possible.

• Setup of Other Emulators

  This page instructs you to set up other emulators we compare in our work, including DAOW, Bluestacks, VMWare, GAE, WSA, and QEMU-KVM, in case you want to run the experiments on the other emulators to compare the results.

• Graphics Benchmark

  This page guides you to perform the graphics benchmark in our evaluation.

• Heavy 3D Apps

  This page tells you how to measure FPS data on different emulators when running the heavy 3D apps in our evaluation.