aboutsummaryrefslogtreecommitdiff
path: root/en/compatibility/cts/setup.html
diff options
context:
space:
mode:
Diffstat (limited to 'en/compatibility/cts/setup.html')
-rw-r--r--en/compatibility/cts/setup.html14
1 files changed, 10 insertions, 4 deletions
diff --git a/en/compatibility/cts/setup.html b/en/compatibility/cts/setup.html
index 16cc43a0..cb235b63 100644
--- a/en/compatibility/cts/setup.html
+++ b/en/compatibility/cts/setup.html
@@ -40,6 +40,12 @@ be of any kind, ranging from a satellite simulator, to a GPS/GNSS repeater of
outdoor signals, simply to placement of the DUT close enough to a window such that
it can directly receive enough GPS/GNSS signal.</p>
+<aside class="caution">
+ <strong>Caution:</strong> For the GPS testing, the internet connection setup
+ must not block connections to supl.google.com port 7276. This port is used to
+ download GPS assistance data for testing position calculation on the local device.
+</aside>
+
<h3 id=wifi>Wi-Fi and IPv6</h3>
<p>CTS tests require a Wi-Fi network that supports IPv6, can treat the Device
Under Test (DUT) as an isolated client, and has an internet
@@ -56,7 +62,8 @@ href="http://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers">list of IPv6
tunnel brokers</a>.</p>
<h2 id=desktop_setup>Desktop machine setup</h2>
-<p>CTS currently supports 64-bit Linux and Mac OS host machines.</p>
+<aside class="caution"><strong>Caution:</strong> CTS currently supports 64-bit
+Linux and Mac OS host machines. CTS will not work on Windows OS.</aside>
<h3 id=adb>ADB and AAPT</h3>
<p>Before running the CTS, make sure you have recent versions of both <a
@@ -94,8 +101,7 @@ directory name are correct.</p>
8u45 or newer</a>.</li>
</ul>
<p>
-For details, see the <a href="https://source.android.com/source/requirements.html#jdk">JDK
-requirements</a>.
+For details, see the <a href="/setup/requirements.html#jdk">JDK requirements</a>.
</p>
<h3 id=CTS_files>CTS files</h3>
@@ -121,7 +127,7 @@ file for Ubuntu Linux.</p>
<p>A compatible device is defined as a device with a user/release-key signed
build, so your device should be running a system image based on the known to be
compatible user build (Android 4.0 and later) from <a
-href="/source/build-numbers.html">Codenames, Tags, and Build
+href="/setup/build-numbers.html">Codenames, Tags, and Build
Numbers</a>.<br>
<p class="caution"><strong>Caution:</strong> When used to confirm Android