| /development/samples/Home/src/com/example/android/home/ |
| ApplicationInfo.java | 24 * Represents a launchable application. An application is made of a name (or title), an intent
29 * The application name.
34 * The intent used to start the application.
39 * The application icon.
49 * Creates the application intent based on a component name and various launch flags.
|
| /development/samples/Spinner/ |
| AndroidManifest.xml | 18 Declares the contents of this Android application. The "namespace"
20 "package" attribute provides a unique Android name for the application.
21 If you use this file as a template in your own application, you must change
37 Sets the application's user-readable label
39 <application android:label="@string/app_name">
54 </application>
|
| /development/samples/SpinnerTest/ |
| AndroidManifest.xml | 18 Declare the contents of this Android application. The "namespace"
20 "package" attribute provides a unique Android name for the application.
21 If you use this file as a template in your own application, you must change
30 <application android:label="@string/app_name">
36 </application>
38 This declares that this application uses the instrumentation test runner targeting
|
| /frameworks/native/opengl/libs/GLES_trace/ |
| DESIGN.txt | 19 Application runtime:
21 While the application is running, all its GLES calls are directly routed to their corresponding
27 Application shutdown:
29 Currently, the application is killed when the user stops tracing from the frontend GUI. We need
30 to explore if a more graceful method of stopping the application, or detaching tracing from the
31 application is required.
|
| /frameworks/base/docs/html/guide/google/gcm/ |
| gcm.jd | 11 <li>Learn the basic features of a GCM application.</li>
12 <li>Understand the role of the 3rd-party application server, and how to send messages and process results.</li>
40 <li><a href="#server">Role of the 3rd-party Application Server</a>
61 devices. This could be a lightweight message telling the Android application
66 Android application running on the target device.</p>
81 <li>It allows 3rd-party application servers to send messages to
84 <li>An Android application on an Android device doesn't need to be running to receive
85 messages. The system will wake up the Android application via Intent broadcast when the message arrives, as long as the application is set up with the proper
89 Android application, which has full control of how to handle it. For example, th
[all...] |
| adv.jd | 50 <p class="note"><strong>Note:</strong> There is a limit on how many messages can be stored without collapsing. That limit is currently 100. If the limit is reached, all stored messages are discarded. Then when the device is back online, it receives a special message indicating that the limit was reached. The application can then handle the situation properly, typically by requesting a full sync.</p>
54 <p>Finally, when GCM attempts to deliver a message to the device and the application was uninstalled, GCM will discard that message right away and invalidate the registration ID. Future attempts to send a message to that device will get a <code>NotRegistered</code> error. See <a href="#unreg">How Unregistration Works</a> for more information.</p>
61 scheme. Messages are throttled on a per application and per <a href="#collapsible">collapse
62 key</a> basis (including non-collapsible messages). Each application
65 the device. If an application collapse key exhausts its supply of
69 of message delivery for an application collapse key that sends a large
71 queue of an application collapse key may be delivered before the time
77 <p>Whenever the application receives a <code>com.google.android.c2dm.intent.REGISTRATION</code> intent with a <code>registration_id</code> extra, it should save the ID for future use, pass it to the 3rd-party server to complete the registration, and keep track of whether the server completed the registration. If the server fails to complete the registration, it should try again or unregister from GCM.</p>
80 <li>Application update</li>
84 <p>When an application is updated, it should invalidate its existing registration ID, as it is not guaranteed to work wit (…)
[all...] |
| /frameworks/base/docs/html/tools/workflow/publishing/ |
| publishing.jd | 47 account, and upload your application. For more information about required assets, listing details,
57 <p>One of the most effective ways to get your application into users' hands is to
58 publish it on an application marketplace like Google Play. Publishing on Google Play is a
77 <a href="{@docRoot}guide/google/play/licensing/index.html">application licensing</a>.</p>
92 <p>Publishing your application on Google Play is a simple process that involves three basic
116 href="{@docRoot}tools/publishing/preparing.html">prepare your application for release</a> before you
117 can publish it on Google Play. When you prepare your application for release you configure it for
118 release and build it in release mode. Building in release mode signs your application's {@code .apk}
119 file with your private release key. You cannot publish an application on Google Play unless it is
127 application and a high resolution application icon. The screenshots are displayed on the detail
[all...] |
| /external/bluetooth/bluedroid/bta/include/ |
| bta_hl_co.h | 44 ** application ID
46 ** Parameters app_id - application ID
48 ** by the application
61 ** Parameters app_id - application ID
76 ** Parameters app_id - HDP application ID
97 ** Parameters app_id - HDP application ID
114 ** Parameters app_id - HDP application ID
129 ** Parameters app_id - HDP application ID
144 ** Parameters app_id - HDP application ID
162 ** Parameters app_id - HDP application I
[all...] |
| /frameworks/base/docs/html/distribute/ |
| open.jd | 30 <h2 id="publishing-email">Distributing your application through email</h2>
38 an application via email.
42 <p>The easiest and quickest way to release your application is to send it to users through
43 email. To do this, you prepare your application for release and then attach it to an email
46 button in the email message (see figure 1). Users can install your application by touching the
52 email with the native Gmail application.</p>
54 <p>Distributing applications through email is convenient if you are sending your application to
56 distribution; that is, anyone you send your application to can simply forward it to someone else.</p>
63 application for release in the normal way. Then all you need to do is host the
73 <p>Although it is relatively easy to release your application on your ow
[all...] |
| /frameworks/base/core/java/android/webkit/ |
| WebViewClient.java | 28 * Give the host application a chance to take over the control when a new
32 * means the host application handles the url, while return false means the
37 * @return True if the host application wants to leave the current WebView
45 * Notify the host application that a page has started loading. This method
60 * Notify the host application that a page has finished loading. This method
72 * Notify the host application that the WebView will load the resource
82 * Notify the host application of a resource request and allow the
83 * application to return the data. If the return value is null, the WebView
102 * Notify the host application that there have been an excessive number of
103 * HTTP redirects. As the host application if it would like to continu
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-sdk-element.jd | 16 <li><a href="#fc">Application forward compatibility</a></li>
17 <li><a href="#bc">Application backward compatibility</a></li>
40 <dd>Lets you express an application's compatibility with one or more versions of the Android platform,
41 by means of an API Level integer. The API Level expressed by an application will be compared to the
64 attributes in each application's manifest to establish its version-compatibility
65 range, then shows or hides the application based on a comparison with the API
77 for the application to run. The Android system will prevent the user from installing
78 the application if the system's API Level is lower than the value specified in
83 application is compatible with all versions of Android. If your application i
[all...] |
| /frameworks/base/docs/html/tools/projects/ |
| projects-eclipse.jd | 33 an .apk file for installation. You need to create an Android project for any application that you
66 Build Target specifies which Android platform you'd like your application built against.
68 <p>Select the lowest platform with which your application is compatible.</p>
79 <li>Enter an <em>Application name</em>. This is the human-readable title for your
80 application — the name that will appear on the Android device.</li>
90 Level required to properly run your application. Entering this here automatically sets
110 as you would a new application project.</p>
112 <p>When you are creating the library project, you can select any application name, package, and
132 <p>You can also convert an existing application project into a library. To do so, simply open the
133 Properties for the project and select the "is Library" checkbox. Other application projects ca
[all...] |
| /tools/motodev/src/plugins/preflighting.core/src/com/motorolamobility/preflighting/core/applicationdata/ |
| ApplicationData.java | 37 * This Class represents the Application either in project or APK format that
41 * Application. From that node is possible to navigate through the Application
87 * Initialize the class properties by reading the Application tree
167 * Return the Application root element.
168 * @return The Element which represents the Application root element.
185 * Return the Application root element path.
186 * @return A string with the Application root element path.
194 * Set the Application root element path.
254 * @return A list of certificates, empty if the application (project or APK) does not have any certificates.
[all...] |
| /frameworks/base/docs/html/guide/google/play/licensing/ |
| adding-licensing.jd | 2 parent.title=Application Licensing
42 <li><a href="#app-publishing">Publishing a Licensed Application</a>
62 <li><a href="#manifest-permission">Adding the licensing permission</a> your application's manifest.</li>
66 <li><a href="#impl-lc">Adding code to check the license</a> in your application's main
73 integration, you should be able to compile your application successfully and you
85 <p>To use the Google Play application for sending a license check to the
86 server, your application must request the proper permission,
87 <code>com.android.vending.CHECK_LICENSE</code>. If your application does
91 <p>To request the licensing permission in your application, declare a <a
98 <p>For example, here's how the LVL sample application declares the permission
[all...] |
| /frameworks/base/docs/html/tools/building/ |
| building-cmdline.jd | 20 <li><a href="#Signing">Application Signing</a></li>
34 <p>There are two ways to build your application using the Ant build script: one for
35 testing/debugging your application — <em>debug mode</em> — and one for building your
36 final package for release — <em>release mode</em>. Regardless of which way you build your application,
44 development device. You cannot distribute an application that is signed with a debug key.
50 you're ready to release your application and share it with end-users. That document describes the
71 <p>For immediate application testing and debugging, you can build your application in debug mode
73 application with a debug key and optimize the package with {@code zipalign}.</p>
93 the latest version of the application.</p
[all...] |
| /development/apps/BuildWidget/ |
| AndroidManifest.xml | 8 <application android:icon="@drawable/icon" android:label="@string/app_name">
16 </application>
|
| /development/ndk/platforms/android-14/samples/native-media/ |
| AndroidManifest.xml | 7 <application android:icon="@drawable/icon" android:label="@string/app_name">
16 </application>
|
| /development/ndk/platforms/android-9/samples/native-plasma/ |
| AndroidManifest.xml | 7 <application android:label="@string/app_name"
18 </application>
|
| /development/ndk/samples/hello-neon/ |
| build.properties | 18 # The name of your application package as defined in the manifest.
20 application.package=com.example.neon
|
| /development/ndk/samples/hello-neon/src/com/example/neon/ |
| HelloNeon.java | 25 * with this application.
29 /* this is used to load the 'helloneon' library on application
|
| /development/samples/ApiDemos/ |
| README.txt | 1 The API Demos application includes a variety of small applications
9 - Persistent application state
|
| /development/samples/CrossCompatibility/ |
| AndroidManifest.xml | 11 <application android:icon="@drawable/icon" android:label="@string/app_name">
20 </application>
|
| /development/samples/SoftKeyboard/ |
| AndroidManifest.xml | 3 <application android:label="@string/ime_name">
18 </application>
|
| /development/samples/ToyVpn/ |
| _index.html | 1 <p>ToyVPN is a sample application that shows how to build a VPN client using the <a href="../../../reference/android/net/VpnService.html">VpnService</a> class introduced in API level 14.</p>
3 <p>This application consists of an Android client and a sample implementation of a server. It performs IP over UDP and is capable of doing seamless handover between different networks as long as it receives the same VPN parameters.</p>
|
| /development/samples/USB/AdbTest/ |
| AndroidManifest.xml | 7 <application>
22 </application>
|
