from web site
You can go back to a saved system state by loading a picture whenever you select, saving you the time of waiting on the operating system and applications on the virtual device to reboot, as well as conserving you the effort of bringing your app back to the state at which you desire to resume your screening.
For each AVD, you can have one Quick Boot photo and any number of basic snapshots. The most basic way to benefit from photos is to utilize Quick Boot snapshots: By default, each AVD is set to automatically conserve a Quick Boot snapshot on exit and load from a Quick Boot photo on start.
If Quick Boot is allowed, all subsequent starts load from the defined snapshot, and the system is restored to the state saved in that picture. Pictures are valid for the system image, AVD setup, and emulator features with which they are saved. When you make a change in any of these locations, all pictures of the affected AVD become void.
A lot of controls for saving, filling, and handling pictures are in the and tabs in the pane in the emulator's Prolonged controls window. You can likewise manage the Quick Boot choices when beginning the emulator from the command line. Conserve Quick Boot snapshots When you close an AVD, you can define whether the emulator automatically conserves a photo when you close.
In the category of controls, browse to the tab. Use the drop-down menu to pick one of the following options:: Always conserve an AVD snapshot when you close the emulator. free roblox is the default. When automated Quick Boot snapshots are made it possible for, you can skip conserving a Quick Boot snapshot by holding the Shift secret down when you close the emulator.
Your choice applies just to the AVD that is presently open. You can not conserve snapshots while ADB is offline (such as while the AVD is still booting). Save basic snapshots Whereas you can only have one Quick Boot picture for each AVD, you can have several basic snapshots for each AVD.