commit | 3a60a87fa0f7eed4475490612bea5f7690a5d8bf | [log] [tgz] |
---|---|---|
author | A. Cody Schuffelen <schuffelen@google.com> | Thu Jan 23 19:03:50 2020 -0800 |
committer | A. Cody Schuffelen <schuffelen@google.com> | Mon Feb 03 15:21:37 2020 -0800 |
tree | 96a0bc875c85a38544291a2f6010ab7f87656212 | |
parent | 5671a8cfd9bdd6e1585eec44503c1f7bf8588d65 [diff] |
Symlink ~/cuttlefish_runtime to ~/cuttlefish_runtime.<first> Automated tools used to the single-instance cuttlefish expect the bare ~/cuttlefish_runtime directory to contain the necessary log files, and this is still convenient when running with a single instance otherwise. This change allows users to still access the files they expect at ~/cuttlefish_runtime, while they will have to give the instance number for other instances. Bug: 140071236 Test: launch_cvd, ls -l ~/ Change-Id: I908b1ee1a7f7062920cc44dbaec6a191f123b644
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!