Searched refs:OKAY (Results 1 – 6 of 6) sorted by relevance
| /packages/apps/Settings/tests/Enable16KbTests/test_16kb_app/src/com/android/settings/development/test/ |
| D | Enable16KbDeviceTest.java | 52 private static final String OKAY = "OK"; field in Enable16KbDeviceTest
108 mDevice.wait(Until.findObject(By.text(OKAY)), TIMEOUT).click(); in enable16k_switchTo16Kb()
122 mDevice.wait(Until.findObject(By.text(OKAY)), TIMEOUT).click(); in enable16k_switchTo4Kb()
157 mDevice.wait(Until.findObject(By.text(OKAY)), TIMEOUT).click(); in openPersistentNotification()
168 mDevice.wait(Until.findObject(By.text(OKAY)), TIMEOUT).click(); in enable16k_disableDeveloperOption()
|
| /packages/modules/adb/ |
| D | OVERVIEW.TXT | 100 1. For success, the 4-byte "OKAY" string
106 Note that the connection is still alive after an OKAY, which allows the
107 client to make other requests. But in certain cases, an OKAY will even
112 the "OKAY" answer, all further requests made by the client will go
|
| D | SYNC.TXT | 15 "OKAY" or "FAIL" as per the usual protocol.
68 request (but not to chunk requests) with an "OKAY" sync response (length can
|
| D | SERVICES.TXT | 19 After the OKAY, this is followed by a 4-byte hex len,
45 <serial-number>. After the OKAY response, every client request will
227 After the OKAY, the service sends 16-byte binary structure
|
| D | protocol.txt | 291 "OKAY" response is sent, otherwise a "FAIL" message is returned. Once
295 server: "OKAY"
|
| /packages/modules/Virtualization/compos/tests/java/android/compos/test/ |
| D | ComposTestCase.java | 72 private static final int OKAY = 0; field in ComposTestCase
151 assertThat(result).exitCode().isEqualTo(OKAY); in testOdrefresh()
|