/frameworks/base/docs/html/guide/topics/fundamentals/ |
D | services.jd | 97 android.app.Service#onStartCommand onStartCommand()} to allow components to start it and {@link 145 <dt>{@link android.app.Service#onStartCommand onStartCommand()}</dt> 161 procedures (before it calls either {@link android.app.Service#onStartCommand onStartCommand()} or 172 android.app.Service#onStartCommand onStartCommand()}), then the service 178 android.app.Service#onStartCommand onStartCommand()} is <em>not</em> called), then the service runs 191 android.app.Service#onStartCommand onStartCommand()}, as discussed later). For more information 267 android.app.Service#onStartCommand onStartCommand()} (in Android 2.0, 269 android.app.Service#onStartCommand onStartCommand()}).</p> 271 the {@link android.app.Service#onStartCommand onStartCommand()} documentation.</p> 277 {@link android.app.Service#onStartCommand onStartCommand()} method.</p> [all …]
|
D | bound-services.jd | 85 <em>or</em> {@link android.app.Service#onStartCommand onStartCommand()}, it's sometimes necessary to 650 started with {@link android.app.Service#onStartCommand onStartCommand()}). As such, you don't have 654 <p>However, if you choose to implement the {@link android.app.Service#onStartCommand 655 onStartCommand()} callback method, then you must explicitly stop the service, because the
|
/frameworks/base/packages/WAPPushManager/tests/src/com/android/smspush/unitTests/ |
D | ReceiverService.java | 45 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in ReceiverService
|
/frameworks/base/core/java/android/app/ |
D | IntentService.java | 129 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in IntentService
|
D | Service.java | 437 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in Service
|
D | ActivityThread.java | 2358 res = s.onStartCommand(data.args, data.flags, data.startId); in handleServiceArgs()
|
/frameworks/base/core/java/com/android/internal/util/ |
D | AsyncService.java | 94 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in AsyncService
|
/frameworks/base/test-runner/src/android/test/ |
D | ServiceTestCase.java | 192 mService.onStartCommand(intent, 0, mServiceId); in startService()
|
/frameworks/base/docs/html/guide/topics/testing/ |
D | service_testing.jd | 71 {@link android.app.Service#onStartCommand(Intent, int, int) onStartCommand()} do not normally 168 <code>Service.onStartCommand()</code>.
|
/frameworks/base/docs/html/resources/articles/ |
D | service-api-changes-starting-with.jd | 130 … the platform). It is replaced with a new {@link android.app.Service#onStartCommand(android.conten… 132 …tform is that it if it gets restarted because its process is killed, onStartCommand() will be call… 136 …e is START_STICKY and you must be prepared to deal with onStart() or onStartCommand() being called… 140 // platform. On 2.0 or later we override onStartCommand() so this 148 public int onStartCommand(Intent intent, int flags, int startId) {
|
/frameworks/base/core/java/com/android/internal/os/storage/ |
D | ExternalStorageFormatter.java | 79 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in ExternalStorageFormatter
|
/frameworks/base/tests/DumpRenderTree2/src/com/android/dumprendertree2/ |
D | ManagerService.java | 156 public int onStartCommand(Intent intent, int flags, int startId) { in onStartCommand() method in ManagerService
|
/frameworks/base/docs/html/sdk/api_diff/5/ |
D | missingSinces.txt | 225 NO DOC BLOCK: android.app.Service Method onStartCommand(android.content.Intent, int, int)
|
/frameworks/base/docs/html/guide/topics/media/ |
D | mediaplayer.jd | 294 public int onStartCommand(Intent intent, int flags, int startId) {
|
/frameworks/base/api/ |
D | current.txt | 3828 method public int onStartCommand(android.content.Intent, int, int);
|
D | 14.txt | 3828 method public int onStartCommand(android.content.Intent, int, int);
|