Google Git
Sign in
android / device / google / cuttlefish / c9f48152e29a051d3fd22d9f3b0e8400197bfa2f
commitc9f48152e29a051d3fd22d9f3b0e8400197bfa2f[log] [tgz]
authorAlistair Delva <[email protected]>Sun Jan 23 16:39:27 2022 -0800
committerAlistair Delva <[email protected]>Mon Jan 31 14:36:20 2022 -0800
treef12b87e3fbea23acb887a26ba82e3165e6b7242a
parente87852178a4ac2db1c3540eda506f0c0b24701d4 [diff]
Re-add aosp_cf_x86_wear

Add build support for a generic wearable device. This is loosely modeled
after the Galaxy Watch 4.

This build just mimics the generic_system.mk split, but cuts away
anything not needed for wear. Some basic, non-representative overlays
are also added.

Bug: 216825898
Change-Id: I4eba8faff9a41a7369719b4e43a95cd5a859ebba
23 files changed
tree: f12b87e3fbea23acb887a26ba82e3165e6b7242a
  1. apex/
  2. build/
  3. common/
  4. guest/
  5. host/
  6. recovery/
  7. shared/
  8. tests/
  9. tools/
  10. vsoc_arm64/
  11. vsoc_arm64_only/
  12. vsoc_arm_only/
  13. vsoc_x86/
  14. vsoc_x86_64/
  15. vsoc_x86_64_only/
  16. vsoc_x86_noapex/
  17. vsoc_x86_only/
  18. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  19. .clang-format
  20. Android.bp
  21. Android.mk
  22. AndroidProducts.mk
  23. CleanSpec.mk
  24. default-permissions.xml
  25. dtb.img
  26. fetcher.mk
  27. host_package.mk
  28. METADATA
  29. multiarch-howto.md
  30. OWNERS
  31. PREUPLOAD.cfg
  32. README.md
  33. required_images
  34. tags
  35. TEST_MAPPING
README.md

Cuttlefish Getting Started

Try Cuttlefish

  1. Make sure virtualization with KVM is available.

    grep -c -w "vmx\|svm" /proc/cpuinfo

    This 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.

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.

  1. 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
sudo dpkg -i ../cuttlefish-common_*_*64.deb || sudo apt-get install -f
sudo usermod -aG kvm,cvdnetwork,render $USER
sudo reboot

    The reboot will trigger installing additional kernel modules and applying udev rules.

  2. Go to http://ci.android.com/

  3. Enter a branch name. Start with aosp-master if you don‘t know what you’re looking for

  4. Navigate to aosp_cf_x86_64_phone and click on userdebug for the latest build

For ARM, use branch aosp-master-throttled-copped and device target aosp_cf_arm64_only_phone-userdebug

  1. Click on Artifacts

  2. Scroll down to the OTA images. These packages look like aosp_cf_x86_64_phone-img-xxxxxx.zip -- it will always have img in the name. Download this file

  3. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.

  4. 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

  5. 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`