Make all writes to the PTY nonblocking

The PTY has a buffer that fills up during writes and can only be
drained by a client. Once the PTY fills up, future writes to it are
blocked until a client connects to the PTY.

To prevent the PTY from filling up and blocking the console forwarder
write thread during writes, make all writes to the PTY nonblocking.
This change effectively voids all writes to the PTY until a client
connects to it.

Bug: 162365412
Test: locally via cf bootloader boot
Change-Id: Idccf165b238c8b65159bab239340dbb7f3fb7dc2
1 file changed
tree: 71d3992ecac78db377ae0f658e4942b5f7cbbd26
  1. common/
  2. guest/
  3. host/
  4. recovery/
  5. shared/
  6. tests/
  7. tools/
  8. vsoc_arm64/
  9. vsoc_arm64_only/
  10. vsoc_x86/
  11. vsoc_x86_64/
  12. vsoc_x86_64_only/
  13. vsoc_x86_noapex/
  14. Android.bp
  15. Android.mk
  16. AndroidProducts.mk
  17. CleanSpec.mk
  18. dtb.img
  19. fetcher.mk
  20. host_package.mk
  21. METADATA
  22. OWNERS
  23. README.md
  24. required_images
  25. TEST_MAPPING
README.md

So you want to try cuttlefish?

  1. 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
  1. Go to http://ci.android.com/
  2. Enter a branch name. Start with aosp-master if you don‘t know what you’re looking for
  3. Navigate to aosp_cf_x86_phone and click on userdebug for the latest build
  4. Click on Artifacts
  5. 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
  6. Scroll down to cvd-host_package.tar.gz. You should always download a host package from the same build as your images.
  7. 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
  1. Launch cuttlefish with:

    $ HOME=$PWD ./bin/launch_cvd

  2. Stop cuttlefish with:

$ HOME=$PWD ./bin/stop_cvd

So you want to debug cuttlefish?

You can use adb to debug it, just like a physical device:

$ ./bin/adb -e shell

So you want to see cuttlefish?

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!