Google Git
Sign in
android / device / google / cuttlefish / 2b04f5db8
commit2b04f5db8653d2cdbfab5c0658090cee89b10d5b[log] [tgz]
authorJooyung Han <jooyung@google.com>Tue Nov 29 16:44:20 2022 +0900
committerJooyung Han <jooyung@google.com>Tue Nov 29 16:53:27 2022 +0900
tree37400b9a20695e8e274c275ad82c5deb564b8557
parentc10dab79ac5cab97a2bfb5b6ba224e0733bfed0f [diff]
Allow camera hal to read apex-info-list.xml

When the hal is in APEX, it monitors apex-info-list.xml to restart
itself.

11-29 07:14:49.034   510   510 I android.hardware.pixel.camera.provider@2.7-service: Google camera provider service is starting.
11-29 07:14:49.036   510   510 E apex_update_listener: Failed to inotify_add_watch(/apex/apex-info-list.xml): Permission denied (13)

Until now, access error has been ignored since updating the apex on
cuttlefish doesn't make sense.

But we'd better make the hal behave the same way even on cuttlefish so
that we can test updates as well.

However, the camera hal monitors a hard-coded apex name which differs
from the AOSP camera hal apex. This will be handled in a follow-up
change.

Bug: n/a
Test: launch_cvd (no errors from apex_update_listener)
Change-Id: I4eaeb75b75bd5d143366f78050dd07b888f351b5
1 file changed
tree: 37400b9a20695e8e274c275ad82c5deb564b8557
  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. rustfmt.toml ⇨ ../../../build/soong/scripts/rustfmt.toml
  18. .clang-format
  19. Android.bp
  20. Android.mk
  21. AndroidProducts.mk
  22. CleanSpec.mk
  23. default-permissions.xml
  24. dtb.img
  25. fetcher.mk
  26. host_package.mk
  27. iwyu.imp
  28. METADATA
  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.

  1. Download, build, and install the host debian packages:

    sudo apt install -y git devscripts config-package-dev debhelper-compat golang curl
git clone https://github.com/google/android-cuttlefish
cd android-cuttlefish
for dir in base frontend; do
  cd $dir
  debuild -i -us -uc -b -d
  cd ..
done
sudo dpkg -i ./cuttlefish-base_*_*64.deb || sudo apt-get install -f
sudo dpkg -i ./cuttlefish-user_*_*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