tag | b05869dbdc71728550632c23ecaf9cc20c980ae7 | |
---|---|---|
tagger | The Android Open Source Project <initial-contribution@android.com> | Tue Sep 20 01:59:35 2022 -0700 |
object | 6aac43f76b22cffc4b1117bf60cdc339000f966a |
Android Mainline Module Release 8848683,com.google.android.captiveportallogin,com.google.android.networkstack
commit | 6aac43f76b22cffc4b1117bf60cdc339000f966a | [log] [tgz] |
---|---|---|
author | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jun 20 20:10:09 2022 +0000 |
committer | Android Build Coastguard Worker <android-build-coastguard-worker@google.com> | Mon Jun 20 20:10:09 2022 +0000 |
tree | 8b051e1052faade9adc1138ad9eef30785386ef0 | |
parent | 5eefb9a3216ab2e898e2cbbe1cc05f392c222a71 [diff] | |
parent | 2fe9b3ae0ae15c39c98e44fe4e161dcdab632139 [diff] |
Snap for 8746144 from 2fe9b3ae0ae15c39c98e44fe4e161dcdab632139 to mainline-networking-release Change-Id: Ib1af7cdc187430f0d613eb5834a4dd8e9c26cb4c
Make sure virtualization with KVM is available.
grep -c -w "vmx\|svm" /proc/cpuinfo
This should return a non-zero value. If running on a cloud machine, this may take cloud-vendor-specific steps to enable. For Google Compute Engine specifically, see the GCE guide.
ARM specific steps:
/dev/kvm
. Note that this method can also be used to confirm support of KVM on any environment.Download, build, and install the host debian package:
sudo apt install -y git devscripts config-package-dev debhelper-compat golang git clone https://github.com/google/android-cuttlefish cd android-cuttlefish debuild -i -us -uc -b -d sudo dpkg -i ../cuttlefish-common_*_*64.deb || sudo apt-get install -f sudo usermod -aG kvm,cvdnetwork,render $USER sudo reboot
The reboot will trigger installing additional kernel modules and applying udev rules.
Go to http://ci.android.com/
Enter a branch name. Start with aosp-master
if you don‘t know what you’re looking for
Navigate to aosp_cf_x86_64_phone
and click on userdebug
for the latest build
aosp-master-throttled-copped
and device target aosp_cf_arm64_only_phone-userdebug
Click on Artifacts
Scroll down to the OTA images. These packages look like aosp_cf_x86_64_phone-img-xxxxxx.zip
-- it will always have img
in the name. Download this file
Scroll down to cvd-host_package.tar.gz
. You should always download a host package from the same build as your images.
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_64_phone-img-xxxxxx.zip
Launch cuttlefish with:
$ HOME=$PWD ./bin/launch_cvd
You can use adb
to debug it, just like a physical device:
$ ./bin/adb -e shell
When launching with ---start_webrtc
(the default), you can see a list of all available devices at https://localhost:8443
. For more information, see the WebRTC on Cuttlefish documentation.
You will need to stop the virtual device within the same directory as you used to launch the device.
`$ HOME=$PWD ./bin/stop_cvd`