Lines Matching refs:to
4 Android to test the cross-device connectivity performance that isn't covered
11 BeToCQ is designed to catch connectivity software and hardware performance
15 Depending on the device capabilities, the test takes two to six hours to
34 fixed wireless mediums. This helps isolate the issue to an individual medium
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
59 device-to-device transfer speed.
62 inputs to customize the test case and set the right performance expectations.
67 test cases are defined to cover:
83 - Both STA and WFD are connected to 5G indoor channel (for example, 5180 in JP).
89 - STA is connected to the 2G band and the transfer medium is connected to the 5G band.
100 Each test case runs multiple iterations to collect the following stats:
113 important to fill in the device capabilities section correctly in the test
118 Running the test is straightforward, but it can be difficult to get insights out
119 of the test results and determine further action to take.
121 BetoCQ takes three steps to address this issue:
130 to a single component. The tool also provides the most likely failure
137 We recommend an RF shielding box or room to run the test.
144 NETGEAR RAX120 AX6000, and NETGEAR R8000b AC3200. It's ideal to use two APs
145 to support all test cases. The test AP must have the access to
166 device setup processes. After the new devices are set up, connect them to
167 the internet for at least one hour to ensure each is properly configured.
171 to turn off Google Play Protect so that the test APK can run properly.
183 Follow these steps to prepare and execute tests and review test results.
187 Prepare the following materials to be used for the tests.
221 …and add its path to the [`Path` environment variable](https://stackoverflow.com/questions/44272416…
227 - There are three Wi-Fi channels to be tested: 2437, 5180, and 5260.
278 1. In the first run, define 2G and 5G SSID but leave the 5G DFS SSID to an empty
281 strings to cover the 5G DFS test case.
306 # if the device supports to start WFD group owner at a STA-associated DFS channel
308 # if the device supports to start WFD group owner at a STA-associated indoor channel
322 - Refer to release instructions below to set up the build environment.
345 If there are more than two devices connected to USB ports, specify the device
373 2. Use Result Uploader to upload the artifact folder to Google's result storage
377 - If this is your first time using the tool, file an issue with Google to
380 output. Click the link, then click **betocq_test_suite** to display
383 3. Click **MoblyTest** to display the overall test results.
390 5. Click each test case (for example, `test_scc_5g_wfd_sta`) to display the
394 6. If the test fails, follow the following steps to triage the results:
402 - Review the failed iterations and reasons. Follow the debugging tips to
405 2. Click the failed (red) iterations to see the timestamp and detailed
410 Failed to connect to SSID
415 Failed to remove networks
439 - Failure signature due to the GMS updates, which repeats a few times before the test exits:
449 stop com.google.android.gms due to installPackage
479 issue. If possible, move the test to a clean environment to rule out the
482 engineering team to resolve the device issue. This might require getting
487 for Google. Be sure to include all test artifacts.
491 Skip this unless you want to release the test binary from AOSP.
505 - Upload these files to a shared drive:
525 - Upload these files to a shared drive: