commit | aa3f38147fa33a8f25821e54988d05466459739f | [log] [tgz] |
---|---|---|
author | Enrico Granata <egranata@google.com> | Thu Jul 21 14:04:26 2022 -0600 |
committer | Enrico Granata <egranata@google.com> | Thu Jul 21 14:07:33 2022 -0600 |
tree | 2fecb5b9d308762e618a038bfdc93d8a27ca4af1 | |
parent | c5633681d0cf0c3e1e6d0e8f709a42ddd08fcb60 [diff] |
Move Audio Effects HAL into its own manifest chunk Some downstream devices use Audio HAL v6, but because cuttlefish's manifest hardcodes Audio Effects v7, audioflinger cannot start the primary audio library because it detects a mismatch of versions In the longer run, an architecture where all cuttlefish and derived devices use the same Audio HAL may be optimal, but for this release move the effects HAL manifest into its own fragment that is only built when no custom audio packages are selected at build time Bug: 239744244 Test: build and boot trout, hear audio working Change-Id: I841989d7b5d76ccbaf9c864b4002c32062c23c39
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:
/dev/kvm
. Note that this method can also be used to confirm support of KVM on any environment.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.
Go to http://ci.android.com/
Enter a branch name. Start with aosp-master
if you don‘t know what you’re looking for
Navigate to aosp_cf_x86_64_phone
and click on userdebug
for the latest build
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 have img
in 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
You can use adb
to debug it, just like a physical device:
$ ./bin/adb -e shell
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.
You will need to stop the virtual device within the same directory as you used to launch the device.
`$ HOME=$PWD ./bin/stop_cvd`