Searched refs:example (Results 1 – 25 of 201) sorted by relevance
123456789
/hardware/interfaces/dumpstate/1.1/default/ |
D | Android.bp | 2 name: "android.hardware.dumpstate@1.1-service.example", 7 "android.hardware.dumpstate@1.1-service.example.rc", 10 "android.hardware.dumpstate@1.1-service.example.xml", 24 "-DLOG_TAG=\"android.hardware.dumpstate@1.1-service.example\"",
|
D | android.hardware.dumpstate@1.1-service.example.rc | 1 service dumpstate-1-1 /vendor/bin/hw/android.hardware.dumpstate@1.1-service.example
|
/hardware/interfaces/tests/extension/vibrator/aidl/client/ |
D | Android.bp | 1 // This example client is written as a test, but it is executing from a system 3 // server for example. 10 // makes the most sense, but both are provided here as an example.
|
/hardware/interfaces/vibrator/1.3/example/ |
D | Android.bp | 17 name: "android.hardware.vibrator@1.3-service.example", 20 init_rc: ["android.hardware.vibrator@1.3-service.example.rc"], 21 vintf_fragments: ["android.hardware.vibrator@1.3-service.example.xml"],
|
D | android.hardware.vibrator@1.3-service.example.rc | 1 service vendor.vibrator-1-3 /vendor/bin/hw/android.hardware.vibrator@1.3-service.example
|
/hardware/interfaces/tests/extension/vibrator/aidl/default/ |
D | Android.bp | 2 name: "android.hardware.tests.extension.vibrator-service.example", 11 // android.hardware.vibrator-service.example. This binary is being tested
|
/hardware/interfaces/radio/config/1.1/ |
D | types.hal | 37 * It's used to evaluate possible phone config change, for example from single 43 * PS attached simultaneously. For example, for L+L modem it 49 * internet PDN connections simultaneously. For example, for L+L
|
/hardware/interfaces/identity/aidl/default/ |
D | identity-default.rc | 1 service vendor.identity-default /vendor/bin/hw/android.hardware.identity-service.example
|
D | Android.bp | 2 name: "android.hardware.identity-service.example",
|
/hardware/interfaces/vibrator/aidl/default/ |
D | vibrator-default.rc | 1 service vendor.vibrator-default /vendor/bin/hw/android.hardware.vibrator-service.example
|
D | Android.bp | 18 name: "android.hardware.vibrator-service.example",
|
/hardware/interfaces/power/aidl/default/ |
D | power-default.rc | 1 service vendor.power-default /vendor/bin/hw/android.hardware.power-service.example
|
D | main.cpp | 23 using aidl::android::hardware::power::impl::example::Power;
|
D | Power.h | 26 namespace example {
|
D | Power.cpp | 26 namespace example { namespace
|
/hardware/interfaces/light/aidl/default/ |
D | lights-default.rc | 1 service vendor.light-default /vendor/bin/hw/android.hardware.lights-service.example
|
D | Android.bp | 2 name: "android.hardware.lights-service.example",
|
/hardware/interfaces/tests/extension/light/2.0/ |
D | ILight.hal | 17 // Would normally be 'vendor.example.extension.light@2.0' however, this is 18 // a google extension example. A vendor extension should also live in the
|
/hardware/interfaces/dumpstate/1.0/default/ |
D | android.hardware.dumpstate@1.0-service.rc | 1 service vendor.dumpstate-1-0 /vendor/bin/hw/android.hardware.dumpstate@1.0-service.example
|
D | Android.bp | 2 name: "android.hardware.dumpstate@1.0-service.example",
|
/hardware/interfaces/memtrack/1.0/ |
D | IMemtrack.hal | 23 * trackable in any other way, for example texture memory that is allocated by 44 * possible. For example, 55 * Memory must not overlap between types. For example, a graphics buffer
|
/hardware/interfaces/identity/support/include/cppbor/ |
D | README.md | 67 the encoding destination. A trivial example: 75 "root" data item will be an `Array` or `Map` which contains a more complex structure.For example 91 This example demonstrates how automatic conversion of C++ types to 98 structures. For example: 155 using namespace cppbor; // For example brevity 174 As the above example demonstrates, the styles can be mixed -- Note the 212 if, for example, you want to find an element inside of a structure,
|
/hardware/interfaces/biometrics/fingerprint/2.1/ |
D | types.hal | 45 * For example, ERROR_CANCELED should follow any acquisition message that 47 * user interaction. For example, if the sensor is dirty during enrollment and 75 * take action on the current operation. For example, ACQUIRED_IMAGER_DIRTY may
|
/hardware/interfaces/gnss/1.1/ |
D | IGnssCallback.hal | 31 * For example "ABC Co., Baseband Part 1234, RF Part 567, Software version 3.14.159" 46 * with GNSS HAL operation, for example, to assist with time to first fix, error recovery, or to
|
/hardware/interfaces/tests/extension/vibrator/aidl/ |
D | Android.bp | 2 // This is an example test interface showing how to add functionality
|
123456789