aml_swc_331318000 (9349189,com.google.android.media.swcodec)
Snap for 8838244 from 782c1214315394f4eada0032db70be48def14028 to mainline-media-swcodec-release

Change-Id: Idbf7072c6f5f1792ebc51d716d1db73b5a7712a9
tree: 8b051e1052faade9adc1138ad9eef30785386ef0
  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_only/
  17. .clang-format
  18. Android.bp
  19. Android.mk
  20. AndroidProducts.mk
  21. CleanSpec.mk
  22. default-permissions.xml
  23. dtb.img
  24. fetcher.mk
  25. host_package.mk
  26. iwyu.imp
  27. METADATA
  28. multiarch-howto.md
  29. OWNERS
  30. PREUPLOAD.cfg
  31. README.md
  32. required_images
  33. 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 -d
    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`