commit | 199971e5f8dfa4ca93441b50e319f706e5f02f74 | [log] [tgz] |
---|---|---|
author | bohu <[email protected]> | Thu Aug 12 17:04:01 2021 -0700 |
committer | Alistair Delva <[email protected]> | Wed Aug 18 19:15:45 2021 +0000 |
tree | 5d1650576be17063ee187a0bf3e5f6b7daa2f5b6 | |
parent | 7f0214665c2237ec4bf3c66dc688e5b81f173974 [diff] |
radio: send unsol network scan result Original change: https://android-review.googlesource.com/c/device/google/cuttlefish/+/1794950 When caller requests a network scan, it is expecting at least one unsol network scan result. This cl emulates that behavior. Bug: 196217757 Test: atest CtsCarrierApiTestCases:android.carrierapi.cts.NetworkScanApiTest#testRequestNetworkScan Change-Id: I28dc258f9ff1110a9e4ca9170c83437283c78e90 Merged-In: I28dc258f9ff1110a9e4ca9170c83437283c78e90
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.
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 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
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
$ HOME=$PWD ./bin/stop_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.
When launching with --start_vnc_server=true
, 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!