/frameworks/base/docs/html/distribute/googleplay/publish/ |
D | index.jd | 4 page.metaDescription=Get started publishing apps on Google Play. 17 …@docRoot}distribute/googleplay/publish/register.html" class="landing-page-link">Get started</a></p>
|
/frameworks/base/docs/html/tools/adk/ |
D | index.jd | 22 to use them, and how to get started building your own accessories for Android.</p> 26 <dd>Guide to getting started with the ADK released at Google I/O 2012.</dd> 29 <dd>Guide to getting started with the original ADK, released at Google I/O 2011.</dd>
|
/frameworks/base/docs/html/design/ |
D | index.jd | 28 <a href="/design/get-started/creative-vision.html" class="landing-page-link">Creative Vision</a> 30 <a id="hero-image" href="/design/get-started/creative-vision.html">
|
/frameworks/base/test-runner/src/android/test/ |
D | TestRunner.java | 101 started(test.toString()); in startTest() 152 void started(String className); in started() method 180 private void started(String className) { in started() method in TestRunner 184 mListeners.get(i).started(className); in started() 271 started(className); in missingTest() 296 started(className); in run() 353 started(test.toString()); in run() 510 started(test.toString()); in runSingleJunitTest()
|
D | TestPrinter.java | 48 public void started(String className) { in started() method in TestPrinter 110 started(test.toString()); in startTest()
|
/frameworks/base/docs/html/training/activity-testing/ |
D | activity-functional-testing.jd | 47 <li>Verifying that a target {@link android.app.Activity} is started when a 70 // Validate that ReceiverActivity is started 82 started, the {@link android.app.Instrumentation.ActivityMonitor ActivityMonitor} 85 the {@code ReceiverActivity} is indeed started, and that the hit count on the 93 …ified by the system whenever an {@link android.app.Activity} that matches your criteria is started. 116 // Validate that ReceiverActivity is started
|
/frameworks/base/core/java/android/view/animation/ |
D | AnimationSet.java | 375 boolean started = false; in getTransformation() 387 started = started || a.hasStarted(); in getTransformation() 391 if (started && !mStarted) { in getTransformation()
|
/frameworks/base/core/java/android/widget/ |
D | Chronometer.java | 208 public void setStarted(boolean started) { in setStarted() argument 209 mStarted = started; in setStarted()
|
/frameworks/base/docs/html/guide/components/ |
D | services.jd | 72 <dd>A service is "started" when an application component (such as an activity) starts it by 73 calling {@link android.content.Context#startService startService()}. Once started, a service 74 can run in the background indefinitely, even if the component that started it is destroyed. Usually, 75 a started service performs a single operation and does not return a result to the caller. 88 service can work both ways—it can be started (to run indefinitely) and also allow binding. 93 <p>Regardless of whether your application is started, bound, or both, any application component 140 requests that the service be started, by calling {@link android.content.Context#startService 141 startService()}. Once this method executes, the service is started and can run in the 179 Otherwise, if the service was started and is long-running, then the system will lower its position 181 killing—if your service is started, then you must design it to gracefully handle restarts [all …]
|
D | bound-services.jd | 13 <li>A bound service is destroyed once all clients unbind, unless the service was also started</li> 75 document, you can create a service that is both started and bound. That is, the service can be 76 started by calling {@link android.content.Context#startService startService()}, which allows the 79 <p>If you do allow your service to be started and bound, then when the service has been 80 started, the system does <em>not</em> destroy the service when all clients unbind. Instead, you must 93 started service.</p> 113 service was also started by {@link android.content.Context#startService startService()}).</p> 644 started with {@link android.app.Service#onStartCommand onStartCommand()}). As such, you don't have 650 service is now considered to be <em>started</em>. In this case, the service runs until the service 655 <p>Additionally, if your service is started and accepts binding, then when the system calls [all …]
|
D | tasks-and-back-stack.jd | 100 never rearranged, only pushed and popped from the stack—pushed onto the stack when started by 141 started Task A. Now, Task A comes to the 145 that started that task (or by selecting the app's task from the <em>recent apps</em> screen). 219 activities started in succession in the same task and in a "last in, first out" stack—works 223 started (instead of being placed within the current task); or, when you start an activity, you want 314 which it was started and routes the intent to it. The activity can be instantiated multiple times, 351 any activities started by this one open in a separate task.</dd> 365 started it, the <em>Back</em> button always takes the user to the previous activity. However, if you 405 <dd>If the activity being started is the current activity (at the top of the back stack), then 412 <dd>If the activity being started is already running in the current task, then instead [all …]
|
/frameworks/base/docs/html/training/system-ui/ |
D | index.jd | 28 <a class="notice-designers wide" href="{@docRoot}design/get-started/ui-overview.html#system-bars"> 42 <p>The <a href="https://developer.android.com/design/get-started/ui-overview.html#system-bars">
|
/frameworks/base/docs/html/training/camera/ |
D | cameradirect.jd | 95 <p>To get started with displaying a preview, you need preview class. The 123 image preview can be started, as shown in the next section.</p> 157 be started before you can take a picture. 182 started before you can take a picture. 202 method to take a picture once the preview is started. You can create {@link
|
/frameworks/base/docs/html/about/ |
D | start.jd | 58 types of devices your app supports. Everything you need to get started with this process is 63 <p style="clear:both">Now that you know what's available, get started by installing the <a
|
/frameworks/base/docs/html/sdk/installing/ |
D | index.jd | 16 <h3>Getting started on Windows</h3> 42 <h3>Getting started on Mac</h3> 66 <h3>Getting started on Linux</h3>
|
D | adding-packages.jd | 38 To get started, read <a href="{@docRoot}training/basics/firstapp/index.html"
|
/frameworks/base/docs/html/training/sharing/ |
D | receive.jd | 82 the corresponding activity (<code>.ui.MyActivity</code> in the example above) will be started. It 91 contents to determine what to do next. Keep in mind that if this activity can be started from other 114 // Handle other intents, such as being started from the home screen
|
/frameworks/base/docs/html/training/basics/intents/ |
D | filters.jd | 82 to the user gesture or location from which it's started. There are several different categories 165 {@link android.content.Intent} that started the activity. You can do so at any time during the 178 // Get the intent that started this activity 231 <p class="note"><strong>Note:</strong> There's no need to check whether your activity was started 235 android.app.Activity#setResult(int,Intent) setResult()} if the intent that started your activity
|
/frameworks/base/docs/html/google/play-services/ |
D | plus.jd | 64 <p>To get started, <a href="{@docRoot}google/play-services/setup.html">set up</a> 73 href="https://developers.google.com/+/mobile/android/getting-started">Getting Started with
|
/frameworks/base/docs/html/guide/practices/ui_guidelines/ |
D | activity_task_design.jd | 52 <li>You can enable activities in your application to be started from intents in other applications.… 196 launched (started) independently, and the user or system can start, 287 <a href=#tasks title=task>task</a> (as long as that task was started 326 It is often, but not necessarily, started from the application 329 choosing the icon for its root activity the same way they started the 375 activity in a different task (Email), because it was not started from 504 started it. The next example illustrates re-use of an activity that 539 activity does not return anything to the Gallery activity that started it. 946 started by the user touching an icon in <em>application 988 is closed loop, where the activity being started must either [all …]
|
/frameworks/base/docs/html/training/location/ |
D | location-testing.jd | 176 in a started {@link android.app.Service}. By using a started service, the provider app is able 215 background thread and the started {@link android.app.Service} continue to run, even if the 223 started {@link android.app.Service} switches from mock mode to normal mode and then 245 While the started {@link android.app.Service} is running, it also posts notifications with the 278 locations by clicking <b>Stop test</b>. This forces the started {@link android.app.Service}
|
/frameworks/base/packages/SettingsProvider/src/com/android/providers/settings/ |
D | SettingsBackupAgent.java | 846 boolean started = false; in getWifiSupplicant() 849 if (!started && line.startsWith("network")) { in getWifiSupplicant() 850 started = true; in getWifiSupplicant() 852 if (started) { in getWifiSupplicant()
|
/frameworks/base/docs/html/guide/practices/app-design/ |
D | index.jd | 6 <p>The documents below help you learn the nuances of Android and get started building great applica…
|
/frameworks/base/docs/html/training/notify-user/ |
D | index.jd | 72 navigation for an {@link android.app.Activity} started from a notification.
|
/frameworks/base/core/java/android/bluetooth/ |
D | BluetoothAdapter.java | 1770 boolean started = false; in waitForRegisteration() 1783 started = (mLeHandle > 0); in waitForRegisteration() 1785 return started; in waitForRegisteration()
|