Searched refs:numbers (Results 1 – 20 of 20) sorted by relevance
/system/core/storaged/ |
D | EventLogTags.logtags | 1 # The entries in this file map a sparse set of log tag numbers to tag names. 4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the 7 # Tag names are one or more ASCII letters and numbers or underscores, i.e. 11 # Tag numbers and names are separated by whitespace. Blank lines and lines
|
/system/logging/logd/ |
D | event.logtags | 1 # The entries in this file map a sparse set of log tag numbers to tag names. 4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the 7 # Tag names are one or more ASCII letters and numbers or underscores, i.e. 11 # Tag numbers and names are separated by whitespace. Blank lines and lines
|
/system/logging/liblog/ |
D | event.logtags | 1 # The entries in this file map a sparse set of log tag numbers to tag names. 4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the 7 # Tag names are one or more ASCII letters and numbers or underscores, i.e. 11 # Tag numbers and names are separated by whitespace. Blank lines and lines
|
D | pmsg_reader.cpp | 288 static const char numbers[] = "0123456789"; in __android_log_pmsg_file_read() local 321 cp = strpbrk(names->name, numbers); in __android_log_pmsg_file_read() 331 cp = strpbrk(r, numbers); in __android_log_pmsg_file_read()
|
/system/memory/lmkd/ |
D | event.logtags | 1 # The entries in this file map a sparse set of log tag numbers to tag names. 4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the 7 # Tag names are one or more ASCII letters and numbers or underscores, i.e. 11 # Tag numbers and names are separated by whitespace. Blank lines and lines
|
/system/logging/logcat/ |
D | event.logtags | 1 # The entries in this file map a sparse set of log tag numbers to tag names. 4 # Tag numbers are decimal integers, from 0 to 2^31. (Let's leave the 7 # Tag names are one or more ASCII letters and numbers or underscores, i.e. 11 # Tag numbers and names are separated by whitespace. Blank lines and lines
|
/system/chre/apps/rpc_world/rpc/ |
D | rpc_world.proto | 12 // Add multiple numbers.
|
/system/sepolicy/private/ |
D | fsck_untrusted.te | 20 # device, comparing the major and minor numbers to the filesystem
|
D | fsck.te | 45 # device, comparing the major and minor numbers to the filesystem
|
/system/timezone/ |
D | README.android | 124 Starting from Android V the tzdata APEX through the inclusion of tz data set version numbers in the 129 - Major version numbers are mutually incompatible. e.g. v2 is not compatible 131 - Minor version numbers are backwards compatible. e.g. a v2.2 time zone data set
|
/system/core/debuggerd/proto/ |
D | tombstone.proto | 16 // If you add custom fields to this proto, do not use numbers in the reserved range.
|
/system/nfc/tools/casimir/ |
D | README.rst | 38 the Android phone. The port numbers for a *local instance* can be obtained from
|
/system/extras/libatrace_rust/ |
D | README.md | 109 This section is an overview, you can find specific numbers in
|
/system/extras/libjsonpb/ |
D | README.md | 83 - JSON numbers should be `(s|fixed|u|)int32`, `float`, or `double` in the schema
|
/system/extras/simpleperf/doc/ |
D | android_platform_profiling.md | 27 source code and disassembly (with line numbers) in the report. Below is an example.
|
/system/chre/chpp/ |
D | README.md | 89 …ze of 127 packets). Note that fragmented messages have multiple sequence numbers, one for each fra… 95 …ber of this packet. Note that fragmented messages have multiple sequence numbers, one for each fra… 205 CHPP’s built-in basic services take advantage of reserved handle numbers, ranging from 0x00 - 0x0f …
|
D | RELEASE_NOTES.md | 86 …layer loopback ignores app layer functionality and state, as well as checksums and sequence numbers
|
/system/libsysprop/srcs/android/sysprop/ |
D | TelephonyProperties.sysprop | 281 # Track CDMA SMS message id numbers to ensure they increment
|
/system/tools/hidl/test/hidl_test/ |
D | hidl_test_client.cpp | 1837 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F() 1845 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F() 1853 .numbers = std::array<double, 10>{ {1, 2, 3, 4, 5, 6, 7, 8, 9, 10} }, in TEST_F()
|
/system/update_engine/ |
D | README.md | 321 respectively. These numbers are [hard coded] in the updater client.
|