commit | 6bba1ec4e30df49b95ab2e07ba3c5a892f1bacc1 | [log] [tgz] |
---|---|---|
author | Jorge E. Moreira <jemoreira@google.com> | Tue Feb 18 17:27:17 2020 -0800 |
committer | Jorge E. Moreira <jemoreira@google.com> | Tue Feb 18 17:27:17 2020 -0800 |
tree | c9e9658f114d12dbe9673fdac42a936192af0f34 | |
parent | 5d8564586cf2f21df1e2fccf95b438dfe09b5d7a [diff] |
[webrtc] React to input socket disconnecting When crosvm exits and starts again it attempts to connect to the input sockets. WebRTC only accepts the connection if it doesn't have a vmm already connected. This change allows it to react immediately to the vmm process exiting and get ready to accept the new connection when it restarts. Bug: 148998856 Test: locally, adb reboot, check cvd reacts to mouse events Change-Id: Ibb5946702ac633638bf464975bba5db4c046f513
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!