Lines Matching full:service
22 Each service is identified by a name and serves a specific purpose. For
47 - sending the service name through the socket
52 corresponding service.
83 communication, the client and service should use a fragmentation
92 - When a client connects to /dev/socket/qemud and sends a service
95 connect:<service>:<id>
97 where <service> is the service name, and <id> is a 2-hexchar string
114 the corresponding emulator service will be passed through the
122 - If an emulator service decides, for some reason, to disconnect
153 the "sensors" service provided by the emulator (if available).
172 must be used depending on which service you talk to by clients.
175 but also has some differences as far as connecting client with the service is
220 sockets, one per service:
230 connect to a given service at a time).
235 connect:<service>
237 where <service> can be one of "gsm", "gps" or "control"
244 ok:connect:<service>:<hxid>
246 where <service> would be the service name, and <hxid> a 4-hexchar channel
255 - adding a new service required to modify /system/etc/init.goldfish.rc
259 - only one client could be connected to a given service at a time,
263 The current implementation moves any service-specific code to the emulator,
276 to allow saving of service-specific state. Next, clients are saved following
277 the same pattern. We save the channel id and the name of service they are
282 no functionality to start start missing services, so loading fails if a service
284 service-specific state.
