Advanced Usages

Emulator Configurations

Currently, Trinity sets up a 4-core virtual CPU, 4 GB memory, 64 GB storage and 1920x1080 display. These configurations conform to that tested in our paper. However, for the guest apps, we mask ourselves as Samsung Galaxy S20 Ultra 5G (a high-end Android device) in terms of CPU, GPU, and vendor information so as to unlock certain app features reserved for high-end mobile phones only (e.g., high-quality graphics).

ADB Connection

1. To establish an ADB connection with Trinity, make sure Trinity's WiFi has been turned on and connected first.

   

2. In a terminal, type adb connect 127.0.0.1:5555. Of course, you need an adb in your PATH, see here.

3. If prompt: connected to 127.0.0.1:5555, you are connected. Else, retry step 2.

Change Screen Resolution

1. If you haven't installed Trinity on disk following the guide, you can change the resolution as follows.

• Upon entering the grub, press the $Tab$ key as instructed on the grub UI.

  

• You can see the video configuration "video=1920x1080" in the boot parameters.

  

• Change it to any resolution you want. For example, you can change it to a vertical 9:16 resolution as follows:

  

2. If you already install Triniy on disk, you can change the resolution in the same way as VMware Workstation following the guide here.

Shutdown and Force Shutdown

1. For normal shutdown, click the upper-right close button. And then click the Power off button here.

   

2. If Trinity unfortunately freezes, you can quickly click the close button several times to force a shutdown. Freezing has been observed on certain machines during their first boot of Trinity without the installation of the Guest OS. A shutdown and reboot can solve this. We have located the bug behind this and are working to fix it.

Formatting the Disk

Resolving Persistent Issues After Installation

If you find that even a reboot cannot resolve some of the issues, particularly after you have installed the guest OS images, you can try the last resort that almost guarantees to solve any problems---erase the disk and start over. To this end, start a terminal and cd to the directory of your hda.img file, and type .\x86_64-softmmu\qemu-img create -f qcow2 hda.img 64G. A fresh start!