Главная » Android

Google sdk android emulators

Содержание
  1. Android Emulator
  2. In this document
  3. See also
  4. Keyboard Commands
  5. Command Line Parameters
  6. How to install Android SDK and setup AVD Emulator without Android Studio
  7. Understanding the Android SDK
  8. Installing the Android SDK
  9. Step 1 — Download the tools package
  10. Step 2— You need Java 8!
  11. Step 3 — Download the essential packages
  12. Step 4 — Set your environmental variables
  13. Step 5 — Download the platform specific packages you want
  14. Step 5 — Create a AVD device
  15. Step 6 — Run the Android Emulator

Android Emulator

In this document

See also

The Android SDK includes a mobile device emulator — a virtual mobile device that runs on your computer. The emulator lets you develop and test Android applications without using a physical device.

This document is a reference to the available command line options and the keyboard mapping to device keys. For a complete guide to using the Android Emulator, see Using the Android Emulator.

Keyboard Commands

Table 1 summarizes the mappings between the emulator keys and the keys of your keyboard.

Table 1. Emulator keyboard mapping

Emulated Device Key Keyboard Key
Home HOME
Menu (left softkey) F2 or Page-up button
Star (right softkey) Shift-F2 or Page Down
Back ESC
Call/dial button F3
Hangup/end call button F4
Search F5
Power button F7
Audio volume up button KEYPAD_PLUS, Ctrl-F5
Audio volume down button KEYPAD_MINUS, Ctrl-F6
Camera button Ctrl-KEYPAD_5, Ctrl-F3
Switch to previous layout orientation (for example, portrait, landscape) KEYPAD_7, Ctrl-F11
Switch to next layout orientation (for example, portrait, landscape) KEYPAD_9, Ctrl-F12
Toggle cell networking on/off F8
Toggle code profiling F9 (only with -trace startup option)
Toggle fullscreen mode Alt-Enter
Toggle trackball mode F6
Enter trackball mode temporarily (while key is pressed) Delete
DPad left/up/right/down KEYPAD_4/8/6/2
DPad center click KEYPAD_5
Onion alpha increase/decrease KEYPAD_MULTIPLY(*) / KEYPAD_DIVIDE(/)

Command Line Parameters

The emulator supports a variety of options that you can specify when launching the emulator, to control its appearance or behavior. Here’s the command-line syntax of the options available to the emulator program:

Table 2. Emulator command line parameters

-datadir

—> -image

—>

-system

—>

-mic

—>

Important: When using this option, make sure it is the last option specified, since all options after it are interpretted as qemu-specific options.

Источник

How to install Android SDK and setup AVD Emulator without Android Studio

If you are trying to develop to Android, you probably will end up installing the Android Studio to get the Android SDK and the AVD Emulator working properly.

But if you are using another code editor, like Sublime Text or VSCode, installing the Android Studio will just mess up with your setup and consume your precious RAM for no good reason.

I had a hard time figuring out how to properly do this setup due the lack of documentation about it, so i hope this article helps you. 🙂

Recommended previous knowledge:

  • SDK (Standard Development Kit); Read about on Wikipedia;
  • AVD (Android Virtual Device); Read about on docs;
  • CLI (Command Line Interface); Read about on Wikipedia;
  • Android API levels; Read about on Vanderbilt University;
  • How to open, navigate and execute files in your OS terminal;
  • Know what are environmental variables;

Understanding the Android SDK

Basically, the Android SDK is a bunch of packages necessary to develop for Android.

These packages stays in subfolders of a folder called “sdk” (or “android-sdk” sometimes). You do not need to know how these packages really work, just what they do.

The picture below is my Android SDK folder, these are the basic packages you will need in order to get everything working properly.

Here is a brief explanation of each package:

  • tools: This package is mainly used to manage the other packages and to create AVD’s;
  • emulator: As the name suggest, this is the Android emulator;
  • platform-tools: Some tools to communicate with Android devices when you plug then in your computer;
  • patcher: This package is automatically downloaded by the SDK. I didn’t find what exactly this is for, so just leave it as it is;

The folders bellow contain sub-folders with the packages for each Android API level.

  • platforms: The platform packages are required to compile your app for the specified API level.
  • system-images: These are the android images used in the emulator.
  • build-tools: These are necessary to build your Android apps

Installing the Android SDK

In order to install the SDK we will use the Command Line Tools. These are some quite simple CLI’s used to manage the Android SDK. You can read the documentation here for more details.

Step 1 — Download the tools package

First, you need to download the tools package. And with this package you can download the others.

  1. First, go to the Android Studio download page: https://developer.android.com/studio;
  2. Then click in “ Download Options”;
  3. There you will find a table named “ Command line tools only”;
  4. This table contain some zip files. Download the appropriate file for your system ( Windows, Mac or Linux);
  5. Extract this zip and you will get a folder called tools: This is the tools package i explained earlier;

Create a folder anywhere you prefer to place your SDK. I recommend you to stick with one of these commonly used places:

  • Globally: C:\Android\sdk or C:\android-sdk (this is not default, but i usually set my SDK here on Windows)
  • One user only: C:\Users\ \AppData\Local\Android\sdk
  • Globally: /Library/Android/sdk
  • One user only: /Users/ /Library/Android/sdk

And move the tools folder to this new sdk folder. Make sure you have admin access to this folder and any sub-folders inside it, or the tools package will fail to download new packages.

Note: You can also download a pre-build package for your SO (like the one available on Ubuntu repository). But i do not recommend you do to so, because they probably will not be updated and will be harder to manage, since it was automatically installed.

Step 2— You need Java 8!

The Android SDK packages require Java 8. If you do not have it, you need to download. If you are using a newer version, you have to downgrade to Java 8 or you will eventually get some errors, because it is not compatible.

If you do not have the Java 8 SDK, here is how you can install it:

On Ubuntu run these commands:

  • # sudo apt-get update
  • # sudo apt-get install openjdk-8-jdk

Sorry for MacOS users, i don’t know how to install it on this OS.

Step 3 — Download the essential packages

Now, download the platform-tools and the emulator packages, because they contain some CLI binary files you will need later. I decided to download these packages first in order to set all the necessary environment variables at once and make the rest of the process easier.

Open a terminal window (you need to use a terminal, not the file explorer), go to your sdk folder and navigate to the /tools/bin directory.

This folder contain the SDKManager binary: this is a CLI used to list the available packages in the Google’s repository and download, update or remove them from your SDK folder.

The bellow command will list all packages installed (the first items on the list) and all packages available to download:

To download the packages, simply copy the package names and pass it as a parameter to the SDKManager CLI using the terminal:

# ./sdkmanager platform-tools emulator

If you open your sdk folder you should see these packages folders there.

Step 4 — Set your environmental variables

You need to set the below environmental variables containing the path to our SDK, so any running program can find it in your pc:

ANDROID_SDK_ROOT = Path to your SDK folder

ANDROID_HOME = The same as ANDROID_SDK_ROOT. This variable is now deprecated, but i recommend setting it because some programs still using it to locate your sdk.

And add these folders to the PATH variable, making their binary files accessible from everywhere:

To add the environment variables on WIndows, just follow these steps:

  1. Open the “Control Panel”;
  2. Go to “ System and Security” option in the side menu;
  3. In the window “ System Properties” open the tab “ Advanced”;
  4. Click in the button “ Environment Variables” in the bottom of the page;
  5. In the “ Environment Variables” window you will see two tables: “User Variables” and ” System Variables”.
  6. If you created your sdk folder for one user only, set the variables in the “ User Variables” table;
  7. But, if you create your sdk folder globally, set the variables in the “ System Variables” table instead;

On Linux, you can set your environment variables in many places. So i choose the ones I found the most appropriate:

    If you created your sdk folder for one user only, set your environment variables in the file

/.bashrc;

  • If you created your sdk folder globally, set your environment variables in the /etc/environment file. But, be very careful! if you do something wrong with the path variable in this file you will broke your system (yes, i did this). This file is not a script, so you can’t use variables like $HOME, you need to write the full path to the folders. Variables declared in this file just will take effect after you logout .

    • Here is how i set these variables in my Ubuntu, using the file /etc/environment:

    And sorry again, no MacOS instructions for this task.

    You can find more about these environmental variables in the oficial docs here.

    Now your SDK is ready! If you do not need to run the emulator there’s no need to follow the next steps.

    Step 5 — Download the platform specific packages you want

    You need more three packages: The platform, the system-image and the build-tools. You can download these packages for any Android version you prefer. In this article, i will download the packages for the API Level 28.

    Use the “ sdkmanager — list” command to find these packages and download them using the command “ sdkmanager

    Here’s an example:

    Step 5 — Create a AVD device

    Creating a AVD device is a simple task: run the AVDManager command (this is a binary file located in the tools/bin folder of your sdk) with the create avd option, a name for the new AVD and the image you want to use.

    Here is a example:

    # avdmanager create avd — name android28 — package “system-images;android-28;default;x86”

    You will be asked if you want to alter some configurations. You can also modify these configurations later in the file config.ini, located in the avd folder (this folder usually is created in your user folder, under the android directory). The currently active configurations can be find in the file hardware-qemu.ini (this file just will be created after the emulator runs for the first time).

    Step 6 — Run the Android Emulator

    Now you just need to run the emulator command (remember that we added this package to the environmental variables?):

    The emulator take some time to init for the first time. But if you done everything correctly you should see this screen:

    Источник

    Читайте также:  Универсальные драйвера для всех андроидов
    Оцените статью
    © 2024 Ваши гэджеты
    Category Option Description Comments
    AVD -avd or
    @     		Required. Specifies the AVD to load for this emulator instance. You must create an AVD configuration before launching the emulator. For information, see Managing AVDs with AVD Manager.
    Disk Images -cache Use as the working cache partition image. An absolute or relative path to the current working directory. If no cache file is specified, the emulator’s default behavior is to use a temporary file instead.

    For more information on disk images, use -help-disk-images .

    -data Use as the working user-data disk image. Optionally, you can specify a path relative to the current working directory. If -data is not used, the emulator looks for a file named userdata-qemu.img in the storage area of the AVD being used (see -avd ).
    Search for the user-data disk image specified in -data in is a path relative to the current working directory.

    If you do not specify -datadir , the emulator looks for the user-data image in the storage area of the AVD being used (see -avd )

    For more information on disk images, use -help-disk-images .

    Use as the system image. Optionally, you can specify a path relative to the current working directory. Default is /system.img.
    -initdata When resetting the user-data image (through -wipe-data ), copy the contents of this file to the new user-data disk image. By default, the emulator copies the /userdata.img . Optionally, you can specify a path relative to the current working directory. See also -wipe-data .

    For more information on disk images, use -help-disk-images .

    -nocache Start the emulator without a cache partition. See also -cache .
    -ramdisk Use as the ramdisk image. Default value is /ramdisk.img .

    Optionally, you can specify a path relative to the current working directory. For more information on disk images, use -help-disk-images .

    -sdcard Use as the SD card image. Default value is /sdcard.img .

    Optionally, you can specify a path relative to the current working directory. For more information on disk images, use -help-disk-images .

    Search for system, ramdisk and user data images in . is a directory path relative to the current working directory.
    -wipe-data Reset the current user-data disk image (that is, the file specified by -datadir and -data , or the default file). The emulator deletes all data from the user data image file, then copies the contents of the file at -inidata data to the image file before starting. See also -initdata .

    For more information on disk images, use -help-disk-images .

    Debug -debug Enable/disable debug messages for the specified debug tags. is a space/comma/column-separated list of debug component names. Use -help-debug-tags to print a list of debug component names that you can use.
    -debug- Enable/disable debug messages for the specified debug tag. Use -help-debug-tags to print a list of debug component names that you can use in .
    -debug-no- Disable debug messages for the specified debug tag.
    -logcat Enable logcat output with given tags. If the environment variable ANDROID_LOG_TAGS is defined and not empty, its value will be used to enable logcat output by default.
    -shell Create a root shell console on the current terminal. You can use this command even if the adb daemon in the emulated system is broken. Pressing Ctrl-c from the shell stops the emulator instead of the shell.
    -shell-serial Enable the root shell (as in -shell and specify the QEMU character device to use for communication with the shell. must be a QEMU device type. See the documentation for ‘-serial dev‘ at http://wiki.qemu.org/download/qemu-doc.html for a list of device types.

    Here are some examples:

    • -shell-serial stdio is identical to -shell
    • -shell-serial tcp::4444,server,nowait lets you communicate with the shell over TCP port 4444
    • -shell-serial fdpair:3:6 lets a parent process communicate with the shell using fds 3 (in) and 6 (out)
    • -shell-serial fdpair:0:1 uses the normal stdin and stdout fds, except that QEMU won’t tty-cook the data.
    -show-kernel Display kernel messages.
    -trace Enable code profiling (press F9 to start), written to a specified file.
    -verbose Enable verbose output. Equivalent to -debug-init .

    You can define the default verbose output options used by emulator instances in the Android environment variable ANDROID_VERBOSE. Define the options you want to use in a comma-delimited list, specifying only the stem of each option: -debug- .

    Here’s an example showing ANDROID_VERBOSE defined with the -debug-init and -debug-modem options:

    For more information about debug tags, use .

    Media -audio Use the specified audio backend.
    -audio-in Use the specified audio-input backend.
    -audio-out Use the specified audio-output backend.
    Use device or WAV file for audio input.
    -noaudio Disable audio support in the current emulator instance.
    -radio Redirect radio modem interface to a host character device.
    -useaudio Enable audio support in the current emulator instance. Enabled by default.
    Network -dns-server Use the specified DNS server(s). The value of must be a comma-separated list of up to 4 DNS server names or IP addresses.
    -http-proxy

    		Make all TCP connections through a specified HTTP/HTTPS proxy The value of

    can be one of the following:
    http:// :

    The http:// prefix can be omitted. If the -http-proxy

    command is not supplied, the emulator looks up the http_proxy environment variable and automatically uses any value matching the

    format described above.

    -netdelay Set network latency emulation to . Default value is none . See the table in Network Delay Emulation for supported values.
    -netfast Shortcut for -netspeed full -netdelay none
    -netspeed Set network speed emulation to . Default value is full . See the table in Network Speed Emulation for supported values.
    -port

    		Set the console port number for this emulator instance to

    .

    		 The console port number must be an even integer between 5554 and 5584, inclusive.

    +1 must also be free and will be reserved for ADB.
    -report-console Report the assigned console port for this emulator instance to a remote third party before starting the emulation. must use one of these formats:

    to view more information about this topic.
    System -cpu-delay Slow down emulated CPU speed by Supported values for are integers between 0 and 1000.

    Note that the does not correlate to clock speed or other absolute metrics — it simply represents an abstract, relative delay factor applied non-deterministically in the emulator. Effective performance does not always scale in direct relationship with values.

    -gps Redirect NMEA GPS to character device. Use this command to emulate an NMEA-compatible GPS unit connected to an external character device or socket. The format of must be QEMU-specific serial device specification. See the documentation for ‘serial -dev’ at http://wiki.qemu.org/download/qemu-doc.html.
    -nojni Disable JNI checks in the Dalvik runtime.
    -qemu Pass arguments to the qemu emulator software.