| /external/robolectric/src/test/java/com/xtremelabs/robolectric/bytecode/ |
| CustomRobolectricTestRunnerTest.java | 3 import android.app.Application;
32 assertNotNull(Robolectric.application);
33 assertEquals(CustomApplication.class, Robolectric.application.getClass());
70 @Override protected Application createApplication() {
75 public static class CustomApplication extends Application {
|
| /frameworks/base/docs/html/guide/faq/ |
| framework.jd | 1 page.title=Android Application Framework FAQ
7 application run in a single process?</a></li>
9 an application process?</a></li>
16 <li><a href="#6">How to avoid getting the Application not
18 <li><a href="#7">How does an application know if a package is
25 <h2>Do all the Activities and Services of an application run in a
28 <p>All Activities and Services in an application run in a single process by
37 <h2>Do all Activities run in the main thread of an application
40 <p>By default, all of the application code in a single process runs
53 application?</h2
[all...] |
| /frameworks/base/tests/HugeBackup/ |
| AndroidManifest.xml | 17 <!-- Declare the contents of this Android application. The namespace
19 supplies a unique name for the application. When writing your
20 own application, the package name must be changed from "com.example.*"
30 <application android:label="Huge Backup"
43 </application>
|
| /frameworks/native/opengl/tests/gl2_cameraeye/ |
| AndroidManifest.xml | 17 <!-- Declare the contents of this Android application. The namespace
19 supplies a unique name for the application. When writing your
20 own application, the package name must be changed from "com.example.*"
28 <application android:label="@string/gl2cameraeye_name">
35 </application>
|
| /prebuilts/tools/darwin-x86/sdl/include/SDL/ |
| SDL_active.h | 25 * Include file for SDL application focus event handling
40 /** @name The available application states */
44 #define SDL_APPACTIVE 0x04 /**< The application is active */
49 * This function returns the current state of the application, which is a
52 * see your application, otherwise it has been iconified or disabled.
|
| /prebuilts/tools/linux-x86/sdl/include/SDL/ |
| SDL_active.h | 25 * Include file for SDL application focus event handling
40 /** @name The available application states */
44 #define SDL_APPACTIVE 0x04 /**< The application is active */
49 * This function returns the current state of the application, which is a
52 * see your application, otherwise it has been iconified or disabled.
|
| /prebuilts/tools/windows/sdl/include/SDL/ |
| SDL_active.h | 25 * Include file for SDL application focus event handling
40 /** @name The available application states */
44 #define SDL_APPACTIVE 0x04 /**< The application is active */
49 * This function returns the current state of the application, which is a
52 * see your application, otherwise it has been iconified or disabled.
|
| /frameworks/base/docs/html/guide/practices/ |
| optimizing-for-3.0.jd | 65 you to enhance your user's experience on tablets and similar devices. Any application you've already
69 your application looks and works great on the new platform and new device form-factors.</p>
71 <p>This document shows how you can optimize your existing application for Android 3.0 and
72 maintain compatibility with older versions or upgrade your application completely with new APIs.</p>
83 <p>Read this section if you have an existing application and want to
85 manifest file to declare support for Android 3.0, test your application on the new platform, and
89 <p>Read this section if you want to upgrade your application to use APIs introduced in
90 Android 3.0 or create a new application targeted to tablets and similar devices. Compared to
93 application that's fully enhanced for tablets.</p></li>
97 application based on screen configuration</a>.</li
[all...] |
| /frameworks/base/docs/html/guide/topics/manifest/ |
| uses-feature-element.jd | 16 <li><a href="#testing">Testing the features required by your application</a></li>
38 <p style="margin-top:1em;">By specifying the features that your application requires,
39 you enable Google Play to present your application only to users whose
40 devices meet the application's feature requirements, rather than presenting it
66 application.
70 application depends. The element offers a <code>required</code> attribute that
71 lets you specify whether your application requires and cannot function without
75 application describe the device-variable features that it uses.</p>
77 <p>The set of available features that your application declares corresponds to
84 element, so if your application requires multiple features, it would declar
[all...] |
| service-element.jd | 20 <dd><code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code></dd>
28 of the application's components. Unlike activities, services lack a
47 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> element has its own
48 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code> attribute that applies to all
49 application components, including services. The
50 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> and {@code <service>}
60 components of the same application or applications
[all...] |
| compatible-screens-element.jd | 23 <dd itemprop="description">Specifies each screen configuration with which the application is compatible. Only one instance
26 specifies a specific screen size-density combination with which the application is compatible.
30 by external services (such as Google Play) to better understand the application's compatibility
32 <em>not</em> declared in this element is a screen with which the application is <em>not</em>
33 compatible. Thus, external services (such as Google Play) should not provide the application to
38 application, by not allowing users to install your application if they have a device with a screen
40 application absolutely does not work with specific screen configurations. Instead of using this
46 <p>If you want to set only a minimum screen <em>size</em> for your your application, then you
48 <supports-screens>}</a> element. For example, if you want your application to be availabl
[all...] |
| supports-gl-texture-element.jd | 38 the application.
40 <p>An application "supports" a GL texture compression format if it is capable of
42 application is installed on a device. The application can provide the
48 <code>android:name</code> attribute. If your application supports multiple
58 (such as Google Play) or applications can check your application's
60 interacting with your application. For this reason, it's very important that
62 your application is capable of supporting. </p>
69 <p>Assuming that the application is built with SDK Platform Tools r3 or higher,
79 <dd>Specifies a single GL texture compression format supported by the application,
[all...] |
| /frameworks/base/docs/html/training/in-app-billing/ |
| list-iab-products.jd | 6 previous.title=Preparing Your In-app Billing Application
32 <p>Before publishing your In-app Billing application, you'll need to define the product list of digital goods available for purchase in the <a href="https://play.google.com/apps/publish/">Google Play Developer Console</a>. </p>
35 <p>From the Developer Console, you can define product information for in-app products and associate the product list with your application.</p>
39 <li>Build a signed APK file for your In-app Billing application. To learn how to build and sign your APK, see <a href="{@docRoot}tools/publishing/preparing.html#publishing-build">Building Your Application for Release</a>. Make sure that you are using your final (not debug) certificate and private key to sign your application.
41 <li>In the Developer Console, open the application entry that you created earlier.</li>
44 <li>Click on the option to add a new product, then complete the form to specify the product information such as the item?s unique product ID (also called its <em>SKU</em>), description, price, and country availability. Note down the product ID since you might need this information to query purchase details in your application later. <p class="note"><strong>Important:</strong> The In-app Billing Version 3 service only supports managed in-app products, so make sure that you specify that the purchase type is 'Managed' when you add new items to your product list in the Developer Console.</p></li>
45 <li>Once you have completed the form, activate the product so that your application can purchase it. <p class="note"><strong>Warning:</strong> It may take up to 2-3 hours after uploading the APK for Google Play to recognize your updated APK version. If you try to test your application before your uploaded APK is recognized by Google Play, your application will receive a ?purchase c (…)
[all...] |
| /frameworks/base/docs/html/guide/topics/data/ |
| install-location.jd | 11 <li>You can allow your application to install on the device's external storage.</li>
34 <p>Beginning with API Level 8, you can allow your application to be installed on the
36 for your application with the <a
39 <em>not</em> declare this attribute, your application will be installed on the internal storage
42 <p>To allow the system to install your application on the external storage, modify your
55 <p>If you declare "{@code preferExternal}", you request that your application be installed on the
56 external storage, but the system does not guarantee that your application will be installed on
58 storage. The user can also move your application between the two locations.</p>
60 <p>If you declare "{@code auto}", you indicate that your application may be installed on the
62 decide where to install your application based on several factors. The user can also move you
[all...] |
| /packages/apps/PackageInstaller/res/values-fr/ |
| strings.xml | 23 <string name="security_settings_desc" msgid="2706691034244052604">"Autoriser cette application à :"</string>
27 <string name="install_done" msgid="3682715442154357097">"Application installée."</string>
28 <string name="install_confirm_question" msgid="7295206719219043890">"Voulez-vous installer cette application ? Elle pourra :"</string>
29 <string name="install_confirm_question_no_perms" msgid="5918305641302873520">"Voulez-vous installer cette application ? Elle n\'exige aucun accès particulier."</string>
30 <string name="install_confirm_question_update" msgid="4624159567361487964">"Voulez-vous installer une mise à jour pour cette application ? Vos données existantes seront conservées. L\'application mise à jour pourra :"</string>
31 <string name="install_confirm_question_update_system" msgid="1302330093676416336">"Voulez-vous installer une mise à jour pour cette application intégrée ? Vos données existantes seront conservées. L\'application mise à jour pourra :"</string>
32 <string name="install_confirm_question_update_no_perms" msgid="4885928136844618944">"Voulez-vous installer une mise à jour pour cette application ? Vos données ne seront pas perdues. Aucun droit d\'accès spécial n\'est requis."</string>
33 <string name="install_confirm_question_update_system_no_perms" msgid="7676593512694724374">"Voulez-vous installer une mise à jour pour cette application intégrée ? Vos données existantes ne seront pas perdues. Aucun droit d\'accès spécial n\'est requi (…)
[all...] |
| /frameworks/base/docs/html/guide/topics/resources/ |
| localization.jd | 2 parent.title=Application Resources
37 your application should handle text, audio files, numbers, currency, and
38 graphics in ways appropriate to the locales where your application will be used.
42 applications. The principles apply whether you are developing your application
51 localized aspects of your application as much as possible from the core Java
55 <li>You can put most or all of the <em>contents</em> of your application's
73 data that your Android application needs. An application can include multiple
75 user runs the application, Android automatically selects and loads the
87 <strong>When you write your application:</strong>
[all...] |
| /development/samples/SkeletonApp/ |
| AndroidManifest.xml | 18 used by the system to determine how to start your application and
21 <!-- Declare the contents of this Android application. The namespace
23 supplies a unique name for the application. When writing your
24 own application, the package name must be changed from "com.example.*"
30 <!-- This package contains an application... The 'label' is the name
31 to display to the user for the overall application, and provides
34 <application android:label="@string/skeleton_app">
36 <!-- An Activity in the application - this is something the user
57 </application>
|
| /external/qemu/android/ |
| multitouch-port.h | 24 * application running on an Android device that provides touch events, and is
31 * NOTE: Application on the device side depends on these values. Any changes
32 * made here must be reflected in the app too. Application location is at
45 * region. This descriptor is also sent to the MT emulation application on the
48 * NOTE: Application on the device side depends on that structure. Any changes
49 * made here must be reflected in the app too. Application location is at
82 * application on the device.
89 /* Sends framebuffer update to the multi-touch emulation application, running on
96 * application on the device.
|
| /frameworks/native/opengl/libs/GLES_trace/ |
| DESIGN.txt | 16 Application runtime:
18 While the application is running, all its GLES calls are directly routed to their corresponding
24 Application shutdown:
26 Currently, the application is killed when the user stops tracing from the frontend GUI. We need
27 to explore if a more graceful method of stopping the application, or detaching tracing from the
28 application is required.
31 Enabling tracing while the application is running:
33 In order to allow tracing of an already running application, we allow DdmServer to enable
34 OpenGL tracing. In such a case, the application already has its GL hooks set up to point to the
|
| /packages/apps/UnifiedEmail/src/com/android/mail/utils/ |
| HelpUrl.java | 27 * Constructs the URL for the context sensitive help page for this mail application. The URL will be
28 * specific to the user's language, application, application version and topic. For example:
31 * help page for version 1 of the mail application</p>
33 * french help page for version 2 of the mail application</p>
41 * Constructs the URL for the context sensitive help page for this mail application.
45 * @return Url for the Help page that is specific to a language, application, version and topic
75 LogUtils.e(LOG_TAG, "Error finding package name for application" + packageName);
76 throw new IllegalStateException("unable to determine package name for application");
|
| /prebuilts/python/darwin-x86/2.7.5/lib/python2.7/plat-mac/lib-scriptpackages/SystemEvents/ |
| Power_Suite.py | 76 class application(aetools.ComponentItem): class in inherits:aetools.ComponentItem
77 """application - The System Events application """
90 """properties - every property of the System Events application """
106 applications = application
107 application._superclassnames = []
113 application._privpropdict = {
118 application._privelemdict = {
136 'capp' : application,
|
| /frameworks/base/docs/html/google/backup/ |
| index.jd | 9 higher. The backup service is <em>not</em> designed for synchronizing application data with other
11 application lifecycle.</p>
17 transparent to your application.</p>
23 <p class="note"><strong>Note:</strong> Registering your application with Android Backup
26 data backup in your application, then it will back up using whichever transport is enabled
27 on the device. Registering with Android Backup Service allows your application to back up
42 <application>
46 </application>
51 <code><application></code> element.</p>
53 <p>When a device that uses Android Backup Service runs your application,
[all...] |
| /frameworks/base/docs/html/tools/devices/ |
| index.jd | 39 To thoroughly test your application, you should create an AVD for each general device configuration
40 (for example, different screen sizes and platform versions) with which your application is compatible
41 and test your application on each one.</p>
46 <li>The API Level of the target is important, because your application will not be able to run
47 on a system image whose API Level is less than that required by your application, as specified
49 <code>minSdkVersion</code></a> attribute of the application's manifest file. For more
50 information about the relationship between system API Level and application
55 by your application, because it allows you to test the
56 forward-compatibility of your application. Forward-compatibility testing ensures that, when
57 users who have downloaded your application receive a system update, your application wil
[all...] |
| /frameworks/base/docs/html/tools/testing/ |
| activity_test.jd | 57 <a href="#InstallCompletedTestApp">Installing the Completed Test Application File</a>
82 instrumentation to give you control over your main application while you are testing it. The entire Android testing environment is discussed in the document
86 This tutorial demonstrates the Android testing tools by presenting a simple Android application and then leading you step-by-step through the creation of a test application for it.
87 The test application demonstrates these key points:
91 An Android test is itself an Android application that is linked to the application under test by entries in its <code>AndroidManifest.xml</code> file.
94 Instead of Android components, an Android test application contains one or more test cases. Each of these is a separate class definition.
100 Android test case classes for activities extend JUnit and also connect you to the application under test with instrumentation. You can send keystroke or touch events directly to the UI.
103 You choose an Android test case class based on the type of component (application, activity, content provider, or service) you are testing
[all...] |
| /external/libnfc-nxp/src/ |
| phOsalNfc_Timer.h | 59 * OSAL timer message .This message type will be posted to calling application thread.
104 * When a timer is created, it is not started by default. The application has to
113 * Application,phOsalNfc;
114 * Application=>phOsalNfc [label="phOsalNfc_Timer_Create()",URL="\ref phOsalNfc_Timer_Create"];
115 * Application<<phOsalNfc [label="Returns Valid timer ID"];
136 * \param[in] Application_callback Application Callback interface to be called
140 * Application,phOsalNfc;
141 * Application=>phOsalNfc [label="phOsalNfc_Timer_Create()", URL="\ref phOsalNfc_Timer_Create"];
142 * Application<<phOsalNfc [label="TIMERID"];
143 * Application=>phOsalNfc [label="phOsalNfc_Timer_Start(TIMERID, TIMEOUT, CB)", URL="\ref phOsalNfc_Timer_Start"]
[all...] |
