commit | c89e6df7d1be3365200ceffed27835a545427d92 | [log] [tgz] |
---|---|---|
author | Jorge Moreira Broche <[email protected]> | Wed Apr 28 17:41:11 2021 +0000 |
committer | Gerrit Code Review <[email protected]> | Wed Apr 28 17:41:11 2021 +0000 |
tree | d11e563c3577fd6a21d8ea2be0e3809d7bcf588d | |
parent | 0cdb0d52e1338ce8706f22d2231a7550aa5d1bdb [diff] | |
parent | ec48fc2875101953419061356e6901c139983af9 [diff] |
Merge changes I9d77a030,I99795f70,I6a4d4479,Icf7a8b53,Ieaa00ee3 * changes: Show the microphone control in webrtc UI No longer claim android.hardware.microphone to be unavailable Claim 1 microphones from the audio hal Revert^4 "Restrict input streams to 48KHz only in audio HAL" Remove capture=false from crosvm's ac97 flag
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.
Download, build, and install the host debian package:
git clone https://github.com/google/android-cuttlefish cd android-cuttlefish debuild -i -us -uc -b sudo dpkg -i ../cuttlefish-common_*_amd64.deb || sudo apt-get install -f 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
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
$ HOME=$PWD ./bin/stop_cvd
You can use adb
to debug it, just like a physical device:
$ ./bin/adb -e shell
You can use the TightVNC JViewer. Once you have downloaded the TightVNC Java Viewer JAR in a ZIP archive, run it with
$ java -jar tightvnc-jviewer.jar -ScalingFactor=50 -Tunneling=no -host=localhost -port=6444
Click “Connect” and you should see a lock screen!