/frameworks/native/cmds/dumpstate/ |
D | README.md | 17 If you're working on device-specific code, you might need to build them as well. 31 you're working with `userdebug` variant, you may need to run the following to 38 * If you're working with `eng` variant, you may need to run the following to
|
/frameworks/base/core/java/com/android/internal/os/ |
D | ProcessCpuTracker.java | 256 public boolean working; field in ProcessCpuTracker.Stats 462 st.working = false; in collectStats() 521 st.working = true; in collectStats() 589 st.working = true; in collectStats() 600 st.working = true; in collectStats() 620 st.working = true; in collectStats() 719 if (stats.working) { 726 if (tstats.working) {
|
/frameworks/base/tools/lint/fix/ |
D | README.md | 21 **WARNING: You probably want to commit/stash any changes to your working tree before doing this...**
|
/frameworks/rs/tests/java_api/RSUnitTests/src/com/android/rs/unittest/ |
D | check_dims.rscript | 26 // are definitely working outside our proper bounds.
|
/frameworks/rs/tests/java_api/RSUnitTests/supportlibsrc_gen/com/android/rs/unittest/ |
D | check_dims.rscript | 28 // are definitely working outside our proper bounds.
|
/frameworks/base/core/java/android/app/ |
D | SearchDialog.java | 319 public void setWorking(boolean working) { in setWorking() argument 320 mWorkingSpinner.setAlpha(working ? 255 : 0); in setWorking() 321 mWorkingSpinner.setVisible(working, false); in setWorking()
|
/frameworks/native/services/inputflinger/docs/ |
D | input_coordinates.md | 13 is important to note when working in InputFlinger, which has to make sure the
|
/frameworks/base/packages/SystemUI/docs/ |
D | dagger.md | 106 Similarly, if you are working on a custom version of SystemUI and have code
|
D | status-bar-data-pipeline.md | 257 hope is that working the new pipeline will be easier and faster.
|
/frameworks/base/core/java/android/content/pm/ |
D | flags.aconfig | 64 …description: "Feature flag to keep app working even if its declared sdk-library dependency is unav…
|
/frameworks/base/core/java/android/window/ |
D | SurfaceSyncGroup.md | 74 See `frameworks/base/tests/SurfaceViewSyncTest` for a working example 91 …/base/tests/SurfaceControlViewHostTest/.../SurfaceControlViewHostSyncTest.java` for working example
|
/frameworks/libs/binary_translation/intrinsics/ |
D | Android.bp | 141 // Note: the following two genrules and this host binary are working together.
|
/frameworks/native/opengl/libs/EGL/ |
D | GLES_layers.md | 241 - How do we know if layers are working on a device?
|
/frameworks/native/libs/binder/ |
D | Android.bp | 827 // If you are working on or own one of these interfaces, the responsible things
|
/frameworks/av/media/tests/benchmark/ |
D | README.md | 228 …Encoder and Decoder). It specifies the mode in which MediaCodec APIs are working. For async mode, …
|
/frameworks/layoutlib/create/ |
D | README.txt | 24 …rences to native code (which we cannot support in Android Studio at the moment, but working on it),
|
/frameworks/compile/mclinker/include/mcld/Config/ |
D | Config.h.cmake | 283 /* Define to 1 if you have a working `mmap' system call. */
|
/frameworks/base/services/core/java/com/android/server/am/ |
D | AppProfiler.java | 2205 if (!st.working) { in updateCpuStatsNow()
|
/frameworks/native/docs/ |
D | Doxyfile | 1851 # Tested and working are Firefox, Chrome, Safari, and Opera. For IE 9+ you
|
/frameworks/av/media/libaaudio/ |
D | Doxyfile | 2221 # and working are Firefox, Chrome, Safari, and Opera.
|
/frameworks/av/media/codec2/docs/ |
D | doxygen.config | 2342 # and working are Firefox, Chrome, Safari, and Opera.
|
/frameworks/base/media/native/midi/include/ |
D | Doxyfile | 2385 # and working are Firefox, Chrome, Safari, and Opera.
|
/frameworks/proto_logging/stats/ |
D | atoms.proto | 9363 * in the system and returns cpu stats for those that are working at the time.
|