commit | 70e6a3f2434529698dc831471a1a7b675cb87cc3 | [log] [tgz] |
---|---|---|
author | Devin Moore <devinmoore@google.com> | Mon Feb 08 09:32:41 2021 -0800 |
committer | Devin Moore <devinmoore@google.com> | Tue Feb 23 07:42:06 2021 -0800 |
tree | 278548f4913ff611657a88b58d57325cbd886f58 | |
parent | fd3a48f2248ff0ce4a1d1990fd0288b6a83b9572 [diff] |
Move androidboot parameters to bootconfig for Cuttlefish Now that boot config is supported, the androidboot parameters that were being passed to the kernel commandline are now being passed to boot config with BOARD_BOOTCONFIG. "bootconfig" kernel parameter is required for the kernel to process the bootconfig. Test: Boot cuttlefish device with bootloader and first_stage_init changes to handle boot config. Bug: 173815685 Change-Id: Id1b3841081ef750644159b8803fe412c25dfdfeb
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!