/frameworks/base/docs/html/google/play/billing/ |
api.jd | 46 <p>Managed in-app products are items that have their ownership information tracked and managed by Google Play. When a user purchases a managed in-app item, Google Play stores the purchase information for each item on a per-user basis. This enables you to later query Google Play at any time to restore the state of the items a specific user has purchased. This information is persistent on the Google Play servers even if the user uninstalls the application or if they change devices.</p> 47 <p>If you are using the Version 3 API, you can also consume managed items within your application. You would typically implement consumption for items that can be purchased multiple times (such as in-game currency, fuel, or magic spells). Once purchased, a managed item cannot be purchased again until you consume the item, by sending a consumption request to Google Play. To learn more about in-app product consumption, see <a href="#consume">Consuming Items</a></p> 72 <li>Your application sends a {@code isBillingSupported} request to Google Play to determine that the target version of the In-app Billing API that you are using is supported. </li> 73 <li>When your application starts or user logs in, it's good practice to check with Google Play to determine what items are owned by the user. To query the user's in-app purchases, send a {@code getPurchases} request. If the request is successful, Google Play returns a {@code Bundle} containing a list of product IDs of the purchased items, a list of the individual purchase details, and a list of the signatures for the purchases.</li> 74 <li>Usually, you'll want to inform the user of the products that are available for purchase. To query the details of the in-app products that you defined in Google Play, your application can send a {@code getSkuDetails} request. You must specify a list of product IDs in the query request. If the request is successful, Google Play returns a {@code Bundle} containing product details including the product?s price, title, description, and the purchase type. 76 <li>If an in-app product is not owned by the user, you can initiate a purchase for it. To start a purchase request, your application sends a {@code getBuyIntent} request, specifying the product ID of the item to purchase, along with other parameters. You should record the product ID when you create a new in-app product in the Developer Console. 78 <li>Google Play returns a {@code Bundle} that contains a {@code PendingIntent} which you application uses to start the checkout UI for the purchase.</li> 79 <li>Your application launches the pending intent by calling the {@code startIntentSenderForResult} method.</li> 92 application can query the user's purchase information when needed. When the user 105 <p>To retrieve the list of product's owned by the user, your application sends a {@code getPurchases} call to Google Play. Your application can make a consumption request (…) [all...] |
/frameworks/base/docs/html/guide/topics/manifest/ |
provider-element.jd | 30 <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> 42 application. All content providers in your application must be defined in a 46 You only declare content providers that are part of your application. Content providers in 47 other applications that you use in your application should not be declared. 100 The <code><a href="{@docRoot}guide/topics/manifest/application-element.html"><application></a></code> element has its own 101 <code><a href="{@docRoot}guide/topics/manifest/application-element.html#enabled">enabled</a></code> attribute that applies to all 102 application components, including content providers. The [all...] |
/frameworks/base/docs/html/guide/topics/data/ |
backup.jd | 57 application data to remote "cloud" storage, in order to provide a restore point for the 58 application data and settings. If a user performs a factory reset or converts to a new 59 Android-powered device, the system automatically restores your backup data when the application 61 application settings. This process is completely transparent to the user and does not affect the 62 functionality or user experience in your application.</p> 64 <p>During a backup operation (which your application can request), Android's Backup Manager ({@link 65 android.app.backup.BackupManager}) queries your application for backup data, then hands it to 68 returns it to your application so your application can restore the data to the device. It's 69 possible for your application to request a restore, but that shouldn't be necessary—Androi [all...] |
/external/chromium_org/content/common/ |
plugin_list_unittest.cc | 19 const char* kFooMimeType = "application/x-foo-mime-type"; 97 // application/octet-stream. 99 "application/octet-stream", 209 "application/x-java-vm:class,jar:IcedTea;application/x-java" 210 "-applet:class,jar:IcedTea;application/x-java-applet;versio" 211 "n=1.1:class,jar:IcedTea;application/x-java-applet;version=" 212 "1.1.1:class,jar:IcedTea;application/x-java-applet;version=" 213 "1.1.2:class,jar:IcedTea;application/x-java-applet;version=" 214 "1.1.3:class,jar:IcedTea;application/x-java-applet;version= [all...] |
/external/chromium_org/tools/telemetry/telemetry/core/platform/ |
android_platform_backend.py | 158 def LaunchApplication(self, application, parameters=None): 159 if application in _HOST_APPLICATIONS: 160 self._host_platform_backend.LaunchApplication(application, parameters) 164 self._adb.RunShellCommand('am start ' + parameters + ' ' + application) 166 def IsApplicationRunning(self, application): 167 if application in _HOST_APPLICATIONS: 168 return self._host_platform_backend.IsApplicationRunning(application) 169 return len(self._adb.ExtractPid(application)) > 0 171 def CanLaunchApplication(self, application): 172 if application in _HOST_APPLICATIONS [all...] |
/frameworks/base/docs/html/guide/practices/ui_guidelines/ |
icon_design_launcher.jd | 39 <p>A launcher icon is a graphic that represents your application. Launcher icons are used by 41 represent shortcuts into your application (for example, a contact shortcut icon that opens detail 49 across the range of devices on which your application can be installed. See <a 53 <p>A high-resolution version of your application launcher icon is also required by Google Play 54 for use in application listings. For more details on this, see <a 55 href="#icons_in_market">Application Icons on Google Play</a> below.</p> 81 <p>Application launcher icons have three primary goals:</p> 99 <li>Avoid including the application name in the icon. The app name will always be displayed 115 icon; for more details on this, see <a href="#icons_in_market">Application Icons in Google 144 <p>Below are some "do and don't" examples to consider when creating icons for your application.</p [all...] |
activity_task_design.jd | 52 <li>You can enable activities in your application to be started from intents in other applications.</li> 92 <li><a href="{@docRoot}guide/components/fundamentals.html">Application Fundamentals</a></li> 99 This document describes core principles of the Android application 101 interaction and application designers as well as application 110 and what control they give you over the UI of your application. 125 complement to the <a href="{@docRoot}guide/components/fundamentals.html">Application 148 An Android <em>application</em> typically consists of one or more 159 Android has an application launcher available at the Home screen, 161 which the user can pick to start an application [all...] |
/ndk/build/core/ |
add-application.mk | 16 # this script is used to record an application definition in the 20 # variable named '_application_mk' which points to a given Application.mk 22 # to describe the application to the build system, and the rest of the 125 $(call ndk_log,Application $(_app) targets unknown platform '$(_bad_platform)') 161 $(call __ndk_info,Application $(_app) targets unknown ABI '$(_bad_abis)') 192 # Determine whether the application should be debuggable. 201 $(call ndk_log,Application '$(_app)' forced debuggable through NDK_DEBUG) 203 $(call ndk_log,Application '$(_app)' forced *not* debuggable through NDK_DEBUG) 214 $(call ndk_log,Application '$(_app)' *is* debuggable) 216 $(call ndk_log,Application '$(_app)' is not debuggable [all...] |
/external/chromium/chrome/browser/cocoa/ |
keystone_glue.h | 28 kAutoupdateCurrent, // version of the running application 66 // have the framework available. Enabling Keystone support in an application 68 // KeystoneRegistration.framework in the application's Frameworks directory 70 // requires that the KSUpdateURL key be set in the application's Info.plist, 131 // Returns YES if the application is running from a read-only filesystem, 135 // -needsPromotion is YES if the application needs its ticket promoted to 136 // a system ticket. This will be YES when the application is on a user 140 // -wantsPromotion is YES if the application wants its ticket promoted to 143 // and it will additionally be YES when the application is on a user ticket 150 // when -needsPromotion is YES, the application can encourage the user t [all...] |
/external/chromium/webkit/glue/ |
site_isolation_metrics.cc | 48 "application/xml", 49 "application/xhtml+xml", 50 "application/rss+xml", 51 "application/atom+xml", 52 "application/json", 53 "application/x-x509-user-cert", 173 mime_type == "application/xml" || 174 mime_type == "application/xhtml+xml" || 175 mime_type == "application/rss+xml" || 176 mime_type == "application/atom+xml" | [all...] |
/external/chromium_org/chrome/browser/mac/ |
keystone_glue.h | 27 kAutoupdateCurrent, // version of the running application 66 // have the framework available. Enabling Keystone support in an application 68 // KeystoneRegistration.framework in the application's Frameworks directory 70 // requires that the KSUpdateURL key be set in the application's Info.plist, 131 // Returns YES if the application is running from a read-only filesystem, 135 // -needsPromotion is YES if the application needs its ticket promoted to 136 // a system ticket. This will be YES when the application is on a user 140 // -wantsPromotion is YES if the application wants its ticket promoted to 143 // and it will additionally be YES when the application is on a user ticket 150 // when -needsPromotion is YES, the application can encourage the user t [all...] |
/frameworks/base/docs/html/sdk/api_diff/18/changes/ |
android.app.Application.html | 10 android.app.Application 74 Class android.app.<A HREF="../../../../reference/android/app/Application.html" target="_top"><font size="+2"><code>Application</code></font></A> 86 <A NAME="android.app.Application.registerOnProvideAssistDataListener_added(android.app.Application.OnProvideAssistDataListener)"></A> 87 <nobr><code>void</code> <A HREF="../../../../reference/android/app/Application.html#registerOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener)" target="_top"><code>registerOnProvideAssistDataListener</code></A>(<code>OnProvideAssistDataListener</code>)</nobr> 93 <A NAME="android.app.Application.unregisterOnProvideAssistDataListener_added(android.app.Application.OnProvideAssistDataListener)"></A> 94 <nobr><code>void</code> <A HREF="../../../../reference/android/app/Application.html#unregisterOnProvideAssistDataListener(android.app.Application.OnProvideAssistDataListener)" t (…) [all...] |
/frameworks/base/docs/html/training/sharing/ |
receive.jd | 33 <p>Just as your application can send data to other applications, so too can it easily receive data 34 from applications. Think about how users interact with your application, and what data types you 35 want to receive from other applications. For example, a social networking application would likely 38 application</a> 45 <p>Intent filters inform the system what intents an application component is willing to accept. 52 element. For example, if your application handles receiving text content, a single image of any 79 <p>When another application tries to share any of these things by constructing an intent and passing 81 application will be listed as an option in the intent chooser. If the user selects your application, 142 know what some other application may send you. For example, the wrong MIME type might be set, or th [all...] |
/frameworks/native/opengl/specs/ |
EGL_ANDROID_blob_cache.txt | 39 application start-up. Additionally, state-based re-compiles done 40 internally by the drivers add an unpredictable element to application 47 program. The management of the cache is handled by the application (or 56 Note that although this extension is written as if the application 60 application that uses EGL if it is supported by the underlying 73 * EGLSetBlobFunc is a pointer to an application-provided function that a 81 * EGLGetBlobFunc is a pointer to an application-provided function that a 106 is slow to compute or collect, the application may specify callback 115 the application. <set> points to a function that inserts a new value into 138 key, a client API implementation can call the application-provided callbac [all...] |
/frameworks/opt/mms/src/java/com/google/android/mms/ |
ContentType.java | 23 public static final String MMS_MESSAGE = "application/vnd.wap.mms-message"; 26 public static final String MMS_GENERIC = "application/vnd.wap.mms-generic"; 27 public static final String MULTIPART_MIXED = "application/vnd.wap.multipart.mixed"; 28 public static final String MULTIPART_RELATED = "application/vnd.wap.multipart.related"; 29 public static final String MULTIPART_ALTERNATIVE = "application/vnd.wap.multipart.alternative"; 63 public static final String AUDIO_OGG = "application/ogg"; 71 public static final String APP_SMIL = "application/smil"; 72 public static final String APP_WAP_XHTML = "application/vnd.wap.xhtml+xml"; 73 public static final String APP_XHTML = "application/xhtml+xml"; 75 public static final String APP_DRM_CONTENT = "application/vnd.oma.drm.content" [all...] |
/hardware/libhardware/include/hardware/ |
bt_rc.h | 131 /** Callback for list player application attributes (Shuffle, Repeat,...) */ 134 /** Callback for list player application attributes (Shuffle, Repeat,...) */ 137 /** Callback for getting the current player application settings value 142 /** Callback for getting the player application settings attributes' text 147 /** Callback for getting the player application settings values' text 152 /** Callback for setting the player application settings values */ 209 /** Lists the support player application attributes (Shuffle/Repeat/...) 214 /** Lists the support player application attributes (Shuffle Off/On/Group) 219 /** Returns the current application attribute values for each of the specified attr_id */ 222 /** Returns the application attributes text ("Shuffle"/"Repeat"/... [all...] |
/external/libnfc-nci/src/nfa/hci/ |
nfa_hci_api.c | 37 ** Description This function will register an application with hci and 38 ** returns an application handle and provides a mechanism to 40 ** When the application is registered (or if an error occurs), 56 NFA_TRACE_API0 ("NFA_HciRegister (): Invalid Application name"); 62 NFA_TRACE_API0 ("NFA_HciRegister (): Application should provide callback function to register!"); 66 NFA_TRACE_API1 ("NFA_HciRegister (): Application Name: %s", p_app_name); 70 /* Register the application with HCI */ 78 /* Save application name and callback */ 96 ** application and list of dynamic pipes created by the 97 ** application. The app will be notified wit [all...] |
/external/chromium/chrome/browser/download/ |
download_util_unittest.cc | 82 "application/octet-stream", 131 "application/rss+xml", 164 "application/x-javascript", 169 "application/json", 184 "application/ecmascript", 189 "application/ecmascript;version=4", 194 "application/foo-bar", 256 "application/octet-stream", 261 "application/foo-bar", 306 "application/foo-bar" [all...] |
/frameworks/base/docs/html/guide/topics/ui/accessibility/ |
checklist.jd | 27 <p>Making an application accessible is about a deep commitment to usability, getting the 29 requirements, recommendations and considerations to help you make sure your application is 30 accessible. Following this checklist does not guarantee your application is accessible, but it's a 33 <p>Creating an accessible application is not just the responsibility of developers. Involve your 43 <p>In most cases, creating an accessible Android application does not require extensive code 45 application, so you can provide them with feedback they can sense and understand. This checklist 51 <p>The following steps must be completed in order to ensure a minimum level of application 73 your application, <a href="{@docRoot}guide/topics/ui/accessibility/apps.html#custom-views"> 82 <li><strong>Test:</strong> Test accessibility by navigating your application 92 <p>The following steps are recommended for ensuring the accessibility of your application. If yo [all...] |
/frameworks/base/docs/html/tools/support-library/ |
setup.jd | 40 application.</p> 80 <p>Before adding a Support Library to your application, decide what features you want to include 88 <p>In order to use a Support Library, you must modify your application's project's 100 application project. </p> 105 <p>To add a Support Library without resources to your application project:</p> 116 <li>Create a {@code libs/} directory in the root of your application project.</li> 119 application's project {@code libs/} directory. 135 <li>Open the {@code build.gradle} file for your application.</li> 154 appcompat</a> for action bar) to your application project:</p> 196 more application projects.</p [all...] |
/frameworks/base/docs/html/tools/testing/ |
testing_accessibility.jd | 41 Testing is an important part of making your application accessible to users with varying 58 <li>Set up and use the application without sighted assistance</li> 59 <li>All task workflows in the application can be easily navigated using directional controls and 66 <p>The following tests must be completed in order to ensure a minimum level of application 70 <li><strong>Directional controls:</strong> Verify that the application can be operated 72 primary tasks in the application. Use the keyboard and directional-pad (D-Pad) controls in the 83 directional controls to move focus between application layout elements.</li> 104 <p>The following tests are recommended for ensuring the accessibility of your application. If you 106 application.</p> 123 accessible app. Some, none or all of the cases described here may apply to your application. B [all...] |
/ndk/docs/text/ |
APPLICATION-MK.text | 0 `Application.mk` file syntax specification 6 This document describes the syntax of `Application.mk` build files 8 application. To understand what follows, it is assumed that you have 19 The purpose of `Application.mk` is to describe which native 21 application. 23 An `Application.mk` file is usually placed under `$PROJECT/jni/Application.mk`, 24 where `$PROJECT` points to your application's project directory. 29 $NDK/apps/<myapp>/`Application.mk` 31 Where <myapp> is a short name used to describe your 'application' [all...] |
/external/bluetooth/bluedroid/stack/avdt/ |
avdt_api.c | 162 ** application in the system. Before this function can be 182 ** created an application can initiate a connection between 220 ** the application is no longer using a stream endpoint. 262 ** is sent to the application via its callback function. 263 ** The application must not call AVDT_GetCapReq() or 268 ** application. This memory is written to by AVDTP as part 270 ** accessible until the application receives the 372 ** sent to the application via its callback function. The 373 ** application must not call AVDT_GetCapReq() or 377 ** application. This memory is written to by AVDTP as par [all...] |
/art/runtime/gc/collector/ |
gc_type.h | 33 // Partial GC that marks the application heap but not the Zygote. 35 // Full GC that marks and frees in both the application and Zygote heap.
|
/cts/hostsidetests/appsecurity/test-apps/AppAccessData/ |
AndroidManifest.xml | 25 <application> 27 </application>
|