Do not install android.hardware.bluetooth.audio-impl This is now an explicit dependency of android.hardware.audio.service-aidl.example (cc_binary). Do not install it separately on trunk_staging. Besides, since android.hardware.audio.service-aidl.example is now a part of com.android.hardware.audio apex, /vendor/lib32/android.hardware.bluetooth.audio-impl.so is not used by any processes. We can remove the following files from /vendor/lib: - android.hardware.audio.common-V3-ndk.so - android.hardware.audio.common@5.0.so - android.hardware.bluetooth.audio-V4-ndk.so - android.hardware.bluetooth.audio-impl.so - android.hardware.bluetooth.audio@2.0.so - android.hardware.bluetooth.audio@2.1.so - android.hidl.safe_union@1.0.so - android.media.audio.common.types-V3-ndk.so - libbluetooth_audio_session_aidl.so - libflatbuffers-cpp.so - libfmq.so - libxml2.so - server_configurable_flags.so Bug: 312265159 Test: atest VtsHalBluetoothAudioTargetTest Change-Id: I38a381deedc45c5768647c8c50699fde385707ca
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 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.
Go to http://ci.android.com/
Enter a branch name. Start with aosp-main 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-main-throttled and device target aosp_cf_arm64_only_phone-trunk_staging-userdebugClick 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