Lines Matching refs:service

9 This will run tests on the test service (described below), the goal being to test the dynamic
10 service infrastructure.
13 With a service: aidl_lazy_test serviceName...
15 This will run tests on the input service, verifying whether it successfully displays lazy behavior.
16 If the service has multiple interfaces, each can be entered as a separate argument to be tested
18 Infrastructure tests that rely on specific features of the dedicated test service will be skipped.
23 aidl_lazy_test_server is a simple test service.
25 Because it represents the bare minimum requirements for implementing a service, it also serves as
26 an example of how to add a new service. The required files are as follows:
34 The implementation of the server. The only required function is main(), wherein the service must be
35 instantiated and added (either to servicemanager as a standard service or to LazyServiceRegistrar
36 to be a dynamic service). The server then joins the thread pool.
41 This file is read by init, which later starts the service. The interface, oneshot, and disabled
47 The implementation of the service's functionality.
52 The AIDL interface for the service, this will generate code that clients can use to interact with
53 the service via IPC.
60 A cc_binary entry will need to be added for the service with:
79 binder_use and binder_call allow for basic use of this service.
80 add_service allows the service to be registered. Note that an additional service type is required
97 Each interface for the service must be mapped to aidl_lazy_test_service here.
100 public/service.te