Google Git
Sign in
android / device / google / cuttlefish / 08377b979
commit08377b9790e131acc6ff614b8ee57a6e8c47e5ae[log] [tgz]
authorSergio Andres Rodriguez Orama <sorama@google.com>Wed Dec 01 13:12:38 2021 -0500
committerSergio Andres Rodriguez Orama <sorama@google.com>Wed Dec 01 13:21:47 2021 -0500
treedd4c6de3c45fd4565422bb230f883b4885eeccf6
parentc6a4797c1b052e039060de76c7209d608aa13a5d [diff]
Remove logic that randomly changes(-1, 0, +1) the current signal strength parameter in favor of coming logic tracked in b/207022371.

- This logic only gets executed when CSQ commands are issued from the RIL being a reactive approach, b/207022371 aims to have a proactive approach towards signal strength simulation.

Bug: 207022371
Test: modem_simulator_test
Change-Id: I69b33e4b95c2ea9208460b14d7d732e16830d486
2 files changed
tree: dd4c6de3c45fd4565422bb230f883b4885eeccf6
  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
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 $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

  5. Click on Artifacts

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

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

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

  9. Launch cuttlefish with:

$ HOME=$PWD ./bin/launch_cvd

  1. Stop cuttlefish with:

$ HOME=$PWD ./bin/stop_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.