commit | 683adf95cd435d63cbfb860e979bab467d7c6253 | [log] [tgz] |
---|---|---|
author | Enrico Granata <egranata@google.com> | Tue Apr 21 15:41:39 2020 -0700 |
committer | Alistair Delva <adelva@google.com> | Thu Apr 23 15:08:01 2020 +0000 |
tree | 441dda2080c9e8f01e47033d13640edaebbc6b50 | |
parent | f8d3125624940ffb0d7961c10b34fcdbdd6ac930 [diff] |
Allow downstream Cuttlefish devices to format userdata as ext4 This is technically already possible as one can set TARGET_USERDATAIMAGE_FILE_SYSTEM_TYPE to be ext4 instead of the default f2fs, but then fstab only allows for mounting userdata as f2fs. Allow setting an ext4-based fstab file if that's what TARGET_USERDATAIMAGE_FILE_SYSTEM_TYPE points to. There are other issues around this that will need solving before the setting actually kicks in, but this is a first step. Bug: 149054714 Test: build Change-Id: I1857ac76bb9700a038954420361e689c79dbc77a Merged-In: I1857ac76bb9700a038954420361e689c79dbc77a
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!