Lines Matching refs:is

3 Better Together Connectivity Quality (BeToCQ) is a new test tool built by
7 This tool is built on the top of the Nearby Connections API. Under Nearby
11 BeToCQ is designed to catch connectivity software and hardware performance
41   debugging is typically more difficult in CUJ tests. That's why CUJ tests run as
82 - Transfer medium is WFD.
89 - STA is connected to the 2G band and the transfer medium is connected to the 5G band.
95 - `scc_indoor_5g_wfd_sta_test` is skipped if the device doesn't
98 - `mcc_5g_all_wifi_non_dbs_2g_sta_test` is skipped for DBS capable devices.
118 Running the test is straightforward, but it can be difficult to get insights out
152     for example, Android 14. **This is the device that is being validated.**
167     the internet for at least one hour to ensure each is properly configured.
177     is especially important for 2G test as the 2G signal is typically stronger
212     -   If your version is lower than Python 3.11, install Python 3.11 or later:
228       5260 is a [DFS channel]
244         In this example, the source device is 17011FDEE0002N and the target
245         device is R3CN90YNAR.
270         Where `wifi_2g_ssid` is for the channel of 2437, `wifi_2g_ssid` is for
271         the channel of 5180 and `wifi_dfs_5g_ssid` is for the channel of 5260.
342 Note that `Quickstart` is the CUJ test name and there are
352 Note that no space is allowed between
370     Where `<TestResultDirectory>` is something like
377     -   If this is your first time using the tool, file an issue with Google to
379     -   Once you upload the artifacts, a link is displayed in the console
388 4. If the test passes, no further action is required.
406      failure signatures. Here is the list of failure signatures:
458    5. Review the Wi-Fi Direct logs in the bug report if the `WIFI_DIRECT` medium is used.
485 8. If the issue can't be resolved by the internal engineering team and there is