| /frameworks/wilhelm/doc/ |
| D | Doxyfile | 6 # All text after a hash (#) is considered a comment and will be ignored
37 # base path where the generated documentation will be put.
38 # If a relative path is entered, it will be relative to the location
39 # where doxygen was started. If left blank the current directory will be used.
43 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
45 # format and will distribute the generated files over these directories.
53 # documentation generated by doxygen is written. Doxygen will use this
65 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
72 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
75 # brief descriptions will be completely suppressed.
[all …]
|
| /frameworks/native/docs/ |
| D | Doxyfile | 6 # All text after a hash (#) is considered a comment and will be ignored
46 # Doxygen will copy the logo to the output directory.
51 # base path where the generated documentation will be put.
52 # If a relative path is entered, it will be relative to the location
53 # where doxygen was started. If left blank the current directory will be used.
57 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create
59 # format and will distribute the generated files over these directories.
67 # documentation generated by doxygen is written. Doxygen will use this
79 # If the BRIEF_MEMBER_DESC tag is set to YES (the default) Doxygen will
86 # If the REPEAT_BRIEF tag is set to YES (the default) Doxygen will prepend
[all …]
|
| /frameworks/av/media/libaaudio/ |
| D | Doxyfile | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
74 # documentation generated by doxygen is written. Doxygen will use this
88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
[all …]
|
| D | Doxyfile.orig | 9 # All text after a single hash (#) is considered a comment and will be ignored.
51 # and the maximum width should not exceed 200 pixels. Doxygen will copy the logo
57 # into which the generated documentation will be written. If a relative path is
58 # entered, it will be relative to the location where doxygen was started. If
59 # left blank the current directory will be used.
63 # If the CREATE_SUBDIRS tag is set to YES, then doxygen will create 4096 sub-
65 # will distribute the generated files over these directories. Enabling this
74 # documentation generated by doxygen is written. Doxygen will use this
88 # If the BRIEF_MEMBER_DESC tag is set to YES doxygen will include brief member
95 # If the REPEAT_BRIEF tag is set to YES doxygen will prepend the brief
[all …]
|
| /frameworks/native/vulkan/doc/implementors_guide/ |
| D | implementors_guide.adoc | 13 …will include a stub +libvulkan.so+ exporting the same symbols as the loader. Calling the Vulkan fu…
17 … enumeration process isn't as elaborate as on other platforms. The loader will use the existing HA…
24 …ly trivial. If support for multiple drivers is ever added, the HAL module will export a list of st…
30 …for later inspection. So only layers delivered as part of the application will be enabled on produ…
36 …will almost always expose extensions. Developers choose which layers, and which versions of those …
38 …cation's knowledge or consent. These violate Android's security policies and will not be supported.
40 …ate the loader will only search in the application's normal library search path (as defined by the…
42 …xists and is non-zero, generally rooted or engineering builds) the loader will also search the dir…
48 …will be handled by the platform and not exposed to drivers. The WSI implementation will rely on a …
60 …ined private gralloc usage flags. When creating a swapchain, the platform will ask the driver to t…
[all …]
|
| /frameworks/compile/slang/ |
| D | README.rst | 13 Virtual Machine) bitcode representation, which will be consumed on
22 distinct, effective features for Android programming. We will use
55 Note that *-MD* will tell llvm-rs-cc to output dependence information.
82 This command will generate:
90 The **Script\*.java** files above will be documented below.
120 Note that the ScriptC_fountain.java will be generated inside
140 In ScriptC_fountain.java, llvm-rs-cc will reflect the following methods::
149 static will generate get, set, or invoke methods. This provides a way
158 llvm-rs-cc will genearte ScriptC_fountain.java as follows::
180 struct. In this case, llvm-rs-cc will reflect two files,
[all …]
|
| /frameworks/native/cmds/surfacereplayer/replayer/ |
| D | README.md | 42 inside the android shell. This will replay the full trace and then exit. Running this command
43 outside of the shell by prepending `adb shell` will not allow for manual control and will not turn
46 The replay will not fill surfaces with their contents during the capture. Rather they are given a
47 random color which will be the same every time the trace is replayed. Surfaces modulate their color
60 When replaying, if the user presses CTRL-C, the replay will stop and can be manually controlled
61 by the user. Pressing CTRL-C again will exit the replayer.
98 - replayManually - **True**: if the replayer will immediately switch to manual replay at the start
99 - numThreads - Number of worker threads the replayer will use.
114 And the trace will start replaying. Once the trace is finished replaying, the function will return.
115 The layers that are visible at the end of the trace will remain on screen until the program
[all …]
|
| /frameworks/base/cmds/bootanimation/ |
| D | FORMAT.md | 36 + `p` -- this part will play unless interrupted by the end of the boot
37 + `c` -- this part will play to completion, no matter what
48 - `c` -- will centre the text
49 - `n` -- will position the text n pixels from the start; left edge for x-axis, bottom edge
51 - `-n` -- will position the text n pixels from the end; right edge for x-axis, top edge
54 * `-24` or `c -24` will position the text 24 pixels from the top of the screen,
56 * `16 c` will position the text 16 pixels from the left of the screen, centred
58 * `-32 32` will position the text such that the bottom right corner is 32 pixels above
72 * For a NxM image each character glyph will be N/16 pixels wide and M/(12*2) pixels high
102 The system will end the boot animation (first completing any incomplete or even entirely unplayed
[all …]
|
| /frameworks/av/media/libnbaio/ |
| D | README.txt | 23 will lose data if reader doesn't keep up
32 if configured to block, then will wait until space available before returning
33 if configured to not block, then will return a short transfer count
34 and will never overwrite data
|
| /frameworks/native/cmds/dumpstate/ |
| D | bugreport-format.md | 44 When systrace is enabled, the zip file will contain a `systrace.txt` file as well.
76 - Services in the new sections will have a new header containing the
80 For example, cpuinfo will now move to `DUMPSYS CRITICAL` and will have a
83 - Bug report will contain proto dumps from all supporting services. Support can be
86 - All protos will be generated into separate files per service, per priority. The files
87 will be stored in `proto/<servicename>(_CRITICAL|_HIGH|).proto`
92 During development, the versions will be suffixed with _-devX_ or
104 Android defining that format, then a new _sub-version_ will be used.
106 release, the version will be called **1.1** or something like that.
|
| /frameworks/base/core/proto/android/os/ |
| D | enums.proto | 78 // will be allowed to go off.
82 // backlight will be allowed to go off. If the user presses the power
83 // button, then the SCREEN_DIM_WAKE_LOCK will be implicitly released by
88 // backlight will be allowed to go off. If the user presses the power
89 // button, then the SCREEN_BRIGHT_WAKE_LOCK will be implicitly released
95 // FULL_WAKE_LOCK will be implicitly released by the system, causing
106 // locks are held, then the device will fall asleep (and lock) as usual.
107 // However, the device will not fall asleep while the screen has been
|
| /frameworks/base/core/proto/android/net/ |
| D | networkrequest.proto | 39 // The framework will issue callbacks about any and all networks that
42 // A hybrid of the two designed such that the framework will issue
49 // semantics, but to the fact that the system will only ever create a
55 // telephony DUN request), the framework will issue callbacks about the
63 // higher-scoring network will not go into the background immediately,
64 // but will linger and go into the background after the linger timeout.
|
| /frameworks/base/core/proto/android/app/ |
| D | alarmmanager.proto | 32 // will wake up the device when it goes off.
36 // asleep, it will not be delivered until the next time the device wakes up.
39 // sleep), which will wake up the device when it goes off.
43 // device is asleep, it will not be delivered until the next time the device
|
| /frameworks/native/opengl/specs/ |
| D | EGL_ANDROID_get_frame_timestamps.txt | 121 eglGetFrameTimestampsANDROID. If any error is generated, the function will
138 compositor will begin composition. This is effectively the deadline
161 will have the value EGL_TIMESTAMP_PENDING_ANDROID. Timestamps for events
162 that did not occur will have the value EGL_TIMESTAMP_INVALID_ANDROID.
163 Otherwise, the timestamp will be valid and indicate the event has occured.
164 Timestamp queries that are not supported will generate an EGL_BAD_PARAMETER
165 error. If any error is generated the function will return EGL_FALSE.
179 this will correspond to buffer's queue time.
190 is composited only once, it will have the same value as
196 the compositor's rendering work for this frame finished. This will be
|
| D | EGL_ANDROID_get_native_client_buffer.txt | 76 If eglGetNativeClientBufferANDROID fails, NULL will be returned, no
77 memory will be allocated, and the following error will be generated:
|
| /frameworks/base/core/tests/BTtraffic/ |
| D | README | 2 Together with the SvcMonitor, which will be called automatically in this android service, can be
11 5. A separate monitor process will be automatically forked and will be reading from /proc file
44 ** if -1 is provided, client will only send the package once.
|
| /frameworks/base/tests/AccessoryDisplay/ |
| D | README | 13 a monitor or video dock that the user will want to plug a phone into.
17 in this arrangement and will provide power to the source.
32 in this arrangement and will receive power from the sink.
48 on each device. The source will then begin to project display
|
| /frameworks/base/core/java/org/chromium/arc/ |
| D | EventLogTags.logtags | 6 # In case of conflicts build will fail, so we do not need to worry too much
10 # These events will be watched in automations like autotests.
|
| /frameworks/rs/tests/lldb/ |
| D | README.txt | 10 LLDB's python bindings. The test suite will push several test app's onto
18 binaries that the testsuite uses. They will be placed in
86 device it will listen on this port. Each successive
87 test will increment onwards from this port.
90 Specify host port which lldb-server will be forwarded
92 server (on the target) will be forwarded to on the
93 host. Each successive test will increment onwards from
103 The path to the file where the log will be written.
105 The path to the file where junit results.xml will be
110 An optional config file can be passed to the test suite which will provide
[all …]
|
| /frameworks/compile/libbcc/ |
| D | README.rst | 185 On ARM, the first 4 arguments will go into r0, r1, r2, and r3, in that order.
186 The remaining (if any) will go through stack.
188 For ext_vec_types such as float2, a set of registers will be used. In the case
189 of float2, a register pair will be used. Specifically, if float2 is the first
190 argument in the function prototype, float2.x will go into r0, and float2.y,
193 Note: stack will be aligned to the coarsest-grained argument. In the case of
194 float2 above as an argument, parameter stack will be aligned to an 8-byte
200 On ARM, we use hardfp. Note that double will be placed in a register pair.
|
| /frameworks/layoutlib/bridge/tests/res/testApp/MyApplication/ |
| D | gradle.properties | 4 # Settings specified in this file will override any Gradle settings
15 # When configured, Gradle will run in incubating parallel mode.
|
| /frameworks/data-binding/integration-tests/TestApp/ |
| D | gradle.properties | 4 # Gradle settings configured through the IDE *will override*
15 # When configured, Gradle will run in incubating parallel mode.
|
| /frameworks/base/tests/TouchLatency/ |
| D | gradle.properties | 4 # Gradle settings configured through the IDE *will override*
15 # When configured, Gradle will run in incubating parallel mode.
|
| /frameworks/base/core/tests/benchmarks/ |
| D | README | 15 # First make sure art has permissions to dalvik-cache, otherwise it will run slower with interprete…
19 # Otherwise you will likely crash with UnsatisfiedLinkError despite having correct JNI code.
|
| /frameworks/base/wifi/tests/ |
| D | README.md | 14 `runtests.sh` will build the test project and all of its dependencies and push the APK to the
15 connected device. It will then run the tests on the device.
17 To pick up changes in framework/base, you will need to:
|