commit | 2837a04be217ab97d2200df6a7505447ee591041 | [log] [tgz] |
---|---|---|
author | Ram Muthiah <rammuthiah@google.com> | Tue Oct 22 16:07:23 2019 -0700 |
committer | android-build-merger <android-build-merger@google.com> | Tue Oct 22 16:07:23 2019 -0700 |
tree | 47c2bd74db6a81af54658178938473ea037cf72c | |
parent | 386aec7225732afe3684ab01b4f8081d69ee777a [diff] | |
parent | 539228054b99be1b5df9e7294213151c1c316b96 [diff] |
Fixed build_test target for arm cf phone build break am: 539228054b Change-Id: I83a63ae46d126706bd11515b0cebe41beb49c001
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
Stop cuttlefish with:
$ 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!