commit | 2f30419e4d7f5540a27eb8d64f3c20d9574348f4 | [log] [tgz] |
---|---|---|
author | Nicole Lee <nicoleytlee@google.com> | Tue Apr 13 05:36:00 2021 +0000 |
committer | Nicole Lee <nicoleytlee@google.com> | Tue Apr 13 07:17:40 2021 +0000 |
tree | 7470ef808f16cfdc03dffbd92e99b04c4a20c151 | |
parent | 8d6ae5590abd4195c4a383272807bd2e05ae8243 [diff] |
Revert "Support auto-generation of ESP, add otheros_root" This reverts commit ff9459ea35d5ec69e68cba8ab14e926192399bba. Reason for revert: DroidMonitor: Potential culprit for Bug 185191460 - verifying through Forrest before revert submission. This is part of the standard investigation process, and does not mean your CL will be reverted. Change-Id: Ib87c85d16bfe7146ba4ffc277a7924c086887b7c
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_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_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_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!