commit | 4c28713091e6a6cab6f8c16e869ab72d36977735 | [log] [tgz] |
---|---|---|
author | A. Cody Schuffelen <schuffelen@google.com> | Fri Feb 07 17:04:23 2020 -0800 |
committer | A. Cody Schuffelen <schuffelen@google.com> | Fri Feb 07 17:14:18 2020 -0800 |
tree | a575f36090eef7e99b711f79c461707d512fbbf7 | |
parent | 90532354e6cc5bfa157c16e8f531268f4857f0f0 [diff] |
Store composite.img in cuttlefish_assembly This fixes an issue with `acloud create --local-image --local-instance` losing track of the composite.img file. Putting it in cuttlefish_assembly is more reliable than ANDROID_PRODUCT_OUT. Test: acloud-dev create --local-instance --local-image, delete, create Bug: 148252240 Change-Id: Ic824196fd1b418b27b35533f9a26918c198ccd6a
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
aosp-master
if you don't know what you're looking foraosp_cf_x86_phone
and click on userdebug
for the latest buildArtifacts
aosp_cf_x86_phone-img-xxxxxx.zip
-- it will always have img
in the name. Download this filecvd-host_package.tar.gz
. You should always download a host package from the same build as your images.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!