Add init_dev_config for CF reference
init_dev_config is a service that can configure the device based on
various conditions. For example, it can set "apex select" sysprops.
$ adb logcat | egrep "disabled.apex|init_dev"
init : starting service 'init_dev_config'...
init : ... started service 'init_dev_config' has pid 161
init : SVC_EXEC service 'init_dev_config' pid 161 (uid 0 gid 0+0 context u:r:init_dev_config:s0) started; waiting...
init : Service 'init_dev_config' (pid 161) exited with status 0 waiting took 0.011000 seconds
init : Sending signal 9 to service 'init_dev_config' (pid 161) process group...
apexd-bootstrap: Found pre-installed APEX /vendor/apex/com.google.cf.disabled.apex
apexd-bootstrap: Skipping APEX at path /vendor/apex/com.google.cf.disabled.apex because it's disabled via sysprop.
apexd : Found pre-installed APEX /vendor/apex/com.google.cf.disabled.apex
apexd : Skipping APEX at path /vendor/apex/com.google.cf.disabled.apex because it's disabled via sysprop.
Bug: 417632996
Flag: EXEMPT cuttlefish host code
Test: cvd create & ensure com.google.cf.disabled is not activated
Change-Id: I840d1b2551a9fad188ce1b69e169f55556ef1aa4
Note
For all host tools development please refer to https://github.com/google/android-cuttlefish/blob/main/docs/HostToolsMigration.md for more information.
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 packages:
sudo apt install -y git devscripts config-package-dev debhelper-compat golang curl git clone https://github.com/google/android-cuttlefish cd android-cuttlefish # Install build dependencies and build debian packages ./tools/buildutils/build_packages.sh sudo dpkg -i ./cuttlefish-base_*_*64.deb || sudo apt-get install -f sudo dpkg -i ./cuttlefish-user_*_*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-main 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-main-throttled and device target aosp_cf_arm64_only_phone-trunk_staging-userdebugClick 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