| 
				
					
						 | 
			||
|---|---|---|
| .. | ||
| apex | ||
| build | ||
| common | ||
| guest | ||
| host | ||
| recovery | ||
| shared | ||
| tests | ||
| tools | ||
| vsoc_arm64 | ||
| vsoc_arm64_only | ||
| vsoc_arm_only | ||
| vsoc_x86 | ||
| vsoc_x86_64 | ||
| vsoc_x86_64_only | ||
| vsoc_x86_only | ||
| .clang-format | ||
| Android.bp | ||
| Android.mk | ||
| AndroidProducts.mk | ||
| CleanSpec.mk | ||
| METADATA | ||
| OWNERS | ||
| PREUPLOAD.cfg | ||
| README.md | ||
| TEST_MAPPING | ||
| default-permissions.xml | ||
| dtb.img | ||
| fetcher.mk | ||
| host_package.mk | ||
| iwyu.imp | ||
| multiarch-howto.md | ||
| required_images | ||
| rustfmt.toml | ||
		
			
				
				README.md
			
		
		
			
			
		
	
	Cuttlefish Getting Started
Try Cuttlefish
- 
Make sure virtualization with KVM is available.
grep -c -w "vmx\|svm" /proc/cpuinfoThis should return a non-zero value. If running on a cloud machine, this may take cloud-vendor-specific steps to enable. For Google Compute Engine specifically, see the GCE guide.
 
*** promo ARM specific steps:
- When running on an ARM machine, the most direct way is to check
for the existence of 
/dev/kvm. Note that this method can also be used to confirm support of KVM on any environment. - Before proceeding to the next step, please first follow the guide to adjust APT sources.
 
- 
Download, build, and install the host debian package:
sudo apt install -y git devscripts config-package-dev debhelper-compat golang git clone https://github.com/google/android-cuttlefish cd android-cuttlefish debuild -i -us -uc -b -d sudo dpkg -i ../cuttlefish-common_*_*64.deb || sudo apt-get install -f sudo usermod -aG kvm,cvdnetwork,render $USER sudo rebootThe reboot will trigger installing additional kernel modules and applying udev rules.
 - 
Go to http://ci.android.com/
 - 
Enter a branch name. Start with
aosp-masterif you don't know what you're looking for - 
Navigate to
aosp_cf_x86_64_phoneand click onuserdebugfor the latest build 
*** promo
For ARM, use branch aosp-master-throttled-copped and device target aosp_cf_arm64_only_phone-userdebug
- 
Click on
Artifacts - 
Scroll down to the OTA images. These packages look like
aosp_cf_x86_64_phone-img-xxxxxx.zip-- it will always haveimgin the name. Download this file - 
Scroll down to
cvd-host_package.tar.gz. You should always download a host package from the same build as your images. - 
On your local system, combine the packages:
mkdir cf cd cf tar xvf /path/to/cvd-host_package.tar.gz unzip /path/to/aosp_cf_x86_64_phone-img-xxxxxx.zip - 
Launch cuttlefish with:
 
$ HOME=$PWD ./bin/launch_cvd
Debug Cuttlefish
You can use adb to debug it, just like a physical device:
$ ./bin/adb -e shell
Launch Viewer (WebRTC)
When launching with ---start_webrtc (the default), you can see a list of all
available devices at https://localhost:8443 . For more information, see the
WebRTC on Cuttlefish
documentation.
Stop Cuttlefish
You will need to stop the virtual device within the same directory as you used to launch the device.
`$ HOME=$PWD ./bin/stop_cvd`