Searched refs:daemon (Results 1 – 16 of 16) sorted by relevance
280 IFingerprintDaemon daemon = getFingerprintDaemon(); in startEnrollment() local281 if (daemon == null) { in startEnrollment()289 final int result = daemon.enroll(cryptoToken, groupId, timeout); in startEnrollment()299 IFingerprintDaemon daemon = getFingerprintDaemon(); in startPreEnroll() local300 if (daemon == null) { in startPreEnroll()305 return daemon.preEnroll(); in startPreEnroll()313 IFingerprintDaemon daemon = getFingerprintDaemon(); in startPostEnroll() local314 if (daemon == null) { in startPostEnroll()319 return daemon.postEnroll(); in startPostEnroll()343 IFingerprintDaemon daemon = getFingerprintDaemon(); in stopEnrollment() local[all …]
1201 for (String daemon : mDaemons) { in execute()1202 while (!SystemService.isStopped(daemon)) { in execute()1235 String daemon = mDaemons[i]; in execute() local1236 SystemService.start(daemon); in execute()1239 while (!SystemService.isRunning(daemon)) { in execute()1246 daemon, LocalSocketAddress.Namespace.RESERVED); in execute()1294 String daemon = mDaemons[i]; in execute() local1295 if (mArguments[i] != null && !SystemService.isRunning(daemon)) { in execute()1296 throw new IllegalStateException(daemon + " is dead"); in execute()1378 for (String daemon : mDaemons) { in execute()[all …]
26 # Specifies the JVM arguments used for the daemon process.35 org.gradle.daemon=true
47 <code>adb</code> device daemon runs on the device or emulator and provides a means for the48 <code>adb</code> host daemon to communicate with the device or emulator.</dd>71 <code>adb</code> device daemon allows communication with the VMs from an outside party.</p>73 <p>On your development machine, the <code>adb</code> host daemon communicates with the74 …<code>adb</code> device daemon and allows tools such as DDMS to communicate with the device or emu…75 The <code>adb</code> host daemon also allows you to access shell commands on the device as well as
22 Eclipse also takes care of starting the ADB host daemon for you, so you do not have to run this
53 VM's debugger, through the adb daemon (adbd) on the device. DDMS can now talk to the VM using a
10 # Specifies the JVM arguments used for the daemon process.
26 # Specifies the JVM arguments used for the daemon process.
25 # Specifies the JVM arguments used for the daemon process.
35 manages communication between the client and the adb daemon running on an emulator or device. </li>36 <li>A daemon, which runs as a background process on each emulator or device instance. </li>46 …5585, the range used by emulators/devices. Where the server finds an adb daemon, it sets up a conn…
263 <td>You can use this command even if the adb daemon in the emulated system is broken.
META-INF/ META-INF/MANIFEST.MF android/ android/databinding/ android/ ...
1149 <li><strong>installd hardening</strong> — The installd daemon does not run