Mulai 27 Maret 2025, sebaiknya gunakan android-latest-release, bukan aosp-main, untuk mem-build dan berkontribusi pada AOSP. Untuk mengetahui informasi selengkapnya, lihat Perubahan pada AOSP.
Mulai ulang memicu penginstalan modul kernel tambahan dan menerapkan aturan
udev.
Cuttlefish adalah bagian dari Platform Open Source Android (AOSP). Build
perangkat virtual dapat ditemukan di situs Android Continuous Integration. Untuk
menemukan indeks semua build Android, buka situs Android Continuous Integration
di
http://ci.android.com/.
Masukkan nama cabang. Gunakan cabang aosp-android-latest-release default atau
gunakan cabang generic system image (GSI)
seperti aosp-android13-gsi.
Buka target build aosp_cf_x86_64_only_phone, lalu klik
userdebug untuk build terbaru.
Klik kotak hijau di bawah userdebug untuk memilih build ini. Panel Details
akan muncul dengan informasi selengkapnya khusus untuk
build ini. Di panel ini, klik Artefak untuk melihat daftar semua
artefak yang dilampirkan ke build ini.
Di panel Artifacts, download artefak untuk Cuttlefish.
Klik artefak aosp_cf_x86_64_phone-img-xxxxxx.zip untuk x86_64 atau
artefak aosp_cf_arm64_only_phone-xxxxxx.zip untuk ARM64, yang
berisi image perangkat. Dalam nama file, "xxxxxx" adalah ID build
untuk perangkat ini.
Scroll ke bawah di panel dan download cvd-host_package.tar.gz. Selalu download paket host dari build yang sama dengan image Anda.
Di sistem lokal, buat folder penampung dan ekstrak paket:
Di folder yang sama tempat Anda meluncurkan Cuttlefish, jalankan perintah
berikut untuk melihat daftar semua perangkat Android yang tersedia melalui adb di
komputer host Anda:
./bin/adb devices
Melihat dan berinteraksi dengan perangkat virtual di web
Secara default, Cuttlefish diluncurkan dengan --start_webrtc, yang mengaktifkan webview
melalui port 8443 di mesin host.
Untuk melihat dan berinteraksi dengan perangkat virtual, buka
https://localhost:8443 di browser web Anda.
Hentikan perangkat virtual dalam direktori yang sama dengan yang Anda gunakan untuk meluncurkan
perangkat:
HOME=$PWD ./bin/stop_cvd
Konten dan contoh kode di halaman ini tunduk kepada lisensi yang dijelaskan dalam Lisensi Konten. Java dan OpenJDK adalah merek dagang atau merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-27 UTC.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Informasi yang saya butuhkan tidak ada","missingTheInformationINeed","thumb-down"],["Terlalu rumit/langkahnya terlalu banyak","tooComplicatedTooManySteps","thumb-down"],["Sudah usang","outOfDate","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Masalah kode / contoh","samplesCodeIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-07-27 UTC."],[],[],null,["# Get started\n\nThis page describes how to launch an AOSP build using\n[Cuttlefish](/docs/devices/cuttlefish).\n\nVerify KVM availability\n-----------------------\n\nCuttlefish is a virtual device and is dependent on virtualization being\navailable on the host machine.\n\nIn a terminal on your host machine, make sure that virtualization with a\nKernel-based Virtual Machine (KVM) is available: \n\n grep -c -w \"vmx\\|svm\" /proc/cpuinfo\n\nThis command should return a nonzero value.\n| **Note:** On a cloud machine, you might need to follow cloud-specific or vendor-specific steps to enable KVM. For Google Compute Engine (GCE), see [About nested virtualization](https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances).\n\nWhen running on an ARM64 machine, the most direct way is to check for\n`/dev/kvm`: \n\n find /dev -name kvm\n\n| **Tip:** You can use this command to confirm support of KVM on any environment.\n\n*** ** * ** ***\n\nLaunch Cuttlefish\n-----------------\n\n1. In a terminal window, download, build, and install the host Debian packages:\n\n sudo apt install -y git devscripts equivs config-package-dev debhelper-compat golang curl\n git clone https://github.com/google/android-cuttlefish\n cd android-cuttlefish\n tools/buildutils/build_packages.sh\n sudo dpkg -i ./cuttlefish-base_*_*64.deb || sudo apt-get install -f\n sudo dpkg -i ./cuttlefish-user_*_*64.deb || sudo apt-get install -f\n sudo usermod -aG kvm,cvdnetwork,render $USER\n sudo reboot\n\n The reboot triggers installing additional kernel modules and applies `udev`\n rules.\n2. Cuttlefish is part of the Android Open-Source Platform (AOSP). Builds of\n the virtual device are found at the Android Continuous Integration site. To\n find an index of all Android builds, navigate to the Android Continuous\n Integration site at\n \u003chttp://ci.android.com/\u003e.\n\n3. Enter a branch name. Use the default `aosp-android-latest-release` branch or\n use a [generic system image (GSI) branch](/docs/setup/create/gsi#building-gsis)\n such as `aosp-android13-gsi`.\n\n4. Navigate to the **aosp_cf_x86_64_only_phone** build target and click\n **userdebug** for the latest build.\n\n | **Tip:** For ARM64, use the branch `aosp-android-latest-release` and the device target `aosp_cf_arm64_only_phone-userdebug`.\n5. Click the green box below **userdebug** to select this build. A **Details**\n panel appears with more information specific to\n this build. In this panel, click **Artifacts** to see a list of all the\n artifacts attached to this build.\n\n6. In the Artifacts panel, download the artifacts for Cuttlefish.\n\n 1. Click the `aosp_cf_x86_64_phone-img-xxxxxx.zip` artifact for x86_64 or\n the `aosp_cf_arm64_only_phone-xxxxxx.zip` artifact for ARM64, which\n contains the device images. In the filename, \"xxxxxx\" is the build\n ID for this device.\n\n 2. Scroll down in the panel and download `cvd-host_package.tar.gz`. Always\n download the host package from the same build as your images.\n\n7. On your local system, create a container folder and extract the packages:\n\n 1. x86_64 architecture:\n\n mkdir cf\n cd cf\n tar -xvf /path/to/cvd-host_package.tar.gz\n unzip /path/to/aosp_cf_x86_64_phone-img-\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nx\"\u003exxxxxx\u003c/span\u003e\u003c/var\u003e.zip\n\n \u003cbr /\u003e\n\n 2. ARM64 architecture:\n\n mkdir cf\n cd cf\n tar -xvf /path/to/cvd-host_package.tar.gz\n unzip /path/to/aosp_cf_arm64_only_phone-img-\u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-nx\"\u003exxxxxx\u003c/span\u003e\u003c/var\u003e.zip\n\n \u003cbr /\u003e\n\n8. Launch Cuttlefish:\n\n HOME=$PWD ./bin/launch_cvd --daemon\n\nVerify that Cuttlefish is visible through adb\n---------------------------------------------\n\nSimilar to a physical device, Cuttlefish is visible through the\n[Android Debug Bridge (adb)](/docs/setup/build/adb).\n\nIn the same folder where you launched Cuttlefish, run the following\ncommand to see a list of all the Android devices available through adb on your\nhost machine: \n\n ./bin/adb devices\n\nView and interact with the virtual device in the web\n----------------------------------------------------\n\nBy default, Cuttlefish launches with `--start_webrtc`, which enables a webview\nthrough port 8443 on the host machine.\n\nTo view and interact with your virtual devices, navigate to\n**https://localhost:8443** in your web browser.\n\nFor more information, see\n[Cuttlefish: WebRTC Streaming](/docs/devices/cuttlefish/webrtc).\n\nStop Cuttlefish\n---------------\n\nStop the virtual device within the same directory as you used to launch the\ndevice: \n\n HOME=$PWD ./bin/stop_cvd"]]