Send Emulator console commands

Each running virtual device provides a console that lets you query and control the emulateddevice environment. For example, you can use the console to manage port redirection, network characteristics, and telephony events while your app is running on the emulator.

The following commands require that you already have an emulator running. For more information about running an emulator, see Run Apps on the Android Emulator and Start the Emulator from the Command Line.

Start and stop a console session

To access the console and enter commands, from a terminal window, use telnet toconnect to theconsole port and provide your authentication token. Each time the console displaysOK, it's ready to accept commands. It doesn't have a typical prompt.

To connect to the console of a running virtual device:

• Open a terminal window and enter the following command:

telnet localhost console-port

The emulator window title lists the console port number. For example, the window title for an emulator using console port 5554 could be Nexus_5X_API_23:5554. Also, the adb devices command prints a list of running virtual devices and their console port numbers. For more information, see Querying for Emulator/Device Instances.

Note: The emulator listens for connections on ports 5554 to 5585 and accepts connections from localhost only.

• After the console displays OK, enter the auth
auth_token command.
  Before you can enter console commands, the emulator console requires authentication. auth_token must match the contents of the .emulator_console_auth_token file in your home directory.

If that file doesn't exist, the telnet localhost console-port command creates the file, which contains a randomly generated authentication token. To disable authentication, delete the token from the .emulator_console_auth_token file or create an empty file if it doesn't exist.

• After you're connected to the console, enter console commands.
  Enter help, help command, or help-verbose to see a list of console commands and learn about specific commands.

• To exit the console session, enter quit or exit.
  Here's an example session:

$ telnet localhost 5554
Trying ::1...
telnet: connect to address ::1: Connection refused
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Android Console: Authentication required
Android Console: type 'auth <auth_token>' to authenticate
Android Console: you can find your <auth_token> in
'/Users/me/.emulator_console_auth_token'
OK
auth 123456789ABCdefZ
Android Console: type 'help' for a list of commands
OK
help-verbose
Android console command help:
 
  help|h|?           print a list of commands
    help-verbose     print a list of cmmands with descriptions
    ping             check if the emulator is alive
    event            simulate hardware events
    geo              Geo-location commands
    gsm              GSM related commands
    cdma             CDMA related commands
    crash            crash the emulator instance
    crash-on-exit    simulate crash on exit for the emulator instance
    kill             kill the emulator instance
    network          manage network settings
    power            power related commands
    quit|exit        quit control session
    redir            manage port redirections
    sms              SMS related commands
    avd              control virtual device execution
    sensor           manage emulator sensors
    finger           manage emulator fingerprint
    debug            control the emulator debug output tags
    rotate           rotate the screen by 90 degrees
 
try 'help <command>' for command-specific help
OK
exit
Connection closed by foreign host.

Emulator command reference

The following table describes the emulator console commands with their parameters and values.

Table 1. Emulator console commands

avd snapshot save firstactivitysnapshot

debug radio

geo nmea $GPGGA ,hhmmss.ss,llll.ll,a,yyyyy.yy,a,x,xx,x.x,x.x,M,x.x,M,x.x,xxxx

event send EVPWR EV_SW:SW_LID EV_REL:REL_X

emulator -netdelay gprs
emulator -netdelay 40,100

network delay gprs
network delay 40 100

emulator -netspeed gsm @Pixel_API_26
emulator -netspeed 14.4,80 @Pixel_API_26

network speed 14.4 80

sensor get acceleration
acceleration = 2.23517e-07:9.77631:0.812348

sensor set acceleration 2.23517e-07:9.77631:0.812348

sms send 4085555555 hi there

Fingerprint simulation and validation

Figure 1. Fingerprint authentication screen.

Use the finger command to simulate and validate fingerprint authentication for yourapp. You need SDK Tools 24.3 or higher, and Android 6.0 (API level 23) or higher.

To simulate and validate fingerprint authentication, follow these steps:

• If you don't yet have a fingerprint ID, enroll a new fingerprint in the emulator by selecting Settings > Security > Fingerprint and following the enrollment instructions.
• Set up your app to accept fingerprint authentication. After you perform this setup, your device displays the fingerprint authentication screen.
• While your app displays the fingerprint authentication screen, go to the console and enter the finger touch command and the fingerprint ID you created. This simulates a finger touch.
• Then, enter the finger remove command to simulate finger removal.
  Your app should respond as if a user touched and then removed their finger from the fingerprint sensor.