Lines Matching refs:in
40 directed test, the CUJ test can use multiple radios in a more dynamic way. So the
41 debugging is typically more difficult in CUJ tests. That's why CUJ tests run as
44 CUJ test are implemented as the test cases defined in the `compound_test`
46 term `compound_test` refers to the fact that it uses multiple radios in a
50 transfer. We plan to add more CUJs in later releases.
58 device-to-device connection in parallel and thus can support higher
81 - WLAN and Wi-Fi Direct (WFD) concurrency mode operates in the same channel.
83 - Both STA and WFD are connected to 5G indoor channel (for example, 5180 in JP).
90 - Device isn't capable of DBS and so it operates in MCC mode.
113 important to fill in the device capabilities section correctly in the test
114 configuration file. We'll discuss this in more detail in the following sections.
146 google.com. Note that in China, this test requires an office VPN network or
147 installing a VPN app in devices.
169 Follow the instructions listed in [Google Play Protect]
192 in a local directory:
221 …ow.com/questions/44272416/how-to-add-a-folder-to-path-environment-variable-in-windows-10-with-scre…
288 20 MHz) at 2G. This device doesn't support STA + WFD concurrency in DBS mode.
296 # The max PHY rate at 5G, in Mbps
298 # The max PHY rate at 2G, in Mbps
302 # if the device supports DBS in STA and Wi-Fi Direct concurrency mode
304 # The max number of spatial streams in DBS mode.
313 and `config_wifiEnableStaIndoorChannelForPeerNetwork` in the Wi-Fi device
343 a few other supported CUJ tests listed in `cuj_and_test_config.yml`.
353 two device serial numbers in the above commafnd.
366 Artifacts are saved in <TestResultDirectory>
367 Test summary saved in <TestResultDirectory>/test_summary.yaml
375 and instructions are provided in the
379 - Once you upload the artifacts, a link is displayed in the console
455 4. Search the following keywords for the related logs in the bug report:
458 5. Review the Wi-Fi Direct logs in the bug report if the `WIFI_DIRECT` medium is used.
470 values but the values are different, the device likely operates in multiple
472 In MCC mode, firmware could have the bugs resulting in bandwidth